For a number of years I've been interfacing Courier to Mailman mailing lists by using Courier support for virtual domains and putting a .courier-listname and .courier-listname-default file in the alias directory for domains which have mailing lists. This pipes to script which is owned by the Mailman distribution called courier-to-mailman.py. (Sam told me years ago that I was crazy for doing it this way, but it works flawlessly and has for years ;-) This script, which is rather similar to the qmail-to-mailman.py script distributed in Mailman's /contrib directory, provides a list-independent method of doing this job concisely and reliably.
Mark Sapiro on the Mailman development team tells me that courier-to-mailman.py will be included in future distributions of Mailman. I've been gently pushing this script from time to time to the Mailman development group for 5 years or so, but what with the other issues they have to deal with it's slipped through the cracks, but it looks as if Courier will soon have some very explicit support in Mailman, which is arguably the most popular F/OSS list server out there. -- Lindsay Haisley | "Everything works | Accredited FMP Computer Services | if you let it" | by the 512-259-1190 | (The Roadie) | Austin Better http://www.fmp.com | | Business Bureau ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
