>Hello All,
>
>I cannot seem to rid myself of error messages caused by
>"[log in to unmask]". The address is not among my 143 subscribers when I
>review my header. For anyone debugging, I am at cwru.edu and the list is
>copfleet-l at american.edu
>
>Here's an error report; any help would be appreciated.
It looks like the user is subscribed from iname or globecomm. You can try
forwarding a copy of the bounce to postmasters at these sites and see if
they can help you (though they may not bother to respond). You can also
try scanning for likely-looking substrings of 'deanwormr', e.g.
SCAN COPFLEET-L dean*@
SCAN COPFLEET-L wormr*@
SCAN COPFLEET-L worm*@
Finally, you could scan your mailing list for subscribers from globecomm
and iname and send them private messages to see which of the addresses are
good.
There are a few other options, but those are the main ones I'd consider.
To see how I figured this out, I'll do a little analysis of the bounce you
forwarded.
First LISTSERV tells you why it thinks the message is a bounce.
>The enclosed message, found in the COPFLEET-L mailbox and shown under the
>spool
>ID 1008453 in the system log, has been identified as a possible delivery
>error
>notice for the following reason: "Message/Delivery-Status" body part
>found in
>the message body.
>
>------------------------ Message in error (165 lines)
>-------------------------
Next it gives you the bounce, including the full headers. This is not
usually that useful, but occasionally helpful information can be found in
these headers.
>Delivered-To: [log in to unmask]
>Received: from hiroshima.american.edu (hiroshima.american.edu [147.9.1.18])
> by fln.american.edu (Postfix) with ESMTP for
><[log in to unmask]>
> id 826B646815; Tue, 23 Mar 1999 13:11:27 -0500 (EST)
>Received: (from daemon@localhost)
> by hiroshima.american.edu (8.8.6/8.8.6) id NAA06430
> for [log in to unmask]; Tue, 23 Mar 1999 13:09:39
>-0500 (EST)
>Received: from fln.american.edu (listserv.american.edu [147.9.238.200])
> by hiroshima.american.edu (8.8.6/8.8.6) with ESMTP id NAA01736
> for <[log in to unmask]>; Tue, 23 Mar 1999 13:09:37 -0500 (EST)
>Received: from fln (fln.american.edu [147.9.238.13])
> by fln.american.edu (Postfix) with ESMTP for <[log in to unmask]>
> id 55B4CF67; Mon, 22 Mar 1999 11:57:19 -0500 (EST)
>Delivered-To: [log in to unmask]
>Received: from hiroshima.american.edu (hiroshima.american.edu [147.9.1.18])
> by fln.american.edu (Postfix) with ESMTP for
> <[log in to unmask]>
> id 308A139801; Tue, 23 Mar 1999 13:07:32 -0500 (EST)
>Received: (from daemon@localhost)
> by hiroshima.american.edu (8.8.6/8.8.6) id NAA04109
> for [log in to unmask]; Tue, 23 Mar 1999
>13:05:29 -0500
> (EST)
>Received: from aolmbd05.mx.aol.com (aolmbd05.mx.aol.com [205.188.156.79])
> by hiroshima.american.edu (8.8.6/8.8.6) with ESMTP id NAA03765
> for <[log in to unmask]>; Tue, 23 Mar 1999 13:05:29
>-0500 (EST)
>Received: from rly-zd03.mx.aol.com (rly-zd03.mail.aol.com [172.31.33.227])
> by aolmbd05.mx.aol.com (8.8.8/8.8.5/AOL-2.0.0)
> with ESMTP id NAA22216 for <[log in to unmask]>;
> Tue, 23 Mar 1999 13:05:44 -0500 (EST)
>Received: from localhost (localhost)
> by rly-zd03.mx.aol.com (8.8.8/8.8.5/AOL-4.0.0)
> with internal id NAA00314;
> Tue, 23 Mar 1999 13:05:40 -0500 (EST)
>Date: Tue, 23 Mar 1999 13:05:40 -0500 (EST)
>From: Mail Delivery Subsystem <[log in to unmask]>
>Message-Id: <[log in to unmask]>
>To: <[log in to unmask]>
>MIME-Version: 1.0
>Content-Type: multipart/report; report-type=delivery-status;
> boundary="NAA00314.922212340/rly-zd03.mx.aol.com"
>Subject: Returned mail: User unknown
>Auto-Submitted: auto-generated (failure)
>Sender: [log in to unmask]
>X-Report-Type: Nondelivery; boundary="> Error description:"
The headers of the bounce end, and the message in the bounce begins.
Usually (if you're lucky) the bounce will include the full headers of the
message that bounced, as in this case.
>An error was detected while processing the enclosed message. A list of
>the affected recipients follows. This list is in a special format that
>allows software like LISTSERV to automatically take action on incorrect
>addresses.
>
>--> Error description:
>Error-For: MAILBOX NOT FOUND
>Error-Code: 3
>Error-Text: User unknown
>
>Error-End: One error reported.
>
>
>This is a MIME-encapsulated message
>
>--NAA00314.922212340/rly-zd03.mx.aol.com
>
>The original message was received at Tue, 23 Mar 1999 13:05:36 -0500 (EST)
>from rmx08.iname.net [165.251.8.85]
>
>
>*** ATTENTION ***
>
>Your e-mail is being returned to you because there was a problem with its
>delivery. The AOL address which was undeliverable is listed in the section
>labeled: "----- The following addresses had permanent fatal errors -----".
>
>The reason your mail is being returned to you is listed in the section
>labeled: "----- Transcript of Session Follows -----".
>
>The line beginning with "<<<" describes the specific reason your e-mail could
>not be delivered. The next line contains a second error message which is a
>general translation for other e-mail servers.
>
>Please direct further questions regarding this message to your e-mail
>administrator.
>
>--AOL Postmaster
>
>
>
> ----- The following addresses had permanent fatal errors -----
><[log in to unmask]>
>
> ----- Transcript of session follows -----
>... while talking to air-zd01.mail.aol.com.:
>>>> RCPT To:<[log in to unmask]>
><<< 550 MAILBOX NOT FOUND
>550 <[log in to unmask]>... User unknown
>
>--NAA00314.922212340/rly-zd03.mx.aol.com
>Content-Type: message/delivery-status
>
>Reporting-MTA: dns; rly-zd03.mx.aol.com
>Received-From-MTA: DNS; rmx08.iname.net
>Arrival-Date: Tue, 23 Mar 1999 13:05:36 -0500 (EST)
>
>Final-Recipient: RFC822; [log in to unmask]
>Action: failed
>Status: 5.1.1
>Remote-MTA: DNS; air-zd01.mail.aol.com
>Diagnostic-Code: SMTP; 550 MAILBOX NOT FOUND
>Last-Attempt-Date: Tue, 23 Mar 1999 13:05:40 -0500 (EST)
>
>--NAA00314.922212340/rly-zd03.mx.aol.com
>Content-Type: message/rfc822
That was all AOL's diagnostic of what went wrong. Now we get to the
message that bounced. The key thing here is that the "Received:" headers
gives you a list of the machines that the message passed through on its way
from the person who sent the original message to the end recipient. These
"Received:" headers are typically added to the top of the message, so they
are in reverse order (most recent first).
>Return-Path: <[log in to unmask]>
The address that bounces are supposed to go to--not useful to determining
who the subscriber is.
>Received: from rmx08.globecomm.net (rmx08.iname.net [165.251.8.85])
> by rly-zd03.mx.aol.com (8.8.8/8.8.5/AOL-4.0.0)
> with ESMTP id NAA00303 for <[log in to unmask]>;
> Tue, 23 Mar 1999 13:05:36 -0500 (EST)
The message was passed from a machine called rmx08.globecomm.net (a.k.a.
rmx08.iname.net) to aol.com; this is the last thing that happened before
the message bounced. At this point the message was supposed to go to
[log in to unmask]
>Received: from smv18.iname.net by rmx08.globecomm.net (8.9.1/8.8.0) with
>SMTP id NAA08298 ; Tue, 23 Mar 1999 13:05:39 -0500 (EST)
Before that, it was passed from smv18.iname.net to rmx08.globecomm.net.
>Received: from fln.american.edu (fln.american.edu [147.9.238.13])
> by smv18.iname.net (8.9.1a/8.9.1SMV) with ESMTP id MAA19285;
> Tue, 23 Mar 1999 12:04:37 -0500 (EST)
Before that, fln.american.edu passed it off to smv.iname.net.
And so on. Now, there's no reason why american.edu should pass off mail
destined for aol.com to iname.net. This is suspicious, and indicates that
the subscriber is signed up from some site that receives mail services from
iname.net, and which is then set up to forward mail sent to that address to
the aol.com address. So I'd look for subscriptions from @*iname* and
@*globecomm* and see where that led me.
Hope this helped,
jwgh
>Received: from fln (fln.american.edu [147.9.238.13])
> by fln.american.edu (Postfix) with ESMTP
> id 8DAE042800; Mon, 22 Mar 1999 11:57:19 -0500 (EST)
>Received: from AMERICAN.EDU by AMERICAN.EDU (LISTSERV-TCP/IP release 1.8d)
>with
> spool id 1005761 for [log in to unmask]; Tue, 23 Mar 1999
> 12:04:40 -0500
>Delivered-To: [log in to unmask]
>Received: from hiroshima.american.edu (hiroshima.american.edu [147.9.1.18]) by
> fln.american.edu (Postfix) with ESMTP for
> <[log in to unmask]> id 3BBFF3B005; Tue, 23 Mar 1999
> 12:04:29 -0500 (EST)
>Received: (from daemon@localhost) by hiroshima.american.edu (8.8.6/8.8.6) id
> MAA12164 for [log in to unmask]; Tue, 23 Mar 1999
> 12:02:48 -0500 (EST)
>Received: from hunny.INS.CWRU.Edu ([log in to unmask] [129.22.8.186]) by
> hiroshima.american.edu (8.8.6/8.8.6) with ESMTP id MAA18668 for
> <[log in to unmask]>; Tue, 23 Mar 1999 12:02:47 -0500 (EST)
>Received: from law-lab-24 (law47544.LAW.CWRU.Edu [129.22.185.184]) by
> hunny.INS.CWRU.Edu with SMTP (8.8.8+cwru/CWRU-2.5-bsdi) id MAA19743;
> Tue, 23 Mar 1999 12:03:37 -0500 (EST) (from [log in to unmask] for
> <[log in to unmask]>)
>X-Sender: [log in to unmask]
>X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>Message-ID: <[log in to unmask]>
>Date: Tue, 23 Mar 1999 12:03:47 -0500
>Reply-To: Police Fleet Discussion List <[log in to unmask]>
>Sender: Police Fleet Discussion List <[log in to unmask]>
>From: John Witherspoon <[log in to unmask]>
>Subject: New Chevy Impala Police Car
>To: [log in to unmask]
>
>According to Automotive News on March 15, 1999, Chevrolet will offer a
>police version of its new Impala when it goes on sale this spring. This
>had been rumored for some time but is now official.
>
>-- John
>
>--NAA00314.922212340/rly-zd03.mx.aol.com--
|
