Bug 1991 - whitelist enhancement
Summary: whitelist enhancement
Status: RESOLVED WONTFIX
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other AIX
: P5 enhancement
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-29 12:04 UTC by Jack Gostl
Modified: 2004-11-30 12:17 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jack Gostl 2003-05-29 12:04:50 UTC 
I propose modifying whitelist, or perhaps creating a super whitelist, so that 
it BYPASSES spamassassin processing rather than simple adjusting the score. 
About the only downside I've had with SA is the amount of CPU it uses. Then I 
noticed that about half my email came from known sources. I am currently using 
procmail to do the bypass, but I think this is worth including in SA.

If I had my druthers, I'd do it right inside spamc. 

Thank you for your consideration.....
Comment 1 David Lohry 2004-08-15 21:31:39 UTC 
I tend to disagree and think that an absolute bypass should be done at the
server level with amavisd or something similar. Amavisd supports bypassing spam
checks.
Comment 2 Duncan Findlay 2004-11-30 21:08:06 UTC 
Simple short circuiting has been discussed in the past, and it seems like it
would be too much of a hack, even if limited to whitelist/blacklist stuff. Plus,
an external tool can implement this quite simply.

Marking WONTFIX.
Comment 3 Daniel Quinlan 2004-11-30 21:17:22 UTC 
Agreed this can be closed, not because we won't do short circuiting, but
because we will and it'll be generalized.