Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: help with regex
From: Amir Caspi <cepheid@3phase.com>
In-Reply-To: <21262.35753.492857.684201@pinky.delphioutpost.com>
Date: Wed, 26 Feb 2014 18:09:14 -0700
Cc: "Kevin A. McGrail" <KMcGrail@PCCC.com>,
        Webmaster <webmaster2@crystal3.com>, users@spamassassin.apache.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A82AE7E-D75C-4DAA-ADF2-B1D5AEAB0389@3phase.com>
References: <530E7E74.2070909@crystal3.com> <530E818A.5020808@PCCC.com>
 <21262.35753.492857.684201@pinky.delphioutpost.com>
To: Jeff Mincy <jeff@delphioutpost.com>

On Feb 26, 2014, at 5:49 PM, Jeff Mincy <jeff@delphioutpost.com> wrote:

> Can't you do something like this using a look ahead regexp?
>=20
> (?=3D[A-Z0-9]{30,})(?:[A-Z]*[0-9]){10,}

According to regexpal.com, that matches the OP's example.  The lookahead =
works properly in this case, since trying to use (say) 28 numbers fails, =
while 10 numbers works.  As long as SA can do lookahead, I think this =
should work.

I'm guessing the OP is trying to make a spam template match, much like =
the AC_SPAMMY_URI_PATTERNS rules.  Typically, though, I've found that =
there's no real need to be THAT specific when matching the template; =
almost no hammy emails will have alphanumeric strings of 30+ characters. =
 As long as the rest of the URI match is sufficiently unique, there =
shouldn't be a need to be overly specific about the string itself.  Of =
course, it all depends on the situation, which would be much easier to =
assess if the OP posted an example. =3D)

Cheers.

--- Amir