sitives. Tons of catches.
Something like:
~(http\:\/\/|@)[^/\s]*\.info(\s(\r|$)|\/|\.\s\s?\w|\.?\r)~=>0.7
> From: "Paul K. Dickson"
> Date: Fri, 30 Apr 2010 14:17:40 -0400
> To: For Users of ASSP
> Conversation: [Assp-user] Fantastic regex
> Subject: Re: [Assp-user] Fan
isn't listing a score.. It's assumes the full
> score and is just telling you it was scored because you have it set to
> score, not block. Maybe someone else can confirm.
>
>
> > From: Alex Davidson
> > Reply-To: For Users of ASSP
> > Date: Fri, 30 Apr 201
SSP
> Date: Fri, 30 Apr 2010 12:32:41 -0600
> To: For Users of ASSP
> Subject: Re: [Assp-user] Fantastic regex
>
> I have 20 assigned to bombValancePB.
> In which case, I see no reason for this to be happening.
>
> Thanks for the updated RegEx, I Searched & Repla
1
> pdick...@frederickcountymd.gov
> 301-600-2399/x12399
>
>
>
> > From: Alex Davidson
> > Reply-To: For Users of ASSP
> > Date: Fri, 30 Apr 2010 09
1701
pdick...@frederickcountymd.gov
301-600-2399/x12399
> From: Alex Davidson
> Reply-To: For Users of ASSP
> Date: Fri, 30 Apr 2010 09:16:49 -0600
> To: For Users of ASSP
> Subject: Re: [Assp-user] Fantastic reg
I know I must be missing something really obvious here, but I don't
normally rely on Bomb detection as I have had issues in the past with
False Positives.
After installing that RegEx I am seeing log entries where bombDataRe
says [scoring] rather than something like [scoring:10]:
Apr-30-10 08:19:31
pr 2010 09:43:30 -0400
> To: For Users of ASSP
> Subject: [Assp-user] Fantastic regex
>
> For catching foreign URL¹s or email addresses in the body of an email.
> Email¹s with foreign country codes can be blocked as part of ASSP¹s native
> functionality, but that does not protect
For catching foreign URL¹s or email addresses in the body of an email.
Email¹s with foreign country codes can be blocked as part of ASSP¹s native
functionality, but that does not protect against a lot of phishing/viagra
sales attempts that come from US domains(yahoo, hotmail), but that have
obvious
