Search results for "user unknown in local recipient table" - Mailman-users

configuring postfix local recipient table

by Alexander Inzinger-Zrock

**System Key Data** OS: Debian 12 mailman: GNU Mailman 3.3.10 (Tom Sawyer) Python: Python 3.11.2 (main, Nov 30 2024, 21:22:50) [GCC 12.2.0] Method: Python Virtual Environment Installation Ahoi, i am trying to configure a mailman3 instance to replace a mailman2 installation (both on different hosts). The mm3 instance is actually not reachable (Incoming) but can send (Outgoing), as is the desired state to be (we intend to swap IPs during change of systems). A. Verify Incoming To verify that emails send to the MTA (postfix) get properly handled and handed over to the mm3-instance i tried to substitute incoming email by a) swaks utility [1] (fail) b) telnet utility [2] (fail) c) command ''mailman inject'' [3] (success) With c) i copied a former generate testmail-file to the mm3-host and injected it directly to my testlist (leaving out the MTA). With a) and b) i tried to hand over a testmail via CLI to the MTA (postfix) what resulted in the error: "Recipient address rejected: User unknown in local recipient table" B. /etc/postfix/main.cfg A search in mailman-users(a)mailman3.org archives [4] pointed me to the configuration of postfix as MTA [5], especially settings with the 'local_recipients_maps' parameter that should be set like [5]: local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/path-to-mailman/var/data/postfix_lmtp what i did / already had done. C. aliasing, restarting services and test without , I then restarted postfix, rebuilt the postfix aliases (command ''newaliases'') and rebuilt the mailman aliases (command ''mailman aliases''), even tried with space-separation instead of coma-separation [6], testet again with same result. D. empty /opt/mailman/mm/var/data/postfix_lmtp and then i just found out that my postfix_lmpt file was empty (that i believe to be the the place from where the hastables take their input). Questions: 1. could somebody suggest a way, an entry should occur in postfix_lmtp? 2. What would be the appropriate order to manually generate aliases? first: postfix-command ''newaliases'' and second: mailman-command ''mailman aliases'' or reverse? 3. finding traces [7] of a file called postfix.cfg i can't find it (anymore) in the official installation instructions. Is that file (still?) necessary regarding: 3.1 parameter for default lookup table type 3.2 pointing to command ''postmap'' 4. to what user should the command ''postmap'' be available [8]? Any pointer to manuals or examples i may have missed or ideas on any of those 4 questions would be greatly appreciated. lg alexander Sources: [1] swaks utility https://jetmore.org/john/code/swaks/ [2] telnet utility https://de.wikipedia.org/wiki/Telnet [3] command ''mailman inject'' https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… [4] search mailman-users(a)mailman3.org archives 'user unknown in local recipient table' https://lists.mailman3.org/archives/search?q=user+unknown+in+local+recipien… [5] docs mm3: 'Hooking up your mail server' https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… [6] docs postfix: local_recipient_maps https://www.postfix.org/postconf.5.html#local_recipient_maps [7] traces of postfix.cfg + https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… + https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [8] docs mm3: transport maps (regarding command ''postmap'') https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…

1 month, 2 weeks

Re: MM3 Postfix FROM header issue

by Stephen J. Turnbull

Mark Sapiro writes: > Presumably that's the 'Recipient address rejected: User unknown in > virtual alias table' message, but I see no virtual_alias_domains in > your posted main.cf. I'm pretty sure that what's going on here is that the message is coming in from outside, Postfix runs down the various relays (including local delivery) available, none matches, the last in line is virtual aliases, and that table is empty so the user is unknown. That's the only way I can see the sender_canonical_maps variable affecting *recipient*-based decisions, by making it look like the sender is local, and so enabling delivery to non-local addresses. Why a Mailman list appears to be non-local is a question I am not sure. My guess is myhostname = localhost because Postfix doc says mydomain "is derived from $myhostname by stripping off the first part (unless the result would be a top-level domain)," so literally "localhost" is the only deliverable domain left, and some-list(a)the.actual.dom doesn't work. Except that the.actual.dom should be in postfix_domains.db, so ... ???? Steve

1 year, 5 months

Re: mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected

by Christian Stalberg

Main.cf had transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains I then changed local_recipient_maps to transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains I then restarted postfix & mailman. When sending a message to the list I am still getting the same error I had before <Deepadaptation(a)lists.ccalternatives.org>: host lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command) help please! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, June 10, 2022 4:22 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected On 6/9/22 18:12, Christian Stalberg via Mailman-users wrote: > > -Added lists.ccalternatives.org to the mydestination line in > /etc/postfix/main.cf and restarted Postfix -Now a new error message: > <Deepadaptation(a)lists.ccalternatives.org>: host > lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 > <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: > User > unknown in local recipient table (in reply to RCPT TO command) See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml#transport-maps - in particular local_recipient_maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 years, 11 months

Re: Migrating from old V2 server to new V3 server. Questions.

