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

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=861
-----------------------------------------------------------------------
 Ticket     | 861
 Updated By | Michael Slusarz <slusarz at mail.curecanti.org>
 Summary    | S/MIME Content-Disposition not inline
 Queue      | Horde Framework Packages
-State      | New
+State      | Assigned
 Priority   | 2. Medium
 Type       | Enhancement
 Owners     | 
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2004-11-19 10:09) wrote:

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'.