Closed
Bug 274528
Opened 20 years ago
Closed 20 years ago
IMAP Attachment Truncated
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 274527
People
(Reporter: commerce, Assigned: mscott)
Details
I have a message with two bitmap attachments, one 972 K and one 970 K. The message shows up in a Thunderbird IMAP folder as being 2551 KB. If I save the attachments from the IMAP folder in Thunderbird, the first one is truncated and is unreadable. If I view the source of the message, it is obvious that it ends too early and the MIME code has been truncated. However, if I save the attachments from an IMAP folder in Outlook Express, they both come out fine. This is also the case with POP in OE (this email account supports both IMAP and POP access). Furthermore, this is also the case with POP in Thunderbird. A possible clue is there seems to be something wrong with the reported size. Both Thunderbird and OE report its size in the IMAP folder as 2551 K, but both Thunderbird and OE report its size as 2593 K when it is downloaded via POP. If I copy the message in OE to another IMAP server it shows up as 2593 K on the second server, and both attachments can be read in OE and in Thunderbird. If I do the same thing with Thunderbird, it is truncated to 2551 K, with a corrupt attachment both in Thunderbird and OE. I'm guessing the size is somehow being reported incorrectly by the server and Thunderbird is only reading that many bytes, but OE IMAP and OE and Thunderbird POP3 are reading the whole message. I think ideally Thunderbird IMAP should be able to handle this (perhaps with a warning). The only way I know how to reproduce this is have someone look a the message on my server, so if you are interested in seeing this problem, please contact me, and I'll give you my account settings so you can reproduce it.
Comment 1•20 years ago
|
||
*** This bug has been marked as a duplicate of 274527 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•