6.0.0-beta1
7/31/25

[#1698] IMP4.1 - Problem with S/MIME
Summary IMP4.1 - Problem with S/MIME
Queue IMP
Queue Version HEAD
Type Bug
State Not A Bug
Priority 2. Medium
Owners slusarz (at) horde (dot) org
Requester chris (at) 65bit (dot) de
Created 04/06/2005 (7421 days ago)
Due
Updated 04/07/2005 (7420 days ago)
Assigned 04/06/2005 (7421 days ago)
Resolved 04/07/2005 (7420 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
04/07/2005 04:13:46 AM Michael Slusarz Comment #6 Reply to this comment
My mistake - I should have been more clear with my description.  By 
saying you should use Horde HEAD I was not saying it was *required* to 
work; I was saying that this is where the issue was fixed.  For 
whatever reason, when I made these changes, I said they could wait 
until the next point release:



http://cvs.horde.org/diff.php/framework/MIME/MIME/Viewer.php?r1=1.64&r2=1.65&ty=h
04/07/2005 04:02:24 AM Chuck Hagenbuch Comment #5 Reply to this comment
Actually our development guidelines/goals/whatever are that any 4.x 
version of IMP should be usable with Horde 3.0.0, barring of course 
bugs fixed in later Horde 3.0.x releases. Is this not the case with 
IMP? If not, why not?
04/07/2005 04:00:07 AM Michael Slusarz Comment #4
State ⇒ Not A Bug
Reply to this comment
You can't use Horde 3.0.x with IMP HEAD.  That just isn't going to 
work.  You need Horde HEAD.  This was fixed long ago (in fact, it is 
the first entry in imp/docs/CHANGES for imp 4.1 CVS).
04/06/2005 02:53:25 PM chris (at) 65bit (dot) de Comment #3 Reply to this comment
sounds right. Than it seems that Netscape/Mozilla/Thunderbird and so on

breaking the RFCs.

But maybe you would like to display these mails in IMP in a correct way like

these mailprogs do it?

Or refers the content-dispositon to the S/MIME attachment and not the 
content of the S/MIME-attachment?
04/06/2005 02:28:19 PM Chuck Hagenbuch Comment #2
Assigned to Michael Slusarz
State ⇒ Feedback
Reply to this comment
Well, if you mark a part as disposition: attachment, the RFCs are 
pretty clear that you mean attachment, and it shouldn't be shown inline.
04/06/2005 07:40:35 AM chris (at) 65bit (dot) de Comment #1
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ IMP4.1 - Problem with S/MIME
Queue ⇒ IMP
New Attachment: test.html Download
Reply to this comment
Hi there,



I have problems with S/MIME Mails sent from Netscape/Moziall/....

I'm not able to view a S/MIME-coded mail-text inline.

(so proper mailhandling is really impossible)

I tried all settings regarding to inline/attachment viewing.



Netscape & co is able to display these mails correct.



The Problem seems that netscape send its mails with

Content-Disposition:           attachment; filename="smime.p7m"



IMP sends it's mails with

Content-Disposition:           inline; filename="smime.p7m"



IMP is not able to override this.



If i then view a Netscape-smime-mail in IMP as attachment, the

mailtext is not very well formatted in the popup-attachment viewer.



running:

horde 3.0.4 stable

imp 4.1 cvs (from today - 06.Apr.2005)

(see attachment)

all in German



mni tnx

Chris

Saved Queries