The long text "<00A4C33...Firstname/i=D/@MHS>" is really a single unbroken
(unwrapped) string of text when it hits LISTSERV.  What you saw as wrapped
text in *my* message was either an anomaly of my mail system or yours.
Again, in this case, my problem is that the original mail header is
wrapped between the "Message-Id:" tag and the string of text that follows
it.  The string of text is not wrapped internally, although it is longer
than 80 characters.

-David L. Merrifield             E-mail: [log in to unmask]
 University of Arkansas                  [log in to unmask]
 SAG-L List Owner

On Fri, 13 Jun 1997, Roger Fajman wrote:

> > Message-Id:
> >   <00A4C33A065C7009*/c=us/admd=imx/prmd=domain.name/o=co/ou=MSMail/s=LASTNAME/g=
> > FirstName/i=D/@MHS>
> >
> > I have narrowed the problem down to the fact that his mail system folds
> > (wraps to a new line) the long Message-Id: header line immediately after
> > the "Message-Id:" header tag.  In the original message, that header line
> > contains:
> >
> >  "Message-Id:" (space) (CR) (LF) (space) (space) "<00A4C33....>" (CR) (LF)
> >
> > LISTSERV appears to ignore all headers past this header, which includes
> > the important From: and Subject: headers.  When LISTSERV distributes the
> > message to the list subscribers, it indicates that the message came from
> > an unknown origin, and does not provide a Subject header.
>
> The problem is that the continuation line (starting with "FirstName")
> does not begin with a space or a tab, as required by RFC 822.  So it
> looks to LISTSERV like the start of a new header that is not properly
> formed.
>