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 |
State ⇒ Not A Bug
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.
New Attachment: B.headers.txt
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.
View Message Source link from the message page) for each message.
State ⇒ Feedback
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.
State ⇒ Assigned
already corrupted.
New Attachment: C.doc
New Attachment: B.doc
A sends B a file. This is attached as B.doc
bug report.
#2- this new issue has already been fixed in HEAD and 4.0.x.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>:
State ⇒ Feedback
example messages (i.e. the A -> B message and the B -> C message) so
we can compare.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Forwarding corrupts attachments
Queue ⇒ IMP
State ⇒ Unconfirmed
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