On Thu October 28 2004 02:39, Martin Duerst wrote:
It's probably only partially useful for email clients. Indeed Bruce
Lilly makes a rather good point that it is not useful at all for
email clients (he however makes the mistake of thinking that
email clients are everything that counts).
To be precise, I pointed out some limited use for MUAs. Focus on
MUAs was based on the fact that the field is defined as a structured
field and has no defined uses for other agents and/or protocols
(MSAs, MTAs, MDAs, filters, access protocols).
It's very useful for
humans. Is there a rule that email headers have to be used by
email clients?
Structured fields (as far as RFC 2822's definition of structured
vs. unstructured fields is concerned) are primarily used by
message handling programs (not only clients, but e.g. IMAP
servers, MTAs, Sieve filtering language (RFC 3028), etc.).
Fields intended to be used only by humans are generally
unstructured (again, in the RFC 2822 sense), e.g. Subject,
Comments, Content-Description. So if it had been clear back
in February that the intent was solely for human use, we
could have avoided a lot of syntax discussion and the field
could have been defined as unstructured; or we could have
arrived then where we are today, with the suggestion that
any existing mechanism for conveying human-readable
non-protocol content could be used, without having to
invent "Yet Another Header Field".
As an example, how much is the X-Mailer: header
used my email clients?
Well, it's not a standardized field... as such it has no
specified uses, semantics, or syntax. As a user-specified
field (RFC 822, fields beginning with "x-"), any use is
subject to and dependent upon agreement between
cooperating parties.
>and at least some
>email clients are already able to download files using http and/or
>ftp.
But that's just files in general, yes? Or is is message/rfc882 in
particular? And if the later, what clients would that be?
MIME is used with the HTTP protocol as well as with RFC [2]822
message format. As such, HTTP can be used to transfer content
of any MIME media type, including message/rfc822. Although
it has been elided from the current version of the FTP specification,
the FTP protocol did have specific commands (MAIL and MLFL)
for message transfer; these have been superseded by message-
specific transfer protocols, viz. MTP, SMTP (introduction of
which predated dropping of the message-specific FTP commands
by several years) and more recent variations such as POP,
IMAP, and NNTP.