| Summary | Message w/ large RFC822 attachment w/many images won't forward |
| Queue | IMP |
| Queue Version | 4.1.3 |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | stpierre (at) nebrwesleyan (dot) edu |
| Created | 11/30/06 (7149 days ago) |
| Due | |
| Updated | 12/1/06 (7148 days ago) |
| Assigned | |
| Resolved | 12/1/06 (7148 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
Bug 3381. This has been fixed in HEAD since messages areforwarded as message/rfc822 parts now.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Message w/ large RFC822 attachment w/many images won't forward
Queue ⇒ IMP
New Attachment: wont-fwd.msg
other of my users comes through "blank." The message had some "funny"
text and a bunch of pictures; when forwarded with IMP, the
pictures come through as 0 byte files and the text is lost. Headers
from the previous sender remain intact.
I'm able to forward this message on using Pine without a problem --
the pictures and text are retained. There are no issues with opening
the message in either IMP or Pine.
I've attached the attachment, which is of type message/rfc822.
This may be a duplicate of
bug #4247, but that ticket has insufficientdetail for me to know for sure.