On Mon, 17 Jul 2006, Shawn Walker wrote:
When I get a UUEncoded attachment, the body encoding member "encoding" is 6,
but all I see in mail.h is:
[snip]
Encoding 6 is dynamically assigned, as are 7, 8, 9, and 10. When c-client
encounters an unknown encoding name, it assigns a free one of these five
slots to it, and sets the name in the associated slot in the
body_encodings[] vector. Only when it runs out of free slots will it
resort to using ENCOTHER (encoding 5); in other words, ENCOTHER is
overflow.
A similar mechanism exists for body types.
The whole idea is that c-client has some extensibility for new body types
and encodings. Fortunately, as I advocated years ago, the registry of new
MIME body types and encodings is more or less closed (I think that MODEL
was the only additional MIME body type ever added) instead of growing
without bounds (as some other people advocated).
I would wager that almost all (if not all) body types and encodings that
go into c-client's extension space, not to mention the TYPEOTHER and
ENCOTHER overflow, is junk created by spammers and thus is safe to treat
as such.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
