Closed
Bug 660919
Opened 15 years ago
Closed 1 month ago
Address book whitelist does not override spamassassin rating - Emails of trusted senders in personal address book marked as spam when rated by spamassassin
Categories
(MailNews Core :: Account Manager, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: prof, Unassigned)
References
Details
When selecting to not treat messages from users who are in the personal addressbook as junk/spam, emails marked by spam-assassin are nevertheless handled as spam if one decides to trust spam-assassin in the corresponding checkbox.
Setting/steps to reproduce:
Mail&Newsgroup Account-Settings => Account => Junk settings:
[x] Enable adaptive junk mail controls for this account
Do not mark mail as junk if the sender is in:
[x] Personal Address Book
[x] Trust junk mail headers set by: [SpamAssassin]
Put the sender-address into your Personal Address-Book.
Wait for an email which is being classified as spam by spam-assassin. (the user reporting this issue was experiencing this for EVERY email of an AOL-user from whom he was receiving emails)
Expected result: Sender is trusted due to personal Addressbook and settings above and email not treated as junk.
Actual result: Email is being treated as Junk.
Disabling the Spam-Assassin checkbox instantly resolves the problem, so this is not an issue of the internal spam-detection but with the treatment of marked emails. (Therefore might also affect the SpamPal setting instead of SpamAssassin)
User testet with Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.19)
Gecko/20110420 Mnenhy/0.8.3 SeaMonkey/2.0.14
I'm not the position to reproduce this bug due to the lack of a corresponding Email-Account known to have Spam-Assassin and a "verified junk sender" (in terms of spam assassin's classification), just reporting this issue due to the language barrier for the original user experiencing this problem.
Updated•14 years ago
|
Component: MailNews: Backend → Backend
Product: SeaMonkey → MailNews Core
QA Contact: mailnews-backend → backend
Version: SeaMonkey 2.0 Branch → 1.9.1 Branch
Comment 1•10 years ago
|
||
I haven't tested to make sure this is true, but I suspect whitelist was never intended to apply to spamassassin. If nothing else, because spamassassin has it's own whitelist capability.
Perhaps the panel arrangement needs to be rethought?
Component: Backend → Account Manager
Flags: needinfo?(acelists)
Summary: Emails of trusted senders saved in the personal addressbook are treated as spam when marked by spam-assassin even when option is checked to not treat them as such → Emails of trusted senders saved in the personal addressbook are treated as spam when marked by spamassassin even when option is checked to not treat them as such
This seems to me to be a dupe of bug 678960.
I think the panel arrangement is correct and shows the current state of the feature. Whitelist by AB is a subfeature of "adaptive junk mail controls" (inside TB) and does not relate to spamassasin (or any other server filter).
If somebody implements the feature, the panel needs to be updated too.
Flags: needinfo?(acelists)
Yeah, seems to be the same issue and that bug ignored this one here.
Although in the other bug he reported that a SpamAssasin-setting to "none" failed to get his emails get through, if I understood that correctly? That would be something else then...
Even with the indentation of that option (which Seamonkey does not have btw. and it's in the same box), I cannot see why a clearly set "trust my addressbook" is outruled by another option, even if not directly related.
Updated•3 years ago
|
Severity: normal → S3
Updated•1 month ago
|
Summary: Emails of trusted senders saved in the personal addressbook are treated as spam when marked by spamassassin even when option is checked to not treat them as such → Address book whitelist does not override spamassassin rating - Emails of trusted senders in personal address book marked as spam when rated by spamassassin
Current layout in TB indicates seeration between the address book feature and the spam assassin setting. So Mailnews Core will never change this in Seamonkey.
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•