LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

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

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

Print Reply
Valdis Kletnieks <[log in to unmask]>
Thu, 11 Jan 2001 13:54:06 -0500
text/plain (34 lines)
On Thu, 11 Jan 2001 11:10:53 CST, "John W. Luther" <[log in to unmask]>  said:
> Greetings!
>
> I've just been handed the job of maintaining our Listserv.
>
> I keep getting copies of posts that are marked with delivery errors.  Here is the "explanation."
>
> The enclosed message has been identified as a delivery error for the EMPNEWS
> list because it was sent to [log in to unmask]  (Where you can replace "empnews" with the name of any other list.
>
> What does it mean?  Is something misconfigured on our system that I keep getting so many of this type of error?  It makes no sense to me.

Well.. it usually means the following:

1) Listserv has a user subscribed to a list 'empnews'.
2) SOmebody posts to the list.
3) The userid is bogus, broken, gone, deactivated, over quota, etc.
4) The mail bounces (correctly) to owner-listname.
5) You get handed the mail to do something about it.

What to do:

1) Look at the enclosed message.  Is there something useful like 'User Unknown'
or 'Uknown Host' in it?  Listserv is able to auto-parse many delivery errors itself,
but some (most notably QMail and Microsoft Exchange) don't follow RFC1891/1894.

2) If the address is in fact broken, unsubscribe them from the list.

3) Consider configuring auto-delete on your lists.
--
                                Valdis Kletnieks
                                Operating Systems Analyst
                                Virginia Tech

ATOM RSS1 RSS2