Rich Kulawiec wrote,
| I was under the impression that [EMAIL PROTECTED] was
| required by RFC. (No, I can't recall the number offhand, even
| though we've discussed it here before. My archives of this list
| aren't available just at the moment or I'd go look.) Given
| that list-request is one of the oldest de facto 'net conventions,
| and given that it appears in RFC ???, I'd suggest that we try
| using it -- I mean REALLY using it, universally and consistently --
| before trying anything else.
The question still remains of exactly how to use it. As John Evershed has
quoted for us from RFC 2142, it is required that list-request exist for
receipt of administrative mail, but there are no specifications of how it
should handle the mail that comes to it. From John's quote from the RFC:
> Mailing lists have an administrative mailbox name to which add/drop
> requests and other meta-queries can be sent. For a mailing list whose
> submission mailbox name is: <LIST@DOMAIN> there MUST be the administrative
> mailbox name: <LIST-REQUEST@DOMAIN>
Note the wording "to which ... can be sent." It doesn't say "at which ...
will be processed." It would appear that list-request could be just an
autoresponder that sends a help file and still comply with RFC 2142.
