6.0.0-beta1
9/24/25

[#1338] Forwarding corrupts attachments
Summary Forwarding corrupts attachments
Queue IMP
Queue Version FRAMEWORK_3
Type Bug
State Not A Bug
Priority 1. Low
Owners Horde Developers (at)
Requester tewner (at) jct (dot) ac (dot) il
Created 02/09/2005 (7532 days ago)
Due
Updated 02/27/2005 (7514 days ago)
Assigned 02/18/2005 (7523 days ago)
Resolved 02/27/2005 (7514 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
02/27/2005 06:45:13 AM Michael Slusarz Comment #13
State ⇒ Not A Bug
Reply to this comment
Once again, I cannot reproduce this.  Forwarding the contents of 
Message Source B produces a perfectly fine attachment in message C for 
me.  You need to make sure you are using the latest version of either 
CVS or FRAMEWORK_3 since there was a recent MIME_Part change that may 
have fixed this behavior.
02/24/2005 03:57:37 PM   New Attachment: C.headers.txt Download
 
02/24/2005 03:57:05 PM tewner (at) jct (dot) ac (dot) il Comment #12
New Attachment: B.headers.txt Download
Reply to this comment
Attached are the full email source for B and C.



recap:

A sends file to B

B can read the file, but when forwarding it to C, the file is 
corrupted. The file is already corrupted in B's "foward" screen, I 
think.




02/24/2005 03:41:30 PM Michael Slusarz Comment #11 Reply to this comment
We need the complete Message Source w/the MIME headers (i.e. using the 
View Message Source link from the message page) for each message.
02/24/2005 02:17:26 PM tewner (at) jct (dot) ac (dot) il Comment #10 Reply to this comment
I'm not sure what you're looking for.
02/24/2005 01:45:27 AM Michael Slusarz Comment #9 Reply to this comment
Still waiting for the original text of both messages.
02/18/2005 07:00:41 AM Michael Slusarz Comment #8
State ⇒ Feedback
Reply to this comment
Obviously, C.doc isn't going to be readable by MSWord since it is 
still binary encoded.  That's why the really interesting information 
is the rawtext of the messages, not the contents of the attachment, 
since this looks like an issue with the Content-Type-Encoding 
parameter in the message.
02/16/2005 10:11:15 AM Jan Schneider Assigned to Horde DevelopersHorde Developers
State ⇒ Assigned
 
02/13/2005 08:48:14 AM tewner (at) jct (dot) ac (dot) il Comment #7 Reply to this comment
B is able to read the document. The preview in B's "forward" window is 
already corrupted.
02/13/2005 08:42:54 AM tewner (at) jct (dot) ac (dot) il Comment #6
New Attachment: C.doc Download
Reply to this comment
Then B forwards it to C. C gets a corrupted file, attached as C.doc




02/13/2005 08:41:45 AM tewner (at) jct (dot) ac (dot) il Comment #5
New Attachment: B.doc Download
Reply to this comment
OK.

A sends B a file. This is attached as B.doc
02/11/2005 03:55:56 AM Michael Slusarz Comment #4 Reply to this comment
#1 - don't post a bug report on a different bug in an already opened 
bug report.

#2 - this new issue has already been fixed in HEAD and 4.0.x.
02/10/2005 01:54:41 PM tewner (at) jct (dot) ac (dot) il Comment #3 Reply to this comment
I'll get to uploading the attachments soon, but this might be related. 
I got a complaint that:



It used to be <Horde framework 3.0 distribution> that when I replied 
to a message, even if it was encoded in Hebrew, I would see the sent 
Hebrew text.  Now, it only shows me the encoded text, in ASCII.



E.g.:



vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv

Quoting Bachar <name@jct.ac.il>:

[Show Quoted Text - 9 lines]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^




02/10/2005 05:15:52 AM Michael Slusarz Comment #2
State ⇒ Feedback
Reply to this comment
I can't reproduce this.  You should post  the message sources of two 
example messages (i.e. the A -> B message and the B -> C message) so 
we can compare.
02/09/2005 09:59:51 AM tewner (at) jct (dot) ac (dot) il Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Forwarding corrupts attachments
Queue ⇒ IMP
State ⇒ Unconfirmed
Reply to this comment
I'm running IMP 4.1-cvs (problem occurs with IE and Firefox)



A sends B an attached word document. B can read the attachment in his 
office application. B then forwards it to C. C's attachment is 
corrupted, ie, just word file full of garbage. C's file is also a few 
KB bigger. C's Open office asks me what CharSet I want to open the 
file as. B's does not ask. The problem was reported on a windows 
machine (MS office), so I don't think it's a openoffice problem.



I tried changing "disposition" from "inline" to "attachment" . Didin't help






Saved Queries