🚀 go-pugleaf

newsspam5REMOVETHIS@robf.de writes:
> Julian Bradfield <jcb@inf.ed.ac.uk> writes:
> > Chris McMahan <first_initiallastname@one.dot.net> writes:
> >
> >> vm-decode-mime-message: Invalid MIME message: line 688: something
> >> other than line break or hex digits after = in quoted-printable
> >> encoding
> >>
> >> Has anyone else seen this or, better yet, fixed it?
> >
> > Yes, I've seen this and similar things - for example, an encoded
> > subject header with an (illegal) space in it causes a crash.
> > VM is not robust against malformed MIMEry, unfortunately.
> >
> > I haven't fixed it, but might do next time it happens to me :-)
> 
> You should get the patched qp-decode which is robust against
> those buggy messages.
> 
> Grab it with my patched VM at
> 
> http://www.robf.de/Hacking/elisp/vmrf.tgz
> 
> Robert.

This is the same bug that I reported a couple of months
ago. Interesting though that this did not seem to be a problem until
recently. Seems like one of the "commercial" MUAs is violating
standards again... (and thanks again for the patch)