GNOME Bugzilla – Bug 205638
Delete locally -> Delete in the server
Last modified: 2002-02-03 22:03:15 UTC
If I delete a email locally, I want to also delete it in the server (I use by default the option "Don't delete messages from server".
not gonna happen anytime soon. in fact, I don't even see the logic in this feature.
The logic is "I want POP to behave like IMAP". This doesn't work at all with the way Evolution works though. (The POP provider has no idea what happens to the messages once they leave the pop server.) So it would have to involve all sorts of icky kludges. This is probably a WONTFIX.
*** bug 205767 has been marked as a duplicate of this bug. ***
*** bug 206932 has been marked as a duplicate of this bug. ***
Please don't dismiss this option outright. It is a valuable option for those of us who don't have the luxury of using IMAP. My ISP simply won't provide IMAP...
How *exactly* is this implemented in other mailers that do it? Or can you say what mailer's behavior you want us to copy here? If you move a message from Inbox to another folder (manually or via a filter rule), does that count as deleting it locally? If you download the message to both your desktop machine and your notebook, and then delete it locally on one but not the other, should it be deleted from the server or not? If your Inbox is shared with another mail program, and you delete the message from that program instead of Evolution, is Evolution supposed to notice? (I'm not trying to be argumentative, I'm just saying, there are a bunch of weird issues involved with trying to implement this feature given the other features already in Evolution.)
The option should work like the one present in Mozilla Mail. I have done some experiments with mozilla to give you a better idea: 1) As soon as one of the clients decides that the mail message should be removed from the server, it is removed from the server. No attempt should be made to sync the various clients. 2) As soon as one of the clients moves the email message out of the inbox the message is removed from the server. These two rules should solve the majority of cases that cause conflict. This is a minimalist aproach to the problem, but hey, it is pop after all. I hope this helps.
oh and one more thing I didn't mention... The delete_from_server action should only happen the next time the pop server is accessed from the client... (meaning no real-time or semi-real-time notification or actions should happen when rule 1 or 2 [from my previous message] is applied.) Therefore, the next time the pop server is connected to, the action should be applied... weither that be the automated "check every x minutes" or explitly executed by the user with the "send/receive" button. This is how I understand it is done in Mozilla Mailer. Thanks
I'll tell you why this is a very very nice feature. I use multiple machines to download email from various POP accounts (laptop, desktop, etc). I want to receive most of it on both machines, so I set my accounts to "leave messages on server". However, all the crap (spam, etc) I really don't want to download multiple places. In Outlook (as in Evo) delete moves it to the trash folder. Shift+Delete in Outlook delete kills immediately (no trash folder), and anything removed from the trash folder (or Shift+Delete) gets removed from the server. Thus not only do I save disk space on the server, but I only have to weed out the spam once since it gets removed from the server. This is a very, very useful little feature and one of the key missing items in my evaluation of Evo versus Outlook.
*** bug 219640 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 201824 ***