Closed Bug 264223 Opened 20 years ago Closed 19 years ago

XP Does NOT delete POP mail from server inbox at end of receiving mail, works fine for Win98.

Categories

(MailNews Core :: Networking: POP, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: calefra, Assigned: sspitzer)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.2) Gecko/20040803
Build Identifier: Mozilla/5.0 (Windows; U; WinXP; en-US; rv:1.7.2) Gecko/20040803

At completion of session when reading NEW e-mail, Mozilla 1.7.2 using WinXP
fails to send server notice to delete e-mails from Inbox.  This works fine
(however) when using Win98.  Next time session is started, it picks up where it
left off with NEW e-mails.  ADDED NOTE: I have Win98 running Mozilla 1.7.2,
Mother-in-law has WinXP running Mozilla 1.7.2.  She is NOT PC literate so I am
sending bug notice for her.

Reproducible: Couldn't Reproduce
Steps to Reproduce:
1.
2.
3.



Expected Results:  
Notify server when session is complete and to delete POP mail from Inbox.
Sounds like "leave messages on server" is enabled, make sure that it is unchecked.
Product: MailNews → Core
I'm getting this too in 1.8a6. When I use "File -> Empty Trash", my deleted
emails disappear from Mozilla, but they stay on the server. They don't get
deleted when I log out, either. Empty Trash on Exit has no effect, either. Is
there a way to trace POP transactions?
(In reply to comment #2)
Comment #3 was for other bug, although the link is usefull for every one.
Sorry for spam.

> Is there a way to trace POP transactions?
See http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#pop for
protocol log.
(See also Bug 227981 if Mac OS X. Command line way is required when Mac OS X.)
Do not forget to change "protocol:5" to "POP3:5" when POP3.
Please note that log file is overlayed on restart.
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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.