Recipient address rejected: User unknown in local recipient table
Hi,
I created a list called list_b@newlistserv.
postfix/smtpd[6757]: NOQUEUE: reject: RCPT from mail-eopbgr750113.outbound.xxx: 550 5.1.1 list_b@newlistserv.xxx: Recipient address rejected: User unknown in local recipient table; from=<xxx> to=list_b@newlistserv.xxx proto=ESMTP helo=
I am new to mailman3, my understanding was, maybe wrong, that when I create a list, mailman3 adds that to the local list of users. I think , I am missing something . . . Or probably this is related to a postfix setting?
Best regards Mohsen
On 4/15/20 3:47 PM, Mohsen Masoudfar wrote:
I am new to mailman3, my understanding was, maybe wrong, that when I create a list, mailman3 adds that to the local list of users. I think , I am missing something . . . Or probably this is related to a postfix setting?
Have you configured Mailman core and Postfix per https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks you so much Mark, I appreciate your help!
Yes, I did: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: newlistserv.aaas.org lmtp_port: 8024 smtp_host: newlistserv.aaas.org smtp_port: 25 configuration: python:mailman.config.postfix
# postconf recipient_delimiter recipient_delimiter = +
# postconf owner_request_special owner_request_special = no
in main.cf: local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp transport_maps = hash:/opt/mailman/var/data/postfix_lmtp virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap
Bur for some reason the postfix_lmtp.db is older than postfix_lmtp, which means it does not get updated automated, I guess.
I restarted the whole stack and added a new list. In postfix logs I see: Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_domains.db: No such file or directory Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_vmap.db: No such file or directory
I touched the /opt/mailman/var/data/postfix_vmap, but it did not help neither.
In addition, I found out this :
On my old mailman2 I have a setting in postfix main.cf: alias_maps = dbm:/usr/local/mailman/data/aliases
the file /usr/local/mailman/data/aliases says in its first line: # This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE
This makes a lot of sense to me.
The point is I am missing any similar settings on postfix on mailman3. Maybe local_recipient_maps do that, but as I mentioned the DB file is older than the text file. The result is that the list (which is actually a postfix user) is unknown to postfix completely. Now what is missing here? It appears that postorius can talk to postfix to send welcome messages out, but Postfix is not aware about the User that Postorius has created and exists in SQLite DB. So rejects any email addressed to that one.
Thanks Mohsen
-----Original Message----- From: Mark Sapiro mark@msapiro.net Sent: Wednesday, April 15, 2020 10:09 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: Recipient address rejected: User unknown in local recipient table
[EXTERNAL EMAIL]
On 4/15/20 3:47 PM, Mohsen Masoudfar wrote:
I am new to mailman3, my understanding was, maybe wrong, that when I create a list, mailman3 adds that to the local list of users. I think , I am missing something . . . Or probably this is related to a postfix setting?
Have you configured Mailman core and Postfix per https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.re...?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...
On 4/17/20 11:24 AM, Mohsen Masoudfar wrote:
[mta] ... configuration: python:mailman.config.postfix
What's in this configuration file (mailman/config/postfix.cfg)?
...
in main.cf: local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp transport_maps = hash:/opt/mailman/var/data/postfix_lmtp virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap
Bur for some reason the postfix_lmtp.db is older than postfix_lmtp, which means it does not get updated automated, I guess.
This leads me to think that your mailman/config/postfix.cfg contains
transport_file_type: regex
in which case all of the Mailman mappings defined in main.cf should be regexp: tables rather than hash: tables.
If you had
transport_file_type: hash
The .db files would be generated/updated whenever the corresponding text files are generated/updated.
I restarted the whole stack and added a new list. In postfix logs I see: Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_domains.db: No such file or directory
Where are you even referencing that? Did you forget
relay_domains = hash:/path-to-mailman/var/data/postfix_domains
in the above list?
...
In addition, I found out this :
On my old mailman2 I have a setting in postfix main.cf: alias_maps = dbm:/usr/local/mailman/data/aliases
the file /usr/local/mailman/data/aliases says in its first line: # This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE
This makes a lot of sense to me.
The point is I am missing any similar settings on postfix on mailman3.
Mailman 2.1's data/aliases and data/virtual-mailman files have been replaced by the data/postfix* files in Mailman 3.
I think your whole issue is you've configured Postfix with hash: tables but Mailman is generating regexp: tables.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I came across this same error and solved it doing some googling and came across this statement.
in main.cf: local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp
change it to: local_recipient_maps =
It fixed the immediate issue but I do not know enough to say why. Hope someone can elaborate on this.
On 4/30/20 1:25 PM, john_warland@hotmail.com wrote:
I came across this same error and solved it doing some googling and came across this statement.
in main.cf: local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp
change it to: local_recipient_maps =
It fixed the immediate issue but I do not know enough to say why. Hope someone can elaborate on this.
Setting
local_recipient_maps =
disables all local recipient checks. If you don't want to do that, you need to specify whatever the current or default setting is in addition, e.g.
local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/var/data/postfix_lmtp
See http://www.postfix.org/LOCAL_RECIPIENT_README.html
We need to update the docs for that setting.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 4/30/20 1:57 PM, Mark Sapiro wrote:
Setting
local_recipient_maps =
disables all local recipient checks. If you don't want to do that, you need to specify whatever the current or default setting is in addition, e.g.
local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/var/data/postfix_lmtp
See http://www.postfix.org/LOCAL_RECIPIENT_README.html
We need to update the docs for that setting.
And we have. https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#transport...
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
john_warland＠hotmail.com -
Mark Sapiro -
Mohsen Masoudfar