GNOME Bugzilla – Bug 501476
move junk out of IMAP inbox option
Last modified: 2012-02-09 11:27:04 UTC
Having switched from Thunderbird due to the PIM functionality in Evolution, I miss having my junk sorted for me. Evolution doesn't seem to actually have a junk folder, which would be real handy for people who sometimes need to use webmail to access the same IMAP account.
evolution has a junk folder. you have to enable the plugin, though.
I have enabled the spamassassin plugin and have spamassassin installed. This bug was filed in some haste, but I now have time to elaborate on why this is a bug. When I say "junk folder" I mean an mbox directory that the junk is moved to. I know that Evolution has "clever" pseudo-folders, but this is not what I want - I want the option to use more bandwidth and more effort to actually perform IMAP move operations to get the e-mails out of the .mail file on the server. I have several times now opened evolution to find a bunch of spam in my inbox, and I'm sure this isn't an uncommon issue. I'm confident enough of the way IMAP inboxes work, where messages aren't actually deleted, but are just marked as deleted. This is not exactly evolution's fault as far as I can see, but I just get the feeling that this isn't the case for Thunderbird, and that must mean it is being less lazy and assuming things about the state of the IMAP account. I also think Evolution knows this because attempting to read mail marked for deletion (or perhaps just after it has run some sanity checks, which may be slow on my connection) I think causes the mail to be marked with a strikethrough. I wouldn't want to force this change in behaviour on the average user - I'm not well-versed in GNOME HIG, but I personally don't think adding an "Advanced Settings" area for a feature like this is a bad idea when you want to cater to everyone. At any rate, if you have understood my rationale and think this isn't a problem with Evolution but merely my problem for using several e-mail clients, or just a server misconfiguration, feel free to mark it as INVALID or something. An explanation of why it would be too difficult to fix satisfiably (because I personally don't have the time) would be a bonus.
This bolis down to bug 206061. *** This bug has been marked as a duplicate of bug 206061 ***