Thomas' original regex will match both of those email addresses. You can test your regex against suspect email addresses at a regex testing site like this one:
http://regexstorm.net/tester Type the pattern in the top box, click "ignore case" and then paste your suspect email address in the bottom. It will show you the part of the email address that matches the regex - in both cases, the entire email address matches: http://regexstorm.net/tester?p=.*%3fnoreply.*%3f%5c%40ymail%5c.com&i=DS122016-noreply%40ymail.com&o=i http://regexstorm.net/tester?p=.*%3fnoreply.*%3f%5c%40ymail%5c.com&i=noreply-EM-12-20-16%40ymail.com&o=i On 12/21/2016 2:25 AM, James Moe wrote: > Hello, > assp 2.5.3-16347 > linux 4.1.34-33-default x86_64 > > The quest to block *some* "@ymail" continues. Thomas recommended using: > .*?noreply.*?\@ymail\.com > > It is not as successful as I first thought. The following addresses > are still getting through: > [email protected] > [email protected] > > I tried modifying the regex to: > (^|.*?)noreply($|.*?)\@ymail\.com > > It made no difference. Obviously I am not very handy with regex's. > Any suggestions? > ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
