On Wed, Apr 23, 2025 at 5:56 PM Alexander Inzinger-Zrock via Mailman-users < mailman-users@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@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:
- could somebody suggest a way, an entry should occur in postfix_lmtp?
- What would be the appropriate order to manually generate aliases? first: postfix-command ''newaliases'' and second: mailman-command ''mailman aliases'' or reverse?
- 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''
- 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]