New update 6.5.0.f-2013031821

[MRatWork]

Change since .21.

To write that in 6.5.0.f-2013031821. Because incomprehensible what is .21. :lol:
I'll update again to 21 and check it out.

Already update to .22 because move certain code to rpm (for qmail-toaster)

[Viking]

Change since .21.

To write that in 6.5.0.f-2013031821. Because incomprehensible what is .21. :lol:
I'll update again to 21 and check it out.

Already update to .22 because move certain code to rpm (for qmail-toaster)

There is no update 22 There is only update 21:

Code: [Select]

Available Packages
kloxomr.noarch      6.5.0.f-2013031821.mr       kloxo-mr-release-neutral-noarch

[MRatWork]

Run 'yum clean up' first

[Viking]

Run files already change since .21/.22 and then become:

pop3:

Code: [Select]

#!/bin/sh

PASSPROG="/home/vpopmail/bin/vchkpw"
HOSTNAME=`hostname --fqdn`

if [ `uname -m` = 'x86_64' ] ; then
SOFTLIMITVAR="48000000"
else
SOFTLIMITVAR="9000000"
fi

IP=0
PORT=110

exec /usr/bin/softlimit -m $SOFTLIMITVAR
/usr/bin/tcpserver -v -R -c 200 $IP $PORT
/var/qmail/bin/qmail-popup $HOSTNAME
$PASSPROG /var/qmail/bin/qmail-pop3d Maildir 2>&1

pop3-ssl:

Code: [Select]

#!/bin/sh

HOSTNAME=`hostname --fqdn`

rm -rf "./env/*";
cat /etc/courier/pop3d-ssl | /usr/bin/envconv

if [ `uname -m` = 'x86_64' ] ; then
SOFTLIMITVAR="48000000"
else
SOFTLIMITVAR="9000000"
fi

IP=0
PORT=995

exec /usr/bin/envdir ./env/
/usr/bin/softlimit -m $SOFTLIMITVAR
/usr/bin/tcpserver -v -R -H -l $HOSTNAME $IP $PORT
/usr/bin/couriertls -server -tcpd
/usr/sbin/pop3login
/usr/bin/pop3d Maildir 2>&1


I have to change it in 22 or have unnecessary?

[MRatWork]

In .22 only bugfix for clearcache.

[MRatWork]

Inform here 'yum list|grep krb'

[Viking]

Inform here 'yum list|grep krb'

Code: [Select]

yum list|grep krb
krb5-devel.x86_64                      1.10.3-10.el6_4.3           @updates    
krb5-libs.x86_64                       1.10.3-10.el6_4.3           @updates    
dcap-tunnel-krb.x86_64                 2.47.7-1.el6                kloxo-mr-epel
freeradius-krb5.x86_64                 2.1.12-4.el6_3              base        
krb5-appl-clients.x86_64               1.0.1-7.el6_2.1             base        
krb5-appl-servers.x86_64               1.0.1-7.el6_2.1             base        
krb5-auth-dialog.x86_64                0.13-3.el6                  base        
krb5-devel.i686                        1.10.3-10.el6_4.3           updates      
krb5-libs.i686                         1.10.3-10.el6_4.3           updates      
krb5-pkinit-openssl.x86_64             1.10.3-10.el6_4.3           updates      
krb5-server.x86_64                     1.10.3-10.el6_4.3           updates      
krb5-server-ldap.i686                  1.10.3-10.el6_4.3           updates      
krb5-server-ldap.x86_64                1.10.3-10.el6_4.3           updates      
krb5-workstation.x86_64                1.10.3-10.el6_4.3           updates      
pam_krb5.i686                          2.3.11-9.el6                base        
pam_krb5.x86_64                        2.3.11-9.el6                base        
python-krbV.x86_64                     1.0.90-3.el6                base        
root-net-krb5.x86_64                   5.28.00h-3.el6              kloxo-mr-epel
samba-winbind-krb5-locator.x86_64      3.6.9-151.el6               base        
samba4-winbind-krb5-locator.x86_64     4.0.0-55.el6.rc4            base

[Viking]

Run files already change since .21/.22 and then become:

pop3:

Code: [Select]

#!/bin/sh

PASSPROG="/home/vpopmail/bin/vchkpw"
HOSTNAME=`hostname --fqdn`

if [ `uname -m` = 'x86_64' ] ; then
SOFTLIMITVAR="48000000"
else
SOFTLIMITVAR="9000000"
fi

IP=0
PORT=110

exec /usr/bin/softlimit -m $SOFTLIMITVAR
/usr/bin/tcpserver -v -R -c 200 $IP $PORT
/var/qmail/bin/qmail-popup $HOSTNAME
$PASSPROG /var/qmail/bin/qmail-pop3d Maildir 2>&1

pop3-ssl:

Code: [Select]

#!/bin/sh

HOSTNAME=`hostname --fqdn`

rm -rf "./env/*";
cat /etc/courier/pop3d-ssl | /usr/bin/envconv

if [ `uname -m` = 'x86_64' ] ; then
SOFTLIMITVAR="48000000"
else
SOFTLIMITVAR="9000000"
fi

IP=0
PORT=995

exec /usr/bin/envdir ./env/
/usr/bin/softlimit -m $SOFTLIMITVAR
/usr/bin/tcpserver -v -R -H -l $HOSTNAME $IP $PORT
/usr/bin/couriertls -server -tcpd
/usr/sbin/pop3login
/usr/bin/pop3d Maildir 2>&1


Mustafa is still the same error:

Code: [Select]

* Account 'Administracja': Connecting to POP3 server: mail.yyyyyy.pl...
[22:32:26] POP3< +OK <1106.1371328346@aaaaa.bbbb.pl>
[22:32:26] POP3> USER yyy@yyyyyy.pl
[22:32:26] POP3< +OK
[22:32:26] POP3> PASS ********
[22:32:26] POP3< /home/vpopmail/bin/vchkpw: error while loading shared libraries: libkrb5support.so.0: failed to map segment from shared object: Cannot allocate memory
*** B??d podczas przetwarzania wiadomo?ci.

[MRatWork]

Try:

Code: [Select]

chown root:root /home/vpopmail/bin/vchkpw
chmod 4755 /home/vpopmail/bin/vchkpw


[Viking]

Try:

Code: [Select]

chown root:root /home/vpopmail/bin/vchkpw
chmod 4755 /home/vpopmail/bin/vchkpw


Mustafa is still the same error.

[MRatWork]

Truly, no different between previous qmail-toaster with latest one except different run script.

Sadly, I didn't test fpr pop3 but imap. After update, I didn't found any issues related to mail.

I am not sure reboot will be fix your issue.

[Viking]

Truly, no different between previous qmail-toaster with latest one except different run script.

Sadly, I didn't test fpr pop3 but imap. After update, I didn't found any issues related to mail.

I am not sure reboot will be fix your issue.

Mustafa did reboot and it does not help or sh/script/fixmail-all.

[MRatWork]

I am not reboot my servers after update. But, qmail have weird behaviour for start/stop/restart after change their run script.

[Viking]

I am not reboot my servers after update. But, qmail have weird behaviour for start/stop/restart after change their run script.

Mustafa does not help. Somewhere you made a mistake in the updates. The .20 was OK.
I'm going back to 20 and block the updates Kloxo-MR because the server will again four days offline as recently as one day online.

[Viking]

I just better not do updates because every update is full of bugs and the server is still offline.
Stable versions should be free of errors.