Bug in vm7-19

[Chris McMahan]

I've had persistent bugs in email messages that cause vm to
essentially crash. I've been manually opening my mbox and moving the
offending message to another file to analyze later (which just arrived
apparently).

Today I got an email from a company that I've dealt with before, and
it crashed. This time, rather than just deleting the message, I tried
to view the raw mime ('D' in the mail buffer) and got the following:

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?

- Chris

--
(. .)
=ooO=(_)=Ooo=====================================
Chris McMahan | first_init...@one.dot.net
=================================================

[Julian Bradfield]

Chris McMahan <first_init...@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 :-)

[newsspam5...@robf.de]

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.

[blueman]

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)