W3C welcomes participation in W3C work through its many mailing lists. See below for information about:
All mailing list administrative requests must be sent
to a *-request
address (per RFC2142),
never to the list itself. For a mailing list named
list-name@w3.org
, the associated request address
would be list-name-request@w3.org
.
The following are examples of how to determine the request form of a list:
list name | request address |
---|---|
www-html@w3.org
|
www-html-request@w3.org
|
www-talk@w3.org
|
www-talk-request@w3.org
|
html-tidy@w3.org
|
html-tidy-request@w3.org
|
If you are participating in a Community or other group, your mailing list subscription is automatic.
Subscribe to the list. If you want to subscribe under a
different address, use a Reply-To
header in the
message. Also, be sure you have read our spam policy
and our Guidelines
for Email Attachment Formats before subscribing.
Example:
To: www-talk-request@w3.org Subject: subscribe
Note that you will not get an acknowledgement if you are already subscribed.
Also note that W3C mailing lists do not currently support a digest mode. RSS feeds are available, however.
If you are participating in a Community or other group, leaving that group terminates your mailing list subscription automatically.
Unsubscribe from the list. This can be done from an address
different from the one with which you subscribed.
For example, to unsubscribe from "www-talk@w3.org" use:
To: www-talk-request@w3.org Subject: unsubscribe
or
From: new@example.org To: www-talk-request@w3.org Subject: unsubscribe old@example.org
Most (un)subscription requests are processed automatically without human intervention. Do not send multiple (un)subscription or info requests in one mail. Only one will be processed per mail.
Get information about the mailing list.
The *-request
server usually does quite a good
job in discriminating between (un)subscribe requests and messages
intended for the maintainer. If you for some reason would like to
make sure a human reads your message, make it look like a reply
(i.e. the first word in the "Subject:" field should be
"Re:", without the quotes of course); the
*-request
server does not react to
replies.
In the event of an address change, first send an unsubscribe for the old address (this can be done from the new address), and then a new subscribe from the new address (the order is important).