On 12/18/20 9:49 AM, costavitor...@gmail.com wrote: > Hi all > > I'm upgrading a mailman2 installation to mailman3. And I using a docker > implementation, created by me and not Maxking's implementation. > > Everything is installed and is served correctly. > I have created a postfix container that relays emails to a smtp server, and I > can send emails by telnet from it. > When I create a new thread in Hyperkitty, I receive an error from postfix > container that the user (mailing list name) is not found. > > And I believe that is obvious because the aliases db are not accessible by > postfix.
In Mailman 3, Postfix uses transport_maps to deliver to Mailman via LMTP. It doesn't use aliases. > So, my questions are: > - Is there a way to share aliases db between containers(different hosts) of > mailman and postfix? I thought about sharing volumes but I'm not quite sure > if it's the best solution I don't know Docker and can't answer this. > - I've seen: > virtual_alias_maps = mysql:/etc/postfix/virtual/existing_aliases.cf, > var/lib/mailman/data/virtual-mailman > to add in postfix main.cf. That looks very strasnge. I don't think Postfix would like a relative path, but ignoring that, it certainly wants a table type. > Is it possible to do the same thing to aliases and transport_maps? And if so, > how to set it in mailman configuration, because this is for mailman I don't know what you mean by "the same thing". See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.html#postfix> for configuring Postfix for Mailman 3. Mailman can generate either hash tables or regexp tables. The above doc has details. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
