linusanderas
Verified User
- Joined
- Nov 8, 2008
- Messages
- 9
I get som problem when the whitelist get to big.
How should i do to prevent the server to populate the list?
How should i do to prevent the server to populate the list?
Prevent server to populate Whitelist
- Thread starter linusanderas
- Start date
nobaloney
NoBaloney Internet Svcs - In Memoriam †
Which whitelist file? What's the name of the file?
Jeff
Jeff
linusanderas
Verified User
- Joined
- Nov 8, 2008
- Messages
- 9
.spamassassin/auto-whitelist
nobaloney
NoBaloney Internet Svcs - In Memoriam †
I'm not familiar with SpamAssassin, as i use SpamBlocker (which I wrote) as my first line of defense.
It's probably populated by a rule you can either change or delete. Perhaps someone else will respond.
Jeff
It's probably populated by a rule you can either change or delete. Perhaps someone else will respond.
Jeff
OliverScott
Verified User
- Joined
- May 4, 2007
- Messages
- 57
The SpamAssassin AWL (auto white list) isn't a whitelist as such...
It keeps a record of the spamassassin score of an email from a particular email address and the IP address it came from. If you receive a second email from the same email address which was sent through the same mail server IP address, spamassassin works out its score for this email as normal and then increases or decreases it a bit to make it nearer to the historical average of the emails from this sender.
Though this doesn't do a lot to help catch spam, it does stop some false positives. Assuming that someone has been sending you genuine emails in the past, and then happens to send you an email which unfortunately looks to be spam (possibly discussing an online canadian pharmacy they have used!), this emails score is dragged down by the low previous average for this sender so that it is not tagged as spam.
The AWL can be used to help delete spam however by the use of a plugin called SAGREY (available from the spamassassin wiki). This looks for emails which are scored highly enough to be considered spam and then if they are not from someone in the AWL (ie they haven't sent to you in the past) it adds a bit to their score. This means that this email is more likely to be pushed over the treshold where directadmin deletes it rather than passing it through with a spam tag added to the subject. Obviously if the email comes from a genuine person and they contact you again (possibly to ask why you didn't reply to their previous email), they will then be in the AWL so their email won't be additionally penalised in this way. Personally I use sagrey to add 1 point to emails which look like spam and are from new senders and this does help to block a few spam from reaching my inbox, and has never caused any issues that I am aware of.
I don't think there is an automatic method for trimming out old data from the AWL database file (unlike bayes), however it is perfectly safe to just delete it. When an email is next processed the file will be recreated and will start to grow again.
If you don't want to use this feature you can dissable it by adding the following line to your spamassassin local.cf file (probably found in /etc/mail/spamassassin/) and then restarting spamassassin/exim:
use_auto_whitelist 0
It keeps a record of the spamassassin score of an email from a particular email address and the IP address it came from. If you receive a second email from the same email address which was sent through the same mail server IP address, spamassassin works out its score for this email as normal and then increases or decreases it a bit to make it nearer to the historical average of the emails from this sender.
Though this doesn't do a lot to help catch spam, it does stop some false positives. Assuming that someone has been sending you genuine emails in the past, and then happens to send you an email which unfortunately looks to be spam (possibly discussing an online canadian pharmacy they have used!), this emails score is dragged down by the low previous average for this sender so that it is not tagged as spam.
The AWL can be used to help delete spam however by the use of a plugin called SAGREY (available from the spamassassin wiki). This looks for emails which are scored highly enough to be considered spam and then if they are not from someone in the AWL (ie they haven't sent to you in the past) it adds a bit to their score. This means that this email is more likely to be pushed over the treshold where directadmin deletes it rather than passing it through with a spam tag added to the subject. Obviously if the email comes from a genuine person and they contact you again (possibly to ask why you didn't reply to their previous email), they will then be in the AWL so their email won't be additionally penalised in this way. Personally I use sagrey to add 1 point to emails which look like spam and are from new senders and this does help to block a few spam from reaching my inbox, and has never caused any issues that I am aware of.
I don't think there is an automatic method for trimming out old data from the AWL database file (unlike bayes), however it is perfectly safe to just delete it. When an email is next processed the file will be recreated and will start to grow again.
If you don't want to use this feature you can dissable it by adding the following line to your spamassassin local.cf file (probably found in /etc/mail/spamassassin/) and then restarting spamassassin/exim:
use_auto_whitelist 0
nobaloney
NoBaloney Internet Svcs - In Memoriam †
For what whitelist for what system filter? And why are you making a first post to a three-year-old thread without referring to anything? I don't read entire threads over again to see if there's a question to answer; please be more specific.
Jeff
Jeff