Re: Well, it ws nice of them to tell me!

2007-12-14 Thread Chris
On Friday 14 December 2007 10:30 am, Loren Wilton wrote: > > So it doesn't happen that often. I did try writing an SA header rule for > > these first, but it appears that SA strips out 'X-Spam-Flag' headers out > > before the rules are run. > > SA Strips out X-Spam-* on the assumption that it prev

Utility to dump public corpus to outlook folder

2007-12-14 Thread gpr
Hi, I am looking for a utility which can dump the mails from SpamAssassin public corpus to an outlook or outlook express folder? Please help me on this.very urgent.. Thanks in advance Ram -- View this message in context: http://www.nabble.com/Utility-to-dump-public-corpus-to-outlook-

Re: Not sure why DOS_OE_TO_MX fired

2007-12-14 Thread Daryl C. W. O'Shea
Andrew Hearn wrote: Hello, I'm not sure why DOS_OE_TO_MX fired on this message, as the headers say it was delivered to b.painless.aaisp.net.uk which relayed it on to z.hopeless.aaisp.net.uk. b.painless isn't the MX for the domain... SA support for IPv6 is currently non-existent so the top mos

Re: "Virus found in this message", probe?

2007-12-14 Thread Joseph Brennan
The control node turned off the switch at 05:00 EST. They were still rolling in during the 04:00 hour but the last one was at 04:54. The customer's paid time on the botnet may have ended. Joseph Brennan Lead Email Systems Engineer Columbia University Information Technology

Re: Well, it ws nice of them to tell me!

2007-12-14 Thread Loren Wilton
So it doesn't happen that often. I did try writing an SA header rule for these first, but it appears that SA strips out 'X-Spam-Flag' headers out before the rules are run. SA Strips out X-Spam-* on the assumption that it previously added them. Previous to 3.0 it did this before the rules ran

RE: Well, it ws nice of them to tell me!

2007-12-14 Thread Giampaolo Tomassoni
> -Original Message- > From: Giampaolo Tomassoni [mailto:[EMAIL PROTECTED] > Sent: Friday, December 14, 2007 2:26 PM > To: users@spamassassin.apache.org > Subject: RE: Not sure why DOS_OE_TO_MX fired > > > -Original Message- > > From: Andrew Hearn [mailto:[EMAIL PROTECTED] > > Sent

Re: Well, it ws nice of them to tell me!

2007-12-14 Thread Duane Hill
On Fri, 14 Dec 2007 12:12:27 + Steve Freegard <[EMAIL PROTECTED]> wrote: > Loren Wilton wrote: > > X-SpamFilter-By: BOX Solutions SpamTrap 1.1 with qID > > lBDNlb6m031347, This message is to be blocked by code: bkndr63272 > > Subject: [Spam-Mail] We invite you to join us as a Silver > > PowerS

RE: Not sure why DOS_OE_TO_MX fired

2007-12-14 Thread Giampaolo Tomassoni
> -Original Message- > From: Andrew Hearn [mailto:[EMAIL PROTECTED] > Sent: Friday, December 14, 2007 1:27 PM > To: users@spamassassin.apache.org > Subject: Not sure why DOS_OE_TO_MX fired > > Hello, > > I'm not sure why DOS_OE_TO_MX fired on this message, as the headers say > it was deli

Not sure why DOS_OE_TO_MX fired

2007-12-14 Thread Andrew Hearn
Hello, I'm not sure why DOS_OE_TO_MX fired on this message, as the headers say it was delivered to b.painless.aaisp.net.uk which relayed it on to z.hopeless.aaisp.net.uk. b.painless isn't the MX for the domain... Any ideas? -Thanks! Return-path: <[EMAIL PROTECTED]> Envelope-to: [EMAIL PROTECTE

Re: Well, it ws nice of them to tell me!

2007-12-14 Thread Steve Freegard
Loren Wilton wrote: X-SpamFilter-By: BOX Solutions SpamTrap 1.1 with qID lBDNlb6m031347, This message is to be blocked by code: bkndr63272 Subject: [Spam-Mail] We invite you to join us as a Silver PowerSeller! (This message should be blocked: bkndr63272) Shame they didn't just block it so I wo