> > 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). > […] > > 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". > >
Thanks for the tipps. > > 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? 1.1 MariaDB 1.2 running ('systemctl status mariadb.service […] Active: active (running)') > Do you have any lists configured for your Mailman 3 instance? If > not, that file will be empty. I have a list ''testliste01@MY_DOMAIN'', i can ''mailman inject'' mails to, 1 owner, 5 members (including the owner). I should point out that MY_DOMAIN is not equal to the HOSTNAME of the machine, but testmails with command ''mail'' or ''telnet'' show the same User-unkown-error, regardles of attempts sending to testliste01@MY_DOMAIN or testliste01@HOSTNAME. > Is Mailman running? (This probably isn't necessary, just > checking.) Running ('systemctl status mailman3.service […] Active: active (running)') also ('systemctl status mailmanweb.service […] Active: active (running)') > Is there a postfix_lmtp.db file in the same place? (Postfix will > not read the plaintext version, it must be a .db file.) Yes, under /opt/mailman/mm/var/data i have 1) mailman.db 2) postfix_domains (empty) 3) postfix_domains.db 4) postfix_lmtp (empty) 5) postfix_lmtp.db I dimly remember a problem with either 2) and 4) or 3) and 5) not beeing automatically created, but i can not tell exactly anymore. > > 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. + this file seems to be missing in my setting + also the postmap command seemed to be unavailable for the user ''mailman''. + [X] placed file in same dir as mailman.cfg (/etc/mailman3/) + [X] replaced old config and pointed to it in mailman.cfg with full path: #+begin_src txt /etc/mailman3/mailman.cfg #configuration: python:mailman.config.postfix configuration: /etc/mailman3/postfix.cfg #+end_src command ''mailman conf'' will show the new configuration path for [mta] but no results for search term 'postmap_command' nor 'transport_file_type'. > > > > 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. + [ ] made postmap-command available for user ''mailman'' (still have to work on that one, will give a follow-up as soon as i tried some ideas) _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/4DVARVFAV3SDTPBFYNJGRGWUQAWUNVKG/ This message sent to arch...@mail-archive.com