Re: Received from rule?

2007-10-24 Thread Matus UHLAR - fantomas 
On 24.10.07 17:54, Christian Nygaard wrote:
> How do I write a local spamassassin rule that matches received from header
> mail?.example.com . I've tried
> writing a header matching rule but it doesnt seem to work. Can you show a
> short example
> of a working header matching rule for received from?
> 
> Received: from mail3.example.com

the mail3.example.com may be (and probably is) a HELO string. It can be
faked. If you want to score according to ReceivedL lines, better check
X-Spam-Relays-Trusted or X-Spam-Relays-Untrusted, following instructions in 
http://wiki.apache.org/spamassassin/TrustPath
-- 
Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I intend to live forever - so far so good.

Re[2]: sa-update Problem with Archive::Tar

2007-10-24 Thread Mike Dillinger 
--- Original Message
From: Michael Scheidell <[EMAIL PROTECTED]>
Sent: Wednesday, October 24, 2007, at 06:10PM PDT (GMT -0700)

>> update [28512] dbg: channel: extracting archive No data could 
>> be read from file at /usr/bin/sa-update line 960
>> fatal: couldn't create Archive::Tar object!

>> Any help is greatly appreciated.  Thanks!
>> -MikeD

MS> You might want to look at the README and dependencies.

MS> Sa-update is new to 3.x and requires the perl module 'Archive::Tar'.
MS> In fact, if you have Archive::Tar, you might check the README for
MS> mininum versions

MS> Missing or down rev module could cause the problem

I figured out the problem.  I forgot to uninstall v2.6.3 first.  So I 
uninstalled v2.6.3 and then installed 3.2.3 again and everything seems to be 
working fine.

SpamAssassin won't install unless you have Archive::Tar installed.  That 
package was already installed.

Thanks!
-MikeD

RE: sa-update Problem with Archive::Tar

2007-10-24 Thread Michael Scheidell 
> update [28512] dbg: channel: extracting archive No data could 
> be read from file at /usr/bin/sa-update line 960
> fatal: couldn't create Archive::Tar object!
> 
> Any help is greatly appreciated.  Thanks!
> -MikeD
> 
> 
You might want to look at the README and dependencies.

Sa-update is new to 3.x and requires the perl module 'Archive::Tar'.
In fact, if you have Archive::Tar, you might check the README for
mininum versions

Missing or down rev module could cause the problem

-- 
Michael Scheidell, CTO
Office: 561-999-5000 x 1259
Direct: 561-939-7259
Real time security alerts: http://www.secnap.com/news
_
This email has been scanned and certified safe by SpammerTrap(tm).
For Information please see http://www.spammertrap.com
_

sa-update Problem with Archive::Tar

2007-10-24 Thread Mike Dillinger 
I am having a problem with sa-update:
No data could be read from file at /usr/bin/sa-update line 960
fatal: couldn't create Archive::Tar object!

I searched and couldn't find anything on the Internet that would help me figure 
out this problem so I'm trying this.  :)

Here are some system details.  I am running Red Hat 9 (Shrike) and I upgraded 
from v2.6.3 to v3.2.3.  I have upgraded before on other systems and not had 
this problem.

I checked /tmp and it looks like the files are being created properly, and 
sa-update is being run as root like so: sa-update --gpghomedir 
/etc/spamassassin/sa-update-keys --channelfile /etc/spamassassin/channels.

SpamAssassin itself (spamd) seems to be running and working fine.  My only 
problem seems to be sa-update.

Here is the verbose sa-update output:
[28512] dbg: logger: adding facilities: all
[28512] dbg: logger: logging level is DBG
[28512] dbg: generic: SpamAssassin version 3.2.3
[28512] dbg: config: score set 0 chosen.
[28512] dbg: dns: no ipv6
[28512] dbg: dns: is Net::DNS::Resolver available? yes
[28512] dbg: dns: Net::DNS version: 0.61
[28512] dbg: generic: sa-update version svn540384
[28512] dbg: generic: using update directory: /var/lib/spamassassin/3.002003
[28512] dbg: diag: perl platform: 5.008 linux
[28512] dbg: diag: module installed: Digest::SHA1, version 2.01
[28512] dbg: diag: module installed: HTML::Parser, version 3.55
[28512] dbg: diag: module installed: Net::DNS, version 0.61
[28512] dbg: diag: module installed: MIME::Base64, version 2.12
[28512] dbg: diag: module installed: DB_File, version 1.806
[28512] dbg: diag: module installed: Net::SMTP, version 2.24
[28512] dbg: diag: module not installed: Mail::SPF ('require' failed)
[28512] dbg: diag: module not installed: Mail::SPF::Query ('require' failed)
[28512] dbg: diag: module not installed: IP::Country::Fast ('require' failed)
[28512] dbg: diag: module not installed: Razor2::Client::Agent ('require' 
failed)
[28512] dbg: diag: module not installed: Net::Ident ('require' failed)
[28512] dbg: diag: module not installed: IO::Socket::INET6 ('require' failed)
[28512] dbg: diag: module not installed: IO::Socket::SSL ('require' failed)
[28512] dbg: diag: module installed: Compress::Zlib, version 1.16
[28512] dbg: diag: module installed: Time::HiRes, version 1.38
[28512] dbg: diag: module not installed: Mail::DomainKeys ('require' failed)
[28512] dbg: diag: module not installed: Mail::DKIM ('require' failed)
[28512] dbg: diag: module installed: DBI, version 1.32
[28512] dbg: diag: module installed: Getopt::Long, version 2.32
[28512] dbg: diag: module installed: LWP::UserAgent, version 2.001
[28512] dbg: diag: module installed: HTTP::Date, version 1.44
[28512] dbg: diag: module installed: Archive::Tar, version 1.32
[28512] dbg: diag: module installed: IO::Zlib, version 1.05
[28512] dbg: diag: module not installed: Encode::Detect ('require' failed)
[28512] dbg: gpg: Searching for 'gpg'
[28512] dbg: util: current PATH is: 
/sbin:/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin/X11:/usr/X11R6/bin
[28512] dbg: util: executable for gpg was found at /usr/bin/gpg
[28512] dbg: gpg: found /usr/bin/gpg
[28512] dbg: gpg: release trusted key id list: 
5E541DC959CB8BAC7C78DFDC4056A61A5244EC45 
26C900A46DD40CD5AD24F6D7DEE01987265FA05B 
0C2B1D7175B852C64B3CDC716C55397824F434CE
[28512] dbg: channel: reading in channelfile /etc/mail/spamassassin/channels
[28512] dbg: channel: adding updates.spamassassin.org
[28512] dbg: channel: attempting channel updates.spamassassin.org
[28512] dbg: channel: update directory 
/var/lib/spamassassin/3.002003/updates_spamassassin_org
[28512] dbg: channel: channel cf file 
/var/lib/spamassassin/3.002003/updates_spamassassin_org.cf
[28512] dbg: channel: channel pre file 
/var/lib/spamassassin/3.002003/updates_spamassassin_org.pre
[28512] dbg: dns: 3.2.3.updates.spamassassin.org => 585505, parsed as 585505
[28512] dbg: channel: preparing temp directory for new channel
[28512] dbg: generic: update tmp directory /tmp/.spamassassin28512yWE8tGtmp
[28512] dbg: generic: lint checking site pre files once before attempting 
channel updates
[28512] dbg: generic: SpamAssassin version 3.2.3
[28512] dbg: config: score set 0 chosen.
[28512] dbg: dns: no ipv6
[28512] dbg: dns: is Net::DNS::Resolver available? yes
[28512] dbg: dns: Net::DNS version: 0.61
[28512] dbg: ignore: using a test message to lint rules
[28512] dbg: config: using "/etc/mail/spamassassin" for site rules pre files
[28512] dbg: config: read file /etc/mail/spamassassin/init.pre
[28512] dbg: config: read file /etc/mail/spamassassin/v310.pre
[28512] dbg: config: read file /etc/mail/spamassassin/v312.pre
[28512] dbg: config: read file /etc/mail/spamassassin/v320.pre
[28512] dbg: config: using "/tmp/.spamassassin28512yWE8tGtmp/doesnotexist" for 
sys rules pre files
[28512] dbg: config: using "/tmp/.spamassassin28512yWE8tGtmp/doesnotexist" for 
default rules dir
[28512] dbg: config: using 
"/tmp/.spamassassin28512yW

Rule for TLS verify=OK?

2007-10-24 Thread Dan Mahoney, System Admin 

Hey all,

In looking through my sendmail logs, I've found that some connecting mail 
servers actually are correctly configured with a signed, valid cert from 
one of the major CA's.


Is there a rule that can match this, on sendmail, based on the connecting 
ip on your network edge?


This could be used to complement domain-assurance tools like SPF, DKIM or 
the like, since it not only matches the fact that in order to get one of 
these certs, the domain owner has had to match at least SOME kind of 
legitimacy test (even with the most automated signers).


This is a length I cannot imagine a spammer going to.

Better still, can someone with a better corpus than I confirm some hit/not 
hit ratios here?


-Dan

--

unless is a pr0no book he wont even come close to the bandwidth quota

-Racer-X, concerning DanMahoney.com's web hits.


Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---

Re: Bayes - one database per user or one for everybody?

2007-10-24 Thread Cedric Knight, GreenNet 
Hi

I've a possibly related enquiry to an old one below, and would be
grateful for advice or pointers.

We haven't actually *needed* Bayes thanks to greylisting, remote URI
lookups and lots of custom rules.  While a few users are interested in
a filter they can manually train, most wouldn't bother, and most
receive similar types of ham mail, which makes me wonder whether a
single group-writeable database is best, currently
/var/amavis/.spamassassin/bayes, probably without bayes_auto_learn.

However, as some tech-savvy users do want their own Bayes db, one
thought was to use the default user .spamassassin folders but have
symbolic links to the central database for most users.  Is this crazy?
Has anyone tried it?  What are the implications on disk I/O of the
various options, including several GB worth of individual databases?
Is there anything I particularly need to look out for in terms of
performance on the live server?

The basic problem is that AFAIK bayes_path can't be set as a user
preference (global and then overridden by say a user preferences
database), as would be needed to have some users use a communal
database, and some their own.  I can see bayes_sql_override_username
could achieve a similar function, but that necessarily rules out
having DBM databases.  Users here do have their own home directories,
and would have ability to train via sending as MIME attachment, but no
shell access.  I realise as I write this that my wish is even more
difficult because amavis doesn't extract or pass user information to
SA in any case, and it would presumably mean running spamc in
procmailrc...  Is there any way of checking two dbs, one global and
one per-user?

A lot of questions, and any pointers or experience is appreciated.

One further one: are per-user databases important for accuracy of
auto-whitelisting?

Thanks

Ced

On 11 July 2007, Micha³ Jêczalik <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm migrating to SQL Bayes storage method. I have plenty of email
> accounts. By this time, all of them had their own database in their
> home directories. Such approach unfortunately consumes a lot of disk
> space, so now I'm thinking about bayes_sql_override_username option,
> which allows me to have one single database for all.
>
> I wonder if it's better to have a single database (which probably
> could be larger than the size of 8MB per user I allowed with DBM
> storage method) or keep per-user ones?
>
> So, what are the advantages of a single database? And does it make
any
> sense to make it larger? Maybe 8MB of tokens is simply enough and it
> doesn't pay to use more resources to seek in a larger base? Are
there
> any security or privacy problems with this setup?
>
> BTW, users don't have access to their databases, they are unable to
> feed any spam/ham manually, so loosing this ability is not a problem
> for me.
>
> Regards,
> --
> Michal Jeczalik, +48.603.64.62.97

RE: Top spam hosters, how to decline email mentioning them

2007-10-24 Thread Karsten Bräckelmann 
On Mon, 2007-10-22 at 11:55 +0200, Chris wrote:

[ snipp mangled full-quote ]

> Is there any way, on shared servers, that I can use
> SpamAssassin to delete email from China, Russia, Korea
> and Japan please ?

No. SpamAssassin does not delete, nor reject mail. It merely tags mail.
However, your mail-processing chain can do any action, based upon that
tagging.

To detect the location of all mail relays, you can use the RelayCountry
plugin [1]. Based on the results, you can identify mail *from* these
countries, as you asked for. (Which is not the same as the thread you
replied to, which talks about links in the email body.)

Regarding "shared servers", and if this is possible (for you): Dunno,
that depends on the details. You'll need the mentioned SA plugin, which
is not possible in the user configs, but needs to be included in the SA
configs. Whether you can do this or not pretty much depends on your
level of control over SA.

  guenther


[1] http://wiki.apache.org/spamassassin/RelayCountryPlugin

-- 
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Another question about Pyzor and other strange issue

2007-10-24 Thread cpayne 

Guys,

I got pyzor working, thanks I got strange issue. It seems that one use 
it's working, in fact DCC and Razor2 are also only work for this one user.


This is what I see in user X headers...

X-Spam-Pyzor: Reported 0 times.

But this is want I am seeing in everyone else

X-Spam-Pyzor: _PYZOR_

Same with Razor

1.5 RAZOR2_CF_RANGE_E8_51_100 Razor2 gives engine 8 confidence level
   above 50%
   [cf: 100]
