On Thu, 15 Sep 2005 19:54:10 -0400, Dan Wheeler <[log in to unmask]> wrote:
>It made me decide to try to help.
Thanks, Dan. Just in case anybody cares, I did verify both sites are
running the same build/version of LISTSERV:
>From: "Princeton University LISTSERV Server (14.3)" <[log in to unmask]>
>Date: Thu, 15 Sep 2005 18:12:21 -0400
>
>> sh vers
>LISTSERV(R) High Performance for unix version 14.3, managed by:
...
>Running under: SunOS 5.8
>Build date: 18 Jan 2005
>From: "LISTS.OLN.ORG LISTSERV Server (14.3)" <[log in to unmask]>
>Date: Thu, 15 Sep 2005 20:15:34 -0400
>
>> sh vers
>LISTSERV(R) for unix version 14.3, managed by:
...
>Running under: SunOS 5.9
>Build date: 18 Jan 2005
My version of LISTSERV is later
>From: [log in to unmask]
>Date: Thu, 15 Sep 2005 18:54:45 -0600
>
>> sh vers
>LISTSERV(R) High Performance for Windows version 14.4, managed by:
...
>Running under: Windows 2000 Server
>Build date: 18 Aug 2005
but my test also show no signs of the errant MIME boundaries (see below).
Perhaps the Princeton.EDU mail flows through some anti-spam or anti-virus
filter or something else that is altering the message after it left LISTSERV
and before it gets to your mailbox? There are various ways to capture
LISTSERV's outgoing mail by piping it to a file. Then you can be sure of
what LISTSERV did or did not generate, uncorrupted by other possible
influences.
The line
>Received: (from csgrpts@localhost)
> by oldmail.Princeton.EDU (8.13.1/8.13.1/Submit)
> id j8F2iUGx018710 for [log in to unmask]; Wed,
suggests that "csgrpts" might be some kind of application (searches on this
term were not productive, but several hits imply it may be some kind of web
application.)
I am not sure what's going on here, but I have found (after working with
LISTSERV for almost 15 years) that these things must be very carefully
investigated. What is at first claimed to be an obvious error in LISTSERV,
often turns out to be an error somewhere else in the SMTP chain of machines
from beginning to end of the process.
enough said for now.
-------
If anybody cares, results of my test:
Subject: Delivery error report from MAIL03.BESTEFFORT.COM
To: [log in to unmask]
Message-ID: <[log in to unmask]>
X-LSV-ListID: None
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="aRHXLIKIIeCWUaUPVJaCcOZGWUXQQS"
Return-Path: <>
X-OriginalArrivalTime: 16 Sep 2005 00:43:03.0281 (UTC)
FILETIME=[98776610:01C5BA57]
--aRHXLIKIIeCWUaUPVJaCcOZGWUXQQS
The enclosed message, found in the LISTSERV mailbox and shown under the
spool
ID 47052 in the system log, has been identified as a possible delivery
error
notice for the following reason: "X-Report-Type:" field found in the
mail
header.
--aRHXLIKIIeCWUaUPVJaCcOZGWUXQQS
Content-Type: message/rfc822
Return-Path: <>
Received: from mail.besteffort.com (127.0.0.1) by mail.besteffort.com (LSMTP
for Windows NT v1.1b) with SMTP id <[log in to unmask]>; Thu, 15
Sep 2005 18:43:03 -0600
From: [log in to unmask]
To: [log in to unmask]
Date: Thu, 15 Sep 2005 18:43:03 -0600
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="9B095B5ADSN=_01C5A29C8B272B0800000432mail.besteffort."
Message-ID: <[log in to unmask]>
Subject: Delivery Status Notification (Failure)
This is a MIME-formatted message.
Portions of this message may be unreadable without a MIME-capable mail
program.
--9B095B5ADSN=_01C5A29C8B272B0800000432mail.besteffort.
Content-Type: text/plain; charset=unicode-1-1-utf-7
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
[log in to unmask]
--9B095B5ADSN=_01C5A29C8B272B0800000432mail.besteffort.
Content-Type: message/delivery-status
Reporting-MTA: dns;mail.besteffort.com
Received-From-MTA: dns;MAIL03
Arrival-Date: Thu, 15 Sep 2005 18:43:02 -0600
Final-Recipient: rfc822;[log in to unmask]
Action: failed
Status: 5.0.0
Diagnostic-Code: smtp;550 No such local user
--9B095B5ADSN=_01C5A29C8B272B0800000432mail.besteffort.
Content-Type: message/rfc822
Received: from MAIL03 ([127.0.0.1]) by mail.besteffort.com with Microsoft
SMTPSVC(5.0.2195.6713);
Thu, 15 Sep 2005 18:43:02 -0600
Date: Thu, 15 Sep 2005 18:43:02 -0600
From: [log in to unmask]
Subject: Command confirmation request (B872350F)
To: [log in to unmask]
Message-ID: <[log in to unmask]>
Return-Path: [log in to unmask]
X-OriginalArrivalTime: 16 Sep 2005 00:43:02.0984 (UTC)
FILETIME=[984A1480:01C5BA57]
Your command:
PW ADD ********
requires confirmation. To confirm the execution of your command, simply
point your browser to the following URL:
http://listserv.besteffort.com/scripts/wa.exe?OK=B872350F
Alternatively, if you have no WWW access, you can reply to the present
message and type "ok" (without the quotes) as the text of your message.
Just the word "ok" - do not retype the command. This procedure will work
with any mail program that fully conforms to the Internet standards for
electronic mail. If you receive an error message, try sending a new
message to [log in to unmask] (without using the "reply"
function - this is very important) and type "ok B872350F" as the text of
your message.
Finally, your command will be cancelled automatically if LISTSERV does
not receive your confirmation within 48h. After that time, you must start
over and resend the command to get a new confirmation code. If you change
your mind and decide that you do NOT want to confirm the command, simply
discard the present message and let the request expire on its own.
------------------------- Original mail header --------------------------
Return-Path: <[log in to unmask]>
Received: from BEN03.besteffort.com (192.168.100.3) by mail.besteffort.com
(LSMTP for Windows NT v1.1b) with SMTP id <[log in to unmask]>;
Thu, 15 Sep 2005 18:43:02 -0600
From: <[log in to unmask]>
To: [log in to unmask]
Subject: should make error
Date: Thu, 15 Sep 2005 18:41:41 -0600
Organization: Best Effort Co.
Message-ID: <[log in to unmask]>
X-Mailer: Forte Agent 3.0/32.763
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
--9B095B5ADSN=_01C5A29C8B272B0800000432mail.besteffort.--
--aRHXLIKIIeCWUaUPVJaCcOZGWUXQQS--
|
