would it help if build new dbs?
and use those to check if the debug will see the toks?
would that affect the sa learning process somehow?


>
>> sa-learn --dbpath /var/spamdb/bayes --dump magic
>
> i get this:
>
> 0.000          0          3          0  non-token data: bayes db version
> 0.000          0       2852          0  non-token data: nspam
> 0.000          0       2515          0  non-token data: nham
> 0.000          0     116330          0  non-token data: ntokens
> 0.000          0 1104894403          0  non-token data: oldest atime
> 0.000          0 1105570140          0  non-token data: newest atime
> 0.000          0          0          0  non-token data: last journal sync
> atime
> 0.000          0 1105571295          0  non-token data: last expiry atime
> 0.000          0     581418          0  non-token data: last expire atime
> delta
> 0.000          0      46098          0  non-token data: last expire
> reduction count
>
>> what are the file sizes?  are the files writable/readable by the
>> appropriate users?
>
> -rw-r-----   1 root  vchkpw   688128 Jan 12 18:08 bayes_seen
> -rw-r-----   1 root  vchkpw  2146304 Jan 12 18:08 bayes_toks
>
>
>> debug: URIDNSBL: domain "svbrseprs.com" listed (URIBL_SBL):
>> "http://www.spamhaus.org/SBL/sbl.lasso?query=SBL9959";
>> debug: URIDNSBL: query for svbrseprs.com took 3 seconds to look up
>> (sbl.spamhaus.org.:2.208.178.207)
>> debug: URIDNSBL: domain "svbrseprs.com" listed (URIBL_SBL):
>> "http://www.spamhaus.org/SBL/sbl.lasso?query=SBL21893";
>> debug: URIDNSBL: domain "svbrseprs.com" listed (URIBL_SBL):
>> "http://www.spamhaus.org/SBL/sbl.lasso?query=SBL13495";
>> debug: URIDNSBL: query for svbrseprs.com took 3 seconds to look up
>> (sbl.spamhaus.org.:2.199.36.69)
>
> non of that in the debug...
>
> i tried a few other undetected spam messages. same result. all of them
> have uris in them like:
> http://xgnuk.arms2nemesis.com/?TTlsSwFFf0pW6GC
> http://uyg.rxpharmagroup.com/track.asp?c=gi&cg=gi
> or have attachments....
>
>
> thanks...
>
>>
>>
>>
>
>
> --
>
>


-- 


Reply via email to