The strange thing I've noticed, upon following the README.courier and the courierfilter manpage, is that ".../sbin/courierfilter start" never seems to complete. I'm assuming this is because amavisd doesn't daemonize and terminate... but is this expected? If so, I'm wondering whether I need to wrap it in a helper script in order to allow for the usual "start/stop" behavior of the courier scripts.
Sounds like amavisd isn't closing file handle 3, which courier expects (strange way of signaling to courier that your filter is finished initing).
If anything, startup behavior -- despite what I've read about Unix sockets needing to be purged each time manually -- seems to be quite normal. So I just need to figure out why amavisd seems not to play nicely with courierfilter and I think I'll have this running quite smoothly. :-)
No wrapper needed -- just make sure you have amavisd configured such that it knows it's playing with Courier (search for '$unix_socket_protocol' in amavisd.conf and make sure it's set to 'courier'). Amavisd knows to look for and close the appropriate file handle.
best, Jeff
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
