Hi Jeff: That thought had occurred to me - but since (at least in my case) by the time I notice a hung filter, the file is no longer in the spool, I haven't had a chance to examine it.
Looking through the filter errors in my /var/log/messages, the sender's addresses all look "spammy", so maybe there's a fubar spam mailer out there that has some screwed headers etc. in it? Again, without being able to recover the actual message spool file, there's no way to tell, and I'm just making (hopefully educated) guesses... Kirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jeffrey Laramie Sent: Tuesday, December 09, 2003 10:48 AM To: [EMAIL PROTECTED] Subject: [xmail] Re: av script not stopping On Tuesday 09 December 2003 11:37, you wrote: > Hi Benny: > > Funny - never thought to try that myself - I'll try playing around with > that myself next time I see a hung process. > > However, the file in the "slog" directory is substantially different from > the message in the "mess" directory - the file is a log of XMail's delivery > attempts for the message (good for debugging frozen and/or bounced > messages). If you're looking for an actual message file in the correct > spool format, you'll probably want to log in the "froz" directory instead. > > Kirk > OK, here's a crazy thought. Benny hung the script by read an incorrectly formatted file. Could there be an exploit out there that screws with the mail headers and causes the same problem? Just throwing out ideas here. Jeff - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
