On 12 May 2025, at 14:18, Stephen J. Turnbull wrote:
This isn't a problem yet. The fact that DEFAULT_EMAIL_HOST and
$myorigin are not in $mydestination looks like a potential problem to
me, but we'll deal with any issues here once you get mail into the
pipes that go to Mailman.
So I had `myorigin = $mydomain` but upon further reading I'm thinking
it's probably better to have `myorigin = $myhostname` (postfix's
default). I've changed that, so now $myorigin *is* in $mydestination
since $mydestination included $myhostname already.
But plain `example.com` is not in $mydestination since there's a big
warning that virtual domains should not be listed there.
This didn't fix it though...
On 12 May 2025, at 16:50, Mark Sapiro wrote:
Hmm, the dovecot-related settings in main.cf seem to be:
mailbox_transport = lmtp:unix:private/dovecot-lmtp
This sends all local deliveries to dovecot before consulting aliases.
Indeed this was wrong. Looking in my notes/docs I don't understand why
I set it like that. Must have been some experimentation with a previous
issue.
This didn't fix it though...
At a certain point (been playing with this all day), I realized the
error message had changed, and that lead me to discover that having
`reject_unverified_recipient` in `smtpd_recipient_restrictions` was
blocking things; so I removed that.
This didn't fix it though...
But now my error message does not appear to involve dovecot, which
seemed like progress:
```
May 13 18:03:03 myhostname postfix/local[27304]: E1F5730DF5:
to=<testl...@myhostname.example.com>, orig_to=<testl...@example.com>,
relay=local, delay=0.53, delays=0.51/0.01/0/0.01, dsn=5.1.1,
status=bounced (unknown user: "testlist")
```
I then hacked `/usr/local/mailman/data/aliases` to add a mapping of:
```
testlist: s...@example.com
```
So I could see if this alias file was being consulted at all. I ran
`postmap /usr/local/mailman/data/aliases` (sic). That output warnings
of `record is in "key: value" format; is this an alias file?`. I should
have used postalias, not postmap! Reran with postalias, and now the
message is delivered! Removed that hack, reran postalias, and now all
is well! So probably one of my problems was that I mixed up postalias
and postmap with some previous experimentation and had a corrupt
`/usr/local/mailman/data/aliases.db`.
Thanks to all for your help! You really helped me understand which
settings I needed to investigate.
Sean
------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@mail-archive.com
