I seem to remember that LISTSERV (ibm vm versions, at least) had
(has?) built-in smarts which weed out a lot of the SUBSCRIBE X ME TOO
subscription messages which were misdirected to X instead of to LISTSERV.
Right?
 
If so, would someone point me to any documentation (not source code; I
don't have access) that describes in general and/or specific terms,
what kinds of traps are set, and how "smart" are they? Or, if there is
no documentation, then just an acknowledgement that the feature exists,
and maybe a few details?
 
(If you can provide some "search" words that you know will work, I can
search the lstsrv-l and lstown-l archives.)
 
Also, what other types of misguided messages are caught by default by
LISTSERV (i.e, not including user-written exits) and redirected to the
list owner/errors-to person? E.g., I know that a "get listname logxxxx"
message send to the list will be returned saying something to the effect
that it appears this message was misdirected, etc.
Peter