Alexander Inzinger-Zrock via Mailman-users writes:
B. /etc/postfix/main.cfg local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/path-to-mailman/var/data/postfix_lmtp
This is the main issue for main.cfg. Others we can deal with later if they apply to your system.
C. aliasing, restarting services and test without ,
I then restarted postfix, rebuilt the postfix aliases (command ''newaliases'')
These are not relevant to Mailman 3, except maybe you have an alias for the Mailman site admin.
and rebuilt the mailman aliases (command ''mailman aliases''),
I usually just restart Mailman instead (building the aliases is most of the time taken up by starting Mailman with Postfix).
D. empty /opt/mailman/mm/var/data/postfix_lmtp
and then i just found out that my postfix_lmpt file was empty
- What database are you using?[1] Is it running? If not, yes, that file is going to be empty.
- Do you have any lists configured for your Mailman 3 instance? If not, that file will be empty.
- Is Mailman running? (This probably isn't necessary, just checking.)
- Is there a postfix_lmtp.db file in the same place? (Postfix will not read the plaintext version, it must be a .db file.)
- could somebody suggest a way, an entry should occur in postfix_lmtp?
Each entry in postfix_lmtp is added to the SQL database when you create a list, then the whole file is refreshed from the SQL database at that time. After that, the file is refreshed from the database every time you start Mailman or run "mailman aliases".
- What would be the appropriate order to manually generate aliases? first: postfix-command ''newaliases'' and
It doesn't matter. newaliases only handles local aliases. Mailman 3's aliases are necessarily *virtual* aliases, and the database is created from the postfix_lmtp file using "postmap", not "postalias".
- finding traces [7] of a file called postfix.cfg
3.1 parameter for default lookup table type 3.2 pointing to command ''postmap''
Both entries must be present or Mailman will error out before creating the postfix_lmtp file. There should be a template (actually, you can probably use it "as is") in site-packages/mailman/mta/postfix.cfg (or maybe in config/postfix.cfg).
This file can be located anywhere, but I recommend putting it where mailman.cfg is (usually /etc/mailman3), and pointing to it in the [mta] section of mailman.cfg with the full path.
- to what user should the command ''postmap'' be available [8]?
The user that the "mailman" command expects to run as. Normally it is installed with a+x in /usr/sbin, so as long as you put the full path in postfix.cfg you'll be fine.
Footnotes: [1] We *strongly* recommend a full-scale SQL implementation like PostgreSQL (what the Mailman developers generally use) or one of the MySQL family (popular but not with us for no particular reason, we just happen to use PostgreSQL). sqlite3 is a great product, but it is not designed for heavy concurrent usage, and a typical Mailman system has about 15 daemons running all the time that are accessing the DB.
-- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan