[vchkpw] vdelivermail delete for the win
After my recent issues with maildrop and delivering mail, I got to know my system a little better. Having scanned through the qmail-queue I noticed a lot of messages just sitting around for days on end trying to deliver to non-existent email boxes, in response to spammers. Some of my bigger customers had all email set to 'bounce' and not 'delete'. Several hundred e-mail accounts getting several thousand spams a day ended up creating a constant flow of between 10,000 and 20,000 mail messages bouncing in the qmail-queue on a daily basis. I was getting pretty worried about the hard disks that contain my mail queue and the /var/vpopmail/domains tree. They were dishing out between 250 - 400 (I've seen it as high as 800) transactions per second on average. After setting vdelivermail delete on some of my bigger domains, my queue has dropped to under 1000 messages, and iostat shows a SIGNIFICANT decrease in disk activity during both peak and off-peak times. I wish someone had told me about that earlier. What a great tool for reducing unnecessary load. !DSPAM:477e0c4c310541912799895!
RE: [vchkpw] vdelivermail delete for the win
Hmm I may have to check that out :) Working with Gentoo ebuilds and what-not, so I don't get all the cl packages. I know you all have a p0f-qmail install too. Almost had you guys do it... I put it aside for the holidays though. -Original Message- From: Matt Brookings [mailto:[EMAIL PROTECTED] Sent: Friday, January 04, 2008 5:31 AM To: vchkpw@inter7.com Subject: Re: [vchkpw] vdelivermail delete for the win -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Goodman wrote: I wish someone had told me about that earlier. What a great tool for reducing unnecessary load. An ever better tool is the chkuser patch and vdelivermail set to bounce so the message never even reaches qmail-queue. - -- /* Matt Brookings [EMAIL PROTECTED] GnuPG Key ABA26FE7 Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFHflE4Yaj0Mauib+cRArpOAKCg61nk0EwTLdZdOQev+uQJ+G7dLQCeK0/o urTGbkw0uXyh5PJ3A7ljbKo= =9imd -END PGP SIGNATURE- !DSPAM:477e726f310541851520309!
RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
I have created a script for now that will go through and create any users that do not currently have a .qmail file and manually set one up. What would be a suitable .qmail file? Something like this? ---.qmail file for users without any maildrop rules to run--- |/var/vpopmail/bin/vdelivermail /var/vpopmail/domains/%d/%u/Maildir I’m still not sure why this would break just because of an upgrade. Has to be a vpopmail thing. Compile options are: ./configure \ --sysconfdir=/var/vpopmail/etc \ --enable-non-root-build \ --enable-qmaildir=/var/qmail \ --enable-qmail-newu=/var/qmail/bin/qmail-newu \ --enable-qmail-inject=/var/qmail/bin/qmail-inject \ --enable-qmail-newmrh=/var/qmail/bin/qmail-newmrh \ --enable-vpopuser=vpopmail \ --enable-vpopgroup=vpopmail \ --disable-many-domains \ --enable-file-locking \ --enable-file-sync \ --enable-md5-passwords \ --enable-logging=y \ --enable-auth-logging \ --enable-log-name=vpopmail \ --enable-qmail-ext \ --disable-tcp-rules-prog \ --disable-tcpserver-file \ --disable-roaming-users \ --enable-maildrop \ --enable-auth-module=mysql \ --enable-libs=/usr/include/mysql \ --enable-libdir=/usr/lib/mysql \ --enable-valias \ --disable-mysql-replication \ --enable-mysql-limits From: Matthew Goodman [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 01, 2008 9:15 AM To: vchkpw@inter7.com Subject: RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues As a workaround, I’ve added: |/var/qmail/bin/preline /usr/bin/maildrop /etc/mailfilter Into everyone’s .qmail-default This delivers mail as if they checked the back “Spam Detection”. From: Tren Blackburn [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 01, 2008 4:25 AM To: vchkpw@inter7.com Subject: Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues I've never run into that behaviour before. A .qmail in a users directory is not required. I would recommend reverting back to your old version and do some testing on a development box, virtual machine, or whatever you can test this on. Perhaps also post more details about your environment, like operating system, qmail version, configuration options, if you're building from source or using a binary distribution (ie. rpm). Hope that helps :) Happy New Year Tren - Original Message - From: Matthew Goodman [EMAIL PROTECTED] To: vchkpw@inter7.com vchkpw@inter7.com Sent: Tue Jan 01 06:14:11 2008 Subject: RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues I should also add that I’ve got about 15,000 messages backed up. Yes, I know 14,982 are SPAM, but there are probably 18 useful ones in there somewhere J Anyways, headed to bed, I’m starting to drift. Any thoughts would be useful. From: Matthew Goodman [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 01, 2008 4:03 AM To: vchkpw@inter7.com Subject: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues Most of my domains in /var/vpopmail/domains/ have a .qmail-default file that looks like this: | /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox After upgrading from vpopmail 5.4.19 to 5.4.26, any user that was created using QmailAdmin 1.2.10 that did NOT have the Spam Detection box checked is not receiving their mail. This is because of absence of the .qmail file for the user’s folder. I was under the impression that each user not having a .qmail file is not bad in itself, as long as a .qmail-default file existed in the parent folder for that domain. Before this upgrade, this was not a problem seeing that a .qmail-default file was in place at the root of each domain’s directory under /var/vpopmail/domains. However, after the upgrade, these users (that don’t have a .qmail file) are having all their messages dropped to their Maildir/tmp folder. I have no idea what is causing this. Replacing the .qmail-default with something that resembles other user’s .qmail file fixes the problem, however, this is not the preferred approach due to some configs being set for catchall-delete or bounce or what-have-you. Totally stuck on New Year’s. Hope yours is better than mine… any ideas here? Matt !DSPAM:477b598f310548813521591!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
To my understanding, --enable-valias just stores alias info into the mysql database. This should not be affecting the delivery of email to non-aliased email, should it? Matt You compiled vpopmail to store its .qmail files in mysql by selecting --enable-valias. Run ./configuration --help to get a summary of the options and what they do. How did you decide which options to use? Regards, Tren - Original Message - From: Matthew Goodman [EMAIL PROTECTED] To: vchkpw@inter7.com vchkpw@inter7.com Sent: Wed Jan 02 01:29:36 2008 Subject: RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues I have created a script for now that will go through and create any users that do not currently have a .qmail file and manually set one up. What would be a suitable .qmail file? Something like this? ---.qmail file for users without any maildrop rules to run--- |/var/vpopmail/bin/vdelivermail /var/vpopmail/domains/%d/%u/Maildir Iâm still not sure why this would break just because of an upgrade. Has to be a vpopmail thing. Compile options are: ./configure \ --sysconfdir=/var/vpopmail/etc \ --enable-non-root-build \ --enable-qmaildir=/var/qmail \ --enable-qmail-newu=/var/qmail/bin/qmail-newu \ --enable-qmail-inject=/var/qmail/bin/qmail-inject \ --enable-qmail-newmrh=/var/qmail/bin/qmail-newmrh \ --enable-vpopuser=vpopmail \ --enable-vpopgroup=vpopmail \ --disable-many-domains \ --enable-file-locking \ --enable-file-sync \ --enable-md5-passwords \ --enable-logging=y \ --enable-auth-logging \ --enable-log-name=vpopmail \ --enable-qmail-ext \ --disable-tcp-rules-prog \ --disable-tcpserver-file \ --disable-roaming-users \ --enable-maildrop \ --enable-auth-module=mysql \ --enable-libs=/usr/include/mysql \ --enable-libdir=/usr/lib/mysql \ --enable-valias \ --disable-mysql-replication \ --enable-mysql-limits From: Matthew Goodman [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 01, 2008 9:15 AM To: vchkpw@inter7.com Subject: RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues As a workaround, Iâve added: |/var/qmail/bin/preline /usr/bin/maildrop /etc/mailfilter Into everyoneâs .qmail-default This delivers mail as if they checked the back âSpam Detectionâ. From: Tren Blackburn [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 01, 2008 4:25 AM To: vchkpw@inter7.com Subject: Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues I've never run into that behaviour before. A .qmail in a users directory is not required. I would recommend reverting back to your old version and do some testing on a development box, virtual machine, or whatever you can test this on. Perhaps also post more details about your environment, like operating system, qmail version, configuration options, if you're building from source or using a binary distribution (ie. rpm). Hope that helps :) Happy New Year Tren - Original Message - From: Matthew Goodman [EMAIL PROTECTED] To: vchkpw@inter7.com vchkpw@inter7.com Sent: Tue Jan 01 06:14:11 2008 Subject: RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues I should also add that Iâve got about 15,000 messages backed up. Yes, I know 14,982 are SPAM, but there are probably 18 useful ones in there somewhere J Anyways, headed to bed, Iâm starting to drift. Any thoughts would be useful. From: Matthew Goodman [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 01, 2008 4:03 AM To: vchkpw@inter7.com Subject: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues Most of my domains in /var/vpopmail/domains/ have a .qmail-default file that looks like this: | /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox After upgrading from vpopmail 5.4.19 to 5.4.26, any user that was created using QmailAdmin 1.2.10 that did NOT have the Spam Detection box checked is not receiving their mail. This is because of absence of the .qmail file for the userâs folder. I was under the impression that each user not having a .qmail file is not bad in itself, as long as a .qmail-default file existed in the parent folder for that domain. Before this upgrade, this was not a problem seeing that a .qmail-default file was in place at the root of each domainâs directory under /var/vpopmail/domains. However, after the upgrade, these users (that donât have a .qmail file) are having all their messages dropped to their Maildir/tmp folder
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
Ok, I took your advice and instead switched each users .qmail file (that did not have one setup) to utilize the maildrop command that Qmailadmin enables once Spam Detection is checked. This seems to work. It's |/var/qmail/bin/preline /usr/bin/maildrop /etc/mailfilter My customers use Qmailadmin to administer their email boxes. For some reason, when they create an account using Qmailadmin, unless they Enable Spam Detection a .qmail file is NOT created. Is this normal behavior from what you know of it? I suppose this might be the wrong list, but again, Qmailadmin's behavior does not explain why after the upgrade Vpopmail has a problem delivering mail. I see about 11,000 messages in the qmail queue at the moment. None of them are being delivered. Users have messages backed up in their /Maildir/tmp folder from several days ago. qmailctl flush does not force the delivery of all these items. The actual setup looks like this: netqmail-1.05, qmail-scanner-2.01-st, vpopmail 5.4.26 - all compiled from Gentoo ebuilds. The vpopmail ebuild I sort of made by hand, so as much as possible I investigate the ebuilds carefully for strange/rogue settings and such. As I stated before, things were working fine with vpopmail 5.4.17 since July without a hitch. I just have to confess that my guru-ness with vpopmail is limited, so this problem is a bit more elusive than my own abilities can track. At any rate, any thoughts would be helpful. On Jan 2, 2008, at 1:29 AM, Matthew Goodman wrote: ---.qmail file for users without any maildrop rules to run--- |/var/vpopmail/bin/vdelivermail /var/vpopmail/domains/%d/%u/Maildir No! You don't want to do this. Reminder to everyone in the world -- vdelivermail should only be in your .qmail-default file. Never anywhere else. I'm not sure I understand why your installation of 5.4.26 isn't working -- if there isn't a .qmail file, the message should just go into the user's maildir. If you absolutely MUST have a .qmail file, it will just contain a single line -- the path to that user's Maildir. Keep in mind that with directory hashing, their maildir might not be in domains/%d/%u/Maildir. You could try using just ./Maildir and see if that works -- I think vdelivermail is already in the user's directory when it's parsing the .qmail file. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:477be26d310542003195226!
Re: [vchkpw] Re: Upgrade to Vpopmail 5.4.26 and .qmail-default issues
I do agree, that the ebuilds are not always very useful. I had edited the build to eliminate the changes from Maildir to .maildir. It is accomplished through a simple sed command across the vpopmail source before compiling. I interrupted this process by commenting it out and the build itself should be operating as normal from source, which would be Maildir. You do raise a good point, I wish Gentoo would get that part of it right. Deviating from the standards are not a good idea. Matt Hi, Be carefull with the Gentoo ebuilds : they are modyfied by the Gentoo team to use .maildir (dot maildir) in place of Maildir, it can be the source of your problems if you've mixed official Gentoo ebuilds (expecting .maildir) with others made by hand (using Maildir). ,- - [ Le mercredi 2 janvier 2008 vers 20:13 Matthew Goodman écrivait: ] - - | netqmail-1.05, qmail-scanner-2.01-st, vpopmail 5.4.26 - all compiled from Gentoo ebuilds. The vpopmail ebuild I sort of made by hand, so as much as possible I investigate the ebuilds carefully for strange/rogue settings and such. | `- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- Bien à vous... _ (_' L'informatique est ma passion, vous la simplifier, mon métier ! ,_)téphane Bouvard [antarex AT freenet DOT be] http://www.antarex.be !DSPAM:477bef8f310541386043568!
Re: [vchkpw] Re: Upgrade to Vpopmail 5.4.26 and .qmail-default issues
I tend to agree with you on all points, however, once a production level system is up and running (quite smoothly for years up until recently here) I try not to upset the chi. Now if I were to do it all over, I'd probably do it very differently. It's always a learning process. Back onto point though, any thoughts as to where I could look for why email is so backed up? And why all of a sudden .qmail-default was not good enough to deliver mail with? Matt You do raise a good point, I wish Gentoo would get that part of it right. Deviating from the standards are not a good idea. I love Gentoo, but every now and then the do something boneheaded that makes me think that I should bail on it for KUbuntu or something like that. The only thing that's kept me on it lately is that while I'm no longer on the bleeding edge (I use a thinkpad R50p - at the time I got it, Gentoo was the only flavor I could tweak things with properly and still use official packages rather than rolling my own and having to remember to upgrade it manually), I still do occasionally tweak things (and rebuilding my primary workstation is a pain :)). Most notably they seem to have had some people with strange ideas of how to maintain qmail/vpopmail etc., but since it was their sandbox they got to make it so... Personally, no matter how good the maintainer, I prefer doing source for qmail/vpopmail et. al. - that way I _know_ what it's gonna do (or at least what I'm expecting it to do :)). Josh Joshua Megerman SJGames MIB #5273 - OGRE AI Testing Division You can't win; You can't break even; You can't even quit the game. - Layman's translation of the Laws of Thermodynamics [EMAIL PROTECTED] !DSPAM:477bfc00310541321314441!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
Here's an odd one: @4000477c1866206baccc delivery 30202: deferral: /usr/bin/maildrop:_Unable_to_create_a_dot-lock_at_/var/vpopmail/./.maildir/25184.0.ark.// I see a few of these... aside from the usual Unable to create log file error that maildrop kicks out for aliases or emails that don't belong to actual accounts. Any ideas? On Jan 2, 2008, at 11:13 AM, Matthew Goodman wrote: My customers use Qmailadmin to administer their email boxes. For some reason, when they create an account using Qmailadmin, unless they Enable Spam Detection a .qmail file is NOT created. Is this normal behavior from what you know of it? I suppose this might be the wrong list, but again, Qmailadmin's behavior does not explain why after the upgrade Vpopmail has a problem delivering mail. This is normal behavior -- if email should just be placed in the user's Maildir, no .qmail file is necessary. It sounds like your vdelivermail is having problems. Have you checked the qmail-send logs? It should be showing you why there's a temp failure. I am personally using 5.4.20 on my system, and according to the CVS logs, vdelivermail in 5.4.26 is the same as in 5.4.20. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:477c18c2310546724113822!
RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
Well I'm glad you asked that question, after rebuilding maildrop, I noticed it *overwrote* my /etc/maildroprc file. Normally, it is a symlink to /etc/mailfilter. So when it overwrote the maildroprc symlink I had created, it brought with it the .maildir reference. Thank you for asking the question :) It spurred some more investigation to get the problem fixed. So far in the time it took to write this, over 500 messages were cleared from the queue :) Looks like it may be finally good to go. Matt -Original Message- From: Tom Collins [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 02, 2008 2:40 PM To: vchkpw@inter7.com Subject: Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues On Jan 2, 2008, at 3:05 PM, Matthew Goodman wrote: @4000477c1866206baccc delivery 30202: deferral: /usr/bin/maildrop:_Unable_to_create_a_dot-lock_at_/var/ vpopmail/./.maildir/25184.0.ark.// I see a few of these... aside from the usual Unable to create log file error that maildrop kicks out for aliases or emails that don't belong to actual accounts. Any ideas? Why does maildrop want to use .maildir instead of Maildir? Odd that it wants to use the vpopmail directory instead of a user's directory as well... -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:477c78e9310545571378502!
[vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
Most of my domains in /var/vpopmail/domains/ have a .qmail-default file that looks like this: | /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox After upgrading from vpopmail 5.4.19 to 5.4.26, any user that was created using QmailAdmin 1.2.10 that did NOT have the Spam Detection box checked is not receiving their mail. This is because of absence of the .qmail file for the user's folder. I was under the impression that each user not having a .qmail file is not bad in itself, as long as a .qmail-default file existed in the parent folder for that domain. Before this upgrade, this was not a problem seeing that a .qmail-default file was in place at the root of each domain's directory under /var/vpopmail/domains. However, after the upgrade, these users (that don't have a .qmail file) are having all their messages dropped to their Maildir/tmp folder. I have no idea what is causing this. Replacing the .qmail-default with something that resembles other user's .qmail file fixes the problem, however, this is not the preferred approach due to some configs being set for catchall-delete or bounce or what-have-you. Totally stuck on New Year's. Hope yours is better than mine. any ideas here? Matt !DSPAM:477a4822310541354829831!
[vchkpw] authdaemond Memory Leak?
Hello, I've noticed that courier-authlib slowly uses up memory over time on my Gentoo linux server. Using 2.6.21-gentoo-r4 kernel, compiler GCC 4.1.2, glibc 2.5-r4. Using the authvchkpw library, authdaemond usage looks like this after about a week: top - 00:42:49 up 22 days, 20:31, 2 users, load average: 2.08, 2.52, 2.54 Tasks: 271 total, 2 running, 269 sleeping, 0 stopped, 0 zombie Mem: 2074712k total, 1966420k used, 108292k free, 134520k buffers Swap: 1951800k total, 1113692k used, 838108k free, 547588k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 7885 root 15 0 217m 68m 932 S0 3.4 0:40.84 /usr/lib/courier/courier-authlib/authdaemond 7884 root 15 0 216m 66m 928 S0 3.3 0:39.71 /usr/lib/courier/courier-authlib/authdaemond 7883 root 15 0 208m 66m 928 S0 3.3 0:38.41 /usr/lib/courier/courier-authlib/authdaemond 7886 root 15 0 217m 65m 928 S0 3.2 0:40.57 /usr/lib/courier/courier-authlib/authdaemond 7882 root 15 0 212m 65m 932 S0 3.2 0:38.97 /usr/lib/courier/courier-authlib/authdaemond Once I restart the service, usage looks much better: root 14565 0.0 0.0 4644 1132 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14569 0.0 0.0 4688 1340 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14570 0.0 0.0 4644 424 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14571 0.0 0.0 4688 1340 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14572 0.0 0.0 4812 1436 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14573 0.0 0.0 4812 1476 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond From /etc/courier/authlib/authdaemonrc: --- authmodulelist=authvchkpw daemons=5 DEFAULTOPTIONS= LOGGEROPTS= There is another post on the courier-users mailing list about this, user is also using a Gentoo environment and he was told to post on the vchkpw mailing list. Link included for reference: http://readlist.com/lists/lists.sourceforge.net/courier-users/0/3901.html Any input would be greatly appreciated. Matt !DSPAM:474fec5f32002133118457!
RE: [vchkpw] authdaemond Memory Leak?
Thanks, I am using Vpopmail 5.4.18. Was the fix after that release? Matt From: tonix (Antonio Nati) [mailto:[EMAIL PROTECTED] Sent: Friday, November 30, 2007 1:03 AM To: vchkpw@inter7.com Subject: Re: [vchkpw] authdaemond Memory Leak? There was a memory problem in an old version of vpopmail library. It was related to usage of vlimits in MySQL. Check within mailing list for such information. You have to ugrade/fix, then recompile vpomail and courier-authdaemon. Ciao, Tonino Matthew Goodman ha scritto: Hello, I've noticed that courier-authlib slowly uses up memory over time on my Gentoo linux server. Using 2.6.21-gentoo-r4 kernel, compiler GCC 4.1.2, glibc 2.5-r4. Using the authvchkpw library, authdaemond usage looks like this after about a week: top - 00:42:49 up 22 days, 20:31, 2 users, load average: 2.08, 2.52, 2.54 Tasks: 271 total, 2 running, 269 sleeping, 0 stopped, 0 zombie Mem: 2074712k total, 1966420k used, 108292k free, 134520k buffers Swap: 1951800k total, 1113692k used, 838108k free, 547588k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 7885 root 15 0 217m 68m 932 S0 3.4 0:40.84 /usr/lib/courier/courier-authlib/authdaemond 7884 root 15 0 216m 66m 928 S0 3.3 0:39.71 /usr/lib/courier/courier-authlib/authdaemond 7883 root 15 0 208m 66m 928 S0 3.3 0:38.41 /usr/lib/courier/courier-authlib/authdaemond 7886 root 15 0 217m 65m 928 S0 3.2 0:40.57 /usr/lib/courier/courier-authlib/authdaemond 7882 root 15 0 212m 65m 932 S0 3.2 0:38.97 /usr/lib/courier/courier-authlib/authdaemond Once I restart the service, usage looks much better: root 14565 0.0 0.0 4644 1132 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14569 0.0 0.0 4688 1340 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14570 0.0 0.0 4644 424 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14571 0.0 0.0 4688 1340 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14572 0.0 0.0 4812 1436 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond root 14573 0.0 0.0 4812 1476 ?S00:43 0:00 /usr/lib/courier/courier-authlib/authdaemond From /etc/courier/authlib/authdaemonrc: --- authmodulelist=authvchkpw daemons=5 DEFAULTOPTIONS= LOGGEROPTS= There is another post on the courier-users mailing list about this, user is also using a Gentoo environment and he was told to post on the vchkpw mailing list. Link included for reference: http://readlist.com/lists/lists.sourceforge.net/courier-users/0/3901.html Any input would be greatly appreciated. Matt -- [EMAIL PROTECTED]Interazioni di Antonio Nati http://www.interazioni.it [EMAIL PROTECTED] !DSPAM:474ff30032002235560276!
