Re: [Mimedefang] SA scores
--On Thursday, October 19, 2006 9:24 AM -0700 Philip Goisman [EMAIL PROTECTED] wrote: Are you now saying mimedefang uses both /var/lib/spamassassin and /usr/share/spamassassin? If mimedefang only uses /usr/share/spamassassin, what's the point in putting the updates in /var/lib/spamassassin unless you want to run spamassassin from procmail? See the FAQ here: http://wiki.apache.org/spamassassin/RuleUpdates Traditionally /usr is treated as read-only (it might be mounted that way) and /var is used for stuff that changes from day to day (such as anti-virus and anti-spam data files). An SA update might only affect a few rules within a file in the main rules directory, and you wouldn't want it overwriting that file and eliminating all the rules that weren't updated. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
Philip Goisman [EMAIL PROTECTED] writes: Why not make LOCAL_STATE_DIR = '/usr/share/spamassassin'? The directory /var/lib/spamassassin does not exist on my system - rhel4. Then you have never run sa-update, have you? /usr/share/spamassassin is where the install time released rules are placed. LOCAL_STATE_DIR is the where updated rules are placed by sa-update. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
David F. Skoll [EMAIL PROTECTED] writes: There should be a way to query Mail::SpamAssassin for this info. Which should not be necessary as if LOCAL_STATE_DIR is not set in the call to Mail::SpamAssassin-new, that function will set it to the correct value. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
From Bugzilla: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5135 --- Additional Comments From [EMAIL PROTECTED] 2006-10-18 18:55 (In reply to comment #0) MIMEDefang needs to know the value of the spamassassin Makefile macro LOCAL_STATE_DIR to access new rules acquired from sa-update. What exactly is the issue? I looked through some of the thread, and it appears people are using updatedir, which they really shouldn't be doing, but that's a different matter. As of 3.1.5, SpamAssassin sets a default LOCAL_STATE_DIR anyway, so as long as mimedefang isn't overriding things, everything should work. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
Hm, another interesting sidenote: after I upgraded SpamAssassin 3.1.4 - 3.1.7 mimedefang apparently doesn't use (/etc/mail/spamassassin/)sa-mimedefang.cf anymore... I've got various scores tweaked in configuration files and with 3.1.4 I get: 2.0 PLING_PLING but with 3.1.7 test got default score: 0.5 PLING_PLING Downgrading back to 3.1.4 fixed the problem. What is the simplest way to test which configuration file is mimedefang acually using? -- Miha ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
Graham Murray wrote: There should be a way to query Mail::SpamAssassin for this info. Which should not be necessary as if LOCAL_STATE_DIR is not set in the call to Mail::SpamAssassin-new, that function will set it to the correct value. Really? Could you point out the code that does that? -- David. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
David F. Skoll [EMAIL PROTECTED] writes:
Graham Murray wrote:
There should be a way to query Mail::SpamAssassin for this info.
Which should not be necessary as if LOCAL_STATE_DIR is not set in the
call to Mail::SpamAssassin-new, that function will set it to the
correct value.
Really? Could you point out the code that does that?
From Mail/SpamAssassin.pm. You will notice that it sets the default if
no LOCAL_STATE_DIR is specified in the call.
=item LOCAL_STATE_DIR
Location of the local state directory, mainly used for installing updates via
Csa-update. Defaults to /var/lib/spamassassin.
=back
=cut
sub new {
my $class = shift;
$class = ref($class) || $class;
my $self = shift;
if (!defined $self) { $self = { }; }
bless ($self, $class);
# basic backwards compatibility; debug used to be a boolean.
# translate that into 'all', which is what it meant before 3.1.0.
if ($self-{debug} $self-{debug} eq '1') {
$self-{debug} = 'all';
}
# enable or disable debugging
Mail::SpamAssassin::Logger::add_facilities($self-{debug});
# first debugging information possibly printed should be the version
dbg(generic: SpamAssassin version . Version());
# if the libs are installed in an alternate location, and the caller
# didn't set PREFIX, we should have an estimated guess ready, values
# substituted at 'make' time
$self-{PREFIX} ||= '/usr';
$self-{DEF_RULES_DIR}||= '/usr/share/spamassassin';
$self-{LOCAL_RULES_DIR} ||= '/etc/mail/spamassassin';
$self-{LOCAL_STATE_DIR} ||= '/var/lib/spamassassin';
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
Graham Murray wrote: From Mail/SpamAssassin.pm. You will notice that it sets the default if no LOCAL_STATE_DIR is specified in the call. OK; this must be relatively new. I'm still running 3.1.4, and it doesn't do this. I will check when it was added, and (yuck) make MIMEDefang check the version and not pass the LOCAL_STATE_DIR into the constructor. :-( Sigh... Thanks, David. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
Replying to myself David F. Skoll wrote: OK; this must be relatively new. I'm still running 3.1.4, and it doesn't do this. Fixed in 3.1.5. :-( Bug #4952 on SpamAssassin bug tracker. Regards, David. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
On Thu, Oct 19, 2006 at 10:39:28AM -0400, David F. Skoll wrote: Graham Murray wrote: From Mail/SpamAssassin.pm. You will notice that it sets the default if no LOCAL_STATE_DIR is specified in the call. OK; this must be relatively new. I'm still running 3.1.4, and it doesn't do this. I will check when it was added, and (yuck) make MIMEDefang check the version and not pass the LOCAL_STATE_DIR into the constructor. :-( In 3.1.5, I just checked (released aug 29th) -- Jan-Pieter Cornet [EMAIL PROTECTED] !! Disclamer: The addressee of this email is not the intended recipient. !! !! This is only a test of the echelon and data retention systems. Please !! !! archive this message indefinitely to allow verification of the logs. !! ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
Date: Thu, 19 Oct 2006 08:01:45 +0100 From: Graham Murray [EMAIL PROTECTED] Subject: Re: [Mimedefang] SA scores To: mimedefang@lists.roaringpenguin.com Philip Goisman [EMAIL PROTECTED] writes: Why not make LOCAL_STATE_DIR = '/usr/share/spamassassin'? The directory /var/lib/spamassassin does not exist on my system - rhel4. Then you have never run sa-update, have you? /usr/share/spamassassin is where the install time released rules are placed. LOCAL_STATE_DIR is the where updated rules are placed by sa-update. Actually, I did - sa-update --updatedir /usr/share/spamassassin. I did it this way since a previous post stated the following: Date: Wed, 18 Oct 2006 10:06:38 -0400 From: Mike Lambert [EMAIL PROTECTED] Subject: Re: [Mimedefang] SA scores To: mimedefang@lists.roaringpenguin.com Miha Verlic wrote: X-Spam-Score: 2.25 (**) BAYES_50,EXTRA_MPART_TYPE,HTML_IMAGE_ONLY_20,HTML_MESSAGE Similiar message from spamassassin: X-Spam-Status: Yes, score=10.8 required=5.0 tests=BAYES_50,EXTRA_MPART_TYPE, HTML_IMAGE_ONLY_20,HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET, SARE_GIF_ATTACH,SARE_GIF_STOX,TVD_FW_GRAPHIC_ID1, TVD_FW_GRAPHIC_NAME_LONG,UNPARSEABLE_RELAY autolearn=no TVD_* rules are located in 80_additional.cf spamassassin configuration file Plain perl Makefile.PL, make, make install only installs 10_* through 60_* configuration files into /usr/share/spamassassin/, but when you run sa-update it downloads updates with 70_* and 80_* rulesets into /var/lib/spamassassin/3.001007/updates_spamassassin_org/. If you invoke spamassassin via shell, it will use both configuration directories, while mimedefang uses only /usr/share/spamassassin/. Are you now saying mimedefang uses both /var/lib/spamassassin and /usr/share/spamassassin? If mimedefang only uses /usr/share/spamassassin, what's the point in putting the updates in /var/lib/spamassassin unless you want to run spamassassin from procmail? ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
Miha Verlic wrote: X-Spam-Score: 2.25 (**) BAYES_50,EXTRA_MPART_TYPE,HTML_IMAGE_ONLY_20,HTML_MESSAGE Similiar message from spamassassin: X-Spam-Status: Yes, score=10.8 required=5.0 tests=BAYES_50,EXTRA_MPART_TYPE, HTML_IMAGE_ONLY_20,HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET, SARE_GIF_ATTACH,SARE_GIF_STOX,TVD_FW_GRAPHIC_ID1, TVD_FW_GRAPHIC_NAME_LONG,UNPARSEABLE_RELAY autolearn=no TVD_* rules are located in 80_additional.cf spamassassin configuration file Plain perl Makefile.PL, make, make install only installs 10_* through 60_* configuration files into /usr/share/spamassassin/, but when you run sa-update it downloads updates with 70_* and 80_* rulesets into /var/lib/spamassassin/3.001007/updates_spamassassin_org/. If you invoke spamassassin via shell, it will use both configuration directories, while mimedefang uses only /usr/share/spamassassin/. In spamassassin's Makefile.PL, LOCAL_STATE_DIR is set by macro on my system to /var/lib/spamassassin. But in mimedefang.pl, LOCAL_STATE_DIR = '/var/lib'. In mimedefang.pl, I changed LOCAL_STATE_DIR from '/var/lib' to '/var/lib/spamassassin'. Problem solved. YMMV. -Mike ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
Jeff Grossman wrote: It appears there is a '--update-dir' command line switch for sa-update which you can tell it where to place those newer files. I have not tried it yet, but it might do what we need with MIMEDefang. Jeff I use 'sa-update --update-dir=/etc/mail/spamassassin'which seems to work for me given that mimedefang uses /etc/mail/spamassassin as it's SA directory. Cheers, Roland ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
Date: Wed, 18 Oct 2006 10:06:38 -0400 From: Mike Lambert [EMAIL PROTECTED] Subject: Re: [Mimedefang] SA scores To: mimedefang@lists.roaringpenguin.com Miha Verlic wrote: X-Spam-Score: 2.25 (**) BAYES_50,EXTRA_MPART_TYPE,HTML_IMAGE_ONLY_20,HTML_MESSAGE Similiar message from spamassassin: X-Spam-Status: Yes, score=10.8 required=5.0 tests=BAYES_50,EXTRA_MPART_TYPE, HTML_IMAGE_ONLY_20,HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET, SARE_GIF_ATTACH,SARE_GIF_STOX,TVD_FW_GRAPHIC_ID1, TVD_FW_GRAPHIC_NAME_LONG,UNPARSEABLE_RELAY autolearn=no TVD_* rules are located in 80_additional.cf spamassassin configuration file Plain perl Makefile.PL, make, make install only installs 10_* through 60_* configuration files into /usr/share/spamassassin/, but when you run sa-update it downloads updates with 70_* and 80_* rulesets into /var/lib/spamassassin/3.001007/updates_spamassassin_org/. If you invoke spamassassin via shell, it will use both configuration directories, while mimedefang uses only /usr/share/spamassassin/. In spamassassin's Makefile.PL, LOCAL_STATE_DIR is set by macro on my system to /var/lib/spamassassin. But in mimedefang.pl, LOCAL_STATE_DIR = '/var/lib'. In mimedefang.pl, I changed LOCAL_STATE_DIR from '/var/lib' to '/var/lib/spamassassin'. Problem solved. YMMV. -Mike -- Date: Wed, 18 Oct 2006 10:17:22 -0400 From: David F. Skoll [EMAIL PROTECTED] Subject: Re: [Mimedefang] SA scores To: mimedefang@lists.roaringpenguin.com Mike Lambert wrote: In spamassassin's Makefile.PL, LOCAL_STATE_DIR is set by macro on my system to /var/lib/spamassassin. But in mimedefang.pl, LOCAL_STATE_DIR = '/var/lib'. We should file a bug with SpamAssassin, because there is *no way* to determine the proper value for LOCAL_STATE_DIR unless you can get the output of spamassassin's configure script. Regards, David. Why not make LOCAL_STATE_DIR = '/usr/share/spamassassin'? The directory /var/lib/spamassassin does not exist on my system - rhel4. Philip ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
--On Wednesday, October 18, 2006 10:17 AM -0400 David F. Skoll [EMAIL PROTECTED] wrote: We should file a bug with SpamAssassin, because there is *no way* to determine the proper value for LOCAL_STATE_DIR unless you can get the output of spamassassin's configure script. Done: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5135 ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] SA scores
This may not be the right list, but I'm having some issues with how mimedefang calls spamassassin and gets scores back. I'm receiving the typical stock spams everyone is getting blasted with. Here's the strange part. If I save the message source and run it against spamassassin, it might score 10.5. When it goes through mimedefang, it only scores 2.5. Any ideas how to debug this? Or suggestions on configuration changes? Here's what I've tried: 1) Run spamc as any user and I get 10.5. 2) Run spamassassin -D as any user and get 10.5 3) Tried various changes to mimedefang-filter, but doesn't seem to make a difference. Here's the report in mimedefang: X-Spam-Score: 2.25 (**) BAYES_50,EXTRA_MPART_TYPE,HTML_IMAGE_ONLY_20,HTML_MESSAGE Similiar message from spamassassin: X-Spam-Status: Yes, score=10.8 required=5.0 tests=BAYES_50,EXTRA_MPART_TYPE, HTML_IMAGE_ONLY_20,HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET, SARE_GIF_ATTACH,SARE_GIF_STOX,TVD_FW_GRAPHIC_ID1, TVD_FW_GRAPHIC_NAME_LONG,UNPARSEABLE_RELAY autolearn=no version=3.1.7 Running: mimedefang-2.57 Mail-SpamAssassin-3.1.7 Thanks! Mark ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] SA scores
On Mon, Oct 16, 2006 at 11:44:58AM -0400, Mark Johnson wrote: This may not be the right list, but I'm having some issues with how mimedefang calls spamassassin and gets scores back. I'm receiving the typical stock spams everyone is getting blasted with. Here's the strange part. If I save the message source and run it against spamassassin, it might score 10.5. When it goes through mimedefang, it only scores 2.5. Any ideas how to debug this? Or suggestions on configuration changes? My first thought is that your spamd/spamc invocation is using a different SpamAssassin configfile or rules directory from the MIMEDefang invocation. What are you using for each? Cheers, Dave -- Dave O'Neill [EMAIL PROTECTED]Roaring Penguin Software Inc. +1 (613) 231-6599http://www.roaringpenguin.com/ For CanIt technical support, please mail: [EMAIL PROTECTED] ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
