>Subject: Owner-XXX and XXX-Request
 
First, these pseudo userid "map" to specific LISTSERV list
keywords:
 
OWNER-listname   maps to the list keyword operand of * ERRORS-TO:
 
listname-REQUEST maps to the list keyword operands of
     * OWNER= (may be more than one non-quiet list-owner).
 
When LISTSERV generates a distribution, it creates the RFC821
header with MAIL FROM:<OWNER-listname>.  This is the address
where mail delivery errors are SUPPOSED TO GO when using
RFC-compliant mailer transport agents.
 
When LISTSERV generates administrative mail e.g., subscribe
responses, it uses a generic FROM: (and perhaps REPLY-TO:)
RFC822 address of listname-REQUEST.
 
In both cases, LISTSERV did not "lookup" the corresponding list
definition keyword values, but used simply the generic pseudo
userids.  Most of the time, those values will not need to be
resolved, unless of course someone replies or, e-mail bounces.
Then, when that mail is replied to the LISTSERV hosting site,
LISTSERV will THEN need to resolve those generic userids to
specific userid(s) (plural if there is more than one).
 
- --  co-owner INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L
[log in to unmask]        "Are you E-mail Diverse?"       +1 814 863 1843
31 Shields Bldg. --   Penn State    -- University Park, PA 16802-1202 USA