What are the factors affecting whether /etc/courier/maildroprc is processed or not?
I have a Courier installation which has some strange behaviors. I have DEFAULTDELIVERY="| /usr/bin/maildrop" in /etc/courier/courierd, which I would assume makes maildrop run in Delivery Mode, however apparently neither ~/.mailfilter nor /etc/courier/maildroprc are processed as a result of this invocation. If I put "|/usr/bin/maildrop" into my ~/.courier file, then ~/.mailfilter gets processed, but once again /etc/courier/maildroprc seems to be ignored. I'm trying to set up SpamAssassin, which needs hooks in /etc/courier/maildroprc, but I can find no way apparently to allow this file to be processed. Any help? Is there an easy way to run debugging tests on an installation of maildrop to see what it is and isn't doing? I'm using the Gentoo build of courier (0.53.2) which includes maildrop, and courier-authlib 0.58, both on a 64bit server. -- Lindsay Haisley | "In an open world, | PGP public key FMP Computer Services | who needs Windows | available at 512-259-1190 | or Gates" | http://pubkeys.fmp.com http://www.fmp.com | | ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
