On Thu, 30 May 2002, maillist wrote:
> no, section 15.3 doesn't say anything about the problem I am facing.
to quote that ms kb article:
"
Some SMTP servers do not implement RFC 2822 completely and create
message headers that are not compliant with the RFC specifications.
Exchange 2000 Server treats the incorrectly configured header as part
of the message body and does not recognize the header field with the
missing colon as a valid header. Because of this, Exchange 2000
assumes that the body of the message has started and includes the
complete header along with the message body. Because the MIME header
is not parsed, e-mail message attachments are displayed as encoded
text in the message body and are not automatically decoded.
"
and then it refers to rfc2822
but it's the *POP CONNECTOR* that barfs up. and the pop rfc quite
clearly states that *everything up until the first empty line are the
headers*.
microsoft is misleading here. as usual, i'd say, and this doesn't make
pop connector one bit more usable. it's quite stange that everything,
and i mean everything besides popconnector handles the case as it
should be handled. "beware on road six, a guys is driving against
the traffic" "one? they are all doing that!"...
besides, whoever made headers like "Content-transfer-encoding: 7-bit"
shall shut the fsck up about referring to rfcs, imho. (thats some ms
passport mailer thing, btw.).
