Re: spurious __alarm__ messages in spamd log

2005-08-22 Thread Andy Jezierski
Steve Martin <[EMAIL PROTECTED]> wrote on 08/20/2005 12:42:44 AM: > Sat Aug 20 00:28:36 2005 [16014] info: spamd: processing message   > <[EMAIL PROTECTED]> for filter:88 > Sat Aug 20 00:28:42 2005 [16014] error: __alarm__ > Sat Aug 20 00:28:42 2005 [16014] error: __alarm__ > Sat Aug 20 00:28:49

Re: spurious __alarm__ messages in spamd log

2005-08-20 Thread Justin Mason
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sander Holthaus - Orange XL writes: > Steve Martin wrote: > > Sat Aug 20 00:28:36 2005 [16014] info: spamd: processing > > message <[EMAIL PROTECTED]> for filter:88 > > Sat Aug 20 00:28:42 2005 [16014] error: __alarm__ Sat Aug 20 > > 00:28:42 2005 [16

RE: spurious __alarm__ messages in spamd log

2005-08-20 Thread Sander Holthaus - Orange XL
Steve Martin wrote: > Sat Aug 20 00:28:36 2005 [16014] info: spamd: processing > message <[EMAIL PROTECTED]> for filter:88 > Sat Aug 20 00:28:42 2005 [16014] error: __alarm__ Sat Aug 20 > 00:28:42 2005 [16014] error: __alarm__ Sat Aug 20 00:28:49 > 2005 [16014] info: spamd: identified spam > (35.1/

RE: spurious __alarm__ messages in spamd log

2005-08-20 Thread Herb Martin
> -Original Message- > From: Loren Wilton [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 20, 2005 10:26 AM > To: users@spamassassin.apache.org > Subject: Re: spurious __alarm__ messages in spamd log > > I suspect __alarm__ is the result of a unix alarm() functi

Re: spurious __alarm__ messages in spamd log

2005-08-20 Thread Loren Wilton
I suspect __alarm__ is the result of a unix alarm() function that is used to set a timeout. Probably has set a timeout for some function, and then succeeded in the function before the timeout and forgotten to clear the timeout. It then hits some other poor unsuspecting function. Alternately AS m

RE: spurious __alarm__ messages in spamd log

2005-08-20 Thread Ed Kasky
On Sat, 20 Aug 2005, Dallas L. Engelken wrote: Anyone know how one might track these down (what debug areas to start with)? I've seen 2 in the last 30 hours or so. Rerunning the same message through with spamc gives the same score, but no __alarm__ messages. SA 3.1rc1 I started to debug thi

Re: spurious __alarm__ messages in spamd log

2005-08-20 Thread Steve Martin
Interesting. The last case of it my log the mail was flagged with both DCC and Pyzor so the "alarm" must not have been fatal if it was in those modules. I'll poke around a little more myself. On Aug 20, 2005, at 9:14 AM, Dallas L. Engelken wrote: -Original Message- From: Steve Mar

RE: spurious __alarm__ messages in spamd log

2005-08-20 Thread Dallas L. Engelken
> -Original Message- > From: Steve Martin [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 20, 2005 12:43 AM > To: users@spamassassin.apache.org > Subject: spurious __alarm__ messages in spamd log > > Sat Aug 20 00:28:36 2005 [16014] info: spamd: processing > message <[EMAIL PROTECTED]