RE: [vchkpw] POP3 authentication - erratic vmysql auth problem - self solved

[shadowplay.net]

 

 On a new linux mailserver I was having an erratic problem 
 with mysql and 
 pop3 authentication.  Authentication works 90+% of the time. 
 However, using The Bat! and Outlook clients, I randomly see the 
 following authentication failure and the user must poll pop3 again - 
 which then succeeds.
 
 SOLUTION:
 In spite of what the qmailctl stat told me, I found that 
 increasing the 
 pop3 'run' file memory limit from 800 to 1200 appears to 
 suppress this issue.
 
 Any thoughts on why would be welcome.  Otherwise, one for 
 the archives... Thanks! Dave.
 

aside from 'the bat!' being a spamware client filtered by most 
mail daemons and spam solutions... on inbound mailservers... 
your clients are probably sending/reciving 
bigger spam attachments than normal
to longer lists...

u might also want to look at the number of cc's and bcc's those clients 
are sending... and if its inbound pop have you looked at the size of the 
pop mailboxes that they are attempting to check?

a good hit with 3 or 4 heavy emails will blow 8m pretty easy... 
remmember the mem limit is the size of the pop binaries \PLUS 
the mailbox size

kenneth gf brown 
ceo shadowplay.net

Re: [vchkpw] POP3 authentication - erratic vmysql auth problem - self solved

[Rick Macdougall]

Dave Richardson wrote:
On a new linux mailserver I was having an erratic problem with mysql and 
pop3 authentication.  Authentication works 90+% of the time.
However, using The Bat! and Outlook clients, I randomly see the 
following authentication failure and the user must poll pop3 again - 
which then succeeds.


-- this text from TheBat --
FETCH - Server reports error.  The response is: vmysql: can't read 
settings from /home/vpopmail/etc/vpopmail.mysql -ERR aack, child crashed


Here's /home/vpopmail/etc/vpopmail.mysql
-rw-r-  1 vpopmail vchkpw   45 Oct  1 08:25 vpopmail.mysql

I didn't think the pop3 daemon is crashing (i.e. bad mem limits in 'run' 
file).

qmailctl stat:
/service/qmail-send: up (pid 2568) 3791 seconds
/service/qmail-send/log: up (pid 2570) 3791 seconds
/service/qmail-smtpd: up (pid 2574) 3791 seconds
/service/qmail-smtpd/log: up (pid 2569) 3791 seconds
/service/qmail-pop3d: up (pid 2571) 3791 seconds
/service/qmail-pop3d/log: up (pid 2576) 3791 seconds
messages in queue: 0
messages in queue but not yet preprocessed: 0

SOLUTION:
In spite of what the qmailctl stat told me, I found that increasing the 
pop3 'run' file memory limit from 800 to 1200 appears to 
suppress this issue.


Any thoughts on why would be welcome.  Otherwise, one for the archives...


Hi,

The actual service didn't crash, tcpserver is always running. 
qmail-popup or the actual qmail-pop3d crashed with a lack of memory.


tcpserver and qmail-pop3d are two different things.

Regards,

Rick