I wonder why this issue keeps getting back after they fixed it
(according to their BTS) several times. See
https://bugs.kde.org/show_bug.cgi?id=108939
Careful; the CTE restriction for message MIME types is no longer valid. It
got repealed as part of RFC 6532. Well, okay ... message/global and
any new message subtypes are allowed to have other CTEs than 7bit, 8bit,
and binary.
Maybe I'll change my opinion about the last statement once I have
to exract attachments from broken messages...
Yeah, that's exactly the situation I was in :-/
So ... I guess what I'm hearing is ... we should do nothing. At least
for now. It sounds like it's relatively infrequent enough that it isn't
impacting too many people, and it can be worked around with relatively
litle pain. I don't particularly like that situation, but it seems like
all of the alternatives are worse (in different ways). Maybe changing the
error message a bit would be useful?
--Ken
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers