Re: problem with MSGID_MULTIPLE_AT
Nicolas Letellier wrote: On Tue, 02 Sep 2008 08:47:18 -0400 Matt Kettler [EMAIL PROTECTED] wrote: Well, it's obvious what the problem is. There's clearly two @ signs in the message-id, which is illegal, but it's what Microsoft is doing anyway. There's also a bug already open on this. https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5707 We might need to convert that rule to a meta and ignore it when the MUA is outlook 12.0 unless we can figure out that the outlook in question has some weird hack that causes it, and normal outlook 12 doesn't cause the problem.. Although I personally feel makers (and knowing users) of broken tools should suffer, I don't think SpamAssassin is the best spot to implement that. :-) Hello Matt, But today, I can't leave this option actived (or not patched). It's important for my business, and too many clients use Outlook 12.0 (I can't force them to use another mail client). For waiting, is it possible to disable the MSGID_MULTIPLE_AT check? And how? Thanks. The best way to disable a rule, is to add a score statement for it setting it's score to 0 in your local.cf score MSGID_MULTIPLE_AT 0 and yes, that does disable it. SA won't even evaluate a rule explicitly set to zero sc0re
Re: sa-update no new rules ?
David Carvalho wrote: Hi ! I’m using spamassassin 3.1.8 on a server. This is the last version available from the repository for this particular linux version. For some months it seems that both channels I use (saupdates.openprotect.com and updates.spamassassin.org) Don’t release any update. I always get a message like “current version = latest version…. Skiping channel” Are these channels deactivated ? If so , are there any other channels I can use with sa-update? There are not likely to ever be any more updates for the 3.1.x branch. We're on the 3.2 family, and 3.3 is starting to take shape. From historical observation, there is a period of overlap when two families get actively updated in sa-update, but once the current release (in this case 3.2) stabilizes and development starts to work on the next release (in this case 3.3) updates for the previous release (3.1.x) are more-or-less dropped unless there's a major issue with one of the rules (ie: if a dos in a rule regex cropped up). Besides, sa-update only updates half of spamassassin, the rules half, and it does not update the code. The latest rules won't help you if your HTML de-obfuscators and other such things are old, and that stuff lives in the code, not the rules. It changes quite a bit slower than the rules, but it does change, and does need updating sometimes.
Re: possible sa-learn issue
Raymond Jette wrote: Good morning, This morning I ran a sa-learn –dump magic and saw the following: Nspam 201 Nham 242 Soon after I ran spamassassin –D –lint to look for problems and it reported: Bayes: not available for scanning, only 189 spam(s) in bayes DB 200 I re-ran sp-learn –dump magic and saw the following: Nspam 189 Nham 0 Any idea what would cause this to happen? Any chance those two were run as different users? (ie: one as root, one as an unprivileged user?)
Re: CPAN Install Fails
Have you got any answers on this? I have the same problem. Other numbers of errors. So I am stuck with 3.1.0 -- Regards Lars Ebeling http://leopg9.no-ip.org Hobbithobbyist It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. -- Mark Twain - Original Message - From: Bob Cohen [EMAIL PROTECTED] To: users@spamassassin.apache.org Sent: Sunday, August 31, 2008 9:19 PM Subject: CPAN Install Fails CPAN install fails consistently. E.g., Failed TestStat Wstat Total Fail List of Failed --- t/spamc_optC.t94 2 4 6 8 t/spamc_optL.t 16 16 1-16 34 tests skipped. Failed 2/143 test scripts. 20/2021 subtests failed. Files=143, Tests=2021, 981 wallclock secs (558.97 cusr + 19.51 csys = 578.48 CPU) Failed 2/143 test programs. 20/2021 subtests failed. make: *** [test_dynamic] Error 255 JMASON/Mail-SpamAssassin-3.2.5.tar.gz /usr/bin/make test -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports JMASON/Mail-SpamAssassin-3.2.5.tar.gz Running make install make test had returned bad status, won't install without force Failed during this command: JMASON/Mail-SpamAssassin-3.2.5.tar.gz: make_test NO I'm running Fedora v9. All of the prerequisite and optional modules installed with no problem. Suggestions?
Re: CPAN Install Fails
Bob Cohen wrote: I'm running Fedora v9. All of the prerequisite and optional modules installed with no problem. Suggestions? Well, there’s always “install it with yum”: yum install spamassassin Hope this helps, James. -- E-mail: james@ | “It has taken 24 years to get the Reichstag wrapped. aprilcottage.co.uk | Chancellor Kohl said it would only be wrapped over his | dead body, so sensing an opportunity the Bundestag | outvoted him.” -- The Guardian
Message flagged as spam missing original message
All - My apologies if this has come up before - but I was unable to find anything relevant in the archives or while searching the docs... I've had a recent problem with a specific piece of mail that was flagged as spam - rightfully so in my opinion based on the flagged rules - but indeed wasn't. The problem is that it appears that spamassassin stripped the original message out after it flagged it as spam. I am running Exim 4.63 with SpamAssassin 3.2.5 being called via procmail. Upon delivery the message contained: 1) The usual Spam detection software, running on the system... message 2) The Content Preview 3) A list of all the rules flagged and points applied to the message (see below) 4) The original message headers (Date, From, To, Subject) but the original actual message seems to have disappeared... If a copy of the actual message as it was delivered is needed I can send it off list. I've checked the spamassassin and my smtp agent's (exim4) logs - but neither shows any warnings or errors for this message. My only guess at this point is from the MIME_QP_LONG_LINE RAW rule... is it possible that one line of the message was too long for spamassassin to parse so it dropped it? Or am I totally off track on this? The rules that tested positive on this message were: MISSING_MID, INVALID_DATE SPF_NEUTRAL DATE_IN_PAST_06_12 HEADER_COUNT_CTYPE BAYES_00 MIME_QP_LONG_LINE #SpamAssassin Log: Aug 29 11:49:37 spamd[20792]: spamd: connection from localhost [127.0.0.1] at port 35098 Aug 29 11:49:37 spamd[20792]: spamd: setuid to user succeeded Aug 29 11:49:37 spamd[20792]: netset: cannot include 127.0.0.0/8 as it has already been included Aug 29 11:49:37 spamd[20792]: spamd: processing message (unknown) for user:uid Aug 29 11:49:38 spamd[20792]: spamd: identified spam (4.8/3.5) for user:uid in 0.9 seconds, 1878 bytes. Aug 29 11:49:38 spamd[20792]: spamd: result: Y 4 - BAYES_00,DATE_IN_PAST_06_12,HEADER_COUNT_CTYPE,INVALID_DATE,MIME_QP_LONG_LIN E,MISSING_MID,SPF_NEUTRAL scantime=0.9,size=1878,user=user,uid=1uid,required_score=3.5,rhost=localhost,raddr=127.0.0.1,rport=35098 ,mid=(unknown),bayes=0.00,autolearn=no Any help in figuring out what happened would be greatly appreciated. Thanks -Chris H -- -Chris Henry Software Engineer Statistics (206)685-1627 begin:vcard fn:Chris Henry n:Henry;Chris org:University of Washington;Statistics adr;dom:Box 354322;;Department of Statistics;Seattle;WA;98195-4322 title:Software Engineer tel;work:(206)685-1627 version:2.1 end:vcard
Re: Logging IP adresses of spammer's SMTP
Thanks. I did a slight change in Received.pm to log only untrusted relays, all on one line for each mail (through enabling own debug channel). Now I'm gonna to write an analyzer, which will walk through spamd log daily and collect these records (only for spam with defined overscore) and add some host information (whois). I know it's a bad idea to feed my blacklist directly, so I will check and edit the output by hand and after that add it to rbl. This won't be too much work as most spam is coming to me from only few ips (or ip ranges) at this time. Thinline Maillist wrote: Hi, I'd like to log IPs from Received headers to spamd's log file for statistics and further analysis (but only from messages marked as spam). I tried to modify the code of spamd program, but unsuccessfully, since I chose to add it to parse_headers() subroutine, where only protocol specific headers are parsed (as it seems to me). parse_received_headers() (in Received.pm) is the function that parses the Received headers. it puts the relays in one of the X-Foo-Relays meta heatders (trusted, Untrusted, Internal, External). but if you do what you intend to do, be cautious: - SA is about heuristics: it doesn't say that a message is spam or not. it gives you a score. this may be right. this may be wrong. - if your trust path is misconfigured, the results may be arbitrary - you can get spam from good relays (mailing lists, subscribed to newsletters, ... etc). it is safer to use the results as a reputation measure instead of directly feeding a blacklist. This is probably not a right piece of source where to place this feature. I'm not a Perl programmer nor SA expert, so has anyone with more experience some idea, how to log spammers remote IPs? Thanks. if you don't want to code anything, just configure SA to add its meta headers (you only need the untrusted relays header) then when you deliver the message, use an MDA that can log this header (maildrop, procmail, or even a silly shell script with a 'grep -m 1 ^X-Untrusted-Relays:' call).
Re: Message flagged as spam missing original message
On 02.09.08 12:01, Chris Henry wrote: The problem is that it appears that spamassassin stripped the original message out after it flagged it as spam. I am running Exim 4.63 with SpamAssassin 3.2.5 being called via procmail. don't you use the '--headers' option to spamc? It causes spamd return only headers... -- 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 feel like I'm diagonally parked in a parallel universe.
rpmbuild spamassassin
Hi! since you guys told be that version 3.1.8 wasn't receiving updates because it's to old, I trying to upgrade spamassassin. Since I can't upgrade the server (I'm using Fedora 3), I've downloaded the latest tarball and did rpmbuild -tb Mail-SpamAssassin-3.2.5.tar.gz. When trying to install the rpm, I got a an error that some perl modules were outdates. So, i run cpan install Bundle::CPAN, which upgrade my perl environment. Now, when trying to build the rpm from the tarball again, after a while I get - + cp -pr README Changes sample-nonspam.txt sample-spam.txt spamd/README.spamd INSTALL BUGS LICENSE TRADEMARK USAGE sql UPGRADE /var/tmp/spamassassin-root/usr/share/doc/spamassassin-3.2.5 cp: cannot stat `BUGS': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) Provides: config(spamassassin) = 3.2.5-1 Requires(interp): /bin/sh /bin/sh /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires(post): /bin/sh Requires(preun): /bin/sh Requires(postun): /bin/sh Requires: /bin/sh /usr/bin/perl config(spamassassin) = 3.2.5-1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libdl.so.2 libz.so.1 perl(Archive::Tar) = 1.23 perl(Carp) perl(Config) perl(Cwd) perl(Data::Dumper) perl(Digest::SHA1) perl(DynaLoader) perl(Errno) perl(ExtUtils::MakeMaker) perl(File::Copy) perl(File::Path) perl(File::Spec) perl(File::Spec) = 0.8 perl(Getopt::Long) perl(HTTP::Date) perl(IO::Handle) perl(IO::Pipe) perl(IO::Zlib) = 1.04 perl(LWP::UserAgent) perl(Mail::SpamAssassin) perl(Mail::SpamAssassin::ArchiveIterator) perl(Mail::SpamAssassin::Logger) perl(Mail::SpamAssassin::Message) perl(Mail::SpamAssassin::NetSet) perl(Mail::SpamAssassin::PerMsgLearner) perl(Mail::SpamAssassin::SpamdForkScaling) perl(Mail::SpamAssassin::SubProcBackChannel) perl(Mail::SpamAssassin::Timeout) perl(Mail::SpamAssassin::Util::Progress) perl(Net::DNS) perl(POSIX) perl(Pod::Usage) perl(Pod::Usage) perl(Socket) perl(bytes) perl(constant) perl(lib) perl(strict) perl(vars) perl(warnings) perl-Mail-SpamAssassin = 3.2.5-1 Processing files: perl-Mail-SpamAssassin-3.2.5-1 error: File not found: /var/tmp/spamassassin-root/usr/share/spamassassin RPM build errors: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) File not found: /var/tmp/spamassassin-root/usr/share/spamassassin Any ideas please ? thanks and regards. David
Re: Logging IP adresses of spammer's SMTP
On Wed, 2008-09-03 at 12:01 +0200, Thinline Maillist wrote: Now I'm gonna to write an analyzer, which will walk through spamd log daily and collect these records (only for spam with defined overscore) and add some host information (whois). You might consider writing it as an additional logwatch filter. The benefit is that logwatch already provides the hooks to prevent a log entry being scanned more than once. Filters are quite easy to write and install. I've used gawk, but any scripting or programming language should be fine. Martin
spam bypass spamassassin
Why this spam scored with 5.1 (requered 5.0) bypass spamassassin?? (clamdscan: 0.93/8144. spamassassin: 3.2.5. Clear:RC:0(aaa.bbb.ccc.ddd):SA:1(5.1/5.0):. Processed in 2.490743 secs); 03 Sep 2008 11:32:21 - X-Spam-Status: Yes, score=5.1 required=5.0 X-Spam-Level: +
Re: spam bypass spamassassin
On 03.09.08 09:18, Rejaine Monteiro wrote: Why this spam scored with 5.1 (requered 5.0) bypass spamassassin?? Why do you think it bypassed spamassassin? The whole fact the spam was tagged means it did NOT bypass it, don't you think? (clamdscan: 0.93/8144. spamassassin: 3.2.5. Clear:RC:0(aaa.bbb.ccc.ddd):SA:1(5.1/5.0):. Processed in 2.490743 secs); 03 Sep 2008 11:32:21 - X-Spam-Status: Yes, score=5.1 required=5.0 X-Spam-Level: + I see no X-Spam-Version, maybe it was scored by SA on other machine. But, always, it's not spamassassin question why some mail are not passsed through it... -- 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. Remember half the people you know are below average.
Re: rpmbuild spamassassin
Same thing happened to me when I tried that . I had to do the build on a different server and copy the rpm file back to the server I orginally intended to run it on . I know that doesn't answer your question on why , but that is how I got my install to work . Best, Jeremy David Carvalho [EMAIL PROTECTED] 09/03/2008 06:17 AM To users@spamassassin.apache.org cc Subject rpmbuild spamassassin Hi! since you guys told be that version 3.1.8 wasn't receiving updates because it's to old, I trying to upgrade spamassassin. Since I can't upgrade the server (I'm using Fedora 3), I've downloaded the latest tarball and did rpmbuild -tb Mail-SpamAssassin-3.2.5.tar.gz. When trying to install the rpm, I got a an error that some perl modules were outdates. So, i run cpan install Bundle::CPAN, which upgrade my perl environment. Now, when trying to build the rpm from the tarball again, after a while I get - + cp -pr README Changes sample-nonspam.txt sample-spam.txt spamd/README.spamd INSTALL BUGS LICENSE TRADEMARK USAGE sql UPGRADE /var/tmp/spamassassin-root/usr/share/doc/spamassassin-3.2.5 cp: cannot stat `BUGS': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) Provides: config(spamassassin) = 3.2.5-1 Requires(interp): /bin/sh /bin/sh /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires(post): /bin/sh Requires(preun): /bin/sh Requires(postun): /bin/sh Requires: /bin/sh /usr/bin/perl config(spamassassin) = 3.2.5-1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libdl.so.2 libz.so.1 perl(Archive::Tar) = 1.23 perl(Carp) perl(Config) perl(Cwd) perl(Data::Dumper) perl(Digest::SHA1) perl(DynaLoader) perl(Errno) perl(ExtUtils::MakeMaker) perl(File::Copy) perl(File::Path) perl(File::Spec) perl(File::Spec) = 0.8 perl(Getopt::Long) perl(HTTP::Date) perl(IO::Handle) perl(IO::Pipe) perl(IO::Zlib) = 1.04 perl(LWP::UserAgent) perl(Mail::SpamAssassin) perl(Mail::SpamAssassin::ArchiveIterator) perl(Mail::SpamAssassin::Logger) perl(Mail::SpamAssassin::Message) perl(Mail::SpamAssassin::NetSet) perl(Mail::SpamAssassin::PerMsgLearner) perl(Mail::SpamAssassin::SpamdForkScaling) perl(Mail::SpamAssassin::SubProcBackChannel) perl(Mail::SpamAssassin::Timeout) perl(Mail::SpamAssassin::Util::Progress) perl(Net::DNS) perl(POSIX) perl(Pod::Usage) perl(Pod::Usage) perl(Socket) perl(bytes) perl(constant) perl(lib) perl(strict) perl(vars) perl(warnings) perl-Mail-SpamAssassin = 3.2.5-1 Processing files: perl-Mail-SpamAssassin-3.2.5-1 error: File not found: /var/tmp/spamassassin-root/usr/share/spamassassin RPM build errors: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) File not found: /var/tmp/spamassassin-root/usr/share/spamassassin Any ideas please ? thanks and regards. David
Re: spam bypass spamassassin
On Wed, Sep 03, 2008 at 09:18:53AM -0300, Rejaine Monteiro wrote: Why this spam scored with 5.1 (requered 5.0) bypass spamassassin?? (clamdscan: 0.93/8144. spamassassin: 3.2.5. Clear:RC:0(aaa.bbb.ccc.ddd):SA:1(5.1/5.0):. Processed in 2.490743 secs); 03 Sep 2008 11:32:21 - X-Spam-Status: Yes, score=5.1 required=5.0 X-Spam-Level: + It did not bypass Spamassassin. Spamassassin did it's job by classifying the message as spam. The rest is up to your mta. Regards Johann -- Johann Spies Telefoon: 021-808 4036 Informasietegnologie, Universiteit van Stellenbosch And he said unto his disciples, Therefore I say unto you, Take no thought for your life, what ye shall eat: neither for the body, what ye shall put on. The life is more than meat, and the body is more than raiment. Consider the ravens: for they neither sow nor reap; which neither have storehouse nor barn; and God feedeth them: how much more are ye better than the fowls! Consider the lilies, how they grow: they toil not, they spin not; and yet I say unto you, that Solomon in all his glory was not arrayed like one of these. If then God so clothe the grass, which is to day in the field, and to morrow is cast into the oven; how much more will he clothe you, O ye of little faith? And seek not what ye shall eat, or what ye shall drink, neither be ye of doubtful mind. But rather seek ye the kingdom of God; and all these things shall be added unto you. Luke 12:22-24; 27-29; 31.
RE: rpmbuild spamassassin
Thanks for the reply... I was able to build the rpm on a Fedora 7. Copyied to my Fedora 3, But couldn't install (dependency issues, as I expected) Is it possible/safe to install it from cpan, since I already have it running Through rpm ? regards -Original Message- From: Jeremy Davila [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 3 de Setembro de 2008 13:58 To: David Carvalho Cc: users@spamassassin.apache.org Subject: Re: rpmbuild spamassassin Same thing happened to me when I tried that . I had to do the build on a different server and copy the rpm file back to the server I orginally intended to run it on . I know that doesn't answer your question on why , but that is how I got my install to work . Best, Jeremy David Carvalho [EMAIL PROTECTED] 09/03/2008 06:17 AM To users@spamassassin.apache.org cc Subject rpmbuild spamassassin Hi! since you guys told be that version 3.1.8 wasn't receiving updates because it's to old, I trying to upgrade spamassassin. Since I can't upgrade the server (I'm using Fedora 3), I've downloaded the latest tarball and did rpmbuild -tb Mail-SpamAssassin-3.2.5.tar.gz. When trying to install the rpm, I got a an error that some perl modules were outdates. So, i run cpan install Bundle::CPAN, which upgrade my perl environment. Now, when trying to build the rpm from the tarball again, after a while I get - + cp -pr README Changes sample-nonspam.txt sample-spam.txt spamd/README.spamd INSTALL BUGS LICENSE TRADEMARK USAGE sql UPGRADE /var/tmp/spamassassin-root/usr/share/doc/spamassassin-3.2.5 cp: cannot stat `BUGS': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) Provides: config(spamassassin) = 3.2.5-1 Requires(interp): /bin/sh /bin/sh /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires(post): /bin/sh Requires(preun): /bin/sh Requires(postun): /bin/sh Requires: /bin/sh /usr/bin/perl config(spamassassin) = 3.2.5-1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libdl.so.2 libz.so.1 perl(Archive::Tar) = 1.23 perl(Carp) perl(Config) perl(Cwd) perl(Data::Dumper) perl(Digest::SHA1) perl(DynaLoader) perl(Errno) perl(ExtUtils::MakeMaker) perl(File::Copy) perl(File::Path) perl(File::Spec) perl(File::Spec) = 0.8 perl(Getopt::Long) perl(HTTP::Date) perl(IO::Handle) perl(IO::Pipe) perl(IO::Zlib) = 1.04 perl(LWP::UserAgent) perl(Mail::SpamAssassin) perl(Mail::SpamAssassin::ArchiveIterator) perl(Mail::SpamAssassin::Logger) perl(Mail::SpamAssassin::Message) perl(Mail::SpamAssassin::NetSet) perl(Mail::SpamAssassin::PerMsgLearner) perl(Mail::SpamAssassin::SpamdForkScaling) perl(Mail::SpamAssassin::SubProcBackChannel) perl(Mail::SpamAssassin::Timeout) perl(Mail::SpamAssassin::Util::Progress) perl(Net::DNS) perl(POSIX) perl(Pod::Usage) perl(Pod::Usage) perl(Socket) perl(bytes) perl(constant) perl(lib) perl(strict) perl(vars) perl(warnings) perl-Mail-SpamAssassin = 3.2.5-1 Processing files: perl-Mail-SpamAssassin-3.2.5-1 error: File not found: /var/tmp/spamassassin-root/usr/share/spamassassin RPM build errors: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) File not found: /var/tmp/spamassassin-root/usr/share/spamassassin Any ideas please ? thanks and regards. David
RE: rpmbuild spamassassin
Meanwhile, I was able to find in DAG repository A package called spamassassin-3.2.4-1.rf-src-rpm I installed it, and generated the rpm binary with rpmbuild from the spec file. When trying to install, again dependency problems, (IO::Zlib, IO::Socket:SSL, HTML::Parser). But when I try to install them from the cpan prompt, I get that These are up to date... I'm avoiding to use the --force option to install spamassassin -Original Message- From: Jeremy Davila [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 3 de Setembro de 2008 13:58 To: David Carvalho Cc: users@spamassassin.apache.org Subject: Re: rpmbuild spamassassin Same thing happened to me when I tried that . I had to do the build on a different server and copy the rpm file back to the server I orginally intended to run it on . I know that doesn't answer your question on why , but that is how I got my install to work . Best, Jeremy David Carvalho [EMAIL PROTECTED] 09/03/2008 06:17 AM To users@spamassassin.apache.org cc Subject rpmbuild spamassassin Hi! since you guys told be that version 3.1.8 wasn't receiving updates because it's to old, I trying to upgrade spamassassin. Since I can't upgrade the server (I'm using Fedora 3), I've downloaded the latest tarball and did rpmbuild -tb Mail-SpamAssassin-3.2.5.tar.gz. When trying to install the rpm, I got a an error that some perl modules were outdates. So, i run cpan install Bundle::CPAN, which upgrade my perl environment. Now, when trying to build the rpm from the tarball again, after a while I get - + cp -pr README Changes sample-nonspam.txt sample-spam.txt spamd/README.spamd INSTALL BUGS LICENSE TRADEMARK USAGE sql UPGRADE /var/tmp/spamassassin-root/usr/share/doc/spamassassin-3.2.5 cp: cannot stat `BUGS': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) Provides: config(spamassassin) = 3.2.5-1 Requires(interp): /bin/sh /bin/sh /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires(post): /bin/sh Requires(preun): /bin/sh Requires(postun): /bin/sh Requires: /bin/sh /usr/bin/perl config(spamassassin) = 3.2.5-1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libdl.so.2 libz.so.1 perl(Archive::Tar) = 1.23 perl(Carp) perl(Config) perl(Cwd) perl(Data::Dumper) perl(Digest::SHA1) perl(DynaLoader) perl(Errno) perl(ExtUtils::MakeMaker) perl(File::Copy) perl(File::Path) perl(File::Spec) perl(File::Spec) = 0.8 perl(Getopt::Long) perl(HTTP::Date) perl(IO::Handle) perl(IO::Pipe) perl(IO::Zlib) = 1.04 perl(LWP::UserAgent) perl(Mail::SpamAssassin) perl(Mail::SpamAssassin::ArchiveIterator) perl(Mail::SpamAssassin::Logger) perl(Mail::SpamAssassin::Message) perl(Mail::SpamAssassin::NetSet) perl(Mail::SpamAssassin::PerMsgLearner) perl(Mail::SpamAssassin::SpamdForkScaling) perl(Mail::SpamAssassin::SubProcBackChannel) perl(Mail::SpamAssassin::Timeout) perl(Mail::SpamAssassin::Util::Progress) perl(Net::DNS) perl(POSIX) perl(Pod::Usage) perl(Pod::Usage) perl(Socket) perl(bytes) perl(constant) perl(lib) perl(strict) perl(vars) perl(warnings) perl-Mail-SpamAssassin = 3.2.5-1 Processing files: perl-Mail-SpamAssassin-3.2.5-1 error: File not found: /var/tmp/spamassassin-root/usr/share/spamassassin RPM build errors: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) File not found: /var/tmp/spamassassin-root/usr/share/spamassassin Any ideas please ? thanks and regards. David
RE: rpmbuild spamassassin
Not to sure . I would install the dependencies. and re-run the RPM if you primarily use RPM you should stick with that . Same thing if you build from source files. I could be wrong... David Carvalho [EMAIL PROTECTED] 09/03/2008 09:33 AM To users@spamassassin.apache.org cc Subject RE: rpmbuild spamassassin Thanks for the reply... I was able to build the rpm on a Fedora 7. Copyied to my Fedora 3, But couldn't install (dependency issues, as I expected) Is it possible/safe to install it from cpan, since I already have it running Through rpm ? regards -Original Message- From: Jeremy Davila [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 3 de Setembro de 2008 13:58 To: David Carvalho Cc: users@spamassassin.apache.org Subject: Re: rpmbuild spamassassin Same thing happened to me when I tried that . I had to do the build on a different server and copy the rpm file back to the server I orginally intended to run it on . I know that doesn't answer your question on why , but that is how I got my install to work . Best, Jeremy David Carvalho [EMAIL PROTECTED] 09/03/2008 06:17 AM To users@spamassassin.apache.org cc Subject rpmbuild spamassassin Hi! since you guys told be that version 3.1.8 wasn't receiving updates because it's to old, I trying to upgrade spamassassin. Since I can't upgrade the server (I'm using Fedora 3), I've downloaded the latest tarball and did rpmbuild -tb Mail-SpamAssassin-3.2.5.tar.gz. When trying to install the rpm, I got a an error that some perl modules were outdates. So, i run cpan install Bundle::CPAN, which upgrade my perl environment. Now, when trying to build the rpm from the tarball again, after a while I get - + cp -pr README Changes sample-nonspam.txt sample-spam.txt spamd/README.spamd INSTALL BUGS LICENSE TRADEMARK USAGE sql UPGRADE /var/tmp/spamassassin-root/usr/share/doc/spamassassin-3.2.5 cp: cannot stat `BUGS': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) Provides: config(spamassassin) = 3.2.5-1 Requires(interp): /bin/sh /bin/sh /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Requires(post): /bin/sh Requires(preun): /bin/sh Requires(postun): /bin/sh Requires: /bin/sh /usr/bin/perl config(spamassassin) = 3.2.5-1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libdl.so.2 libz.so.1 perl(Archive::Tar) = 1.23 perl(Carp) perl(Config) perl(Cwd) perl(Data::Dumper) perl(Digest::SHA1) perl(DynaLoader) perl(Errno) perl(ExtUtils::MakeMaker) perl(File::Copy) perl(File::Path) perl(File::Spec) perl(File::Spec) = 0.8 perl(Getopt::Long) perl(HTTP::Date) perl(IO::Handle) perl(IO::Pipe) perl(IO::Zlib) = 1.04 perl(LWP::UserAgent) perl(Mail::SpamAssassin) perl(Mail::SpamAssassin::ArchiveIterator) perl(Mail::SpamAssassin::Logger) perl(Mail::SpamAssassin::Message) perl(Mail::SpamAssassin::NetSet) perl(Mail::SpamAssassin::PerMsgLearner) perl(Mail::SpamAssassin::SpamdForkScaling) perl(Mail::SpamAssassin::SubProcBackChannel) perl(Mail::SpamAssassin::Timeout) perl(Mail::SpamAssassin::Util::Progress) perl(Net::DNS) perl(POSIX) perl(Pod::Usage) perl(Pod::Usage) perl(Socket) perl(bytes) perl(constant) perl(lib) perl(strict) perl(vars) perl(warnings) perl-Mail-SpamAssassin = 3.2.5-1 Processing files: perl-Mail-SpamAssassin-3.2.5-1 error: File not found: /var/tmp/spamassassin-root/usr/share/spamassassin RPM build errors: Bad exit status from /var/tmp/rpm-tmp.80526 (%doc) File not found: /var/tmp/spamassassin-root/usr/share/spamassassin Any ideas please ? thanks and regards. David
Re: CPAN Install Fails
I've found that the 'make test' part of spamassassin fails when run as root on some machines. Since you need to run CPAN as root to install spamassassin I've found that it fails for me on most systems. A workaround I've done in the past is exiting cpan - finding the cpan source (usually /root/.cpan/build/packagename-random key) and running make test as non-root. This usually succeeds and I can also run make install from that directory to install it. Hope this helps -Chris H James Wilkinson wrote: Bob Cohen wrote: I'm running Fedora v9. All of the prerequisite and optional modules installed with no problem. Suggestions? Well, there’s always “install it with yum”: yum install spamassassin Hope this helps, James.
Re: Message flagged as spam missing original message
Matus - No I didn't pass the --headers option to spamc. All the other messages in my system include the original message - this is the only one out of millions that stripped it. -Chris H Matus UHLAR - fantomas wrote: On 02.09.08 12:01, Chris Henry wrote: The problem is that it appears that spamassassin stripped the original message out after it flagged it as spam. I am running Exim 4.63 with SpamAssassin 3.2.5 being called via procmail. don't you use the '--headers' option to spamc? It causes spamd return only headers...
spamassassin upgrade
Hi all ! I gave up trying to install spamassassin from rpms I made: Cpan install Mail::SpamAssassin I look up and the folder structure previously used by version 3.1.8 is the same. The program is still running, and I was able to use sa-update. So, it seems this is the best way to upgrade spamassassin. No package deps, no lib versions.. Anyone see any inconvenient ? Regards david
RE: spam bypass spamassassin
-Original Message- From: Rejaine Monteiro [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2008 7:19 AM To: users@spamassassin.apache.org Subject: spam bypass spamassassin Why this spam scored with 5.1 (requered 5.0) bypass spamassassin?? (clamdscan: 0.93/8144. spamassassin: 3.2.5. Clear:RC:0(aaa.bbb.ccc.ddd):SA:1(5.1/5.0):. Processed in 2.490743 secs); 03 Sep 2008 11:32:21 - X-Spam-Status: Yes, score=5.1 required=5.0 X-Spam-Level: + I'm also seeing this, it is not that it bypass Spamassassin but that it is not adding the Subject. I've lately been getting a lot of spam that score 5.1 the spam threshold is 5.0 but at 5.1 it does not change the subject. An example: Subject: Aaca aaiiuo Date: Mon, 1 Sep 2008 06:18:26 -0500 Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0018_01C90D17.8D566C70 X-Mailer: Microsoft Office Outlook 11 Thread-Index: AckMJHQQXzDI+JlySi+ENdpaQUGHHQM+ content-class: urn:content-classes:dsn x-originalarrivaltime: 01 Sep 2008 11:18:25.0639 (UTC) FILETIME=[73B55770:01C90C24] x-spam-level: + x-spam-status: Yes, score=5.1 required=5.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 x-dsncontext: 7ce717b1 - 1391 - 0002 - C00402D1 This is a multi-part message in MIME format. Notice the subject does not say *SPAM* which is what we have rewrite subject set to. J
Re: spam bypass spamassassin
Jason Esman wrote: -Original Message- From: Rejaine Monteiro [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2008 7:19 AM To: users@spamassassin.apache.org Subject: spam bypass spamassassin Why this spam scored with 5.1 (requered 5.0) bypass spamassassin?? (clamdscan: 0.93/8144. spamassassin: 3.2.5. Clear:RC:0(aaa.bbb.ccc.ddd):SA:1(5.1/5.0):. Processed in 2.490743 secs); 03 Sep 2008 11:32:21 - X-Spam-Status: Yes, score=5.1 required=5.0 X-Spam-Level: + I'm also seeing this, it is not that it bypass Spamassassin but that it is not adding the Subject. I've lately been getting a lot of spam that score 5.1 the spam threshold is 5.0 but at 5.1 it does not change the subject. An example: Subject: Aaca aaiiuo Date: Mon, 1 Sep 2008 06:18:26 -0500 Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0018_01C90D17.8D566C70 X-Mailer: Microsoft Office Outlook 11 Thread-Index: AckMJHQQXzDI+JlySi+ENdpaQUGHHQM+ content-class: urn:content-classes:dsn x-originalarrivaltime: 01 Sep 2008 11:18:25.0639 (UTC) FILETIME=[73B55770:01C90C24] x-spam-level: + x-spam-status: Yes, score=5.1 required=5.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 x-dsncontext: 7ce717b1 - 1391 - 0002 - C00402D1 This is a multi-part message in MIME format. Notice the subject does not say *SPAM* which is what we have rewrite subject set to. How do you call SA? if you call SA from a program that adds its own header (notice the case in the x-spam-* headers. here, they are X-Spam-...), then the same program is probably responsible for changing the subject. in which case, this is not an SA issue.
Re: CPAN Install Fails
On Sep 3, 2008, at 11:24 AM, Chris Henry wrote: I've found that the 'make test' part of spamassassin fails when run as root on some machines. Since you need to run CPAN as root to install spamassassin I've found that it fails for me on most systems. Here's some info I found on this issue. http://markmail.org/message/6rriowqf3brbntiv#query :t%2Fspamc_optC.t+page:2+mid:h5kfzxb2izwrdjmn+state:results A workaround I've done in the past is exiting cpan - finding the cpan source (usually /root/.cpan/build/packagename-random key) and running make test as non-root. This usually succeeds and I can also run make install from that directory to install it. How did you run make test as non-root? I ended up installing SpamAssassin from source and it worked fine. Of course maintenance will be a little more difficult but I just wanted to get the thing done. Bob Cohen Principal, MojoTools Web Design W: www.mojotools.com O: 508.384.0405
Re: CPAN Install Fails
Bob - You can give read permissions (if needed) on the SpamAssassin CPAN build folder (usually /root/.cpan/build/packagename-random-key - on my system it was: /root/.cpan/build/Mail-SpamAssassin-3.2.5-Bpy3vr) to some non-root user on your system - ie: bob as bob run make test in the /root/.cpan/build/packagename-random-key folder. If that succeeds then you can switch back to root and finish installing via make install. -Chris H Bob Cohen wrote: On Sep 3, 2008, at 11:24 AM, Chris Henry wrote: I've found that the 'make test' part of spamassassin fails when run as root on some machines. Since you need to run CPAN as root to install spamassassin I've found that it fails for me on most systems. Here's some info I found on this issue. http://markmail.org/message/6rriowqf3brbntiv#query:t%2Fspamc_optC.t+page:2+mid:h5kfzxb2izwrdjmn+state:results A workaround I've done in the past is exiting cpan - finding the cpan source (usually /root/.cpan/build/packagename-random key) and running make test as non-root. This usually succeeds and I can also run make install from that directory to install it. How did you run make test as non-root? I ended up installing SpamAssassin from source and it worked fine. Of course maintenance will be a little more difficult but I just wanted to get the thing done. Bob Cohen Principal, MojoTools Web Design W: www.mojotools.com O: 508.384.0405
USER_IN_DEF_WHITELIST wrongly triggers
I got the following spam, and am feeling that USER_IN_DEF_WHITELIST at -15 is not really the right thing to be doing - but I know there are often good reasons for the SA decisions. spamassassin -t says: -15 USER_IN_DEF_WHITELIST From: address is in the default white-list and this is misleading, as it's really the envelope sender: [7751] dbg: rules: address [EMAIL PROTECTED] matches (def_)whitelist_from_rcvd [EMAIL PROTECTED] yahoo.com [7751] dbg: rules: ran eval rule USER_IN_DEF_WHITELIST == got hit (1) So, I wonder: is the -15 really justified? why is [EMAIL PROTECTED] in the default whitelist? shouldn't addresses from senders known to use dkim/etc. only be recognized if a dkim signature is present (assuming there is dkim support). All that said, this is my first spam that got through because of USER_IN_DEF_WHITELIST, where got through means score 1.0. Return-Path: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on fnord.ir.bbn.com X-Spam-Level: X-Spam-Status: No, score=-7.7 required=1.0 tests=AWL,BAYES_99, SUBJECT_NEEDS_ENCODING,SUBJ_ILLEGAL_CHARS,TVD_SPACE_RATIO, USER_IN_DEF_WHITELIST autolearn=no version=3.2.5 X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from n6.smail.tw1.yahoo.com (n6.smail.tw1.yahoo.com [119.160.244.173]) by fnord.ir.bbn.com (Postfix) with ESMTP id B13A252A5 for [EMAIL PROTECTED]; Wed, 3 Sep 2008 19:24:26 -0400 (EDT) Received: from w1.mtf.tw1.yahoo.com (w1.mtf.tw1.yahoo.com [119.160.244.159]) by n6.smail.tw1.yahoo.com (Postfix) with ESMTP id 20EBA201FD7F; Thu, 4 Sep 2008 06:06:46 +0800 (CST) Received: (from [EMAIL PROTECTED]) by w1.mtf.tw1.yahoo.com (8.14.2/8.14.2) id m83M6j89036233; Thu, 4 Sep 2008 06:06:45 +0800 (CST) (envelope-from [EMAIL PROTECTED]) Date: Thu, 4 Sep 2008 06:06:45 +0800 (CST) Message-Id: [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Reply-To: [EMAIL PROTECTED] Subject: Yahoo!©_¼¯¥Í¬¡+ - ¤p¥i·R¤º·f¥un$9¤¸ Åwªï¦Û¨ú Errors-To: [EMAIL PROTECTED] X-Originating-IP: 218.172.243.237 X-Greylist: Delayed for 01:17:35 by milter-greylist-4.0 (fnord.ir.bbn.com [0.0.0.0]); Wed, 03 Sep 2008 19:24:26 -0400 (EDT) [EMAIL PROTECTED] [EMAIL PROTECTED] µ¹±zªº¯d¨¥¡G ¡¹¡¹¡¹¡¹´«©u ÅåÃz¶W§C»ù ¡¹¡¹¡¹¡¹ http://tw.f4.page.bid.yahoo.com/tw/auction/d34340110?u=may26tw ¤p¥i·R ®öº©©Ê·P¤º·f ¬y¦æ´Ú ¥un $ 9 ¤¸ ¤p¥i·R¤º·f¥un$9¤¸ Åwªï¦Û¨ú http://tw.lifestyle.yahoo.com/0229316c/080625/143/3urg1.html Yahoo!©_¼¯¥Í¬¡+ http://lifestyle.yahoo.com.tw/ ª©Åv©Ò¦³ Yahoo!©_¼¯
RE: CPAN Install Fails
-Original Message- From: James Wilkinson [mailto:[EMAIL PROTECTED] Sent: 3 September 2008 7:23 p.m. To: users@spamassassin.apache.org Subject: Re: CPAN Install Fails Bob Cohen wrote: I'm running Fedora v9. All of the prerequisite and optional modules installed with no problem. Suggestions? Well, there's always install it with yum: yum install spamassassin Hope this helps, James. Or, install it from source. I've had problems myself installing Spamassassin via CPAN, so many problems at a time, in fact, that I simply gave up and went with package management - which worked first time and every time after. Installation from source has been a bit more hairy, but nowhere near as hairy as a CPAN install. From what I have read on the net, it would appear that CPAN installs are best left alone unless you really know what you're doing and are willing to fix things before you get the product installed - but that's just _my opinion_. I don't want to tick anyone off on the list who really likes CPAN - I have nothing against it - I just don't use it :). 2cents. Cheers, Mike
Bayesian Test Oddities
I recently did a --force-expire on my bayesian database as I was getting some false positives with it and the information it in was getting to be over a year old. Since then, when automatically scanning, bayesian tests are not being run. This can be seen in the headers of each of my inbound emails. I took one of the messages that SpamAssassin did not tag as SPAM and ran it through manually (spamassassin -D emailfile) and bayesian tests were run, marking the message as high spam. Any ideas why the test is running when I manually scan a message, but not automatically as it was doing prior to the --force-expire? Thanks in advance.
Re: Bayesian Test Oddities
On Wed, 3 Sep 2008, Bill Gunty wrote: I recently did a --force-expire on my bayesian database as I was getting some false positives with it and the information it in was getting to be over a year old. Since then, when automatically scanning, bayesian tests are not being run. This can be seen in the headers of each of my inbound emails. I took one of the messages that SpamAssassin did not tag as SPAM and ran it through manually (spamassassin -D emailfile) and bayesian tests were run, marking the message as high spam. Any ideas why the test is running when I manually scan a message, but not automatically as it was doing prior to the --force-expire? Thanks in advance. Perhaps the automated scan is running under a different user than when you did a manual scan. It's common. -d
