On Thu, 10 Dec 1998 13:42:26 -0500, "Erich L. Markert" <[log in to unmask]> wrote:
>Here's one example of the problem. A message was sent to 53listserv, it was disseminated
>to all subscribers.
Are you sure about this? Is it in the archives for the list (if any)? I think you are confused because it came to you as the Owner or Errors-To address in the
List Header, not because you received it through an actual list mailing.
> As you can see this one bounced because the user could not be found,
>but LSMTP
LISTSERV, not LSMTP
>complained because this was being sent to owner-53listserv.
It is not complaining. It is reporting why it is sending you the message, which
appears to be an error. The message has 3 parts (see below)
>BTW, the subject
>heading for this message was: 53listserv: error report from ....
>I understand that LSMTP creates all the needed aliases that's why this is so confusing.
LISTSERV, not LSMTP here.
This entire message is what is known as a bad-address error bounce. However,
its format does not conform to any of the several standard formats LISTSERV
knows about. Since it comes from Groupwise this is no surprise. The address
(grimsleybernard) must be found and deleted manually.
>Here's the error message.
>
PART one: (LISTSERV is reporting why it is forwarding the message to you)
>The enclosed message has been identified as a delivery error for the
>53listserv list because it was sent to [log in to unmask]
>
PART two: (the contents of the error message received from the remote site)
>------------------------------ Message in error -------------------------------
>Received: from ns1.optec.army.mil by orator.usma.edu (LSMTP Lite for Windows NT
> v1.1a) with SMTP id <[log in to unmask]>; Thu, 10 Dec 1998
> 13:39:43 -0500
>Received: from hq.optec.army.mil (optec-hq.optec.army.mil [10.0.0.20])
> by ns1.optec.army.mil (8.8.6 (PHNE_14041)/8.8.6) with SMTP id NAA21247
> for <[log in to unmask]>; Thu, 10 Dec 1998 13:28:45 -0500 (EST)
>Received: from HQDOMAIN-Message_Server by hq.optec.army.mil
> with Novell_GroupWise; Thu, 10 Dec 1998 13:33:13 -0500
>Message-Id: <[log in to unmask]>
>X-Mailer: Novell GroupWise 4.1
>Date: Thu, 10 Dec 1998 13:33:13 -0500
>From: [log in to unmask]
>To: [log in to unmask]
>Subject: Message status - undeliverable
>Mime-Version: 1.0
>Content-Type: multipart/mixed; boundary="=_C4938FF9.345531A4"
>
>This is a MIME message. If you are reading this text, you may want to
>consider changing to a mail reader or gateway that understands how to
>properly handle MIME multipart messages.
>
>--=_C4938FF9.345531A4
>Content-Type: text/plain
>Content-Disposition: inline
>
>The message that you sent was undeliverable to the following:
> grimsleybernard (user not found)
>
>Possibly truncated original message follows:
>
>--=_C4938FF9.345531A4
>Content-Type: message/rfc822
PART three: (original message from the List that created the error)
>Received: from orator.usma.edu ([129.29.2.57])
> by hq.optec.army.mil (GroupWise SMTP/MIME daemon 4.1 v3)
> ; Thu, 10 Dec 98 13:33:08 EST
>Received: from www2 (129.29.2.57) by orator.usma.edu (LSMTP Lite for Windows NT v1.1a)
>with SMTP id <[log in to unmask]>; Thu, 10 Dec 1998 13:33:07 -0500
>Received: from ORATOR.USMA.EDU by ORATOR.USMA.EDU (LISTSERV-TCP/IP release
> 1.8d) with spool id 0150 for [log in to unmask]; Thu, 10 Dec
> 1998 13:33:07 -0500
>Received: from smtp02.primenet.com by orator.usma.edu (LSMTP Lite for Windows
> NT v1.1a) with SMTP id <[log in to unmask]>; Thu, 10 Dec 1998
> 13:23:05 -0500
>Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id
> LAA23695 for <[log in to unmask]>; Thu, 10 Dec 1998 11:18:11
> -0700 (MST)
>Received: from ip-47-053.fhu.primenet.com(206.165.47.53),
> claiming to be "hoyte" via SMTP by smtp02.primenet.com,
> id smtpd023649; Thu Dec 10 11:18:09 1998
>MIME-Version: 1.0
>Content-Type: text/plain; charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Priority: 3 (Normal)
>X-MSMail-Priority: Normal
>X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
>Importance: Normal
>X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
|
