Hi Harold,
 
>There is a way, however to get that person who is at the "WRONG" server.
>Use the "GLOBAL" parameter on the delete command.  This will cause the
>"RIGHT" server to receive the command, and if the person is not subscribed
>locally, to forward the command to all other peer servers.  One of them
>will be the server where the user is subscribed and he will be deleted.
 
That's the point I was referring to.  What if your header says that
there are several peers (EB0 among them), but an intermediate LISTSERV
doesn't not mention one as peer (e.g. EB0) ?   The DEL-REQ will not be
propagated to that server.
In the example brought by Richard, the subscriber is located in DEARN,
so even if you sent the req to EB0 and our server resends the req to the
'peers' mentioned in its header, may be the server at DEARN will reject
the req as coming from a non-peered list -if EB0 is not mentioned there
as a peer-  ( am I wrong ? )
 
BUT, if the server is mentioned as a 'slave' or 'listening' one,
the poor subscriber who wanted his name deleted will still receive
the contributions.
 
Best regards,  Miguel