On Thu, 29 Jan 2004, Paul Jarc wrote:
> Ok, I'd missed that. (But mostly, I was confused about what I was
> seeing in a message/delivery-status bounce.) So, I'll assign
> sequential part numbers for components of multipart/*, assign .1 for
> all message/*, and assign .HEADER and .BODY just for me
On Thu, 29 Jan 2004, Paul Jarc wrote:
> Lastly (I hope), exactly which content-types must a server delve into?
> multipart/mixed, multipart/alternative, message/rfc822, ...
> message/delivery-status? multipart/digest? Others?
Did you read RFC 3501? The answer is to be found on page 55.
-- Mark
Lastly (I hope), exactly which content-types must a server delve into?
multipart/mixed, multipart/alternative, message/rfc822, ...
message/delivery-status? multipart/digest? Others?
paul
