New bug in sa-update

Hi everyone. I've discovered a new bug in sa-update after I noticed some blatant porn spam in my inbox today. Manually running sa-update resulted in the following output: http: GET http://www.sa-update.pccc.com/3.tar.gz request failed: 404 Not Found:

Re: sa-update not updating since March 30.

John Hardin wrote: > > On Mon, 1 Jun 2009, Ernie Dunbar wrote: > >> We have a cron job that runs every day to update the spamassassin rules, >> but there have been no new updates since March 30. > > That's because there haven't been any updates rece

sa-update not updating since March 30.

We have a cron job that runs every day to update the spamassassin rules, but there have been no new updates since March 30. When I run it manually with the -D (debug) flag, I get this output: [24667] dbg: logger: adding facilities: all [24667] dbg: logger: logging level is DBG [24667] dbg: gener

Colored-in table attack.

This week, we've been getting plenty of Viagra spam from one spammer who is using a very large HTML table (180+ 's) with a space in each table data field. The spammer then creates his message (or usually, just a word) by using the bgcolor tag in certain table data fields. An example is provide

Re: So you wanted to firewall your mail server...

Daryl C. W. O wrote: > > Ernie Dunbar wrote: >> >> >> Ken A wrote: >>>> May 11 12:00:09 pop spamd[47940]: dns: sendto() failed: No route to >>>> host >>>> Host: 190.57.78.66.bl.spamcop.net. at >>>> /usr/local/lib/p

Re: So you wanted to firewall your mail server...

Ken A wrote: > >> May 11 12:00:09 pop spamd[47940]: dns: sendto() failed: No route to host >> Host: 190.57.78.66.bl.spamcop.net. at >> /usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/DnsResolver.pm >> line >> 340, line 137. >> >> Of course, hosts like 190.57.78.66.bl.spamcop.net are D

Re: So you wanted to firewall your mail server...

Theo Van Dinter-2 wrote: > > On Fri, May 11, 2007 at 01:34:06PM -0700, Ernie Dunbar wrote: >> Of course, hosts like 190.57.78.66.bl.spamcop.net are DNSBL blacklist >> members, and they resolve to nothing at all, which is why there is no >> route >> to host. But

So you wanted to firewall your mail server...

We just put our mailserver (with SpamAssassin of course) behind a firewall, and now we get many many interesting error messages from spamd telling me that there's no route to some host or other. I tweaked the DnsResolver.pm module to show what host it was trying to route to, and I got this output:

Rulesdujour is broken?

In another thread, I noticed that someone had a SARE ruleset for stock scams and the like. Since they had been plaguing us constantly in recent months, I decided I should get rules_du_jour to update that ruleset for us. I quickly found out that rules_du_jour was horribly out of date on our system,

Problems upgrading to SA 3.1.0 from 3.0.4

I'm running SpamAssassin on FreeBSD 4.9, with perl 5.6.1, and I'll be hooking it up to qmail once it's working properly. :) I upgraded from SA-3.0.4 to SA-3.1.0 today, and the make seemed to work fine, but starting spamd spews forth copious error messages that are included at the bottom of this e-

RE: Spamd children starting as root?

> Rick Macdougall wrote: >> [EMAIL PROTECTED] wrote: >>> Ernie Dunbar wrote: >>> /usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10 >> The spamd children start out as the correct user >> but over time (I'm assuming when max-connections are h

Re: Spamd children starting as root?

> [EMAIL PROTECTED] wrote: >> Ernie Dunbar wrote: >> >>>I'm running Spamassassin v3.0.0 on FreeBSD 4.9-RELEASE, and I >>>run spamd like this: >>> >>>/usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10 >> >> >&g

Spamd children starting as root?

I'm running Spamassassin v3.0.0 on FreeBSD 4.9-RELEASE, and I run spamd like this: /usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10 When I use `ps aux |grep spamd` I get this: spamc 61970 0.5 3.9 21292 20032 ?? Is3:04PM 0:00.47 /usr/local/bin/spamd -A 127.0.0.1 -L -x -u

Re: Odd syslog errors.

> Ernie Dunbar wrote: >>>>Oct 5 13:26:39 pop spamd[19660]: Cannot open bayes databases >>>>/home/spamc/.spamassassin/bayes_* R/O: tie failed: Permission denied >>>> Oct >>> >>>The typical cause of this is that the file ownership changed

Re: Odd syslog errors.

> On Wed, 6 Oct 2004, Ernie Dunbar wrote: > >> Every hour or so, it spews forth a dozen or so messages like this: >> >> Oct 5 13:26:25 pop spamd[267]: server hit by SIGCHLD >> Oct 5 13:26:25 pop spamd[267]: handled cleanup of child pid 9980 >> Oct 5 13:26:25

Odd syslog errors.

I'm running spamassassin 3.0.0 on FreeBSD 4.9-STABLE with the spamd daemon accepting connections locally from qmail-scanner for all incoming mail. Our server does some 80K messages per day. Spamd runs like this: /usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10 Every hour or so, it spews