Marvin Gülker writes:
I've accidentally sent from an unregisted address to one of my lists. Mailman correctly held the message back for moderation, but when I go to the page for held messages in postorios, I receive a 500 error. I've included an except from the log below. To me, it looks as if it errors on processing my last name (which has a non-ascii character in it).
You're the "it's 2019, let's use SMTP UTF8 everywhere" guy, right? If you're right about the umlaut being the trigger, the first thing I'd look at is a feature-negotiation problem in the MTA delivering to Mailman. I'm pretty sure our LMTP does not offer the SMTP UTF8 feature.
Ideas? And how do I discard the message without access to the held messages page?
I would guess this is in the shunt queue. If there's only one file there, you can just delete it.
To get more information about the content of posts, use "mailman qfiles".
UnicodeEncodeError: 'ascii' codec can't encode character '\ufffd' in position 269: ordinal not in range(128)
Assuming you're right about your name being the trigger, U+FFFD REPLACEMENT CHARACTER is not in your name. So the non-ASCII character was replaced *on the way in*, and on the way out Mailman assumes ASCII in the header because Mailman doesn't know how to negotiate SMTP UTF8, and SMTP UTF8 specifies UTF8 in a context where there is no MIME way to indicate it to Mailman. So Mailman has no way of knowing it needs to encode to anything but ASCII (as specified by the Ancient Wisdom of RFC 5322).
I'll put SMTP UTF8 support as a feature request in the tracker. I'm not sure how difficult this will be; it presumably involves RFC something (6532 or so?) internationalization support etc. and may not be trivial. So no short term promises, just medium term aspirations (next year's GSoC task list, for example).
Steve