4 messages in net.sourceforge.lists.courier-users[courier-users] Maildrop problem (not...
FromSent OnAttachments
James HouseJan 26, 2007 9:13 pm 
Sam VarshavchikJan 27, 2007 5:35 am 
James HouseJan 27, 2007 11:11 am 
Sam VarshavchikJan 27, 2007 3:47 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Maildrop problem (not being called?)Actions...
From:James House (jho@revolition.net)
Date:Jan 26, 2007 9:13:00 pm
List:net.sourceforge.lists.courier-users

First off, let me say I've got a courier install that has been humming along for a few years without any updates or tweaks. I'm running version 0.41, on a redhat variant, and I built it back in the day with the following options (in case this helps):

./configure --with-transport="local esmtp dsn" --without-ipv6 --without-authpam --without-ldap --without-authmysql --without-authpgsql --enable-https --with-mailuser=courier --with-mailgroup=courier --enable-softtimeout=7200 --disable-autorenamesent --with-shellpath=/bin:/usr/bin:/usr/local/bin:/usr/local/ssl/bin --enable-workarounds-for-imap-client-bugs

Also, just as information, if I run "maildrop -v" it reports version 1.5.2.

My issue is this: it seems that I can't get maildrop to run as mail is delivered (either that, or at least I can't get it to do anything). I haven't edited the "courierd" config file since it was set up a few years ago, but it has the following setting:

DEFAULTDELIVERY="| /usr/lib/courier/bin/maildrop"

So I've always assumed maildrop was being used. However, I never setup a maildroprc or any .mailfilter files to do anything with it. But mail has always been delivered just fine (I'm using maildirs).

I'm now trying to setup some maildrop rules, and it seems as if maildrop is never invoked! I say this because of the following findings:

* Regardless of what I put in /usr/lib/courier/etc/maildroprc nothing happens, no errors, nothing - the mail is just delivered as before * If I temporarily rename '/usr/lib/courier/bin/maildrop' to something else, so that it shouldn't be able to be found, the mail is still delivered just as before * Similarly I've changed the courierd file to have the entry DEFAULTDELIVERY="| /usr/lib/courier/bin/maildropXXXX" (non existant file name) and the mail is still delievered as before

Questions:

* Any idea why maildrop seems to not be used? (I've double checked for any overriding DEFAULTDELIVERY definitions in any other config files, and there are none) * Is there any way that I can determine definitively whether it's being used or not? (should some logging show up somewhere? (my /var/logs/maillog has no mention of maildrop in it)

thanks for any help, james