I recently got an error report that looked like this:

Err First Last  Address
--- ----- ----- -------
  1 06/13 06/13 Some  Body <[log in to unmask]>
                Last error: User unknown

  1 06/13 06/13 Some Body <[log in to unmask]>
                Last error: User unknown

This led me to beleive that someone was subscribed twice to my list,
although based on the way the subscribers for this particular list had
been generated, duplicates were highly unlikely if not impossible.  It
also happens that these two domains are registered in the aliases.names
file as synonymous.  Since I knew this person had changed addresses, I
set out to tackle the "first" address occurrence as follows:

quiet change listname-l [log in to unmask] [log in to unmask]

At first I got a message from LISTSERV that said "No entry updated."  I
thought this was strange.  But soon thereafter I got another message
from LISTSERV that said:

> ok
Confirming:
> quiet change listname-l [log in to unmask] [log in to unmask]
LISTNAME-L: [log in to unmask] changed to [log in to unmask]

One entry updated. No notification has been sent.

When I queried the list for the old address, (query listname-l for
nobody@*), LISTSERV said there was no subscription found, from which I
gathered the address had only existed once in the first place.

Is this behavior normal?  Will synonymous hostnames always appear
multiple times in an error report?

Thanks,
Kathy Montgomery
University at Albany, NY