[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Quoted printable problem

From: Harald Geyer
Subject: Re: [Nmh-workers] Quoted printable problem
Date: Tue, 18 Dec 2012 21:05:25 +0100

David wrote:
> RFC 2045, Sec. 6.4:
>    If an entity is of type "multipart" the
>    Content-Transfer-Encoding is not permitted to have any
>    value other than "7bit", "8bit" or "binary".
> Would you or anyone else notify KMail?  I'm looking into
> Alpine and will notify them if they have a bug.

After reading some of there bug reports I think they know that
already and have fixed similiar issues in the past. I don't what
I can do besides voting these bugs to raise the importance...

I wonder why this issue keeps getting back after they fixed it
(according to their BTS) several times. See

of even 

for some really old instance of this.

Ken wrote:
> >One seems to be https://bugs.kde.org/show_bug.cgi?id=296629
> So, the activity on this bug suggests that we're not the only one who
> has issues with this malformed MIME; other prominent MUAs (and listserv
> software) refuse to parse this email.  My previous thinking was that if
> nmh was the only client in the world that refused to deal with this then
> there was absolutely no hope of getting the rest of the world on board,
> but since we're not the only one there is a chance that enough people
> will complain that offending software will get fixed.

Indeed. OTOH this issue seems to come back at about the same rate as
people upgrade their MUA ... :(
> But still ... choking on this just sticks in my craw.  What do people
> think of a -force option (or something similar) that can override MIME
> consistency checks like this one?

As somebody who has to read the occasional message from my contact
via less since about two years: I'm not sure if it is worth the
effort and extra complexity:

If you see an easy way to handle this type of malformed messages
gracefully without adding options, writing new documentation for them,
etc. then great: nmh is a MUA and not MIMElint.

If there is no easy solution and I need to read the occasional
message in less, I don't mind too much. I'd rather see proper MIME
support in nmh than worry about support for broken MIME.

Maybe I'll change my opinion about the last statement once I have
to exract attachments from broken messages...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]