#3067: PGP/MIME signatures incorrectly assigned "Content-Disposition: inline"
Comment (by jmcclelland): > The notion that the PGP/MIME signature is "supposed to be an > attachment", and that that somehow influences the choice of value > for Content-Disposition is bogus: That makes a lot of sense. Thanks for the explanation. Given the lack of clarity in the spec, what do you think of leaving the Content-Disposition header out entirely? > A config-controlled option for this would be ridiculous, sorry. I don't understand why that would be ridiculous. Can you explain or point me to documentation that might help me understand that? Thanks. -- Ticket URL: <http://dev.mutt.org/trac/ticket/3067#comment:6>
