Re: spamassassin --lint fails - undefined symbol
I retried that and it still does the same thing. In make test however I find some errors, they dont seem to stop the process, so it appears as if Net::DNS can live without them, if you will. ## make test PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/00-load..ok t/00-pod...skipped all skipped: Test::Pod v0.95 required for testing POD t/00-version...ok t/01-resolver-env..ok t/01-resolver-file.ok 7/8 skipped: Could not read configuration file t/01-resolver-opt..ok t/01-resolver..ok 2/44 skipped: Tests may not run succesful from private IP(192.168.1.2) t/02-headerok t/03-question..ok t/04-packet-unique-pushok t/04-packetok t/05-rr-optok t/05-rr-rrsort.ok t/05-rr-sshfp..skipped all skipped: Digest::BubbleBabble not installed. t/05-rr-txtok t/05-rr-unknownok t/05-rrok t/06-updateok t/07-misc..ok t/08-onlineok t/09-tkey..ok t/10-recurse...skipped all skipped: Cannot run these tests from this IP:192.168.1.2 t/11-escapedchars..# Using the XS compiled dn_expand function t/11-escapedchars..ok 1/141# # disabling XS based dns_expand for a moment. # # Continuing to use the XS based dn_expand() t/11-escapedchars..ok t/11-inet6.ok 1/11# # The libraries needed for IPv6 support have been found # Now we establish if we can bind to ::1 # # # Testing for global IPv6 connectivity... #preparing... # #Will try to connect to ns-pri.ripe.net (193.0.0.195) # #Will try to connect to ns-pri.ripe.net (2001:610:240:0:53:0:0:3) # #Connection failed: Send error: Network is unreachable # #It seems you do not have global IPv6 connectivity' #This is not an error in Net::DNS #You can confirm this by trying 'ping6 2001:610:240:0:53:0:0:3' # # You can safely ignore the following message: # configuring 2001:610:240:0:53:0:0:3 193.0.0.195 as nameservers t/11-inet6.ok 7/11# #Trying to connect to ns-sec.ripe.net (2001:610:240:0:53:0:0:4) t/11-inet6.ok 3/11 skipped: various reasons All tests successful, 3 tests and 12 subtests skipped. Files=24, Tests=1039, 6 wallclock secs ( 3.65 cusr + 0.48 csys = 4.13 CPU) ### ### /usr/bin/perl -V Summary of my perl5 (revision 5 version 8 subversion 8) configuration: Platform: osname=linux, osvers=2.6.9-22.18.bz155725.elsmp, archname=i386-linux-thread-multi uname='linux hs20-bc1-6.build.redhat.com 2.6.9-22.18.bz155725.elsmp #1 smp thu nov 17 15:34:08 est 2005 i686 i686 i386 gnulinux ' config_args='-des -Doptimize=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -Dversion=5.8.8 -Dmyhostname=localhost [EMAIL PROTECTED] -Dcc=gcc -Dcf_by=Red Hat, Inc. -Dinstallprefix=/usr -Dprefix=/usr -Darchname=i386-linux -Dvendorprefix=/usr -Dsiteprefix=/usr -Duseshrplib -Dusethreads -Duseithreads -Duselargefiles -Dd_dosuid -Dd_semctl_semun -Di_db -Ui_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio -Dinstallusrbinperl=n -Ubincompat5005 -Uversiononly -Dpager=/usr/bin/less -isr -Dd_gethostent_r_proto -Ud_endhostent_r_proto -Ud_sethostent_r_proto -Ud_endprotoent_r_proto -Ud_setprotoent_r_proto -Ud_endservent_r_proto -Ud_setservent_r_proto -Dinc_version_list=5.8.7 5.8.6 5.8.5 5.8.4 5.8.3 -Dscriptdir=/usr/bin' hint=recommended, useposix=true, d_sigaction=define usethreads=define use5005threads=undef useithreads=define usemultiplicity=define useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='gcc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm', optimize='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables', cppflags='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include -I/usr/include/gdbm' ccversion='', gccversion='4.1.0 20060228 (Red Hat 4.1.0-1)', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
Re: spamassassin --lint fails - undefined symbol
Perl, Spamassassin and most of the modules were installed via Yum. I have currently uninstalled Spamassassin, Net::DNS + depeds, and am going to install via cpan. Funny thing was Mail::SPF::Query when I installed from cpan had a deped that was needed, and it was something like Mail::Hostheader or something. On 11/4/06, Mark [EMAIL PROTECTED] wrote: -Original Message- From: Dan McCullough [mailto:[EMAIL PROTECTED] Sent: zaterdag 4 november 2006 21:45 To: users@spamassassin.apache.org Subject: spamassassin --lint fails - undefined symbol su amavis -c 'spamassassin --lint' /usr/bin/perl: symbol lookup error: /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/auto/ Net/DNS/DNS.so: undefined symbol: Perl_sv_2uv_flags can someone tell me what I am doing wrong? Sound more like a library/perl mismatch issue. Are you sure /usr/bin/perl is the Perl you want? And not /usr/local/bin/perl or some such? Also, run /usr/bin/perl -V (the capital V), and see what its INC path is. Usually. something with site_perl comes first. And do an ldd /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/auto/Net/DNS/DNS. so, to see what libraries it needs itself. Or re-install Net::DNS, and make sure you run make test. - Mark
RE: spamassassin --lint fails - undefined symbol
-Original Message- From: Dan McCullough [mailto:[EMAIL PROTECTED] Sent: zondag 5 november 2006 15:00 To: users@spamassassin.apache.org Subject: Re: spamassassin --lint fails - undefined symbol Characteristics of this binary (from libperl): Compile-time options: MULTIPLICITY PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP USE_ITHREADS USE_LARGE_FILES USE_PERLIO USE_REENTRANT_API Built under linux Compiled at Mar 1 2006 18:29:53 @INC: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /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.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /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 /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /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.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 See, considering the INC path, you'd expect a newly compiled Net:DNS to be installed in the site_perl hierarchy, /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi, in this case. And NOT in the vendor_perl tree (where the base system resides). CPAN should install in site_perl, too. This has nothing to do with misconfigured DNS servers, btw. But everything with a missing symbol in a C library. Usual causes are inadvertent linkage against an older library during compilation time (when you install the software); or at run-time level. I would definitely give CPAN a try first. Should give you something shiny and new under site_perl. - Mark
Is the short circuit plugin available yet?
I'm looking to run SA on some mailing list mail that's constantly getting bombarded by asian spam. So I would like the check to be as efficient as possible such that as soon as I know the mail has asian character sets or unwanted language I don't want it to check any more. Any chance I can short circuit the additional checking once I know the mail is likely to be asian or unwanted language?
Re: spamassassin --lint fails - undefined symbol
Okay I got it to work about 30 minutes after sending, but right before I could send an email we had a power outage. :( Anyway I uninstalled serveral of the Yum installed perl modules and spamassassin and reinstalled via CPAN, while doing that one of the Net::DNS depeds said that there was a dependancy on another module that wasnt installed, so it downloaded and installed, I added everything back in and ran the command and it went through without a problem. :) So thanks everyone for the help. My advice should to those looking through the archive about a similar issue. Install from CPAN for SpamAssassin, it looks as if one of the perl mod rpms doesnt have all the depends properly accounted for. On 11/5/06, Mark [EMAIL PROTECTED] wrote: -Original Message- From: Dan McCullough [mailto:[EMAIL PROTECTED] Sent: zondag 5 november 2006 15:00 To: users@spamassassin.apache.org Subject: Re: spamassassin --lint fails - undefined symbol Characteristics of this binary (from libperl): Compile-time options: MULTIPLICITY PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP USE_ITHREADS USE_LARGE_FILES USE_PERLIO USE_REENTRANT_API Built under linux Compiled at Mar 1 2006 18:29:53 @INC: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /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.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /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 /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /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.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 See, considering the INC path, you'd expect a newly compiled Net:DNS to be installed in the site_perl hierarchy, /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi, in this case. And NOT in the vendor_perl tree (where the base system resides). CPAN should install in site_perl, too. This has nothing to do with misconfigured DNS servers, btw. But everything with a missing symbol in a C library. Usual causes are inadvertent linkage against an older library during compilation time (when you install the software); or at run-time level. I would definitely give CPAN a try first. Should give you something shiny and new under site_perl. - Mark
RE: Amazon / RFCI false positives
On Sat, 4 Nov 2006, Michael Scheidell wrote: So? Build something better. Its open source. Don't use the RFCI scores, drop them, stop bithing about somehting YOU can change. Well, I've added a -2 for email from Amazon, but I thought other people might like a warning. No need to flame someone who's trying to help. Tony. -- f.a.n.finch [EMAIL PROTECTED] http://dotat.at/ THAMES: WEST OR NORTHWEST 4 OR 5. SLIGHT TO MODERATE. FAIR. GOOD.
Re: R: R: R: Relay Checker Plugin (code review please?)
On 1 Nov 2006, Andreas Pettersson stated: Steven Dickenson wrote: I can't agree with this. Many small businesses in the US get just these kind of static connections from broadband ISPs. Comcast, for example, has all of their static customers using rDNS that would fail your tests, and they refuse to set up a custom PTR record or delegate the record to someone else. I disagree on your disagreement. This is my opinion: If you don't have control over your rDNS, do NOT run any mail server, unless you relay all outbound mail through a server at your ISP. What if you don't *have* a server at your ISP that you can relay your mail through, because your ISP expects you to send mail directly from your own mailserver? What if your ISP provides a server but it is horrifically unreliable? Most of these static customers are legitimate business networks running their own mail server, and have neither the need nor desire to relay their mail through Comcast's SMTP servers. I think your general idea is very good, but you're reaching a little too far with this one. 'No need nor desire', that's not really any good excuse. Use a relay or find your mail rejected, I'd say. Charming. They're not spammers, but you want to punish them as if they were, because reality makes your tests too complicated. -- `When we are born we have plenty of Hydrogen but as we age our Hydrogen pool becomes depleted.'
Re: R: Relay Checker Plugin (code review please?)
On 31 Oct 2006, John Rudd verbalised: And, while I may be a little unyielding wrt to people whose ISPs are like Telecom Italia, I'm not unsympathetic. I think, in this case, if Italy did get mass quarantined by the rest of the world, it might cause enough of an uproar to force Telecom Italia to change its practices and allow custom RDNS. SPEWS tried that. It didn't really work :( -- `When we are born we have plenty of Hydrogen but as we age our Hydrogen pool becomes depleted.'
Re: R: R: R: Relay Checker Plugin (code review please?)
Nix wrote: On 1 Nov 2006, Andreas Pettersson stated: Steven Dickenson wrote: I can't agree with this. Many small businesses in the US get just these kind of static connections from broadband ISPs. Comcast, for example, has all of their static customers using rDNS that would fail your tests, and they refuse to set up a custom PTR record or delegate the record to someone else. I disagree on your disagreement. This is my opinion: If you don't have control over your rDNS, do NOT run any mail server, unless you relay all outbound mail through a server at your ISP. What if you don't *have* a server at your ISP that you can relay your mail through, because your ISP expects you to send mail directly from your own mailserver? What if your ISP provides a server but it is horrifically unreliable? In those two cases: Go to a service that hosts web/email servers under your custom domain, and relay through your own hosted server. They exist. Some of them aren't expensive at all. Most of these static customers are legitimate business networks running their own mail server, and have neither the need nor desire to relay their mail through Comcast's SMTP servers. I think your general idea is very good, but you're reaching a little too far with this one. 'No need nor desire', that's not really any good excuse. Use a relay or find your mail rejected, I'd say. Charming. They're not spammers, but you want to punish them as if they were, because reality makes your tests too complicated. Punishing them would be blocking them outright. Quarantining them is merely recognizing that they haven't obtained a class of service that would indicate a well configured and well maintained email server, as opposed to a fly-by-night or rinky-dink operation running on a bottom-feeder ISP's network ... characteristics that would indicate that the ISP is careless and not diligent, or that their customers have no care nor concern about their quality of service, either one making it more likely that I am dealing with a spambot or an open-relay. So, I make them jump through an extra hoop in order to get through to me. That extra hoop is either a) going through my quarantine process, or b) paying for a hosted service with proper RDNS. Either don't look like part of a botnet or accept being in my quarantine all of the time. It is not my obligation to accept nor view every email that hits my server. It is my prerogative to establish whatever hurdles I want to in getting through to my email inbox. It's not punishment, as punishment implies that I am removing your rights or privileges ... which doesn't apply, because you have no rights nor privileges with regard to my inbox. And, the fact is, the people you're trying to raise as a counter-case, are not only such a minority that they aren't on my radar, they're such a minority that they don't exist at all in my 15 months of experience in doing these checks. Every sender which has connected to my machines, without being on my own subnet, nor performing SMTP-AUTH, and without passing these checks, has been sending spam or a virus. Without exception. I realize that not everyone else is going to have the same experience with their email traffic that I do, which is why I'm making the plugin ever more flexible. First, I set a preference for just skipping some tests. Then, last night, I removed the hard-coded dynhostname and clienthostname checks. Now there's a keyword check, with the keywords used being supplied in the cf file. So, each site can set their own keyword requirement ... or leave it blank and skip that check entirely. (I haven't released this new code yet)
Re: R: R: R: Relay Checker Plugin (code review please?)
I like the ability to give individual scores to the various tests... Per my patch.. Allows for minor tweaking for each kind of issue. - Original Message - From: John Rudd [EMAIL PROTECTED] To: Nix [EMAIL PROTECTED] Cc: Andreas Pettersson [EMAIL PROTECTED]; Steven Dickenson [EMAIL PROTECTED]; Giampaolo Tomassoni [EMAIL PROTECTED]; users@spamassassin.apache.org Sent: Sunday, November 05, 2006 1:57 PM Subject: Re: R: R: R: Relay Checker Plugin (code review please?) Nix wrote: On 1 Nov 2006, Andreas Pettersson stated: Steven Dickenson wrote: I can't agree with this. Many small businesses in the US get just these kind of static connections from broadband ISPs. Comcast, for example, has all of their static customers using rDNS that would fail your tests, and they refuse to set up a custom PTR record or delegate the record to someone else. I disagree on your disagreement. This is my opinion: If you don't have control over your rDNS, do NOT run any mail server, unless you relay all outbound mail through a server at your ISP. What if you don't *have* a server at your ISP that you can relay your mail through, because your ISP expects you to send mail directly from your own mailserver? What if your ISP provides a server but it is horrifically unreliable? In those two cases: Go to a service that hosts web/email servers under your custom domain, and relay through your own hosted server. They exist. Some of them aren't expensive at all. Most of these static customers are legitimate business networks running their own mail server, and have neither the need nor desire to relay their mail through Comcast's SMTP servers. I think your general idea is very good, but you're reaching a little too far with this one. 'No need nor desire', that's not really any good excuse. Use a relay or find your mail rejected, I'd say. Charming. They're not spammers, but you want to punish them as if they were, because reality makes your tests too complicated. Punishing them would be blocking them outright. Quarantining them is merely recognizing that they haven't obtained a class of service that would indicate a well configured and well maintained email server, as opposed to a fly-by-night or rinky-dink operation running on a bottom-feeder ISP's network ... characteristics that would indicate that the ISP is careless and not diligent, or that their customers have no care nor concern about their quality of service, either one making it more likely that I am dealing with a spambot or an open-relay. So, I make them jump through an extra hoop in order to get through to me. That extra hoop is either a) going through my quarantine process, or b) paying for a hosted service with proper RDNS. Either don't look like part of a botnet or accept being in my quarantine all of the time. It is not my obligation to accept nor view every email that hits my server. It is my prerogative to establish whatever hurdles I want to in getting through to my email inbox. It's not punishment, as punishment implies that I am removing your rights or privileges ... which doesn't apply, because you have no rights nor privileges with regard to my inbox. And, the fact is, the people you're trying to raise as a counter-case, are not only such a minority that they aren't on my radar, they're such a minority that they don't exist at all in my 15 months of experience in doing these checks. Every sender which has connected to my machines, without being on my own subnet, nor performing SMTP-AUTH, and without passing these checks, has been sending spam or a virus. Without exception. I realize that not everyone else is going to have the same experience with their email traffic that I do, which is why I'm making the plugin ever more flexible. First, I set a preference for just skipping some tests. Then, last night, I removed the hard-coded dynhostname and clienthostname checks. Now there's a keyword check, with the keywords used being supplied in the cf file. So, each site can set their own keyword requirement ... or leave it blank and skip that check entirely. (I haven't released this new code yet)
Re: Is the short circuit plugin available yet?
On Sun, 5 Nov 2006, Robert Nicholson wrote:
I'm looking to run SA on some mailing list mail that's constantly
getting bombarded by asian spam.
So I would like the check to be as efficient as possible such that
as soon as I know the mail has asian character sets or unwanted
language I don't want it to check any more. Any chance I can short
circuit the additional checking once I know the mail is likely to
be asian or unwanted language?
Don't limit yourself to options within SA if you can do MTA checks. As
a slash-and-burn tactic you can RBL large regions of asia (using e.g.
cn.countries.nerd.dk, tw.countries.nerd.dk)
Of course, that won't catch asian-language messages originating
elsewhere, and isn't language-sensitive.
You might also want to take a look at milter-regex. Here's what I use
on my MTA:
reject Sorry - only English spoken here
header /Subject/i
/=[?](KOI8-[RU]|GB2312|GB2312_CHARSET|ISO-2022-JP|SHIFT[-_]JIS|BIG5|WINDOWS-125[15])[?][QB][?]/ie
header /Subject/i
/charset=(3D)??(KOI8-[RU]|GB2312|GB2312_CHARSET|ISO-2022-JP|SHIFT[-_]JIS|BIG5)/ie
header /Subject/i /[?-?]{6}/e
header /Content-Type/i ,text/(plain|html);
*charset=?(KOI8-[RU]|GB2312(_CHARSET)?|ISO-2022-JP|SHIFT[-_]JIS|BIG5),ie
body ,Content-Type(: | content=)text/(plain|html);
charset=?(KOI8-[RU]|GB2312(_CHARSET)?|ISO-2022-JP|SHIFT[-_]JIS|BIG5),ie
body ,http-equiv=3DContent-Type content=3Dtext/(plain|html);
charset=3D(KOI8-[RU]|GB2312|ISO-2|SHIFT|BIG5),ie
--
John Hardin KA7OHZICQ#15735746http://www.impsec.org/~jhardin/
[EMAIL PROTECTED]FALaholic #11174pgpk -a [EMAIL PROTECTED]
key: 0xB8732E79 - 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
---
If someone has a gun and is trying to kill you, it would be
reasonable to shoot back with your own gun.
-- the Dalai Lama, May 15, 2001
---
2 days until the campaign ads stop
RE: Amazon / RFCI false positives
On Sun, 5 Nov 2006, Tony Finch wrote: Well, I've added a -2 for email from Amazon, but I thought other people might like a warning. No need to flame someone who's trying to help. RFCi and SA is a somewhat sensitive topic here, as you'll see if you check the archives from about a month back. I'm assuming you weren't on-list the last time this came up, or you probably wouldn't have mentioned it. :) -- John Hardin KA7OHZICQ#15735746http://www.impsec.org/~jhardin/ [EMAIL PROTECTED]FALaholic #11174pgpk -a [EMAIL PROTECTED] key: 0xB8732E79 - 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- If someone has a gun and is trying to kill you, it would be reasonable to shoot back with your own gun. -- the Dalai Lama, May 15, 2001 --- 2 days until the campaign ads stop
Spamc not working, spamassassin is.
Help! I am trying to get spamassassin 3.1.7 working with net-qmail 1.05 and vpopmail 5.4.16. It's not going too well. I have the QMAILQUEUE patch applied and am using the qmail-scanner-queue.pl script in an attempt to get spamassassin working. The juxt of the problem: scanc is reporting all emails back with a score of 0, where if I send the same email through spamassassin itself, the email gets scored properly. I am running scanc with no options. scand is running with the following options: -d -C /etc/mail/spamassassin -m 5 -v -u qscand --nouser-config The headers are being added to emails as they pass through, but every email scores at 0.0 - even the gtube email. If I run spamc /root/.cpan/Mail-SpamAssassin-3.1.7/sample-spam.txt - it comes back with a score of 0.0. If I run spamassassin /root/.cpan/Mail-SpamAssassin-3.1.7/sample-spam.txt, it comes back with a score of 998.5. I am not seeing any indications of errors in /var/log/maillog or anywhere else. spamassassin --lint reports nothing. What am I doing wrong here? ROn
Re: Is the short circuit plugin available yet?
Robert Nicholson writes: I'm looking to run SA on some mailing list mail that's constantly getting bombarded by asian spam. So I would like the check to be as efficient as possible such that as soon as I know the mail has asian character sets or unwanted language I don't want it to check any more. Any chance I can short circuit the additional checking once I know the mail is likely to be asian or unwanted language? If you start using SVN trunk -- unreleased code -- you can use Shortcircuit. That check would work nicely ;) for what it's worth, I use SVN trunk on my own personal MX and it works great there... --j.
Re: Spamc not working, spamassassin is.
Can you copy/paste your header here please? The one with spamd and the one with spamassassin .2006/11/5, Ron Gage [EMAIL PROTECTED]: Help!I am trying to get spamassassin 3.1.7 working with net-qmail 1.05 and vpopmail 5.4.16.It's not going too well.I have the QMAILQUEUE patch applied and am using theqmail-scanner-queue.pl script in an attempt to get spamassassin working.The juxt of the problem: scanc is reporting all emails back with a score of 0, where if I send the same email through spamassassin itself, theemail gets scored properly.I am running scanc with no options.scand is running with the followingoptions: -d -C /etc/mail/spamassassin -m 5 -v -u qscand --nouser-config The headers are being added to emails as they pass through, but everyemail scores at 0.0 - even the gtube email.If I run spamc /root/.cpan/Mail-SpamAssassin-3.1.7/sample-spam.txt -it comes back with a score of 0.0.If I run spamassassin /root/.cpan/Mail-SpamAssassin-3.1.7/sample-spam.txt, it comes back witha score of 998.5.I am not seeing any indications of errors in /var/log/maillog oranywhere else.spamassassin --lint reports nothing. What am I doing wrong here?ROn
Re: Spamc not working, spamassassin is.
François Rousseau wrote: Can you copy/paste your header here please? The one with spamd and the one with spamassassin . [EMAIL PROTECTED]:~/.cpan/build/Mail-SpamAssassin-3.1.7# spamc sample-spam.txt X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on host-l1.mi-connect.com X-Spam-Level: X-Spam-Status: No, score=0.0 required-5.0 tests=none autolearn=unavailable version=3.1.7 X-Spam-Report: Subject: Test spam mail (GTUBE) Message-ID: [EMAIL PROTECTED] Date: Wed, 23 Jul 2003 23:30:00 +0200 From: Sender [EMAIL PROTECTED] To: Recipient [EMAIL PROTECTED] Precedence: junk MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit [EMAIL PROTECTED]:~/.cpan/build/Mail-SpamAssassin-3.1.7# spamassassin sample-spam.txt X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on host-l1.mi-connect.com X-Spam-Level: ** X-Spam-Status: Yes, score=999.3 required-5.0 tests=AWL,GTUBE,NO_RECEIVED, NO_RELAYS autolearn=no version=3.1.7 X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP * 1000 GTUBE BODY: Generic Test for Unsolicited Bulk Email * -0.0 NO_RECEIVED Informational: message has no Received headers * -0.7 AWL AWL: From: address is in the auto white-list Subject: 1 Test spam mail (GTUBE) Message-ID: [EMAIL PROTECTED] Date: Wed, 23 Jul 2003 23:30:00 +0200 From: Sender [EMAIL PROTECTED] To: Recipient [EMAIL PROTECTED] Precedence: junk MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Prev-Subject: Test spam mail (GTUBE) 2006/11/5, Ron Gage [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Help! I am trying to get spamassassin 3.1.7 working with net-qmail 1.05 and vpopmail 5.4.16. It's not going too well. I have the QMAILQUEUE patch applied and am using the qmail-scanner-queue.pl script in an attempt to get spamassassin working. The juxt of the problem: scanc is reporting all emails back with a score of 0, where if I send the same email through spamassassin itself, the email gets scored properly. I am running scanc with no options. scand is running with the following options: -d -C /etc/mail/spamassassin -m 5 -v -u qscand --nouser-config The headers are being added to emails as they pass through, but every email scores at 0.0 - even the gtube email. If I run spamc /root/.cpan/Mail-SpamAssassin-3.1.7/sample-spam.txt - it comes back with a score of 0.0. If I run spamassassin /root/.cpan/Mail-SpamAssassin-3.1.7/sample-spam.txt, it comes back with a score of 998.5. I am not seeing any indications of errors in /var/log/maillog or anywhere else. spamassassin --lint reports nothing. What am I doing wrong here? ROn
spam filter working, but not well
Hi all, Spam filtering is working, but I'm getting about half the spam in my mailbox. Anyone have tips on adjustments I could make? Here's what I have in the local.cf file: rewrite_header SUBJECT **SPAM** dns_available yes required_score 4.0 bayes_path /etc/mail/spamassassin/bayesfiles/bayes use_bayes 1 bayes_auto_learn 1 bayes_auto_learn_threshold_spam 10 bayes_file_mode 0777 report_safe 0 trusted_networks 192.168.1.101 bayes_ignore_header X-purgate bayes_ignore_header X-purgate-ID bayes_ignore_header X-purgate-Ad bayes_ignore_header X-GMX-Antispam bayes_ignore_header X-Antispam bayes_ignore_header X-Spamcount bayes_ignore_header X-Spamsensitivity Thanks, Brian -- All people who think everything is either black or white are idiots.
Re: spam filter working, but not well
On Sunday 05 November 2006 15:48, Brian S. Meehan wrote: Hi all, Spam filtering is working, but I'm getting about half the spam in my mailbox. Anyone have tips on adjustments I could make? Here's what I have in the local.cf file: rewrite_header SUBJECT **SPAM** dns_available yes required_score 4.0 bayes_path /etc/mail/spamassassin/bayesfiles/bayes use_bayes 1 bayes_auto_learn 1 bayes_auto_learn_threshold_spam 10 bayes_file_mode 0777 report_safe 0 trusted_networks 192.168.1.101 bayes_ignore_header X-purgate bayes_ignore_header X-purgate-ID bayes_ignore_header X-purgate-Ad bayes_ignore_header X-GMX-Antispam bayes_ignore_header X-Antispam bayes_ignore_header X-Spamcount bayes_ignore_header X-Spamsensitivity Its not clear if you have network tests running or not. How is spamassassin invoked? -- _ John Andersen pgpwTBBRp147g.pgp Description: PGP signature
Re: Spamc not working, spamassassin is.
Ron Gage wrote: Help! I am trying to get spamassassin 3.1.7 working with net-qmail 1.05 and vpopmail 5.4.16. It's not going too well. I have the QMAILQUEUE patch applied and am using the qmail-scanner-queue.pl script in an attempt to get spamassassin working. The juxt of the problem: scanc is reporting all emails back with a score of 0, where if I send the same email through spamassassin itself, the email gets scored properly. I am running scanc with no options. scand is running with the following options: -d -C /etc/mail/spamassassin -m 5 -v -u qscand --nouser-config Please remove that -C /etc/mail/spamassassin from your spamd command line. -C should have the DEFAULT rules directory, not the site rules directory. By adding that, you're effectively eliminating /usr/share/spamassassin from your configuration.
Re: Spamc not working, spamassassin is.
Matt Kettler wrote: Ron Gage wrote: Help! I am trying to get spamassassin 3.1.7 working with net-qmail 1.05 and vpopmail 5.4.16. It's not going too well. I have the QMAILQUEUE patch applied and am using the qmail-scanner-queue.pl script in an attempt to get spamassassin working. The juxt of the problem: scanc is reporting all emails back with a score of 0, where if I send the same email through spamassassin itself, the email gets scored properly. I am running scanc with no options. scand is running with the following options: -d -C /etc/mail/spamassassin -m 5 -v -u qscand --nouser-config Please remove that -C /etc/mail/spamassassin from your spamd command line. -C should have the DEFAULT rules directory, not the site rules directory. By adding that, you're effectively eliminating /usr/share/spamassassin from your configuration. This appears to have done it. Thank you VERY much! Ron
RE: Amazon / RFCI false positives
On Sat, November 4, 2006 02:34, Tony Finch wrote: On Fri, 3 Nov 2006, Michael Scheidell wrote: Not a false positive if their servers are broken. True from the RFCI point of view, but NOT true from the SpamAssassin point of view. These messages are wanted by their recipients so should not be scored as spam by SpamAssassin. complains go to spamassassin not to amazon.com ? what a wonderfull world this is :/ -- This message was sent using 100% recycled spam mails.
Re: R: R: BIG increase in spam today
On Fri, November 3, 2006 11:53, Giampaolo Tomassoni wrote: Due to the dynamic nature of this test, I guess that at least in the postfix case it should need to be somehow embedded into the greylisting server: it seems postfix doesn't allow to specify more than one policy server in the check_policy_service directive. can be made with a combo of restriction classes and policy restrictions on postfix, how you do this is your problem :-) -- This message was sent using 100% recycled spam mails.
Bayes 0.5 on everything
What would cause all messages to score 0.5 on everything?
