On 15/10/2011 5:56 PM, Benny Pedersen wrote:
On Sat, 15 Oct 2011 16:40:48 -0700, Paul Cabot wrote:
blacklist_from *@aol.com
whitelist_from_spf good-us...@aol.com
users can then get a new url for free :-)
Would that not blacklist everyone from aol.com unless I specifically
allowed them with the whitelist_from_spf setting?
currect
if it was url, it would be easy to whitelist non spam urls that does
not have any other url that is not known, basicly spammers get 100000
new free domains, and spam you random from aol.com, no ?
thats why i sugest blacklist_from aol.com and whitelist non spammers
on aol, then the spam urls is not important anymore
good rules comes from strong thinking on how spammers thinks or not
think at all
bad rule is if spammers just put in one single whitelisted url to get
it scored as ham msgs, i maked my local url blacklist but got tired of
mainained it, and changed to fokus on sender domain instad :)
the random chars is to make bayes training it, but if you lower bayes
ham autolearn threashold level and make more manuel training then
spammers loose bayes poising
i also update ip2cc db myself now since the current does not contain
my own ip, if there is intrest to get the geoip license fixed to be
free included in spamassassin go for it, i stick to ip2cc for now
I'm not really a fan of blacklisting an entire domain. If it is a
domain that for sure is 100% spam or close to it then sure. But for
domains like yahoo or hotmail or even aol. There are legitimate
accounts on them. So unless someone gives me their email address
before sending me an email. I may never know they sent me an email.
Unless I spend time going over my logs.
The random chars I sort of realized had something to do with a way of
trying to mess up a program like spamassassin. Funny thing about them
is everyone knows that an email with random chars is almost certaintly
going to be 100% spam. I have downloaded the chickenpox rules. But
they don't seem to be hitting on the emails I'm getting.
