Robert Abatecola wrote: > Has anyone else noticed a hugs increase in the amount of spam lately? > In the last month or so the volume has more than doubled and a very > large portion of it gets through spamassassin 2.41.
At the very least, you should upgrade to 2.44 (or 2.45 if it ever existed)- there were a number of known holes in 2.4[0-3] that spammers took advantage of IIRC. There were no core functionality changes I'm aware of. Look into using the sets of custom rules a number of people have been discussing on this list, and look into more memory in your server to allow you to use them. :/ > I have been running spamassassin for almost two years. I have > resisted upgrading because of the changes in default behavior in > versions after 2.41. Exactly why I haven't upgraded on the filter server I maintain- just on a new server and on my own system. But I'm planning to upgrade that machine from 2.55->2.6x sometime in November (probably)- although I've been thinking that waiting for 2.61 might be a good idea. > How would I configure the latest version to act > like 2.41? I don't recall offhand what options are set by default in 2.4x, but my own setup includes the following config fragment: rewrite_subject 0 use_terse_report 1 #report_header 1 #defang_mime 0 skip_rbl_checks 1 report_safe 0 report_safe replaces defang_mime and report_header with a set of similar but different behaviours; setting it to 0 means that SA will not alter the message body; just add the X-Spam-whatever headers- as 2.3x did IIRC, and 2.4x did with defang_mime 0 IIRC. There is no way to have the spam report *in* the message body as was briefly attempted in 2.(4?)x. report_safe 1 will take any message considered to be spam, and attach it to a new message. report_safe 2 will do the same, but set the content-type of the attachment to text/plain to attempt to defuse and HTMLish nasties that may be in the spam. There is NO method I know of to provide the same behaviour as defame_mime 1 in >= 2.5x. If you're calling SA as a Perl library from something like MIMEDefang, most of this means little or nothing, as SA is just a set of processing routines that don't have the opportunity to actually modify the message- anything you're doing now should be OK. <g> > I'd like to upgrade and then switch to the new behavior > in a few weeks. Difficult. Better to install the current release on a test box; read the documentation and pick out the options that most closely match your preferred/current behaviour, and make *very* careful note of any potential oddities or pitfalls. Play with it for a while, divert your personal email account through it and see how it works on "real" email. In two to three weeks rip it out, replace it with the old version, then see how much trouble you have switching back to the new release. <g> That will give you some idea of how many things will break (and they will; 2.44->2.5x was decent but still a little flaky on the filter server I maintain- and would have been FAR worse had I not spent a number of weeks watching 2.5x develop). The biggest difference in the rulesets is the change from the "spam phrases" rules in <= 2.4x, to the Bayesian database system in 2.5x and 2.60. -kgd -- <erno> hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