by jkoral＠luc.edu

Mark, This turned out to be our external firewall. Since we are using O365. I was able to successfully telnet to port 25, but when sending e-mails, it was going outside and had to come back in. I then had to change some settings on our F5 and now the traffic is finally flowing through to the server. Now I am getting this error in mail.log. I have changed quite a few settings to try and not bother you anymore, but nothing seems to be working. Hopefully this will be an easy one for you. The unknown IP address is our F5 where the mail is coming through. 2024-11-13T20:31:15.988423-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] 2024-11-13T20:31:16.486460-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=1 quit=1 commands=2 2024-11-13T20:31:18.246010-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] 2024-11-13T20:31:18.708146-06:00 lstprdls01 postfix/smtpd[2261655]: NOQUEUE: reject: RCPT from unknown[10.18.3.105]: 550 5.1.1 <joetest(a)listservnew.luc.edu>: Recipient address rejected: User unknown in local recipient table; from=<jkoral(a)luc.edu> to=<joetest(a)listservnew.luc.edu> proto=ESMTP helo=<CO1PR03CU002.outbound.protection.outlook.com> 2024-11-13T20:31:18.852290-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=2 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6

6 months, 3 weeks

Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 11/13/24 18:44, jkoral(a)luc.edu wrote: > > Now I am getting this error in mail.log. I have changed quite a few settings to try and not bother you anymore, but nothing seems to be working. Hopefully this will be an easy one for you. The unknown IP address is our F5 where the mail is coming through. > > 2024-11-13T20:31:15.988423-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] > 2024-11-13T20:31:16.486460-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=1 quit=1 commands=2 > 2024-11-13T20:31:18.246010-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] > 2024-11-13T20:31:18.708146-06:00 lstprdls01 postfix/smtpd[2261655]: NOQUEUE: reject: RCPT from unknown[10.18.3.105]: 550 5.1.1 <joetest(a)listservnew.luc.edu>: Recipient address rejected: User unknown in local recipient table; from=<jkoral(a)luc.edu> to=<joetest(a)listservnew.luc.edu> proto=ESMTP helo=<CO1PR03CU002.outbound.protection.outlook.com> > 2024-11-13T20:31:18.852290-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=2 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6 What is joetest(a)listservnew.luc.edu? Is that a list? If so, is it mentioned in Mailman's var/data/postfix_lmtp and is that included in transport_maps and in local_recipient_maps in Postfix main.cf? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

Re: mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected

by Mark Sapiro

On 6/9/22 18:12, Christian Stalberg via Mailman-users wrote: > > -Added lists.ccalternatives.org to the mydestination line in > /etc/postfix/main.cf and restarted Postfix > -Now a new error message: > <Deepadaptation(a)lists.ccalternatives.org>: host > lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 > <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: > User > unknown in local recipient table (in reply to RCPT TO command) See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… - in particular local_recipient_maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected

by Christian Stalberg

Environment: Debian 10; Postfix 3.4.14; GNU Mailman 3.3.5; Mailman Core API Version 3.1; Mailman Core Python Version 3.7.3 Digging a hole after having simply created a new mailing list. This has not happened before. Steps taken: -Created list via web interface -Added subscribers via web interface -Sent email to listname -Received error bounce: This is the mail system at host zarathustra.ccalternatives.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <Deepadaptation(a)lists.ccalternatives.org>: mail for lists.ccalternatives.org loops back to myself -Added lists.ccalternatives.org to the mydestination line in /etc/postfix/main.cf and restarted Postfix -Now a new error message: <Deepadaptation(a)lists.ccalternatives.org>: host lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command)

2 years, 11 months

After importing my old databases, the mail local_recipient map is suddenly not working any more

by Wikinaut

After importing old databases everythimng looks fine now. But the mail local_recipient maps are not working (/etc/postfix/main.cf looks fine, as before, and postfix was restarted). Mails to test(a)example.org rejected with Error 550 Recipient address rejected: User unknown in local recipient table /* as in your installation guide */ transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains The files appears to be present: /var/lib/mailman3/data# dir 4 -rw-rw---- 1 mailman mailman 339 Oct 20 21:13 postfix_domains 8 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_domains.db 4 -rw-rw---- 1 mailman mailman 2714 Oct 20 21:13 postfix_lmtp 12 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_lmtp.db What else is needed to get the list-addresses working and not rejected? It worked before the import.

1 year, 7 months

Re: Unable to get Postfix to bounce messages to non-existent lists

by skenny＠scss.tcd.ie

