[Mailman-Users] transport-mailman and virtual-mailman not updated with new list

[Mark Sapiro]

On 01/08/2016 08:42 AM, Eggert Ehmke wrote:
> Am Freitag, 8. Januar 2016, 14:05:49 schrieb Eggert Ehmke:
>>
>> When I send a mail to list at domain2.de, it is forwarded to list at domain1.de,
>> which does not work of course.
>>
>> Jan  8 13:56:05 domain1 postfix/pipe[2066]: 9EE1C1003F1:
>> to=<list at domain1.de>, orig_to=<list at domain2.de>, relay=dovecot, delay=0.03,
>> delays=0.02/0/0/0.02, dsn=5.1.1, status=bounced (user unknown)


Something is wrong here because if everything is properly configured per
the FAQ at <http://wiki.list.org/x/10715238> the transport (relay)
should be 'local' not 'dovecot'
.

> I think this is because in the virtual_mailman all list addresses are mapped 
> to the naked list name, and postfix then appends the default domain.


Again, if things are properly configured per the FAQ at
<http://wiki.list.org/x/10715238>, virtual-mailman is only used to build
transport-mailman and only aliases and transport-mailman are used by
postfix for Mailman mail.


> I thought 
> this would be prevented by the mailman/bin/postfix-to-mailman.py script, but it 
> does not work.


postfix-to-mailman.py is incompatible with this and definitely won't
work well in a multi-domain environment. See the FAQ at
<http://wiki.list.org/x/15564817>.


> I also found a comment of you stating you don't see the reason 
> for this script. However, what can be done to make it work?


You probably can't make it work in your environment.

For further help, please post the output from 'postconf -n' and the
contents of /etc/postfix/master.cf.

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