On Sun, Sep 10, 2006 at 11:14:13AM -0500, Steven Stern wrote:
> The following appears periodically in my maillog. I think it has to do
> with an attempt to do a cpan upgrade or SpamAssassin that I had to back
> out and replace with the Fedora RPM. In any case, is this anything to
> worry about?
I
The following appears periodically in my maillog. I think it has to do
with an attempt to do a cpan upgrade or SpamAssassin that I had to back
out and replace with the Fedora RPM. In any case, is this anything to
worry about?
Sep 10 11:12:30 mooch spamd[26250]: (?:(?<=[\s,]))* matches null strin
I updated my SA to 3.1.0 recently (from the last 3.x release - FreeBSD
port), and I just caught this error:
Sep 25 22:50:17 forrie spamd[86764]: Can't call method "finish" on an
undefined value at
/usr/local/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Plugin/AWL.pm
line 397, line 94.
While
On Monday 31 January 2005 09:47 am, Martin Schröder wrote:
> On 2005-01-31 15:41:13 +, Ron McKeating wrote:
> > Shutting down spamd: [ OK ]
> > Starting spamd: Could not create INET socket on 127.0.0.1:783: Address
> > already in use (IO::Socket::INET: Address already in use)
> > [FAILED]
> >
At 07:41 AM 1/31/2005, you wrote:
We have a cron job which shuts down spamd and restarts it every hour.
Since we upgraded to the latest version of SA 3 one of our server keeps
giving this error.
Shutting down spamd: [ OK ]
Starting spamd: Could not create INET socket on 127.0.0.1:783: Address
alr
On 2005-01-31 15:41:13 +, Ron McKeating wrote:
> Shutting down spamd: [ OK ]
> Starting spamd: Could not create INET socket on 127.0.0.1:783: Address
> already in use (IO::Socket::INET: Address already in use)
> [FAILED]
>
> Any thoughts as to why this shuold happen?
The restart is too soon
We have a cron job which shuts down spamd and restarts it every hour.
Since we upgraded to the latest version of SA 3 one of our server keeps
giving this error.
Shutting down spamd: [ OK ]
Starting spamd: Could not create INET socket on 127.0.0.1:783: Address
already in use (IO::Socket::INET: Ad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 22. Dezember 2004 18:14 schrieb Ryan Pavely:
> Well your email did bring me to an interesting observation.
> I am using SpamC for SA 3.0, and had upgraded from SA 2.63
>
> Notice the layout of my error message.. although ALL machines tha
At 12:14 PM 12/22/2004, Ryan Pavely wrote:
Well your email did bring me to an interesting observation.
I am using SpamC for SA 3.0, and had upgraded from SA 2.63
Notice the layout of my error message.. although ALL machines that run
spamc (/usr/local/bin/spamc) are 3.0 somehow
my error is displ
Well your email did bring me to an interesting observation.
I am using SpamC for SA 3.0, and had upgraded from SA 2.63
Notice the layout of my error message.. although ALL machines that run
spamc (/usr/local/bin/spamc) are 3.0 somehow
my error is displaying the SA 2.63 help message!
That's pretty
At 08:55 AM 12/22/2004, you wrote:
-H Randomize IP addresses for the looked-up
hostname.
My bad, sorry. Worth a try though. Sometimes you miss the obvious. :)
-H Randomize IP addresses for the looked-up
hostname.
Ryan Pavely
Director Research And Development
Net Access Corporation
Evan Platt wrote:
At 08:32 AM 12/22/2004, you wrote:
Since my upgrade to SA 3.0 I have a few more timeouts on occasion.
Therefore I
At 08:32 AM 12/22/2004, you wrote:
Since my upgrade to SA 3.0 I have a few more timeouts on occasion.
Therefore I decided to test adding -x to my .qmail spamc line.
eg. |/usr/local/bin/spamc -x -H -d spamd.nac.net -u [EMAIL PROTECTED]
On occasion I get a message here and there that looks like this.
Since my upgrade to SA 3.0 I have a few more timeouts on occasion.
Therefore I decided to test adding -x to my .qmail spamc line.
eg. |/usr/local/bin/spamc -x -H -d spamd.nac.net -u [EMAIL PROTECTED]
On occasion I get a message here and there that looks like this...
Return-Path: <[EMAIL PROTECTE
14 matches
Mail list logo
