Re: 2 MIME questions re: message/rfc822

Keith Moore writes:
> yeah, maybe I misunderstood, but my take was that the problem was 
> caused by the some intermediary which did not treat the 
> message/rfc822 body part as an opaque object.
If the body part were meant to be treated as an opaque object, it should 
have been labelled application/octet-stream.
IMO, there are many good reasons for a mailing list processor to look 
closely at the mime parts it receives. For example, it should try to 
not retransmit bounces, virii, etc. Looking very closely at 
message/rfc822 parts is a defensible choice.
Arnt