"Jesse Houwing" <[EMAIL PROTECTED]> writes:
> I did a quick grep through my corpus, but it turned out that there
> actually are just 10 such urls in there. The other hits were on
> messages that had the . encoded as =3e. But I'm afraid that to catch
> those I'd have to make this rule full (yuk!).
Yeah, I think for 3.1 (in our copious spare development time), we should
probably clean-up the rule types a bit. This has been discussed before,
but the basics would be:
- undecoded type ("undecoded", new type)
- decoded type ("rawbody", probably rename to "decoded" for clarity,
but support old name for backwards compatibility)
- rendered type ("body", keep old name)
"full" should probably just remain as the entire pristine message.
Daniel
--
Daniel Quinlan
http://www.pathname.com/~quinlan/
