Thanks On 22/6/22 15:36, Wietse Venema <wie...@porcupine.org> wrote:
Francesc Pe?alvez: > > I have a problem with postfix + mailman3. Mailman creates the necessary aliases of the mailing lists and they are added as follows in postfix: > > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains > swap_bangpath = no > > > having that conf in the postfix main.cf to which a mail is sent, some alias created in /etc/aliases indicates the following: > > activate postfix/smtp[424780]: EF29FFF8AE: to=<fil...@almogavers.net>, relay=mail.almogavers.net[46.26.57.213]:25, delay=1.9, delays=0.07/0.06/1.6/0.1, dsn =5.1.1, status=bounced (host mail.almogavers.net[46.26.57.213] said: 550 5.1.1<fil...@almogavers.net>: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command)) > > What would I have to change in postfix to accept normal aliases outside of mailman3?Nornally, local_recipient_maps specifies the usernames for UNIX system accounts. By default, - domains listed in mydestination are delivered with $local_transport. - recipients are listed in local_recipient_maps - By default, local_recipient_maps = proxy:unix:passwd.byname $alias_maps - By default, local_transport = local You removed the unix:passwd.byname and alias_maps tables from local_recipient_maps, and therefore broke delivery to those recipients. Wietse
