6.0.0-beta1
7/6/25

[#7945] replying to a smime signed email results in mimeheaders in the mailtext
Summary replying to a smime signed email results in mimeheaders in the mailtext
Queue IMP
Queue Version 4.3.3
Type Bug
State Resolved
Priority 1. Low
Owners chuck (at) horde (dot) org
Requester michael.menge (at) zdv (dot) uni-tuebingen (dot) de
Created 02/04/2009 (5996 days ago)
Due
Updated 02/19/2009 (5981 days ago)
Assigned 02/19/2009 (5981 days ago)
Resolved 02/19/2009 (5981 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
02/19/2009 07:08:04 PM Chuck Hagenbuch Comment #13 Reply to this comment
It should. If not we need __clone methods to do proper cloning.
02/19/2009 07:03:46 PM michael (dot) menge (at) zdv (dot) uni-tuebingen (dot) de Comment #12 Reply to this comment
Will this function work with Horde 4?
02/19/2009 06:02:50 PM Chuck Hagenbuch Comment #11
State ⇒ Resolved
Reply to this comment
Reverted use of clone() in FW3.
02/19/2009 11:07:37 AM Jan Schneider Comment #10
State ⇒ Assigned
Assigned to Chuck Hagenbuch
Reply to this comment
Ah, yes. I can reproduce this now with a combination of PHP 5.2 and FW_3.
02/19/2009 10:57:31 AM michael (dot) menge (at) zdv (dot) uni-tuebingen (dot) de Comment #9 Reply to this comment
I could track this problem back to the following change



http://cvs.horde.org/diff.php/framework/Util/Util.php?r1=1.384.6.30&r2=1.384.6.31



As the comment mentions a php bug, the system is a SLES 10, SP2 on x86_64
php --version
PHP 5.2.5 with Suhosin-Patch 0.9.6.2 (cli) (built: Jan 13 2009 18:41:31)

Copyright (c) 1997-2007 The PHP Group

Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies

with eAccelerator v0.9.5.3, Copyright (c) 2004-2006 eAccelerator, by 
eAccelerator




02/17/2009 01:11:01 PM Jan Schneider Comment #8 Reply to this comment
I don't see this.
02/17/2009 10:11:34 AM michael (dot) menge (at) zdv (dot) uni-tuebingen (dot) de Comment #7 Reply to this comment
This bug is not limit to simime only but also affects pgp-signed emails.

Can someone please change the summary of this bug and confirm/reopen it.


02/13/2009 01:41:58 PM michael (dot) menge (at) zdv (dot) uni-tuebingen (dot) de Comment #6 Reply to this comment
Testing with older versions of Horde and Imp showed that this bug did 
not exist in Horde-3.3

and Imp 4.3 but ocured the first time after upgrade form Horde-3.3 and 
Imp 4.3 to Horde-3.3.2

and IMP 4.3.2
02/13/2009 08:36:07 AM michael (dot) menge (at) zdv (dot) uni-tuebingen (dot) de Comment #5 Reply to this comment
This BUG is more serious as i first thought, as ist forwarding signed 
e-mails breakes attachments

Downloading an attachment form a signed e-mail works fine.



To reproduce this bug:



1. write a signed messag with attachment to an accout you have acces to

2. forward this message (Body Text with Attchments), you don't need to 
sign this message





here is the begining of an forwarded xls attachment as example.





--=_xpquy01jvyo

Content-Type: application/vnd.ms-excel;

  name="example.xls"

Content-Disposition: inline;

  filename="example.xls"

Content-Transfer-Encoding: 8bit



Content-Type: application/vnd.ms-excel;

  name="example.xls"

Content-Transfer-Encoding: base64

Content-Disposition: inline;

  filename="example.xls"



0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAOwADAP7/CQAGAAAAAAAAAAAAAAABAAAAXQAAAAAA

AAAAEAAAEgAAAAEAAAD+////AAAAAAAAAAD/////////////////////////////////////




02/05/2009 09:21:01 PM Michael Slusarz Comment #4 Reply to this comment
It depends on whether the body text is plaintext or embedded in s/mime 
data.  So it may work sometimes but not others.
02/05/2009 08:16:37 PM michael (dot) menge (at) zdv (dot) uni-tuebingen (dot) de Comment #3 Reply to this comment
as far as i remember this bug did not exist in

Imp 4.2.x
02/05/2009 05:33:39 PM Michael Slusarz Comment #2
State ⇒ Not A Bug
Reply to this comment
This is due to technical limitations in IMP 4 and can't be fixed in 
that release.  This has already been fixed in IMP 5.
02/04/2009 05:48:22 PM michael (dot) menge (at) zdv (dot) uni-tuebingen (dot) de Comment #1
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ replying to a smime signed email results in mimeheaders in the mailtext
Type ⇒ Bug
Reply to this comment
If you reply to a smime signed email or forward such an email,

the quoted/forwarded textarea in the composewindow contains the

header informations form the mimepart. e.g.



Content-Type: text/plain; charset=ISO-8859-1

Content-Transfer-Encoding: 7bit








Saved Queries