Thanks Mark Sapiro and Stephen J. Turnbull for your responses. Re the output of mailq - this was initially confusing (to me anyway). The diagnostic for the message stuck in the queue was "connection timed out", but the IP listed was the Postfix mail server's not Mailman's. At a guess, Postfix was trying to send the message to Postfix's local domain after it failed to LMTP it over to the Mailman server, and was unable to do that too. Since I posted yesterday, I hit upon a solution that seems to work ... I set relay_recipient_maps to the same value as transport_maps, so that the relevant config lines now look like this: transport_maps = regexp:/var/mailman-data/postfix_lmtp local_recipient_maps = $alias_maps relay_domains = regexp:/var/mailman-data/postfix_domains relay_recipient_maps = regexp:/var/mailman-data/postfix_lmtp This seems to have the desired effect (and, I hope, no unintended consequences). If I fire a message at a non-existent list now, I get an immediate bounce message in my mail client - "Recipient address rejected: User [nonexistent-list(a)lists.scss.tcd.ie] unknown in relay recipient table". No longer is the message loitering in the Postfix queue. The Postfix documentation for relay_recipient_maps says "Optional lookup tables with all valid addresses in the domains that match $relay_domains. [...] Technically, tables listed with $relay_recipient_maps are used as lists: Postfix needs to know only if a lookup string is found or not, but it does not use the result from the table lookup." For transport_maps, it says "Optional lookup tables with mappings from recipient address to (message delivery transport, next-hop destination). " Postfix does what we want now: bounce the message is the list name isn't found in relay_recipient_maps, forward it on to the Mailman server via LMTP (transport_maps setting) if it is. Re Stephen J. Turnbull's comment about the patch allowing Postfix to query Mailman's database and more, I think I'll hold off for the moment, but good to know. We will reconfigure when it makes it into an official release (we're using Maxking's Docker images). As ever I'm really grateful for your taking the time to respond, many thanks. Kind regards.

1 year, 3 months

Re: configuring postfix local recipient table

by Odhiambo Washington

On Wed, Apr 23, 2025 at 5:56 PM Alexander Inzinger-Zrock via Mailman-users < mailman-users(a)mailman3.org> wrote: > **System Key Data** > OS: Debian 12 > mailman: GNU Mailman 3.3.10 (Tom Sawyer) > Python: Python 3.11.2 (main, Nov 30 2024, 21:22:50) [GCC 12.2.0] > Method: Python Virtual Environment Installation > > > Ahoi, > > i am trying to configure a mailman3 instance > to replace a mailman2 installation (both on different hosts). > The mm3 instance is actually not reachable (Incoming) but can send > (Outgoing), > as is the desired state to be (we intend to swap IPs during change of > systems). > > A. Verify Incoming > > To verify that emails send to the MTA (postfix) get properly handled > and handed over to the mm3-instance i tried to substitute incoming email by > > a) swaks utility [1] (fail) > b) telnet utility [2] (fail) > c) command ''mailman inject'' [3] (success) > > With c) i copied a former generate testmail-file to the mm3-host > and injected it directly to my testlist (leaving out the MTA). > > With a) and b) i tried to hand over a testmail via CLI to the MTA (postfix) > what resulted in the error: > > "Recipient address rejected: User unknown in local recipient table" > > > B. /etc/postfix/main.cfg > > A search in mailman-users(a)mailman3.org archives [4] pointed me to the > configuration of postfix as MTA [5], especially settings with the > 'local_recipients_maps' parameter that should be set like [5]: > > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/path-to-mailman/var/data/postfix_lmtp > > what i did / already had done. > > > C. aliasing, restarting services and test without , > > I then restarted postfix, rebuilt the postfix aliases (command > ''newaliases'') > and rebuilt the mailman aliases (command ''mailman aliases''), > even tried with space-separation instead of coma-separation [6], > testet again with same result. > > > D. empty /opt/mailman/mm/var/data/postfix_lmtp > > and then i just found out that my postfix_lmpt file was empty > (that i believe to be the the place from where the hastables take their > input). > > > Questions: > > 1. could somebody suggest a way, an entry should occur in postfix_lmtp? > 2. What would be the appropriate order to manually generate aliases? > first: postfix-command ''newaliases'' and > second: mailman-command ''mailman aliases'' > or reverse? > 3. finding traces [7] of a file called postfix.cfg > i can't find it (anymore) in the official installation instructions. > Is that file (still?) necessary regarding: > 3.1 parameter for default lookup table type > 3.2 pointing to command ''postmap'' > 4. to what user should the command ''postmap'' be available [8]? > > > Any pointer to manuals or examples i may have missed or ideas > on any of those 4 questions would be greatly appreciated. > There is just one definitive manual: https://docs.mailman3.org/en/latest/install/virtualenv.html If this is NOT what you followed, then my suggestion is you start over afresh and follow the steps without skipping anything. You can test Mailman3+Postfix with a phony domain name. As long as the domain name is local, deliveries to the list should happen. Try and apply the KISS principle. For instance, you could submit a post to Mailman by: echo "This is a test post" | mail -s " Testing ML Delivery" listname@phony-domain-name If submitted from an address you have subscribed to the list, you should see it in the archives of that list. Otherwise, you can see it in Postorius under held messages. The transaction details will be in mailman.log as well as your Postfix logfile. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 month, 2 weeks

Mailman-users search results for query "user unknown in local recipient table"