-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday, October 26, 2002, Thomas Fernandez wrote...

>>> Due to a bug in filtering mime headers (apparently can't do it)

>> I wouldn't call it a bug myself, more of a design theory.

> It's a bug. You can search the headers, the body, but not the "lower
> headers", even if you tick on "anywhere".

This is the reason I said I don't think it is a bug. Maybe I agree it
should allow you to search lower headers too... but when you select
the anywhere clause, I think it shouldn't actually hit the
attachments.

>> I have two theories as to why they stop filtering past the standard
>> headers, and the main body.

> The biggest part of the message may be the body; you can search for
> signla strings in it. The "lower headers" are just a line or two.
> You cannot search for signal string in them, though. What is the
> logic behind this?

Attach a 10kb file to an email, write 25 lines of jumbled up rubbish,
email it to yourself, then view the source of the email. Which bit is
longer?

Just as a silly point, the actual headers used with attachment are
technically part of the body. The headers end after the last line up
the top, and a double CRLF. Although technically still headers, they
are not the emails headers, just MIME headers for attachments. If
you're into that kind of thing, try reading RFC 821, 822, and 2045.
The last is more of an extension of RFC 822, describing more on the
body part of emails (MIME attachments for example), as RFC 821, and
822 limited it's descriptions to just plain text emails only. I'm sure
we can forgive them, RFC822 was written in 1982 ;)

- --
Jonathan Angliss
([EMAIL PROTECTED])

-----BEGIN PGP SIGNATURE-----
Comment: Fingerprint: 676A 1701 665B E343 E393  B8D2 2B83 E814 F8FD 1F73

iQA/AwUBPbuKnCuD6BT4/R9zEQJsXwCgk1qQEmjEe1jhdbAEwUQ4C7r9y1UAnA25
r8BfKm4v/YJz+A4vW6wY75RX
=cWJX
-----END PGP SIGNATURE-----


________________________________________________
Current version is 1.61 | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html

Reply via email to