obscured URL not being tokenized

[Tom Anderson]

On Sat, 2003-12-20 at 16:43, David Relson wrote:
> based on them.  Unfortunately, this isn't adequate.  Directives are
> nested, for example a table contains table data which can include font
> directives.  Proper processing of all this requires a stack for saving
> the previous state and popping the stack as end tags are encountered. 
> It all gets more complicated since the html may be improperly formed, as
> in <table><tr><td><font>...</table>, where the end directive pops
> several stack levels.

I don't think bogofilter needs to be interpreting html.  Simply
recognizing the tokens such as 'size=-5' and 'color="#fffffe"' ought to
be enough.  If there were to be such functionality as html
interpretation and image recognition attempted, it should be in a
preprocessor seperate from bogofilter which perhaps sets its own
"x-bogosity"-type line.  This way it could be turned on or off easily. 
Let's not bloat the core of bogofilter with such stuff.

Tom

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://www.bogofilter.org/pipermail/bogofilter/attachments/20031220/3699694f/attachment.sig>