|
Mime-Version: |
1.0 |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Fri, 7 Aug 1998 16:45:21 -0400 |
Content-Type: |
text/plain; charset="us-ascii" |
Reply-To: |
|
Environment: VM/ESA 2.2.0, IBM TCP/IP 2.3, LMail 1.2c, Listserv/TCPIP 1.8c
* LMail version 1.2c/1.8c, managed by:
* U9505RP@DOEVM
*
* Master nodes file version: 97/04/16 08:49:21 (VERS9703)
* Running under: CMS release 12 (SLU 801 - XA mode)
* LISTSERV(R)-TCP/IP for VM version 1.8c, managed by:
* "Roger D. Parish" <[log in to unmask]>
*
* Master nodes file version: 97/04/16 08:49:21 (VERS9703)
* NJE peers file version: 97/03/19 08:54:08
* Internet peers file version: 97/03/13 15:26:34
* Service file version: 95/12/22 19:43:20 (VERS9512)
* Running under: CMS release 12 (SLU 801 - XA mode)
E-mail message sent from cc:Mail with a file attachment, via Worldtalk
NetJunction gateway. I've captured the message out of SMTP and out of
LMail. In both cases, the Content-type line is folded between parameters,
thus:
>Content-Type: multipart/mixed;
> boundary="---- =_WT17695.35cb5df4.0a0/hqrtmta1.doe.gov"
This is good; it works just fine. But, if the message is sent to a Listserv
list, the line gets split thusly:
>Content-Type: multipart/mixed; boundary="----
> =_WT17695.35cb5df4.0a0/hqrtmta1.doe.gov"
It appears that Listserv is re-flowing that line, and breaking at the first
white-space encountered on a right-to-left scan, not withstanding the fact
that the white-space is inside a quoted string!
Has anyone else seen this, or have a fix/circumvention?
--
Roger
301-903-5238
Office of Information Management
U.S. Department of Energy
|
|
|