In the "To:" field, where are the CR/LF's (if any)?  The way the message got here, 
there are 5 CRLFs (making 6 lines in the To: field), but I'm guessing that somewhere 
along the way wordwrap got involved.

If there are less than 5 CRLFs, are there spaces or tabs on the lines that follow?  I 
checked RFC822, and it says that long headers can be split with a CRLF followed by at 
least one space or tab.  The split can only occur somewhere that a space or tab could 
normally appear (IE I could split "Scott Perry" into "ScottCRLF Perry" but not 
"ScoCRLF tt Perry".
                               -Scott

---------- Original Message ----------------------------------
From: "Michael Gartner" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Mon, 15 May 2000 14:09:03 -0500

Here's a sample header from a "bad" message. I appreciate any help you can
give.


**** BEGINNING OF BAD MESSAGE HEADER ****

Received: from joepa [172.16.1.87] by mail.arrowheadconveyor.com
  (SMTPD32-6.00) id A59C14A0150; Wed, 23 Feb 2000 08:58:36 -0600
Received: by localhost with Microsoft MAPI; Wed, 23 Feb 2000 09:01:54 -0600
Message-ID: <[EMAIL PROTECTED]>
From: Joe Pahlow <[EMAIL PROTECTED]>
Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: "Dudley Dorrell (E-mail)" <[EMAIL PROTECTED]>, "Jerry Tappy
(E-mail)" <[EMAIL PROTECTED]>, "Judy Weber (E-mail)"
<[EMAIL PROTECTED]>, "Mark Wessing (E-mail)"
<[EMAIL PROTECTED]>, "Matt Stanek (E-mail)" <
[EMAIL PROTECTED]>, "Scott Dehne (E-mail)"
<[EMAIL PROTECTED]>
Subject:  CO00614 DOUGLAS MACH.
Date: Wed, 23 Feb 2000 09:01:53 -0600
Organization: Arrowhead Conveyor
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----
=_NextPart_000_01BF7DDC.A16214E0"
X-RCPT-TO: <mwessing>
X-UIDL: 250540567
Status: U


------ =_NextPart_000_01BF7DDC.A16214E0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit


------ =_NextPart_000_01BF7DDC.A16214E0
Content-Type: application/msword; name="Project Change Form 1.doc"
Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAACAAAA2gAAAAAAAAAA
...

*** garbage deleted ***

...AAAAAAAAA



------ =_NextPart_000_01BF7DDC.A16214E0--


**** END OF BAD MESSAGE HEADER ****

Michael Gartner
Network Administrator
Arrowhead Conveyor
3255 Medalist Dr.
Oshkosh, WI 54902

Ph. 920-235-5562
Fax 920.235.4950

www.arrowheadsystems.com

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, May 15, 2000 1:24 PM
To: [EMAIL PROTECTED]
Subject: Re: [IMail Forum] Message.txt - still a problem


> I know that the "To:" line in the bad messages is wrapping at 256
> characters - it doesn't in good messages.

It turns out the references to this problem that I had seen on here were the
messages you had sent before, to which I didn't see any solutions.

If you don't mind, you could post the headers to one of the messages that is
having this problem?  That way, we can see if IMail is following the RFC
properly or if Microsoft is choking on something that it shouldn't choke on.
FYI, we recently brought up that the maximum length of a header seems to be
512 bytes, but mail clients/servers can use shorter lines split into
multiple lines.  Of course, if the splitting of the line was not done
properly, that could account for the problem.
                             -Scott
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.

Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

Reply via email to