On Thu, 3 Jun 2004, Damrose, Mark wrote:
> Shouldn't this part have a "Content-Type: text/plain" header?
Surprisingly, it's not required. According to RFC 2045:
5.2. Content-Type Defaults
Default RFC 822 messages without a MIME Content-Type header are taken
by this protocol to be plain text in the US-ASCII character set,
which can be explicitly specified as:
Content-type: text/plain; charset=us-ascii
This default is assumed if no Content-Type header field is specified.
So it could be that the mail client is barfing because of the missing
Content-type header, but if so, it's not RFC-compliant.
Regards,
David.
_______________________________________________
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