0.5 RAZOR2_CHECK   Listed in Razor2 (http://razor.sf.net/)
0.5 RAZOR2_CF_RANGE_51_100 Razor2 gives confidence level above 50%


Everyone else nothing. 


Any clues as why only one user gets those check and every one else nothing?

Payne
   [cf: 100]

Re: Received from rule?

2007-10-24 Thread Karsten Bräckelmann 
On Wed, 2007-10-24 at 17:54 +0200, Christian Nygaard wrote:
> How do I write a local spamassassin rule that matches received from
> header mail?.example.com . I've tried writing a header matching rule
 ^
>  but it doesnt seem to work. Can you show a short example of a working
> header matching rule for received from? 
> 
> Received: from mail3.example.com
 ^

Just a guess, since you failed to paste any example of the rules you
tried already -- however, given the above, I guess the reason your rules
didn't match is, cause you confused wildcards for REs.

In RE syntax, the question mark means "optional". Thus, a SA rule
containing "mail?" will match "mai" or "mail", but it will *not* match
"mail3"...

Maybe this will help writing your custom rules, in addition to the
already posted examples.


Also, you're not trying to create some rules to subtract points for
trusted SMTP relays, are you? In that case, you should have a look at
the trusted_networks option instead, I guess.

  guenther


-- 
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: Received from rule?

2007-10-24 Thread Mr. Gus 

Christian Nygaard wrote:
How do I write a local spamassassin rule that matches received from 
header mail?.example.com . I've tried
writing a header matching rule but it doesnt seem to work. Can you show 
a short example

of a working header matching rule for received from?

Received: from mail3.example.com 


Something like

header  HappyRuleName   Received =~ /mail\d\.example\.com/i

or

header  HappyRuleName   Received =~ /^from mail\d+\.example\.com/i

?

--
Gus

Re: Received from rule?

2007-10-24 Thread Adam Lanier 
On Wed, 2007-10-24 at 17:54 +0200, Christian Nygaard wrote:
> How do I write a local spamassassin rule that matches received from
> header mail?.example.com . I've tried
> writing a header matching rule but it doesnt seem to work. Can you
> show a short example
> of a working header matching rule for received from? 
> 
> Received: from mail3.example.com

header   MADF_T2MR3 Received =~ /t2mr3\.com/i

or if you wanted to match the literal 'from' as well:

header FROM_EXAMPLE_COM Received =~ /from mail3\.example\.com/i

Received from rule?

2007-10-24 Thread Christian Nygaard 
How do I write a local spamassassin rule that matches received from header
mail?.example.com . I've tried
writing a header matching rule but it doesnt seem to work. Can you show a
short example
of a working header matching rule for received from?

Received: from mail3.example.com

Kind regards,
Christian

Re: Can't locate MLDBM.pm in @INC

2007-10-24 Thread Wolfgang Zeikat 



On 24.10.2007 17:08, Emmanuel Seyman wrote:


How can I fix that?


Install the perl-MLDBM rpm which should be provided by your distribution.


Yep, it is. Thanks!

wolfgang

Re: What has change, can't use pyzor and terse any more

2007-10-24 Thread cpayne 

Evan Platt wrote:

At 05:09 AM 10/24/2007, cpayne wrote:

Hey Guys,

Got a problem, I been looking on the net no clear answer. But why 
can't I use this have they change


Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line, 
skipping, in "/etc/mail/spamassassin/local.cf": pyzor_add_header 1
Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line, 
skipping, in "/etc/mail/spamassassin/local.cf": use_terse_report 1


Any help you can give.


Did you just upgrade?

Googling pyzor_add_header and use_terse_report show quite a few answers:

http://spamassassinbook.packtpub.com/chapter11_preview.htm


Versions of SpamAssassin before 3.0 used the pyzor_add_header 
configuration directive to add a header to emails. This has been 
deprecated, and will be removed in future versions of SpamAssassin. 
The current method is to add an email header with Pyzor information. 
This is achieved by adding the following to 
/etc/mail/spamassassin/local.cf or ~/.spamassassin/user_prefs:


add_header all Pyzor _PYZOR_

and googling use_terse_report, the first google hit:
http://www.hoboes.com/Mimsy/?ART=201

The use_terse_report rule has also changed in SpamAssassin 3. I 
couldn't find the replacement, but thanks to Wolfgang from Vienna, I 
now know the answer:


remove_header all Report

This doesn't switch from a detailed to a terse report header; it 
removes the detailed report completely. But (as I understand it) in 
SpamAssassin 3, the terse and detailed reports have been separated out 
into X-Spam-Status (the terse version) and X-Spam-Report (the detailed 
version). Removing the detailed version leaves just the terse version.



OK, I am not getting anything in the headers still this is my test


From - Wed Oct 24 11:13:08 2007

X-Account-Key: account5
X-UIDL: a%[!!?%C!!!II"!CQ!#!
X-Mozilla-Status: 0001
X-Mozilla-Status2: 
X-Mozilla-Keys: 
Return-Path: <[EMAIL PROTECTED]>

X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: from localhost (unknown [127.0.0.1])
by magi.magidesign.com (Postfix) with ESMTP id 849D81AAE6
for <[EMAIL PROTECTED]>; Wed, 24 Oct 2007 15:15:30 + (UTC)
Received: from magi.magidesign.com ([127.0.0.1])
by localhost (magi.magidesign.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 12072-04 for <[EMAIL PROTECTED]>;
Wed, 24 Oct 2007 11:15:28 -0400 (EDT)
Received: by magi.magidesign.com (Postfix, from userid 65534)
id EBB701AAEA; Wed, 24 Oct 2007 11:15:28 -0400 (EDT)
X-Spam-DCC: _DCCB_:_DCCR
X-Spam-ASN:  
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on magi.magidesign.com
X-Spam-Level: 
X-Spam-Status: No, score=(-102.3), required=1.5, tests=BAYES_00,SPF_PASS,

USER_IN_WHITELIST, autolearn=ham, bayes score = 0., version=3.2.3 
date
scan = Wed, 24 Oct 2007 11:15:28 -0400
X-Spam-Pyzor: _PYZOR_
X-Spam-remote: hostinfo = localhost @ 127.0.0.1
Received-SPF: pass (gmail.com ... _spf.google.com: 64.233.184.237 is authorized to use 
'[EMAIL PROTECTED]' in 'mfrom' identity (mechanism 'ip4:64.233.160.0/19' matched)) 
receiver=magi.magidesign.com; identity=mfrom; envelope-from="[EMAIL 
PROTECTED]"; helo=wr-out-0506.google.com; client-ip=64.233.184.237
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237])
by magi.magidesign.com (Postfix) with ESMTP id 0956E1AADC
for <[EMAIL PROTECTED]>; Wed, 24 Oct 2007 11:15:21 -0400 (EDT)
Received: by wr-out-0506.google.com with SMTP id c57so239522wra
   for <[EMAIL PROTECTED]>; Wed, 24 Oct 2007 08:12:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
   d=gmail.com; s=beta;
   
