I believe this means that the HTML is decoded/unescaped now BEFORE 
doing the regex. This means that when the spammers include things 
like &#60; and &#61; (which decode to < and >) in their html, we no 
longer have to set up the regex to look for "&#60;" as well as the 
decoded "<". Instead, it decodes the escaped characters like &#60; 
and THEN runs the regex, so the regex only has to look for the "<" 
character instead.


At 04:44 PM 9/17/2010, K Post wrote:

>all HTML entities in the mail body are now decoded before the bomb
>checks are running. Regular expressions must no more contain checks for
>HTML encoded text.
>
>  What do you mean by HTML entities?  Does this mean we couldn't search using
>a regex for something like:
>
><b>f r e e</b>
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to