karsten bräckelmann qmitxmehrudersportde thu 20080228 1028 0500 randy ramsdell wrote karsten bräckelmann wrote awl score averager sa seen sender httpwikiapacheorgspamassassinautowhitelist run sa see awl score getting closer 0 since score without awl constant awl score negative previous scores lower understand awl averaging seen must seen message ham awl know concept spam ham know required_score spam threshold merely knows previous scores would one salearn message spam multiple times didnt say awl keeps track seen messages opposed learned ones given initial score message learned automatically observe awl score sufficient said run message spamassassin require salearn note comment regarding intended demonstrate awl see mean imply regularly one time see awl behaves also please note awl fact keeps track pair sender ip address space imho kind explains confusing naming namely whitelist part useful legit senders send single spammy message awl rescue lower score drastically general spam hand really unlikely ever sent second time forged sender address origina ting network odds particular awl entry never ever used new incoming spam also means system wide approach improving spam effectiveness requires parse awl score salearning message determine need run would monumental task resource intensive see also please note bayes train using salearn awl entirely unrelated bayes tokenbased mechanism words message know concept email addresses let alone sender wouldnt better approach set awl max positive manually learn message spam way modify db correct previous awl hits message see never get spam forged come sender wont make difference also bayes awl unrelated besides stands automatic need correct anything ever need clear awl score usually learned average legit sender high using spambuttbuttin salearn see man spambuttbuttinrun 1 guenther 1 see another recent post justin char t10pse0r0dtu0ghnox4exc8x79xf4xabx51x8ax10xf4xf4xc4 main char hmhtxt2hcilxs0 i0i1tsh putchartshms0 fri 08 aug 2008 061803 0100 awl bayes_99 general questions