I seem to be catching a lot more SPAM, but no matter what I try, it seems Bayes isn't getting utilized. I have ~700 SPAMS and 2400 HAMS. When I run "spamassassin -D --lint" (as the same user Postfix is running spamc as), it comes back with a report that seems to utilize Bayes, but when normal e-mail flows through, I don't see any indication of Bayes in the headers. Also, when I run "sa-learn --dump magic" (as user spamd), I can see that nspam and nham are correct. I've also tried setting bayes_path, but still no Bayes in the headers. Any idea what could be wrong? Here is a most recent header:
http://pastebin.com/J6TbrVG8 (had to use pastebin as the mailing list was rejecting me!) Thanks, Nick -----Original Message----- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Saturday, October 04, 2014 12:47 PM To: users@spamassassin.apache.org Subject: Re: spamassassin working very poorly Am 04.10.2014 um 18:36 schrieb andybalholm: > On Oct 4, 2014, at 4:39 AM, Benny Pedersen-2 wrote: > > > So anti spammer would now stop reading here ? :) > > No, but I sometimes wonder if it’s wise to post my anti-spam ideas here, > since that makes it easier for spammers to work around them a valid point on the other if you post your ideas as well as get the ideas from others and people implement the combination of all the ideas well at the end it makes spammers life harder and i still did not give up the idea that sooner or later spam dies because it may become no longer a business case frankly i *every* MX out there would implement Postscreen or something else let any new IP wait 10 seconds before answer with REJECT for whatever reason and even if the cient is on the 7-days-whitelist for this test wait 2 seconds before try to receive data i doubt that it would be a business case simple mathematics how much mail you in theory can deliver in a timeframe while completly ignore filters at that calculation that combind with every ISP close outgoing port 25 for endusers and force them to use 587 with smtp-out as well as start every endusers PTR with "dynamic-" until one said "i run a mailserver here and need 25 opened as well as PTR xyz" and spam would be dead from one day to the next leaving only hacked real accounts which can be fixed with abuse mails and blacklist straight away everybody bouncing on postmaster/abuse there are enough weapons to let spam die completly if every mailadmin and every tech people on ISP sides takes 30 minutes for brainstorming how to solve the problem and starts to act
