Hi,
Am 10. Dezember 2019 um 17:09 Uhr +0900 schrieb Stephen J. Turnbull:
You're the "it's 2019, let's use SMTP UTF8 everywhere" guy, right?
No, I'm not that guy. I've not said anything like that, nor have I knowingly configured Postfix to use that. I've looked up how to do it now that you mention it, and found the smtputf8_enable parameter1. I have not used it, but it turns out that it is enabled by default. I can turn it off and see if that makes any difference in the future. Testing with telnet, Postfix indeed announced "250 SMTPUTF8" on EHLO.
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.
In that case the problem should go away with disabling SMTPUTF8, I suppose?
I would guess this is in the shunt queue. If there's only one file there, you can just delete it.
There was a whole bunch of files in that directory. I've taken a look several of them, and as they were all spam, I've taken the liberty to delete them all (this list is so low volume that I know all the senders personally anyway). However, even after restarting mailman, the 500 error persists when visiting the held messages page in postorius.
I've also looked into all the other queue directories, they were all empty.
Assuming you're right about your name being the trigger, U+FFFD REPLACEMENT CHARACTER is not in your name.
I confess that I haven't visited the held messages page for a very long time (because I didn't have a reason to; I received no notifications of held messages). Only after I received the notification that my errorneous message was being held, I visited it, and I was faced with the 500 error. If Mailman failed to notify me of held messages previously, they might have been in hold status already and one of them might be the cause.
Marvin
PS: Sorry for the missing link 1 from the last mail. Here it is: https://gitlab.com/mailman/hyperkitty/issues/201
-- Blog: https://mg.guelker.eu