On 10/26/2017 03:54 PM, Bjoern Franke wrote:

Hi,

I created & imported a bunch of 2.1 lists and for one of the lists mm3 replies mailbox unavailable to postfix.

I have no clue why this happens because the other lists work.

We need more information.

What are the postfix log messages associated with the error?

Is the list's domain the same as the working ones?

Are there entries for the list in Mailman's var/data/postfix_lmtp?

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 10/26/2017 11:30 PM, Bjoern Franke wrote:

Oct 27 08:24:58 srv20 postfix/lmtp[2981]: 8798E40979: to=<admin@lists.ffnw.de>, relay=localhost[127.0.0.1]:8024, delay=0.51, delays=0.43/0.02/0.02/0.03, dsn=5.0.0, status=bounced (host localhost[127.0.0.1] said: 550 Requested action not taken: mailbox unavailable (in reply to end of DATA command))

This may be a Mailman bug. I'll look further when I have time. The message above says that Postfix tried to deliver the message to Mailman's lmtp runner and the runner said there was no such list.

I'm guessing that there may be confusion between the admin@... list address and a listname-admin@... address. If this is the case, it means there is a bug which would affect any lists named 'admin', 'bounces', 'confirm'. 'join', 'leave', etc.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Hi,

This is definitely a bug. See the issue I just created at <https://gitlab.com/mailman/mailman/issues/433>

Thanks, I've patched our instance and admin@ works again.

Regards Bjoern