h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
   bh=Gk/6ooN1Pk2Mpq7YYSyqMsMgt9nymf5EccMI7jdTSSU=;
   
b=I0ugLNrKg4LQ//CQyP3Je3qSNxsCnABUglKBil1mxHeBubxtTENKj6MQ5nc8GMk2Fg2fu+8YElpn1+xZf6r7Hj3ztqIYVC03oFOQcg8FIMKQSfv7zrI+rqJfZU9asstqJ81UEp7mOECfqK+JVdf4tT9aYRNF5W7EZh+qRgYn47w=
DomainKey-Signature: a=rsa-sha1; c=nofws;
   d=gmail.com; s=beta;
   
h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
   
b=V30QqjKFrq11N7VWq1x97QXoKWXzOklv/lXcbgV/ZiUfZkRjx8zgPUV276ENlZikvDJun1sK/Ao5LZAK8qkaZljJfSN5ctRaJGuyl2v4NkYGsT8kYkQJL4CyApDwlrCJnpWd605d8s0maTLhKOI1wETMMTkQzNhkhjJm8g9jpNo=
Received: by 10.142.99.21 with SMTP id w21mr169209wfb.1193238754526;
   Wed, 24 Oct 2007 08:12:34 -0700 (PDT)
Received: by 10.143.41.17 with HTTP; Wed, 24 Oct 2007 08:12:34 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 24 Oct 2007 11:12:34 -0400
From: "Chuck Payne" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Please check the headers


This is my config, any clues as to what I am doing wrong

# New Header Information

add_header spam Flag _YESNOCAPS_
add_header all

Re: Can't locate MLDBM.pm in @INC

2007-10-24 Thread Emmanuel Seyman 
* Wolfgang Zeikat :
>
> With SpamAssassin version 3.1.8 running on Perl version 5.8.5, I get the
>   spamd error "Can't locate MLDBM.pm in @INC" even after installing
> MLDBM.pm (on a redhat EL 4 based Scientific Linux system).
>
> # find / -iname "MLDBM.pm"
> /usr/lib/perl5/vendor_perl/5.8.5/IO/All/MLDBM.pm

This is the IO::All::MLDBM module, not the MLDBM one.

> How can I fix that?

Install the perl-MLDBM rpm which should be provided by your distribution.
If it doesn't exist, you can install the module from CPAN.

Emmanuel

Re: What has change, can't use pyzor and terse any more

2007-10-24 Thread cpayne 

Evan Platt wrote:

At 05:09 AM 10/24/2007, cpayne wrote:

Hey Guys,

Got a problem, I been looking on the net no clear answer. But why 
can't I use this have they change


Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line, 
skipping, in "/etc/mail/spamassassin/local.cf": pyzor_add_header 1
Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line, 
skipping, in "/etc/mail/spamassassin/local.cf": use_terse_report 1


Any help you can give.


Did you just upgrade?

Googling pyzor_add_header and use_terse_report show quite a few answers:

http://spamassassinbook.packtpub.com/chapter11_preview.htm


