Geoff Shang wrote:
This would appear to be the sticking point. The aliases file doesn't generate fully-qualified Email addresses, only local parts. How do I ensure that a message to annou...@foo.com doesn't go to annou...@bar.org? This must be doable, because if it's not, then this defeats the whole point of doing this in the first place.

Presumably I need to do this in postfix/main.cf somehow but I'm at a loss as to how to do this.
   Not sure if this will help you or not, but I'll share anywhere ...

I have a multi setup for mailman to host multiple domains. All my list domains are configured as 'lists.$domain', for example 'lists.yeehaw.net'. My mailman installations all go under /home/mailman/lists.$domain

I don't know how this is done in postfix, but in sendmail I have the following:

   =====> /etc/mail/aliases/$domain-aliases
   mailman-lists.$domain           \
       "|/home/mailman/lists.$domain/mail/$domain-mailman post mailman"
   mailman-admin-lists.$domain:    \
       "|/home/mailman/lists.$domain/mail/$domain-mailman admin mailman"
   mailman-bounces-lists.$domain:  \
       "|/home/mailman/lists.$domain/mail/$domain-mailman bounces mailman"
   mailman-confirm-lists.$domain:  \
       "|/home/mailman/lists.$domain/mail/$domain-mailman confirm mailman"

   =====> /etc/mail/virtusertable
   mail...@lists.$domain              mailman-lists.$domain
   mailman-ad...@lists.$domain        mailman-admin-lists.$domain
   mailman-boun...@lists.$domain      mailman-bounces-lists.$domain
   mailman-conf...@lists.$domain      mailman-confirm-lists.$domain

This ensures that an incoming e-mail to say for example 'mailman-ad...@lists.$domain' gets rerouted to 'mailman-admin-lists.$domain' which the alias then expands in to
'"|/home/mailman/lists.$domain/mail/$domain-mailman admin mailman"'

This allows one to have various mailman@'various domains' going to the same server through the same MTA without it going nutso.

Now you may be wondering why I renamed the 'mailman' binary to '$domain-mailman'. That's because of permissions within sendmail. Any binary that is going to be sending stuff out needs to be allowed by sendmail, and since I have multiple installations of mailman, in different paths, you can't just tell sendmail it's called 'mailman'. It will get utterly confused when the various lists are trying to send something out. So, by renaming each one to their respective $domain, it keeps sendmail from going bonkers.

In my /usr/adm/sm.bin/ I have various symlinks to $domain-mailman which link back to /home/mailman/lists-$domain/mail/$domain-mailman

   Cheers

--
W | It's not a bug - it's an undocumented feature.
 +--------------------------------------------------------------------
 Ashley M. Kirchner <mailto:ash...@pcraft.com>   .   303.442.6410 x130
 IT Director / SysAdmin / Websmith             .     800.441.3873 x130
 Photo Craft Imaging                       .          2901 55th Street
http://www.pcraft.com ..... . . . Boulder, CO 80301, U.S.A.
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Reply via email to