Closed
Bug 278846
Opened 20 years ago
Closed 20 years ago
Downloading POP email that exceeded max size causes it to duplicate in the inbox
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: benjamingslade+mozilla, Assigned: sspitzer)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041122 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041122 I have my POP inbox set the following way: * Automatically download new mail * Leave messages on the server, until I delete or move them from the inbox * Cleanup trash on exit * Do not download messages larger than 300Kbytes When I receive a large email (eg. 390Kbytes), the body appropriately displays the "message exceeded the Maximum Message Size" and asks me to "Click here to download the rest of the message" When I do that, the message does download properly, but a new copy of the email pops up in my inbox. When I look at the headers (view source), all the headers are the same except for the following lines: % diff FirstEmail.txt DuplicateEmail.txt 1c1 < From - Tue Jan 18 10:49:08 2005 --- > From - Tue Jan 18 10:49:00 2005 4c4 < X-Mozilla-Status: 0001 --- > X-Mozilla-Status: 0601 Reproducible: Always Steps to Reproduce: 1.Setup your inbox as described above (auto download new mail, leave msgs on server, until I delete or move, cleanup trash on exit, don't download emails greater than 300Kbytes) 2.Send your self an email with embedded image where the email exceeds 300Kbytes. A 390Kbyte email caused the problem for me. 3.Select the email in the inbox, then click on "Click here to download the rest of the message" Actual Results: The email showed up a second time in my inbox with the header diff's noted above. Expected Results: Just read the first email and not created a dupliate
Nevermind, it seems to be working in the latest in the latest 1.8a6 build
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•