Tickets :: Comment on [#861] S/MIME Content-Disposition not inline

* Your Email Address
* Spam protection	Enter the letters below: .___.._.. .. ..___. _/ \| \|_/ \|\ \| _/ ./__._\|_\| \\| \\|./__.
Comment	> No. RFC 2183 allows the user agent to choose what the default should > be if no Content-Disposition is defined - We have chosen 'attachment' > for a variety of reasons. Never honoring the Content-Disposition > header, as your patch suggests, is incompatible with RFC 2183. If > the user wants us to display a MIME part as an attachment, there is > no reason we should go against their wishes. > > > > A correct fix may be to look at our S/MIME implementation and > determine if it is desirable to send as 'inline' instead of > 'attachment'. > >
Attachment
Watch this ticket