On 3/18/2008 7:50 AM, Steve Eckard wrote:
 > Good morning. I seem to have seen something about this in faq. This owner
 > continues to receive this monitoring error for a user she has removed
 > approximately 2 weeks ago. Any way to stop this message manually? Thanks
 > once again.

(List configuration and DEMR text deleted for brevity)

The report shows two errors, on 03/10 and 03/12, and the last error was
'user unknown'.

The opening statement in the Daily Error Monitoring Report is misleading
when it refers to "subscribers" who are being monitored. In fact, these
are addresses which may or may not have ever been subscribed to the list.

There are at least two scenarios which can cause address 'X' to be added
to the Daily Error Monitoring Report for a given list:

1. A message is posted to the list and LISTSERV receives a delivery error
    message for the copy of the posting that was sent to subscriber 'X'.
    In this case, the DEMR is correct; the address is a subscriber address.

2. A message with sender address 'X' is sent to a list or list-related
    address. The inbound message generates a response from LISTSERV, but
    the response is undeliverable. In this case, the DEMR may be misleading,
    particularly if address 'X' is not currently subscribed to the list.

The inbound message may be anything that causes LISTSERV to associate the
message with a specific list and send a response. It might be an attempt to
post to the list; it might be a subscription or signoff request; it might
be command to search the archives or change subscriber options; it might
be spam or malware that just happened to be sent to the list address or
a list-related address. In any case, when the response from LISTSERV
bounces, the sender address on the inbound message is added to the DEMR.

Given the information available in this case, I would guess that the former
subscriber's address is being forged on spam or malware that is being sent
to the list address or a list-related address. LISTSERV is sending an
appropriate response, but the sender address on the inbound message is no
longer valid, so the server response is undeliverable. There are other
possible explanations, but this one fits the facts presented in your message.

--
Paul Russell, Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame
[log in to unmask]