On 1/4/24 9:42 PM, Stephen J. Turnbull wrote:
Dan Caballero writes:
I've got a message that keeps getting re-queued to the /hyperkitty/spool/ folder. [...] "During handling of the above exception (expected atom at a start of dot-atom-text but found '[1db292f04b54496ab40544b0989a2122-JFBVALKQOJXWILKNK4YVA7CPNZSVMZLUPRCW2YLJNRKGK43UPRCXQ32TNV2HA===@microsoft.com]>')"
This is arguably a HyperKitty bug. The email package is correctly refusing to parse that as a Message-ID (it's been illegal syntax since RFC 822 if I remember correctly), but something, presumably HyperKitty, should catch the error and do something to sanitize it to message-id syntax. On the other hand, I never heard of a message trigger that exception before a couple months ago, so maybe it's the responsibility of spam filters.
This is <https://gitlab.com/mailman/mailman/-/issues/1065> fixed in Mailman 3.3.9 by <https://gitlab.com/mailman/mailman/-/merge_requests/1099>.
In a later post you say that message came back, but I suspect it isn't the same message, but a new one likely from the same source.
I agree.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan