Kris Deugau wrote: > > > Remove the current nameserver entries, and add "nameserver 127.0.0.1". > > Here's my "new" resolv.conf: # Generated by NetworkManager domain maine.rr.com search maine.rr.com # nameserver 209.18.47.61 # nameserver 209.18.47.62 nameserver 127.0.0.1 It works! The following test works! $ cat spam.mbox | spamassassin -dt >temp In other words, websiterepairguy.com is passing all the tests and is no longer generating false positives. The 'spam.mbox' email is the one that was causing false positives on the domain 'websiterepairguy.com'. It is no longer doing so. Is it really this simple? Ed Abbott -- View this message in context: http://old.nabble.com/False-Positive-on-Domain-Name-tp33975030p33982947.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
- Re: False Positive on Domain Name Benny Pedersen
- Re: False Positive on Domain Name Dave Funk
- Re: False Positive on Domain Name Kris Deugau
- Re: False Positive on Domain Name Ed Abbott
- Re: False Positive on Domain Name John Hardin
- Re: False Positive on Domain Name Benny Pedersen
- Re: False Positive on Domain Name Benny Pedersen
- Re: False Positive on Domain Name Ed Abbott
- Re: False Positive on Domain Name Kris Deugau
- Re: False Positive on Domain Name Ed Abbott
- Re: False Positive on Domain Name Ed Abbott
- Re: False Positive on Domain Name Benny Pedersen
- Re: False Positive on Domain Name Ed Abbott
- Re: False Positive on Domain Name Ed Abbott
- Re: False Positive on Domain Name Ed Abbott
- Re: False Positive on Domain Name Ed Abbott
- Re: False Positive on Domain Name Kris Deugau
- Re: False Positive on Domain Name Ed Abbott
- Re: False Positive on Domain Name Benny Pedersen
- Re: False Positive on Domain Name John Hardin
- Version control config files (was Re: False Po... David F. Skoll