Arnt Gulbrandsen wrote:
Nathaniel Borenstein writes:
Hmm, now I'm really confused. If you're about to transmit a set of
messages, and what you have is an mbox file whose format you think you
understand, why don't you package it up as a proper MIME multipart
before transmitting??? -- Nathaniel
HTTP too uses content-types. What's the proper type for something like
http://www.imc.org/ietf-822/entire-arch.txt?
Presumably the HTTP server in question can parse the archive in question
("whose format you think you understand"). In that case, it could be
sent as multipart/digest, which is the "proper MIME multipart" for a
collection of messages.
Failing that, application/octet-stream would be a discrete media type
possibility, equivalent to the proposal in the draft w/o the parameters
suggested in discussion here, with the subtype tag "octet-stream" instead
of "mbox" (and lacking any parameters or specified format, the receiver
has to play guessing games with the content with either subtype tag).