Versions of SpamAssassin before 3.0 used the pyzor_add_header 
configuration directive to add a header to emails. This has been 
deprecated, and will be removed in future versions of SpamAssassin. 
The current method is to add an email header with Pyzor information. 
This is achieved by adding the following to 
/etc/mail/spamassassin/local.cf or ~/.spamassassin/user_prefs:


add_header all Pyzor _PYZOR_

and googling use_terse_report, the first google hit:
http://www.hoboes.com/Mimsy/?ART=201

The use_terse_report rule has also changed in SpamAssassin 3. I 
couldn't find the replacement, but thanks to Wolfgang from Vienna, I 
now know the answer:


remove_header all Report

This doesn't switch from a detailed to a terse report header; it 
removes the detailed report completely. But (as I understand it) in 
SpamAssassin 3, the terse and detailed reports have been separated out 
into X-Spam-Status (the terse version) and X-Spam-Report (the detailed 
version). Removing the detailed version leaves just the terse version.


Thanks for the link, not only did you help me fix Pyzor, but Razor and 
DCC, which were working but stop and now I know why. Thanks.


Payne

Can't locate MLDBM.pm in @INC

2007-10-24 Thread Wolfgang Zeikat 
With SpamAssassin version 3.1.8 running on Perl version 5.8.5, I get the 
 spamd error "Can't locate MLDBM.pm in @INC" even after installing 
MLDBM.pm (on a redhat EL 4 based Scientific Linux system).


# find / -iname "MLDBM.pm"
/usr/lib/perl5/vendor_perl/5.8.5/IO/All/MLDBM.pm

How can I fix that?

Regards,

wolfgang

spamd error from maillog:
spamd[8110]: Can't locate MLDBM.pm in @INC (@INC contains: .. 
/etc/mail/spamassassin lib ../lib 
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi 
/usr/lib/perl5/vendor_perl/5.8.5 
/usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 
/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.2/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi 
/usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 
/usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2 
/usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 
/usr/lib/perl5/site_perl 
/usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi 
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi 
/usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi 
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-mul

Re: What has change, can't use pyzor and terse any more

2007-10-24 Thread Evan Platt 

At 05:09 AM 10/24/2007, cpayne wrote:

Hey Guys,

Got a problem, I been looking on the net no clear answer. But why 
can't I use this have they change


Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line, 
skipping, in "/etc/mail/spamassassin/local.cf": pyzor_add_header 1
Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line, 
skipping, in "/etc/mail/spamassassin/local.cf": use_terse_report 1


Any help you can give.


Did you just upgrade?

Googling pyzor_add_header and use_terse_report show quite a few answers:

http://spamassassinbook.packtpub.com/chapter11_preview.htm


Versions of SpamAssassin before 3.0 used the pyzor_add_header 
configuration directive to add a header to emails. This has been 
deprecated, and will be removed in future versions of SpamAssassin. 
The current method is to add an email header with Pyzor information. 
This is achieved by adding the following to 
/etc/mail/spamassassin/local.cf or ~/.spamassassin/user_prefs:


add_header all Pyzor _PYZOR_

and googling use_terse_report, the first google hit:
http://www.hoboes.com/Mimsy/?ART=201

The use_terse_report rule has also changed in SpamAssassin 3. I 
couldn't find the replacement, but thanks to Wolfgang from Vienna, I 
now know the answer:


remove_header all Report

This doesn't switch from a detailed to a terse report header; it 
removes the detailed report completely. But (as I understand it) in 
SpamAssassin 3, the terse and detailed reports have been separated 
out into X-Spam-Status (the terse version) and X-Spam-Report (the 
detailed version). Removing the detailed version leaves just the terse version.

What has change, can't use pyzor and terse any more

2007-10-24 Thread cpayne 

Hey Guys,

Got a problem, I been looking on the net no clear answer. But why can't 
I use this have they change


Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line, 
skipping, in "/etc/mail/spamassassin/local.cf": pyzor_add_header 1
Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line, 
skipping, in "/etc/mail/spamassassin/local.cf": use_terse_report 1


Any help you can give.

Thanks,

Chuck