Bad mail processing / handling



15 years ago
10 years ago


(Reporter: lordbyron, Assigned: sspitzer)


Windows 2000

Firefox Tracking Flags

(Not tracked)




15 years ago
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113

Not sure if this happens in other mail protocals but with my imap account when
you delete or move a mail message it does not move it on the server and seems to
continue to keep it in memory until you exit all of Mozilla. Once you exit
Mozilla and then look at the server it will have moved all messages, deleted the
messages that you deleted during your session. 

I think mozilla is storing the events in memory and then executing them on the
server when you exit because as these events continue over a day the memory foot
print often gets to over 100M in ram. It is not unusual for me to after 6 to 8
hours have 100-200M of ram dedicated to Mozilla. 

Reproducible: Always
Steps to Reproduce:
1. Set up an Imap account
2. Move a message from the Inbox to a local folder
3. watch memory increase
4. look at the server... message has not been updated
5. close mozilla 
6. check server see message is no longer there now...

I am marking this as critical because it has caused me many problems with system
crashes and software issues


15 years ago
Component: LDAP Mail/News Integration → Networking: IMAP
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.