On 10/02/2017 05:37 AM, Marc Sluiter wrote:
I got almost everything working besides confirm mails (see my other mail), but I had to use another postfix configuration than recommended, I’m wondering why the recommended way didn’t work. Sidenote: I’m not a postfix expert.
Neither am I ;)
This is recommended:
transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains
This didn’t work, all mails to mailman were rejected. Postfix did not even check the “local_recipient_maps”. After a lot of reading that made sense to me, because when I understand it correctly, “local_recipient_maps” is only checked for domains in “mydestinations”. And there I only have localhost.
On mail.python.org which is a complex Postfix environment with both Mailman 2 and Mailman 3 lists in the @python.org domain, for Mailman 3 I have just transport_maps and relay_domains as recommended (but as hash tables) I don't have anything for Mailman in local_recipient_maps, but python.org is in virtual_alias_domains (not in virtual_mailbox_domains).
I think it could be either, and virtual_alias_maps (or virtual_mailbox_maps) does not require anything for Mailman because transport_maps handles it.
I think the bottom line here is the list domain must be in one of mydestination or virtual_*_domains.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan