#3987: Bug in Yahoo Mail where body contains an empty text attachment if sent
through mutt
----------------------+----------------------
Reporter: Peter92 | Owner: mutt-dev
Type: defect | Status: new
Priority: minor | Milestone:
Component: mutt | Version: 1.5.24
Resolution: | Keywords:
----------------------+----------------------
Comment (by kevin8t8):
This isn't "more of" a bug on the side of Yahoo; it's unequivocally
Yahoo's issue (which, strangely, I still can't reproduce).
Peeking at RFC 2183, the abstract at the very beginning says:
It specifies the "Content-Disposition" header field, which is optional
and valid for any MIME entity ("message" or "body part").
and to make it perfectly clear, section 2.10 plainly states:
It is permissible to use Content-Disposition on the main body of an
[RFC 822] message.
Furthermore, as if it weren't ridiculous enough that they are mishandling
a 20-year old RFC, the header itself says {{{inline}}}. Sigh. Okay,
enough ranting, it's not as if this is your fault.
I need to take a closer look at the code to see what, if anything, is
possible. The code for writing headers and body are reused in many
situations, and things like $fcc_attach, encryption, signing, and
$fcc_clear, make this less easy than one might initially think.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3987#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
