Re: [Nmh-workers] mhshow: invalid QUOTED-PRINTABLE encoding

[Paul Fox]

this is a revival of an old thread, from last december.  the symptom is:

 > mhshow: invalid QUOTED-PRINTABLE encoding -- expecting hexidecimal-digit,
 >         but got char 0x6c

i believe there was consensus that a) this behavior was a result
of a problem with the original content encoding, and that b) the
nmh decoder should be more tolerant when decoding, and simply
pass mis-codings through untouched.

was this change ever made?  (i confess i'm not running the latest
code...  "show -version" reports 1.1, built 2/27/2004.)

paul
p.s.  the main sources of such mis-encodings in my experience are
mailing lists (specifically sourceforge lists) which
indiscriminately apply a signature containing encodable
characters to message bodies which have already been encoded.  i
tried filing a bug against the sourceforge infrastructure, but i
doubt anything came of it.

 > ===============
 > 
 > I'm having a problem with mhshow which Google seems to know nothing about;
 > maybe somebody here could shed some light on it?
 > 
 > I have a message which, when I try to show it, I get the following output:
 > 
 > address@hidden ~]$ show
 > (Message inbox:180)
 > mhshow: invalid QUOTED-PRINTABLE encoding -- expecting hexidecimal-digit,
 >         but got char 0x6c
 >         (content text/plain in message 180)
 > 
 > I don't see anything seriously weird about he message itself, and it looks
 > like mhshow is complaining about an 'l' (0x6c). Any ideas as to what might
 > be the cause?
 >  
 > -- 
 > J.
 > 
 > 
 > _______________________________________________
 > Nmh-workers mailing list
 > address@hidden
 > http://lists.nongnu.org/mailman/listinfo/nmh-workers

=---------------------
 paul fox, address@hidden (arlington, ma, where it's 24.3 degrees)