hi guys, it's a NetAddr::IP regression. Mark Martinec said (on the
SA users list):
> Looks like a but in NetAddr::IP 4.034, it forgets to adjust the > CIDR mask
> when converting an IPv4 address to an IPv6 notation:
>
> correct (NetAddr-IP-4.033):
> $ perl -le 'use NetAddr::IP; print NetAddr::I
opened upstream as
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6157 . thanks
for spotting this...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Francesco, thanks for all that config! I was able to repro and fix the
bug (in 3.3.0 at least). Can you try out the patch at
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5989 and tell me
if it works for your site?
--j.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject o
Francesco Potorti` writes:
> Package: spamassassin
> Version: 3.2.5-1
> Severity: normal
>
> For each mail received, spamassassin logs 58 kB of errors of this type:
>
> Sep 5 18:25:04 tucano spamd[7793]:
> Subroutine __VBOUNCE_VALERT_one_line_body_test redefined at
> /var/lib/spamassassin/3
> > Now the problem is with -A:
> > # spamd -i ::1 -A ::1
> > [5654] warn: netset: illegal network address given: '::1'
> > [5654] error: spamd: aborting due to add_cidr error
> > spamd: aborting due to add_cidr error
>
> Hmm... it's another bug, this time in upstream code. And it doesn't look
>
On Tue, May 20, 2008 at 10:10:02AM -0400, Noah Meyerhans wrote:
> On Tue, May 20, 2008 at 06:20:33AM -0700, Daniel Burrows wrote:
> > A much larger amount of spam than usual got through my filters, I
> > think because most of my spam checks couldn't run due to this error.
> > After some confusio
Paul Wise writes:
> Package: spamassassin
> Version: 3.2.4-1
> Severity: normal
>
> I couldn't get spamassassin to start after upgrading to perl
> 5.10. Srangely it works with -D enabled, but then doesn't let you stop
> it. The issue seems to be a problem with sa-compile and a symbol removed
>
Thijs Kinkhorst writes:
> I suggest in README.Debian, where it says that re2c is a
> required package, also to mention that build-essential should be
> installed, or a specified subset thereof.
It may make more sense for re2c to require build-essential; re2c is
useless without a C compiler to com
Francois Marier writes:
> Hi Sven,
>
> On 2007-10-31 at 10:28:26, Sven Hartge wrote:
> > I don't think that changing the logcheck rules is a proper fix. If
> > making razor log via syslog changes the way spamd represents itself,
> > there must be somethin fishy going on which should be investigat
this is fixed in 3.2.x and SVN trunk, upstream.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
this has been fixed upstream for quite a while; see
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5361
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> I'm not sure we can right now. (The architecture is there so that we
> could handle it if we wanted to, but we'd better mitigate it if
> possible.)
That's my thinking -- the architecture is already there.
sa-update's DNS polling is incredibly lightweight and can handle millions
of clients upda
Marc A. Donges writes:
> sa-update being started from cron.daily is probably a DoS attack against
> Spamassassin update servers.
Actually, we can handle it just fine. We know what we're doing ;)
--j.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
Duncan Findlay writes:
> SpamAssassin uses DNS to test messages against various blacklists and
> such; so my guess is that these ports are open and awaiting DNS
> responses.
yep, this is definitely the case. UDP sockets are connectionless,
so the "listening" is required to receive responses from
David Muir Sharnoff writes:
>
> My problem can be traced to a change in the command line
> options. "--max-children N" changed to "--max-children=N".
>
> I suggest that the upgrade script edit /etc/default/spamassassin
> and do a simple regex change. Another option is to increase
> the default
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
> On Sat, Jan 07, 2006 at 09:37:51AM -0800, H. S. Teoh wrote:
> > tags 340753 + patch
> > thanks
> >
> > Hi,
> >
> > I've run into this same problem, and it's very annoying. So I made a
> > quick fix to cause spamd not to abor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Mehnle writes:
> package libmail-spf-query-perl
> owner 334687 !
> retitle 334687 libmail-spf-query-perl: Can't locate object method "new" via
> package "Net::DNS::RR::PTR"
> tags 334687 + moreinfo
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philip Armstrong writes:
> > This may not have been the wisest choice by the administrator
> > considering the circumstances, but I think it's hard to argue that
> > people should use an HELO string different from the rDNS...
>
> Quite. If I set it d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
HELO_DYNAMIC_DHCP and HELO_DYNAMIC_IPADDR both will not match if an ISP's
relay is used; they fire only if the "last untrusted" IP delivered them
directly.
They also do not act on rDNS; they act on HELO strings that match that
kind of rDNS. Major di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> spamassassin from stable (not very often) spits out this error (with
> libnet-dns-perl installed of course)
> Oct 19 00:40:30 filippo spamd[22604]: SPF: lookup failed: Can't locate
> object method "new" via
> +package "Net::DNS::RR::PTR" at /usr/lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Chubb writes:
> Should spamassassin depend on libsys-hostname-long-perl ?
no, but libmail-spf-query-perl should. that's the module which
is attempting to use Sys::Hostname::Long, iirc.
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
opened upstream as http://bugzilla.spamassassin.org/show_bug.cgi?id=4631
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFDS+6xMJF5cimLx9ARAvnAAKCcJj3D/juw2KLZB5Oih2yeG1ChswCdFJyM
6oerbfEu4kGL7/ttOrJTyp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Findlay writes:
> On Tue, Jul 19, 2005 at 12:09:12PM +0100, Gavin Love wrote:
> > I am wondering if this is a in the wild version of the remote DOS that
> > was reported against spamassassin previously and either the patch has
> > not been back
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
another nail in Storable's coffin as far as its use in SpamAssassin is
concerned ;) Good to hear that fixes the problem on your side.
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFCysQ4MJF5cimLx9AR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
please run spamd with -D and post the logfile it generates.
I suspect that a perl XS module is at fault, possibly DB_File (again).
- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFCOIWNMJF5cimLx9ARAgC6A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FWIW, that bug is MacOS X/BSD-specific, and I think is due to
a bug in perl on those platforms. Linux platforms should be
just fine.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFCNKODMJF5cimLx9ARAhKYAJ9UIc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
actually, it's not so simple.
> stat64("/home/asuffield/.spamassassin/bayes_toks.expire2054", 0xb580) =
> -1 ENOENT (No such file or directory)
this stat is performed by SpamAssassin code;
> open("/home/asuffield/.spamassassin/__db.bayes_toks.
27 matches
Mail list logo
