CTYPE_NULL false-positive for Content-Type: multipart/related ?

2011-09-08 Thread Edward Prendergast

Hi,

I'm seeing CTYPE_NULL triggering for certain messages from gmail.

If I compare a message that doesn't trigger CTYPE_NULL:

Content-Type: multipart/related;

With one that does:

Content-Type: multipart/related;

I'm thinking it looks like a false positive rather than a legitimate hit?

This is on SpamAssassin 3.3.1.

Thanks,
Edward



The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.




Re: CTYPE_NULL false-positive for Content-Type: multipart/related ?

2011-09-08 Thread Edward Prendergast

On 08/09/11 16:23, John Hardin wrote:

On Thu, 8 Sep 2011, Edward Prendergast wrote:


I'm seeing CTYPE_NULL triggering for certain messages from gmail.

If I compare a message that doesn't trigger CTYPE_NULL:

Content-Type: multipart/related;

With one that does:

Content-Type: multipart/related;


CTYPE_NULL certainly shouldn't fire on either of those. Are they 
really identical, or is that a cut-and-paste error? Are those complete 
copies of ALL of the Content-Type headers in the message?


Would it be possible to post the full FP message to a pastebin? Given 
what we're looking at, anonymization of email addresses, host names 
and body content shouldn't affect the analysis, just make sure you 
don't alter any of the MIME-related headers.




Sorry, that WAS a typo, I meant to show a more standard content-type 
from a message not triggering CTYPE_NULL:


Content-Type: multipart/mixed;

It's quite heavily redacted, but haven't made any changes to the MIME 
header stuff.


https://gist.github.com/1203746

Thanks


The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.




Re: Supporting 3.3 and 3.2?

2011-03-04 Thread Edward Prendergast

 On 04/03/11 16:10, Dennis German wrote:

On 3/3/11 10:09 PM, Karsten Bräckelmann wrote:

On Fri, 2011-03-04 at 03:36 +0100, Karsten Bräckelmann wrote:

On Thu, 2011-03-03 at 15:52 -1000, Warren Togami Jr. wrote:

Could we please make an official project statement that 3.2.x is
unsupported and people should really update to 3.3.x?

That said, personally, with various Open Source projects, I have never
given up support for old versions. As long as I *can* help people, I
will.
Besides, in this particular case, the *real* underlying issue of a 
badly

trained Bayes won't get fixed by updating. Yes, the overall score would
change drastically, as shown, but the training has been rather poor and
won't change over night by updating.

I would surely use a more recent version of SA if I could.
My hosting service uses CPanel and Centos and I cannot convince them 
to upgrade.




If you're using cPanel I think you should be able to upgrade to the 
latest version with /scripts /perlinstaller Mail::SpamAssassin - but 
proceed with caution, such a big upgrade could have a host of issues 
with dependencies.



The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.




[SOLVED] Re: (no report template found) - no 10_misc.cf but sa-update shows correct paths

2010-09-29 Thread Edward Prendergast

 On 28/09/2010 12:45, Karsten Bräckelmann wrote:

On Tue, 2010-09-28 at 10:36 +0100, Edward Prendergast wrote:

clear_report_template - I don't have this set in any of my configs

It's part of 10_default_prefs.cf of the stock rule-set.



To get the no template found error I'm running:
spamassassin -C /etc/opt/mail/spamassassin/ -t  /path/to/message

^^
Why are you using that option? The given path looks like your site
config dir, not the default rule-set dir. The latter, which is what -C
sets, also is the dir where sa-update puts the rules.

See 'man spamassassin-run'. Also see 'man spamassassin' for the dirs
used by default on your site, as set during configure.



Not sure if it's OK to paste debug output here (20k) - if so (and it's
wanted) please let me know and I'll include it/

It is OK -- or use a pastebin, if you prefer.




 Right you are - thanks! I should have been using the --siteconfigpath= 
switch for a more accurate test.


Thanks


The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.




(no report template found) - no 10_misc.cf but sa-update shows correct paths

2010-09-28 Thread Edward Prendergast

 Hi,

I'm seeing (no report template found) on:

SpamAssassin version 3.3.2-r929478
  running on Perl version 5.12.2
This is a build of perl installed in /opt/perl5.
Took SpamAssassin from the SVN repo to get around the taint issue as 
this doesn't seem to have made it onto CPAN yet 
(https://svn.apache.org/repos/asf/spamassassin/branches/3.3/


The docs I've seen from googling all seem to point to:

clear_report_template - I don't have this set in any of my configs
Failure to access 10_misc.cf - I don't have this on my system, but it 
also doesn't seem to exist on other systems which are working?


To get the no template found error I'm running:
spamassassin -C /etc/opt/mail/spamassassin/ -t  /path/to/message

Not sure if it's OK to paste debug output here (20k) - if so (and it's 
wanted) please let me know and I'll include it/


Any pointers in the right direction would be much appreciated!

Thanks,
Edward




The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.




Re: SpamAssassin cpan install @INC lib issue on CentOS 5.4

2009-12-04 Thread Edward Prendergast

Kris Deugau wrote:

(Please keep the discussion on-list.)


Sorry about that - just hit 'reply' without checking where the message 
was actually going.




Edward Prendergast wrote:

Kris Deugau wrote:

Edward Prendergast wrote:

@@INSTALLSITELIB@@ /opt/perl5/lib/5.10.1/x86_64-linux

  ^^
