| commit | 8daeda90d0d9e2ca0ab6b7dd8f088db3b18eccc8 | |
| author | Steffen (Daode) Nurpmeso <steffen@sdaoden.eu> | |
| Fri, 19 Feb 2016 16:13:42 +0000 (19 17:13 +0100) | ||
| committer | Steffen (Daode) Nurpmeso <steffen@sdaoden.eu> | |
| Thu, 15 Sep 2016 13:57:05 +0000 (15 15:57 +0200) | ||
| tree | 37347bf785f8e0946bd4fc20b0f978d09d79f26e | treesnapshot (tar.gz zip) |
| parent | 77d4f5c9566bb5d0f7d438628fdd4847d1eb06ba | commitdiff |
send.c:sendpart(): "support" malformed messages..
It happens that mutt doesn't only support messages in base64
encoding that is false (silently ignoring the faulty data), but
also supports messages where the header and the body are not
separated with a(n) (completely) empty line, obviously silently
assuming that the body is what follows and doesn't specify a valid
header field.
That is sick, but simply not showing anything is also pretty
weird, as we did until now and another tested MUA does.
So do the same, but at least with error message, so that the user
knows (or can guess) we're guessing.
While here, join some useless locals into a single flag carrier.
It happens that mutt doesn't only support messages in base64
encoding that is false (silently ignoring the faulty data), but
also supports messages where the header and the body are not
separated with a(n) (completely) empty line, obviously silently
assuming that the body is what follows and doesn't specify a valid
header field.
That is sick, but simply not showing anything is also pretty
weird, as we did until now and another tested MUA does.
So do the same, but at least with error message, so that the user
knows (or can guess) we're guessing.
While here, join some useless locals into a single flag carrier.
| send.c | diffblobblamehistory |