[vchkpw] "not existing recipient" under high load

2007-05-01 Thread Alastair Battrick
Hello I'm a subscriber to a few Yaho groups, and recently have been unsubscribed by them, automatically. When I view my Yahoo bounce history I can see: "Last Bounced Message: Remote host said: 511 sorry, no mailbox here by that name (#5.1.1 - chkuser) [RCPT_TO]" Now I know that the mailbox i

RE: [vchkpw] "not existing recipient" under high load

2007-05-01 Thread Charles J. Boening
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've seen this as well. Are you using an SQL backend? Charlie > -Original Message- > From: Alastair Battrick [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 01, 2007 12:33 AM > To: vchkpw@inter7.com > Subject: [vchkpw] "not existing recipie

Re: [vchkpw] "not existing recipient" under high load

2007-05-01 Thread Alastair Battrick
Charles J. Boening wrote: I've seen this as well. Are you using an SQL backend? Yes, vpopmail stores user data in MySQL -- Alastair Battrick http://www.aj8.org

RE: [vchkpw] "not existing recipient" under high load

2007-05-01 Thread Charles J. Boening
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My guess would be some sort of SQL timeout or connection limit. Charlie > -Original Message- > From: Alastair Battrick [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 01, 2007 1:01 PM > To: vchkpw@inter7.com > Subject: Re: [vchkpw] "not exi

Re: [vchkpw] "not existing recipient" under high load

2007-05-01 Thread DAve
Alastair Battrick wrote: Charles J. Boening wrote: I've seen this as well. Are you using an SQL backend? Yes, vpopmail stores user data in MySQL Query caching is your friend here, there are also lots of archive messages concerning setup in MySQL to avoid issues with authentication, chkuse

[vchkpw] Vpopmail CVS changes

2007-05-01 Thread Rick Widmer
I hope to roll out a new dev version of vpopmail (5.4.18) this weekend. There will be a number of fixes to things that have been found in 5.4.17, and new maildrop and spamassassin support by Bill Shupp. As soon as that happens I am going to move the current 5.5 / HEAD code to a dead-end branc