This looks a little fishy...


I agree, I'm not sure where it's coming from.


FWIW, nothing like that showed up in my brief test - missing 
substitutions like that are usually a sign of a build gone wrong from 
early on.


That's a good question, but my qualms are mainly down wanting to 
perhaps use local::lib and have up to date CPAN modules as it seems 
to take a long time for these to filter down via redhat.


Mmm.  I use the RPMForge repo for more up-to-date Perl modules, but 
I've yet to run into any problems using the nominally outdated ones 
filtering down from RedHat/CentOS.  Net::DNS is the only module I can 
think of where there are/were known issues (at least with respect to 
SA's usage) in the stock version.


My motivations aren't purely SpamAssassin related - there are other 
programs that want current Perl modules (MailScanner) and I wanted to 
get SpamAssassin along side these.





This is based around what I've seen from local::lib:

http://search.cpan.org/~apeiron/local-lib-1.004009/lib/local/lib.pm#SYNOPSIS 



Ah, hm.  I think you should be fine just setting your path to call 
your custom Perl ahead of the system Perl;  that looks to be targetted 
at cherrypicking module updates alongside the packaged system Perl.


Right you are! When I change my .bashrc to this:

#export MODULEBUILDRC=/opt/perl5/.modulebuildrc
#export PERL_MM_OPT=INSTALL_BASE=/opt/perl5
#export 
PERL5LIB=/opt/perl5/lib/perl5:/opt/perl5/lib/perl5/x86_64-linux:/opt/perl5/lib/5.10.1:/opt/perl5/lib/site_perl/5.10.1

export PATH=/opt/perl5/bin:$PATH

SpamAssassin now installs OK.



 Essentially when I use perl from the command
line (and install other modules from CPAN) everything seems to be OK, 
issues only appear to be arising with Mail::SpamAssassin.


Yeah, that's the weird bit.  You might try installing SA from the 
tarball instead of CPAN - I had some odd errors come up when I tried 
via CPAN, but I have a feeling some of that had to do with doing the 
whole test as non-root.


Still unsure where that @@INSTALLSITELIB@@ stuff was coming from but it 
certainly looks like the issue is now resolved. Many thanks for all your 
help.


-Edward


The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.




SpamAssassin cpan install @INC lib issue on CentOS 5.4

2009-12-03 Thread Edward Prendergast

Hi,

I'm getting errors when I trying to install Mail::SpamAssassin via cpan. 
The crux of this seems to be:


Can't locate Digest/SHA1.pm in @INC (@INC contains: ../blib/lib 
@@INSTALLSITELIB@@ /opt/perl5/lib/5.10.1/x86_64-linux 
/opt/perl5/lib/5.10.1 /opt/perl5/lib/site_perl/5.10.1/x86_64-linux 
/opt/perl5/lib/site_perl/5.10.1) at 
../blib/lib/Mail/SpamAssassin/Bayes.pm line 61.


Whole output is available here: http://pastebin.com/m404a0ffc

This is already installed via CPAN and lives in 
/opt/perl/lib/perl5/x86_64-linux/Digest/SHA1.pm


It is accessible via @INC in other scripts. For example if I run perl 
-MDigest::SHA1 -e 'exit' I don't get any errors.  @INC for a normal perl 
script looks like this:


]# perl -e 'print join(, , @INC)'
/opt/perl5/lib/perl5/x86_64-linux, /opt/perl5/lib/perl5, 
/opt/perl5/lib/perl5/x86_64-linux, /opt/perl5/lib/5.10.1/x86_64-linux, 
/opt/perl5/lib/5.10.1, /opt/perl5/lib/site_perl/5.10.1/x86_64-linux, 
/opt/perl5/lib/site_perl/5.10.1, /opt/perl5/lib/5.10.1/x86_64-linux, 
/opt/perl5/lib/5.10.1, /opt/perl5/lib/site_perl/5.10.1/x86_64-linux, 
/opt/perl5/lib/site_perl/5.10.1, .


The reason perl lives in /opt is that this is a CentOS 5.4 and I'm 
looking to bypass the perl that comes with RPM without overwriting or 
deleting it so it's still around if something RPM-specific needs to use 
it. The way I ensure that I'm using the right version of perl while I'm 
trying to install Mail::SpamAssassin via the following environment 
variables in /root/.bashrc:


export MODULEBUILDRC=/opt/perl5/.modulebuildrc
export PERL_MM_OPT=INSTALL_BASE=/opt/perl5
export 
PERL5LIB=/opt/perl5/lib/perl5:/opt/perl5/lib/perl5/x86_64-linux:/opt/perl5/lib/5.10.1:/opt/perl5/lib/site_perl/5.10.1

export PATH=/opt/perl5/bin:$PATH

]# grep export ~/.bashrc
export MODULEBUILDRC=/opt/perl5/.modulebuildrc
export PERL_MM_OPT=INSTALL_BASE=/opt/perl5
export 
PERL5LIB=/opt/perl5/lib/perl5:/opt/perl5/lib/perl5/x86_64-linux:/opt/perl5/lib/5.10.1:/opt/perl5/lib/site_perl/5.10.1

export PATH=/opt/perl5/bin:$PATH
]# perl -v
This is perl, v5.10.1 (*) built for x86_64-linux

I'm running all of this as root.

Any pointers in the right direction would be much appreciated.

Thanks,
Edward



The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.