Re: New versions of Perl are slower

On Wed, Apr 11, 2012 at 3:03 PM, Lee Dilkie wrote: > On 4/11/2012 8:23 PM, Julian Yap wrote: > > On Tue, Apr 10, 2012 at 4:57 PM, Lee Dilkie wrote: > > On 4/10/2012 10:50 PM, Julian Yap wrote: > > Hmm, thanks for the info. It certainly explains things. Yeah, SpamAssassin > previously used to blaz

Re: New versions of Perl are slower

On 4/11/2012 8:23 PM, Julian Yap wrote: > On Tue, Apr 10, 2012 at 4:57 PM, Lee Dilkie wrote: >> On 4/10/2012 10:50 PM, Julian Yap wrote: >> >> Hmm, thanks for the info. It certainly explains things. Yeah, SpamAssassin >> previously used to blaze through mail scans (everything scanned in less tha

Re: Spam from Moniker Privacy Services.

On 30-03-2012 16:08, Frank Chan wrote: On 30-03-2012 10:11, Robert Schetterer wrote: Am 30.03.2012 17:44, schrieb Richard Doyle: On 03/29/2012 05:10 PM, Frank Chan wrote: On 02-03-2012 15:49, Frank Chan wrote: Here are some samples of this spam in pastebin: http://pastebin.com/djidF7dg http:

Re: New versions of Perl are slower

On Tue, Apr 10, 2012 at 4:57 PM, Lee Dilkie wrote: > On 4/10/2012 10:50 PM, Julian Yap wrote: > > Hmm, thanks for the info. It certainly explains things. Yeah, SpamAssassin > previously used to blaze through mail scans (everything scanned in less than > 3 seconds) on the same hardware. It's annoyi

Re: Mail::SpamAssassin::Plugin::SpamCop

On 04/12/2012 12:58 AM, Benny Pedersen wrote: > Den 2012-04-11 15:37, Simon Loewenthal skrev: > >> Partially answered. >> # spamassassin --lint >> Apr 11 15:35:06.700 [24545] warn: config: failed to parse line, >> skipping, in "/etc/spamassassin/local.cf": auto_report_threshold 30 >> Was it replace

Re: Mail::SpamAssassin::Plugin::SpamCop

Den 2012-04-11 15:37, Simon Loewenthal skrev: Partially answered. # spamassassin --lint Apr 11 15:35:06.700 [24545] warn: config: failed to parse line, skipping, in "/etc/spamassassin/local.cf": auto_report_threshold 30 Was it replaced by something else, or simply superceded? is spamcop plugin

Re: new / tests to verify

Den 2012-04-10 22:31, McGranahan, Jamen skrev: box and updated it, but would like to test it to verify it is working correctly. Is this possible? test shows here you post html, please disable that atleast on public maillists, most email software can do this pr sender today, but to your quest

Re: New versions of Perl are slower

On 4/11/12 3:09 PM, Julian Yap wrote: Hey Michael, I noticed that in Perl 5.8, PERL_MALLOC is on by default and on 5.10 onwards it is off by default. I have been building with the old option of PERL_MALLOC being on since I've been upgrading from old versions. Do you know if that makes any perf

Re: New versions of Perl are slower

On Tue, Apr 10, 2012 at 8:09 PM, xTrade Assessory wrote: > Julian Yap wrote: >> I'm running SpamAssassin 3.3.2 port revision 6 (latest from FreeBSD >> ports) on FreeBSD 8.2-RELEASE 64-bit. >> >> I recently upgraded my Perl from 5.10 to 5.14 but I needed to >> downgrade because SpamAssassin was cra

Re: spamc/spamd SSL issues

On 4/10/2012 5:43 PM, Trey Nolen wrote: I'm using a combination of Ubuntu and Debian servers for scanning email with spamc/spamd. I'm running the following version: spamd -V SpamAssassin Server version 3.3.1 running on Perl 5.10.1 with SSL support (IO::Socket::SSL 1.33) with zlib suppor

Re: Mail::SpamAssassin::Plugin::SpamCop

On 11/04/12 15:30, Simon Loewenthal wrote: > Hi, > > Are these options still valid for > Mail::SpamAssassin::Plugin::SpamCop settings in the local.cf > http://spamassassin.apache.org/full/3.3.x/doc/Mail_SpamAssassin_Plugin_SpamCop.html > > (from spamcop.net http://spamcop.net/fom-serve/cache/33

Mail::SpamAssassin::Plugin::SpamCop

Hi, Are these options still valid for Mail::SpamAssassin::Plugin::SpamCop settings in the local.cf http://spamassassin.apache.org/full/3.3.x/doc/Mail_SpamAssassin_Plugin_SpamCop.html (from spamcop.net http://spamcop.net/fom-serve/cache/331.html ). *It is recommended the default settings in Sp

Re: New versions of Perl are slower

ps, if you can get them to package 3.4, I can push a p5-Mail-SpamAssassin-devel out. visit here and ping them: That's really not necessary. I know about the issue just haven't figured out how in Jenkins to get it to do the build.