Message from Erich L. Markert [18:10 98-12-10 ]: >I'm running LISTSERV 1.8d with LSMTP 1.1a on NT 4.0 SP3. > >I'm receiving mail delivery errors that are complaining about delivery >errors to listname >because an error message is trying to be delivered to owner-listname. > >The original error occurs for any number of reasons, i.e. unknown users, >etc. This error >message is then being delivered back to my LSMTP host but is being addressed to >owner-listname which according to LSMTP doesn't exist. I checked through my >configuration >of LSMTP and didn't not find an owner-listname alias anywhere. > >Has anyone experienced this before? If so, is there a solution? Most probably the subscriber uses a so called forwarding address or an alias. Try to examinate the Received: fields. Let me quote the manual: Let's say that suddenly you are bombarded with delivery errors for [log in to unmask] Your immediate reaction is to set this person to NOMAIL or (in some cases) to delete him/her altogether. You therefore send set xxxxx-L nomail for [log in to unmask] to LISTSERV. LISTSERV responds: "No subscription for [log in to unmask] in list XXXXX-L." In a best-case scenario, you can query the list for *@*.baz.net and find either a user like [log in to unmask] (the address has changed and the local sysadmins didn't inform the user) or a redistribution-list account like [log in to unmask] These are easily-fixed redistribution bounces. In the first case, you delete the user and let him or her resubscribe. In the second case, you can try sending a message to [log in to unmask] with a cc: to [log in to unmask] and inform them of the problem. If it persists, you could send a further message informing them that you are suspending the redistribution list's subscription until such time as they tell you the problem on their end is fixed, and simply set [log in to unmask] to NOMAIL. The worst-case scenario is as follows: baz.net may be bouncing the mail to you, but there may not be a single subscription for baz.net in your list. Here's where you have to do some careful sleuthing. First, run a wildcard query such as QUERY xxxxx-l FOR *@*baz* or QUERY xxxxx-l FOR *baz*@*. The former will find users at baz.com, for instance, where baz.net is a synonym for baz.com. The latter query may seem somewhat strange, but it's possible that the mail is being routed through a gateway and the actual subscription is for [log in to unmask] or something of that sort. mjw