Re: How was this missed?
On Thu, Apr 13, 2006 at 10:39:29AM -0600, wrote: Any idea how this one got through? body BRIAN_PHONE_NUMBERS /2.0.6.9.8.4.2.3.2.7|2.0.6.3.3.3.0.0.5.1|2.0.6.9.8.4.0.1.0.6|3.3.8.3.5.7.9|2.0.6.3.3.8.6.0.6.1|2.0.6 .2.0.2.2.0.3.3/ A Gen_uine Coll`ege Deg.ree in 2 weeks Cal_l us now_!- 2*0*6*984-2327 Sure, the pattern doesn't match. . means there has to be some (any) character between the numbers. 984 has no characters between the numbers. -- Randomly Generated Tagline: 1-900-Tech Support...hold...all operators are busy. pgpwSxDV5mFul.pgp Description: PGP signature
Re: How was this missed?
Please start a new thread instead of replying to an unrelated message. Thursday 13 April 2006 18:39 wrote: Any idea how this one got through? body BRIAN_PHONE_NUMBERS /2.0.6.9.8.4.2.3.2.7|2.0.6.3.3.3.0.0.5.1|2.0.6.9.8.4.0.1.0.6|3.3.8.3.5.7.9| 2.0.6.3.3.8.6.0.6.1|2.0.6 .2.0.2.2.0.3.3/ describe BRIAN_PHONE_NUMBERS Phone number or address pulled from spam scoreBRIAN_PHONE_NUMBERS 5.5 A period (.) matches exactly one arbitrary character (except newline). Try putting a question mark (?) after each period. - Message - Good day, A Gen_uine Coll`ege Deg.ree in 2 weeks Cal_l us now_!- 2*0*6*984-2327 Within 2 weeks! No Study Required! 1_0_0_% Veri.fiable! Right now the following deg.rees are being offered: B/A, .B/S/C,.M/A,.M/S/C,.M/B/A, .P/H/D, C.al_l us now_ for more information, 2*0*6*984-2327 -- Magnus Holmgren pgpxO9V9dnv05.pgp Description: PGP signature
RE: How was this missed?
Theo Van Dinter wrote: On Thu, Apr 13, 2006 at 10:39:29AM -0600, wrote: Any idea how this one got through? body BRIAN_PHONE_NUMBERS /2.0.6.9.8.4.2.3.2.7|2.0.6.3.3.3.0.0.5.1|2.0.6.9.8.4.0.1.0.6|3.3.8.3.5.7 .9|2.0.6.3.3.8.6.0.6.1|2.0.6 .2.0.2.2.0.3.3/ A Gen_uine Coll`ege Deg.ree in 2 weeks Cal_l us now_!- 2*0*6*984-2327 Sure, the pattern doesn't match. . means there has to be some (any) character between the numbers. 984 has no characters between the numbers. Fixed version: /2.?0.?6.?9.?8.?4.?2.?3.?2.?7|2.?0.?6.?3.?3.?3.?0.?0.?5.?1|2.?0.?6.?9.?8 .?4.?0.?1.?0.?6|3.?3.?8.?3.?5.?7.?9|2.?0.?6.?3.?3.?8.?6.?0.?6.?1|2.?0.?6 .?2.?0.?2.?2.?0.?3.?3/ Or, perhaps, better: /2\D?0\D?6\D?9\D?8\D?4\D?2\D?3\D?2\D?7|2\D?0\D?6\D?3\D?3\D?3\D?0\D?0\D?5 \D?1|2\D?0\D?6\D?9\D?8\D?4\D?0\D?1\D?0\D?6|3\D?3\D?8\D?3\D?5\D?7\D?9|2\D ?0\D?6\D?3\D?3\D?8\D?6\D?0\D?6\D?1|2\D?0\D?6\D?2\D?0\D?2\D?2\D?0\D?3\D?3 / -- Matthew.van.Eerde (at) hbinc.com 805.964.4554 x902 Hispanic Business Inc./HireDiversity.com Software Engineer
Re: How was this missed?
On Thursday 13 April 2006 11:55, [EMAIL PROTECTED] wrote: Theo Van Dinter wrote: On Thu, Apr 13, 2006 at 10:39:29AM -0600, wrote: Any idea how this one got through? body BRIAN_PHONE_NUMBERS /2.0.6.9.8.4.2.3.2.7|2.0.6.3.3.3.0.0.5.1|2.0.6.9.8.4.0.1.0.6|3.3.8.3.5.7 .9|2.0.6.3.3.8.6.0.6.1|2.0.6 .2.0.2.2.0.3.3/ There's a ruleset I use from: http://www.emtinc.net/includes/chickenpox.cf .. that checks for the d.i.f.f.e.r.e.n.t kinds of spacing like this... a lot of the spam that has those kinds of characteristics will have several of the CHICKENPOX_ rules that have fired positive. It checks for some 60+ different patterns.. describe J_CHICKENPOX_12 1alpha-pock-2alpha describe J_CHICKENPOX_13 1alpha-pock-3alpha describe J_CHICKENPOX_14 1alpha-pock-4alpha describe J_CHICKENPOX_15 1alpha-pock-5alpha describe J_CHICKENPOX_16 1alpha-pock-6alpha describe J_CHICKENPOX_17 1alpha-pock-7alpha describe J_CHICKENPOX_18 1alpha-pock-8alpha describe J_CHICKENPOX_19 1alpha-pock-9alpha describe J_CHICKENPOX_110 1alpha-pock-10alpha describe J_CHICKENPOX_111 1alpha-pock-11alpha describe J_CHICKENPOX_21 2alpha-pock-1alpha describe J_CHICKENPOX_22 2alpha-pock-2alpha describe J_CHICKENPOX_23 2alpha-pock-3alpha describe J_CHICKENPOX_24 2alpha-pock-4alpha describe J_CHICKENPOX_25 2alpha-pock-5alpha describe J_CHICKENPOX_26 2alpha-pock-6alpha describe J_CHICKENPOX_27 2alpha-pock-7alpha describe J_CHICKENPOX_28 2alpha-pock-8alpha describe J_CHICKENPOX_29 2alpha-pock-9alpha describe J_CHICKENPOX_210 2alpha-pock-10alpha describe J_CHICKENPOX_31 3alpha-pock-1alpha describe J_CHICKENPOX_32 3alpha-pock-2alpha describe J_CHICKENPOX_33 3alpha-pock-3alpha describe J_CHICKENPOX_34 3alpha-pock-4alpha describe J_CHICKENPOX_35 3alpha-pock-5alpha describe J_CHICKENPOX_36 3alpha-pock-6alpha describe J_CHICKENPOX_37 3alpha-pock-7alpha describe J_CHICKENPOX_38 3alpha-pock-8alpha describe J_CHICKENPOX_39 3alpha-pock-9alpha describe J_CHICKENPOX_41 4alpha-pock-1alpha describe J_CHICKENPOX_42 4alpha-pock-2alpha describe J_CHICKENPOX_43 4alpha-pock-3alpha describe J_CHICKENPOX_44 4alpha-pock-4alpha describe J_CHICKENPOX_45 4alpha-pock-5alpha describe J_CHICKENPOX_46 4alpha-pock-6alpha describe J_CHICKENPOX_47 4alpha-pock-7alpha describe J_CHICKENPOX_48 4alpha-pock-8alpha describe J_CHICKENPOX_51 5alpha-pock-1alpha describe J_CHICKENPOX_52 5alpha-pock-2alpha describe J_CHICKENPOX_53 5alpha-pock-3alpha describe J_CHICKENPOX_54 5alpha-pock-4alpha describe J_CHICKENPOX_55 5alpha-pock-5alpha describe J_CHICKENPOX_56 5alpha-pock-6alpha describe J_CHICKENPOX_57 5alpha-pock-7alpha describe J_CHICKENPOX_61 6alpha-pock-1alpha describe J_CHICKENPOX_62 6alpha-pock-2alpha describe J_CHICKENPOX_63 6alpha-pock-3alpha describe J_CHICKENPOX_64 6alpha-pock-4alpha describe J_CHICKENPOX_65 6alpha-pock-5alpha describe J_CHICKENPOX_66 6alpha-pock-6alpha describe J_CHICKENPOX_71 7alpha-pock-1alpha describe J_CHICKENPOX_72 7alpha-pock-2alpha describe J_CHICKENPOX_73 7alpha-pock-3alpha describe J_CHICKENPOX_74 7alpha-pock-4alpha describe J_CHICKENPOX_75 7alpha-pock-5alpha describe J_CHICKENPOX_81 8alpha-pock-1alpha describe J_CHICKENPOX_82 8alpha-pock-2alpha describe J_CHICKENPOX_83 8alpha-pock-3alpha describe J_CHICKENPOX_84 8alpha-pock-4alpha describe J_CHICKENPOX_91 9alpha-pock-1alpha describe J_CHICKENPOX_92 9alpha-pock-2alpha describe J_CHICKENPOX_93 9alpha-pock-3alpha describe J_CHICKENPOX_101 10alpha-pock-1alpha describe J_CHICKENPOX_102 10alpha-pock-2alpha -- Tyler Nally [EMAIL PROTECTED] 317-989-2028
Re: How was this missed?
On Thu, Apr 13, 2006 at 09:55:59AM -0700, [EMAIL PROTECTED] wrote: 2*0*6*984-2327 /2.?0.?6.?9.?8.?4.?2.?3.?2.?7|2.?0.?6.?3.?3.?3.?0.?0.?5.?1|2.?0.?6.?9.?8 .?4.?0.?1.?0.?6|3.?3.?8.?3.?5.?7.?9|2.?0.?6.?3.?3.?8.?6.?0.?6.?1|2.?0.?6 .?2.?0.?2.?2.?0.?3.?3/ Or, perhaps, better: /2\D?0\D?6\D?9\D?8\D?4\D?2\D?3\D?2\D?7|2\D?0\D?6\D?3\D?3\D?3\D?0\D?0\D?5 \D?1|2\D?0\D?6\D?9\D?8\D?4\D?0\D?1\D?0\D?6|3\D?3\D?8\D?3\D?5\D?7\D?9|2\D ?0\D?6\D?3\D?3\D?8\D?6\D?0\D?6\D?1|2\D?0\D?6\D?2\D?0\D?2\D?2\D?0\D?3\D?3 / Now you won't catch (206) 984-2327 [206] 984-2327 206 - 984 - 2327 etc. FYI. -- Randomly Generated Tagline: Thinking of using NT for your critical apps? Isn't there enough suffering in the world? - Sun Microsystems Ad pgpWQfHPF8Wbh.pgp Description: PGP signature
Re: How was this missed?
!Sure, the pattern doesn't match. . means there has to be some (any) !character between the numbers. 984 has no characters between the !numbers. DOH!!! Thanks. your right...
