On October 25, 2017 9:17:33 PM EDT, "Fabian A. Santiago" <fsantiago@garbage-juice.com> wrote:
On October 25, 2017 9:13:20 PM EDT, Mark Sapiro <mark@msapiro.net> wrote:
On 10/25/2017 05:41 PM, Fabian A. Santiago wrote:
No to the domains part and I think virtual alias maps is needed:
mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx
Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not
Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: reject: RCPT from
in BOTH virtual_mailbox_domains and relay_domains list domain xxx in BOTH virtual_mailbox_domains and relay_domains pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 <test123@xxx>: Recipient address rejected: User unknown in virtual mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP helo=<[10.0.0.29]>
(above slightly sanitized for return to the list)
The issue here is your list domain cannot be a virtual_mailbox_domain or a virtual_alias_domain.
I have the same issue on mail.python.org where we have both Mailman 2 and Mailman 3 lists @python.org. and python.org is a virtual_alias_domain.
I have a group of MRs for a branch that implements "alias_domains" to deal with this.
Basically it works by creating another (virtual_alias_maps) postfix_vmap mapping to map list addresses @python.org to addresses @x.python.org. Then the postfix_domains and postfix_lmtp maps have the x.python.org domain and there is a patch to mailman/runners/lmtp.py to map the x.python.org domain back to python.org.
The various MRs are <https://gitlab.com/mailman/mailman/merge_requests/202> for the core, <https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the REST bindings used by Postorius and <https://gitlab.com/mailman/postorius/merge_requests/186> to be able to set an alias_domain via Postorius.
That's not all implemented at mail.python.org. What's there is the basic Postfix config, a bash script the generate the new mappings from the old and a simple patch to mailman/runners/lmtp.py.
So, the bottom line is it can be done and it's in process, but it won't really be supported until Mailman 3.2. In the mean time, you just need to have a separate domain for your lists that isn't a virtual_*_domain.
Ok thanks. At least I have a clear answer now. Any ETA on 3.2 in mind yet?
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Mark,
Ok I have it almost perfectly working now having taken your direction and configuring a unique domain not in my email system already.
But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error.
Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions.
https://github.com/maxking/docker-mailman
Thanks.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC