Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20091121 Thunderbird/3.0 (tb3rc1build3) STR 1 first time ever mark a mail as junk manually (default settings still on) 2 due to some other bug, only this will trigger the first automatic junk detection Actual result - an IMO perfectly non-suspicious mail msg that I had bcc'ed to myself got marked junk automatically (I'll forward that mail to Ludo for examination) Expected result - never mark msgs from myself (known identities) as junk automatically (automatical whitelisting of own identities in from) - alternatively, at least reduce spam probability drastically for those msgs (so that they only get junked when the other content is clearly rubbish, so maybe someone else misused my from header) We'd have to exame what this proposal does for msgs that are spams but someone misused my from header.
Tb has already next option. > Account Settings/Junk Settings > [ X ] Do not mark mail as junk if the sender is in: xxx > (where xxx is Personal Address Book or Collected Addresses) You can avoid "junk from yourself" by putting your mail address in the address book you selected at the option setting. By the way, many spammers set your mail address(held in identity setting) in From: header. So oppositte request like next exists. Don't mark as non-junk even if From: is placed in the address book, if mail is sent from spammer. But how can we know sender is spammer by mail header/mail data only?
I think we explicitly changed this behaviour from TB 2 so that spam emails wouldn't avoid the spam filter. Kent might remember more...
By default, we will still analyze messages for junk even if your address exists in the address book, unlike in TB2 where that would whitelist the email. You can override this behavior (which will then whitelist mail from you if your name is in your address book) by setting this preference to false: mail.server.default.inhibitWhiteListingIdentityUser Since many spammers now spoof incoming messages as "from You" specifically looking for the behavior requested in this bug, this was necessary. In principle this could be selectively enabled/disabled on a per-server basis, but there is no UI for that either. I would be tempted to mark this bug WONTFIX by the way because of the spoofing problem.
(In reply to comment #3) > I would be tempted to mark this bug WONTFIX by the way because of the spoofing > problem. Bug 486420 implemented mail.server.default.inhibitWhiteListingIdentityUser and by extension (in addition to comment 3) makes this is invalid, if not wontfix. Bug 482617 is the place for adding the UI
You need to log in before you can comment on or make changes to this bug.