Douglas Palmer wrote:
[...]
>> Our MTAs do not generate e-mail messages with either of the following 
>> headers:
>>
>> From: [log in to unmask]
>> Message-id: <[log in to unmask]>
>>
>> LISTSERV apparently does.
> 
> 
> The message you forwarded did not have those details (and they are still 
> insufficient). From the message you forwarded to the list, the actual 
> culprit it the MTA on lists.princeton.edu (which should not be receiving 
> SMTP anyway given the MX records, though internal routing might change 
> that).
> 
>> In any case, such a terse response from L-Soft is unacceptable.
> 
> 
> I would not argue with that.
> 
> -- DCP


My original posting to the list did include those two headers.  Here is 
the full set of headers, which I did send to L-Soft, and which indicate 
that the message did indeed originate from LISTSERV:

Return-path: <[log in to unmask]>
Received: from mailserver3.Princeton.EDU ([128.112.130.43])
  by mailserver3.Princeton.EDU
  (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005))
  with SMTP id <[log in to unmask]> for
  [log in to unmask]; Wed, 14 Sep 2005 22:44:33 -0400 (EDT)
Received: from smtpserver1.Princeton.EDU ([128.112.129.65])
  by mailserver3.Princeton.EDU (NAVGW 2.5.2.12)
  with SMTP id M2005091422443224773 for <[log in to unmask]>; Wed,
  14 Sep 2005 22:44:32 -0400
Received: from oldmail.Princeton.EDU (oldmail.Princeton.EDU 
[128.112.129.175])
	by smtpserver1.Princeton.EDU (8.12.9/8.12.9) with ESMTP id 
j8F2iXHl017275	for
  <[log in to unmask]>; Wed, 14 Sep 2005 22:44:33 -0400 (EDT)
Received: from oldmail.Princeton.EDU (csgrpts@localhost [127.0.0.1])
	by oldmail.Princeton.EDU (8.13.1/8.13.1) with ESMTP id j8F2iX5A018711	for
  <[log in to unmask]>; Wed, 14 Sep 2005 22:44:33 -0400 (EDT)
Received: (from csgrpts@localhost)
	by oldmail.Princeton.EDU (8.13.1/8.13.1/Submit)
  id j8F2iUGx018710	for [log in to unmask]; Wed,
  14 Sep 2005 22:44:30 -0400 (EDT)
Received: from smtpserver2.Princeton.EDU
  (smtpserver2.Princeton.EDU [128.112.129.148])
	by oldmail.Princeton.EDU (8.13.1/8.13.1) with ESMTP id j8F2iTsi018707	for
  <[log in to unmask]>; Wed, 14 Sep 2005 22:44:29 -0400 (EDT)
Received: from lists.Princeton.EDU (lists01.Princeton.EDU [128.112.129.193])
	by smtpserver2.Princeton.EDU (8.12.9/8.12.9) with ESMTP id 
j8F1TrxA011009	for
  <[log in to unmask]>; Wed, 14 Sep 2005 22:44:29 -0400 (EDT)
Date: Wed, 14 Sep 2005 22:44:29 -0400
From: [log in to unmask]
Subject: Undelivered mail
To: "[log in to unmask] c/o LISTSERV postmaster"
  <[log in to unmask]>
Message-id: <[log in to unmask]>
MIME-version: 1.0
Content-type: multipart/report; report-type=delivery-status;
  boundary=--HQMTEQaJeNcOPZUAIbccPKHJWVUALb
X-Spam-KB: http://www.Princeton.EDU/spam
Original-recipient: rfc822;[log in to unmask]

We do have internal routing from our MX servers to LISTSERV, and also 
use external (sendmail) SMTP servers for delivery to and from LISTSERV, 
so checking the MX for lists.Princeton.EDU does not alone indicate how 
e-mail gets to and from our LISTSERV, or the "cuplrit" of this problem.

A 'strings' of the lsv executable indicates that LISTSERV does generate 
e-mail messages with Content-type and Subject headers like those shown 
above.

All evidence that I see indicates that LISTSERV generated the message 
and its inconsistent MIME boundaries.

I understand that bugs happen, and that they may take some time to fix, 
but I do expect them to eventually be fixed, particularly bugs such as this.

I've replied to L-Soft Support again (as well as posting relevant 
information to this list), and look forward to receiving a better 
response from L-Soft Support soon.

			Alex