Re: When rules run amok....

2006-02-22 Thread jdow
From: "Gene Heskett" <[EMAIL PROTECTED]> On Wednesday 22 February 2006 21:51, jdow wrote: Try that again Dig that forged origin ID: Received: from ADSL-200-59-108-16.capfed2.uolsinectis.com.ar ([200.59.108.16]) by mx-clapper.atl.sa.earthlink.net (EarthLink SMTP Server) with SMTP \ id 1fbZE76yn3

Re: When rules run amok....

2006-02-22 Thread Gene Heskett
On Wednesday 22 February 2006 21:51, jdow wrote: >Try that again >Dig that forged origin ID: > Received: from ADSL-200-59-108-16.capfed2.uolsinectis.com.ar > ([200.59.108.16]) by mx-clapper.atl.sa.earthlink.net (EarthLink SMTP > Server) with SMTP \ id 1fbZE76yn3Nl34b0; Wed, 22 Feb 2006 14:27:31 > -

Re: When rules run amok....

2006-02-22 Thread jdow
Try that again Dig that forged origin ID: Received: from ADSL-200-59-108-16.capfed2.uolsinectis.com.ar ([200.59.108.16]) by mx-clapper.atl.sa.earthlink.net (EarthLink SMTP Server) with SMTP \ id 1fbZE76yn3Nl34b0; Wed, 22 Feb 2006 14:27:31 -0500 (EST) X-Originating-IP: 37.111.211.35 by smt

Re: When rules run amok....

2006-02-22 Thread jdow
Dig that forged origin ID: - Original Message - From: "Chris" <[EMAIL PROTECTED]> To: Sent: Wednesday, February 22, 2006 15:33 Subject: Re: When rules run amok

Re: When rules run amok....

2006-02-22 Thread Chris
On Wednesday 22 February 2006 6:24 pm, Daryl C. W. O'Shea wrote: > On 2/22/2006 4:58 AM, Justin Mason wrote: > > the errors are harmless AFAIK. > > Harmless and already fixed in both trunk and the 3.1 branch (they're > caused by the extremely liberal IPv6 regex that was in use). > > Daryl Thanks f

Re: When rules run amok....

2006-02-22 Thread Daryl C. W. O'Shea
On 2/22/2006 4:58 AM, Justin Mason wrote: the errors are harmless AFAIK. Harmless and already fixed in both trunk and the 3.1 branch (they're caused by the extremely liberal IPv6 regex that was in use). Daryl

Re: When rules run amok....

2006-02-22 Thread Chris
On Wednesday 22 February 2006 4:30 pm, jdow wrote: > I've been wondering if anybody would call "1_801.457.4483" and find out > who it is, just for grins and giggles. > > And it's not QUITE what you posted. The "3" in "3BER" is spurious. That > is the last digit of the phone number. > > Chris mentio

Re: When rules run amok....

2006-02-22 Thread jdow
I've been wondering if anybody would call "1_801.457.4483" and find out who it is, just for grins and giggles. And it's not QUITE what you posted. The "3" in "3BER" is spurious. That is the last digit of the phone number. Chris mentions that the bozoid continues to do it, too. {^_-} - Origin

Re: When rules run amok....

2006-02-22 Thread Justin Mason
haha. "NUMBER[0-255]" s/NUM/randomdigit/g -> "3BER[0-255]" oops! the errors are harmless AFAIK. --j. jdow writes: > I received this from a fellow on another list. It took some puzzling > until I figured out what went wrong. He has yet to get back to me with > whether or not there

When rules run amok....

2006-02-21 Thread jdow
I received this from a fellow on another list. It took some puzzling until I figured out what went wrong. He has yet to get back to me with whether or not there was a score on the message or not. But I think SA should guard itself if this leads to a message escaping getting marked. ===8<--- Joann