

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
8 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier-mta and m...| From | Sent On | Attachments |
|---|---|---|
| Edwin Culp Williams | Aug 29, 2006 5:31 pm | |
| Jay Lee | Aug 29, 2006 6:14 pm | |
| Bernd Wurst | Aug 29, 2006 11:44 pm | |
| ecu...@conejoblanco.info | Aug 30, 2006 4:13 am | |
| Edwin Culp Williams | Aug 30, 2006 4:18 am | |
| Bill Schindler | Aug 30, 2006 9:42 am | |
| Edwin Culp Williams | Aug 31, 2006 7:30 am | |
| Martin Schuster | Sep 4, 2006 12:25 am |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [courier-users] Courier-mta and mailman | Actions... |
|---|---|---|
| From: | ecu...@conejoblanco.info (ecu...@conejoblanco.info) | |
| Date: | Aug 30, 2006 4:13:03 am | |
| List: | net.sourceforge.lists.courier-users | |
Quoting Jay Lee <jl...@pbu.edu>:
On Tue, August 29, 2006 8:31 pm, Edwin Culp Williams wrote:
I've been using couriermlm happily for several years but now need something with a webbased frontend. Mailman seems to be the choice of the day but looking at the configuration, courier-mta was not taken into consideration. I would sure like to find a howto for courier/mailman but have only found postfix and exim. Does anyone know of one or could share their esperiences and alias solution that I assume is solved with dot courier files. I'm assuming that they need to be created for each mailling list manually more or less like couriermlm but if not it would be great to find out.
I'm using mailman that shipped with RHEL4 with Courier-MTA and it works well. I had to rebuild the RPM though in order to add the daemon user as one who was allowed to call mailman directly (why that's a compile time option instead of a config file option beats me).
My solution was to create actual accounts for mailing lists like I would create real users in my LDAP database (although I disable logins since no one should be using IMAP, POP3 or worse, Auth. SMTP to the mailing list account). Then in the mailing list accounts home I just copy a blank .courier-default file (guess I could have done one per list extension but I'm lazy) and a .mailfilter that looks like below. I change the LIST= to match the list name, guess I might be able to find an already set variable that would work but this has been fine. Once I've got this setup, I create the list in mailman and all works well.
Thanks a lot, Jay, That is similar to what I had in mind, although untested. I appreciate your sharing it. I now know that it will work, if I can set it up properly. I'm going to give it a try and see. I also think that Bernd has an interesting solution that I want to try also to see if I understand it.
Thanks again,
ed
Jay
-- begin .mailfilter --
import EXT LIST=STAFF
if ($EXT eq 'admin') { to "|/usr/lib/mailman/mail/mailman admin $LIST" }
if ($EXT eq 'bounces') { to "|/usr/lib/mailman/mail/mailman bounces $LIST" }
if ($EXT eq 'confirm') { to "|/usr/lib/mailman/mail/mailman confirm $LIST" }
if ($EXT eq 'join') { to "|/usr/lib/mailman/mail/mailman join $LIST" }
if ($EXT eq 'leave') { to "|/usr/lib/mailman/mail/mailman leave $LIST" }
if ($EXT eq 'owner') { to "|/usr/lib/mailman/mail/mailman owner $LIST" }
if ($EXT eq 'request') { to "|/usr/lib/mailman/mail/mailman request $LIST" }
if ($EXT eq 'subscribe') { to "|/usr/lib/mailman/mail/mailman subscribe $LIST" }
if ($EXT eq 'unsubscribe') { to "|/usr/lib/mailman/mail/mailman unsubscribe $LIST" }
to "|/usr/lib/mailman/mail/mailman post $LIST"
-- end .mailfilter --
-- Jay Lee Network / Systems Administrator Information Technology Dept. Philadelphia Biblical University
--







