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