W3C hosts hundreds of mailing lists and archives, many of them public, for the benefit of the Web community at large. By providing this service, we hope to foster a highly responsive and interactive community for creating new ideas and advancing web technologies and culture.
Anyone with a valid email address can participate on a W3C public mailing list following the steps below.
Each W3C mailing list has its own policies regarding who may post to the list. Those subscribed to each list are generally able to post directly to the list without delay; those who are not may be subject to manual moderation (at least the first time they post.)
First-time posters to our lists with public archives will need to give us permission to publish their message in our public archives using our archive approval system.
Each mailing list has a specific purpose; please try to avoid widely cross-posting to multiple lists if possible.
Conference announcements are generally not welcome on W3C lists; if you feel a specific conference is of very high interest to the subscribers of a given list, you should write a custom message to that list, containing a very short summary with a pointer to more information.
Posting of Unsolicited Bulk E-mail (UBE), or spam is strictly forbidden .
Posts to our lists are generally not removed or edited, except in very rare circumstances. See our Archive Editing Policy for more information.
Once you have chosen a list (say, "example@w3.org"), to subscribe send a message to example-request@w3.org with the subject line "subscribe" (the body can be empty).
To reduce spam, we may require you to confirm your subscription request; learn more about W3C's archive approval system and forgery prevention using SPF (Sender Policy Framework).
To unsubscribe from example@w3.org, send a message to example-request@w3.org with the subject line "unsubscribe" (the body can be empty).
Further information on subscription administration is available.
An archive search tool is available.
It is frequently useful to refer to a message (say, from the body of an email or from a Web page) using a URI to the message in the archive. In addition, you can use the message's own "message-id" and map it to the archive URI using the message-id mapping tool.