LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Jacob Haller <[log in to unmask]>
Sun, 19 Dec 1999 23:04:06 -0500
text/plain (90 lines)
>Getting following error from lisrtserve. Please help on this.

Nasty format for bounces.

If you just got the one bounce I'd probably just file it away or
delete it; in that case it's probably the result of an abortive
subscribe request or other command issued by a bad address.  If
they're coming in more often then it's more likely that one of your
mailing lists has a subscriber with a nastily misconfigured mailer.
In that case I'd issue the following commands in roughly this order.
I'd probably put them in seperate emails but you can put them all in
the same if you prefer.

        q * for *dsagupta*@*
        q * for *manash*@*
        q * for *standardchartered*@*
        q * for *@*standardchartered*
        q * for *@*interliant.com
        q * for *@*interliant.*

If there's an address that matches two or more of the above patterns
then I'd take a closer look at it.  There are various things you
could try:

1) Set the subscriber nomail.

2) Delete the subscription.

3) "QUIET SET listname NOMAIL FOR email@address" followed by "SET
listname MAIL FOR email@address" and see if this results in an
immediate bounce, hopefully one that's recognizably associated with
the message the above commands generate.

4) Send mail to the suspect email address asking if they've been
having email problems.  If the message bounces, delete the
subscription.

If you can't find a possible problem subscription using the above
methods (or if you find too many) then the next step is probably to
send mail to [log in to unmask] and ask them if they have any
records of what the message was that generated the bounce, or at
least who the message's recipients were.  In that case you should
include the full text of the bounce (as I guess you did below).

Good luck,
Jacob Haller

>The enclosed message, found in the LISTSERV mailbox and shown under the
>spool ID 0993 in the  system log, has been identified as  a possible
>delivery error notice for the following reason: mail origin seems to be a
>mailer.
>------------------------ Message in error (23 lines)
>--------------------------
>Received: (from root@localhost <mailto:root@localhost> )
>by iss05.interliant.com (8.9.3/8.9.3) id AAA21029
>                 for [OUT][log in to unmask]; Sat, 18 Dec 1999
>00:00:33 -0600 (CST)
>Received: from localhost (localhost)
>                 by iss05.interliant.com (8.9.3/8.9.3) with internal id
>AAA21023;
>                 Sat, 18 Dec 1999 00:00:33 -0600 (CST)
>Date:   Sat, 18 Dec 1999 00:00:33 -0600 (CST)
>From:   Mail Delivery Subsystem <[log in to unmask]
><mailto:[log in to unmask]> >
>         Message-Id: <[log in to unmask]
><mailto:[log in to unmask]> >
>To:     [log in to unmask] <mailto:[log in to unmask]>
>         MIME-Version: 1.0
>Subject:        Returned mail: Host unknown (Name server:
>in.standardchartered: host not found)
>         Auto-Submitted: auto-generated (failure)
>
>The original message was received at Sat, 18 Dec 1999 00:00:28 -0600 (CST)
>from root@localhost <mailto:root@localhost>
>         ----- The following addresses had permanent fatal errors -----
>[OUT][log in to unmask]
>         ----- Transcript of session follows -----
>550
>[OUT]manash.dsagupta%IN.standardchartered%stanchart@IN.standardchartered...
>Host unknown (Name server: in.standardchartered: host not found)
>
>
>Thanks & Regards
>Priya

--
Jacob Haller, Technical Support
L-Soft international, Inc
http://www.lsoft.com/

ATOM RSS1 RSS2