(This bug imported from BugSplat, Netscape's internal bugsystem. It was known there as bug #333006 http://scopus.netscape.com/bugsplat/show_bug.cgi?id=333006 Imported into Bugzilla on 01/27/99 18:28) Related to bug 98380 (...reproducable bug - attachments download twice) Builds: Solaris 2.5.1 Nova RTM build installed on Sun Ultra 1, unix box "buggy" Irix 62 Nova RTM build installed on "buggy" rlogin to "esthersgi" Problem: On unix only, when you receive a message that has an attached (large) Jpeg/Gif attachment, the attachment is downloaded two or three times as the image is being displayed inline. Visually, on the status bar, you see the progress of the download occurs 2 to 3 times. If you have IMAP logging turned on, you can see in the log the message attachment being downloaded multiple times. The problem appears to occur if you use a file attachment greater than the Mime Parts on Demand threshold of 30K. This problem occurs whether you have MPOD enabled or disabled. Note: This problem does not appear to occur on Win32 Oct 20b Nova RTM build or PPC Oct 20.2 Nova RTM build. Setting priority to P2 since attaching Gif/Jpeg files is a common occurrence. Steps to reproduce problem: 0) Enable IMAP Logging 1) Mail Server type is IMAP 2) Launch Communicator Oct 13 build (Irix/Solaris) 3) Use another machine to send a machine to your unix box. Be sure to attach a gif/jpeg attachment larger than 30K 4) Open Inbox 5) Select the new message The messages begins to display. The image starts to display and the status bar indicates that the message is being downloaded. As the image is being displayed, it stops loading and the image is downloaded again. After 2-3 downloads, the image is displayed. **I will post my IMAP log.

Posted IMAP logs file to http://jazz/users/pmock/publish/bug333006 There are two logs here. The Moxena.log is less than 500K and the Largejpeg log is over 7.7 MB in size. In the Moxena log, I sent a jpeg that was 75KB and in the Largejpeg.log, I used a jpage that was over 900KB.

Batch reassigning chrisf's empty-TFV bugs to mscott and marking TFV 5.0

Setting all current Open/Normal to M4.

qa contact to pmock

This has a current target milestone of M4. Would you consider this an M4 stopper? If not, please change the milestone accordingly.

M7...we don't have imap yet so we can't fix bugs for it.

This bug was in 4.x imap. I know we aren't at 4.x quality imap yet and won't be for M7. Pushing off to M10. Maybe I'll know how to fix it after i work on mime parts on demand & such.

This seems like a "really nice to fix" for PR1, but I wouldn't consider it a blocker

post beta 1.

Peter,can you verify that this doesn't happen in mozilla? Sounds like an old 4.x bug.

I can reproduce this problem using the Mac commercial seamonkey build 1999-12-17- 10-m12 build. I enabled IMAP logging in 5.0 and then viewed a 4.7 mail message that had an attached gif/jpeg file. I quit and viewed the logs which appears to be downloading the attachment twice. There's two separate stream of binary data. I will attach my IMAP log file

I can reproduce this problem on Win32 1999-12-17-13-m12 and Linux 1999-12-17-10-m12 commercial builds. On Mac, it downloaded the gif twice. On Win32 and Linux, it downloaded the gif file multiple times. This problem occurs on all platforms. Updating summary to remove "Unix only,".

I can't attach the win32 or linux imap log to this bug report. Their over 1MB in size and bugzilla won't allow me to post. I will email imap logs to mscott.

Peter, can you also post the logs to rocknroll (internal Netscape server)? This way, if the bug gets reassigned or something, we can still have access to the logs.

IMAP log files posted to my publish area on server jazz. http://jazz/users/pmock/publish/bug2731/ I also included the gif file I used. Please note that all I did to generate this log was: 1) Open Messenger 2) Log into my IMAP account 3) Select the IMAP message with the gif attachment. The image loads. 4) Quit Seamonkey

perf bug....

Is this similar to 22034 and, is this still happening now?

per mail triage, mark dup of more recent bug report, 22034 *** This bug has been marked as a duplicate of 22034 ***

Verify as a duplicate of bugzilla bug 22034