[Mailman-Users] Postfix won't recognise lists built by Mailman.

[Mark Sapiro]

Rod at freeserve wrote:
>
>Because my server is a pre-configured appliance I need to be careful with changing
>transport for the whole domain, but Postfix lets you change the transport for individual
>addresses, like this:
>
>list at mydomain.net    local:
>list-owner at mydomain.net  local:
>etc
>
>Putting these into the Postfix transport table got Postfix sending messages for these
>addresses to the Mailman commands. Of course it didn't work straight off, but a look at
>the maillog showed a very clear diagnostic from Mailman telling me that Postfix was trying
>to execute the commands with a gid of nobody, when I had it set up to use the Postfix gid.
>After reconfiguring Mailman with the right gid, the lists started to work and now my
>service is back on the air.
>
>A big thankyou to Mark for identifying the problem so clearly and quickly.
>
>I'll look at integrating more closely with Postfix and moving the aliases as suggested in
>a few days.


There are two things to be aware of.

If/when you configure Mailman/Postfix integration, you will have to reconfigure
Mailman again with a different --with-mail-gid because Postfix runs pipes as
the user who owns the alias file in which the pipe is found, and this will be
different from the current /etc/postfix/aliases.db.

The integration will not be complete in your case because the transport table
will also need updating, and Mailman doesn't know about that. It wouldn't be
too difficult for a Python Programmer to modify Mailman/MTA/Postfix.py to
maintain a transport table in the same way as it currently does the aliases
and virtual-mailman tables, and then add that table to Postfix transport_maps.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan