User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 I use several POP3 accounts and usually have the same stored messages at my workplace and at home. To do so, I usually leave all messages on the server and only delete them after they are in "both places". The problem is that I can't manage my stored messages on POP3 servers, the only option available for deleting messages is when they get stored in another folder or trashed. A relatively simple (?) way to solve this would be to have an option on the right-button click over the message to "delete this message from server" or even a sub-menu for server-side actions to take on the message. What would be really cool would be a small, simple UI to query the POP server and manage all the messages stored there, pretty much like TheBat's (another e-mail client). Reproducible: Always Steps to Reproduce: 1. 2. 3.
The context menu part is covered by bug 47297
Reporter, There is an option to "Delete messages on the server when they are deleted or moved from the inbox" in the Account Setting for POP accounts. As pointed out in the bug mentioned above for the context menu, it would be nice to do this on a message per message basis instead of as a default for deleting pop messages. I just tried the check box and it works for me. Messages I downloaded from system 1 and then deleted, did not download from the server when I did Get Msgs from system 2. Note: any msgs already downloaded on both systems will not be deleted on both systems just because you delete them on one system.
morphing summary to reflect the remaining part of this enhancement request: UI controlling pop server contents. Is there any useful "management" function other than deleting?
Summary: There's no way to manage messages stored in POP servers → create UI to manage messages on POP server directly
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.