This particular form of spam should be tested against 3.0, and soon. They
have made a bunch of changes to html scanning, and may have fixed this. If
not, they really should fix it. They are planning on locking things down
and going into release mode on MONDAY, so may stop being interested in new
bug reports on problems that have been around since 2.63 until after the
release.
(I think you will find that the problem here is that the 2.63 html scanner
probably broke the body into two separate strings at the blank line, so the
re to find the color tag hit the end of the string and failed.)
Loren
