Aditya <aditya@grot.org> wrote:
> D) Included as a header AND a machine-parseable line in the body of the
> confirmation AND welcome message.
Sounds very good
> > and what should the format of this file look like?
Here's a suggestion. I'll start with some examples
Example 1 (just one line)
List-Robots: * disallow *
Example 2 (two lines)
List-Robots: * disallow *
List-Robots: gmane.org allow sterilized-*-archive
Example 3 (two lines)
List-Robots: * disallow *
List-Robots: *.maillist.info allow subscribe
In example 1, robots are supposed to simply leave the list alone.
A robot which is subscribed for any reason should unsub immediately.
In example 2, gmane.org (and only this site) is invited to create
a "sterilized archive", i.e. an archive with all email addresses
removed (so that it won't result in list members getting spammed).
In example 3, robots from anyhost.maillist.info are invited to
subscribe but not archive. All other robots are supposed to leave
the list alone.
So each line would start with "List-Robots:" and then three items:
- a hostname field, where '*' is allowed as a wildcard
- a verb, either "allow" or "disallow"
- one of the following keywords, where again '*' is allowed as a
wildcard:
subscribe
unsterilized-mangled-archive
unsterilized-faithful-archive
sterilized-mangled-archive
sterilized-faithful-archive
(In a mangled-archive, the site with the robot is allowed to mangle
the messages in any way. In a faithful-archive, any site which
hosts archives must provide a complete record of the flow of
discussion on the list, with unmangled message text for each
posting.)
Greetings, Norbert.
--
Founder & Steering Committee member of http://gnu.org/projects/dotgnu/
Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland)
Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch
List hosting with GNU Mailman on your own domain name http://cisto.com
Follow-Ups:
References:
|
|
