-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transition mail server and lists.whatwg.org to new hosting #75
Comments
https://www.c0ffee.net/blog/mail-server-guide and https://news.ycombinator.com/item?id=16238937 might be useful here. |
This issue came up in #107 and I have a proposal for how to proceed. Running a mail server and mailman ourselves is so much hassle that none of us have been willing to tackle it, but if we only had to maintain simple forward email aliases things would be much simpler. https://lists.w3.org/Archives/Public/public-whatwg-archive/ is the W3C-hosted archive of the list, so what I suggest is that we ask to use the W3C's list management system for membership too. I think there are two options:
@sideshowbarker I think the first option would be fine, but can you check if the second is possible? Finally, for actually forwarding email, we'd configure the MX records to point to something that WHATWG admins have shared access to, and DigitalOcean does not provide that. Rather, we will need to use an email provider with custom domains using MX records. I've done this for foolip.org for ages, and also just confirmed that fastmail.com is easy to set up with way using foolip.com. @Hixie I'll email you with a few more questions. |
cc @gosko (who manages the W3C mail systems) so he can comment here directly |
Hosting the list seems doable, but if W3C were to host it I would prefer to change the canonical address and not pretend it's still [email protected], though that could be an alias. I was going to suggest renaming public-whatwg-archive to public-whatwg and redirecting the archives but unfortunately public-whatwg is already taken: https://lists.w3.org/Archives/Public/public-whatwg/ Note that moving the list to W3C would mean the email headers would change, in particular the List-Id: would be different and the subject tagging would no longer be available. |
@gosko, changing the canonical address would be fine, but if sending to [email protected] could still work that would be good. Perhaps just setting it up to forward to the w3.org address would allow that to work? The WHATWG Community Group is closed, so would it be possible to use [email protected] while keeping the existing archives of that? I think we'll just have to accept that people will need to update their email filters, but I don't think the volume of email will be high, so that's OK. |
@gosko there is a problem with any plan to transfer that I didn't think of at the outset, and that's that those who signed up to lists.whatwg.org didn't agree to such a transfer of their contact info. Trying to sort that out is probably more effort than it's worth, so which I'd still appreciate understanding the options here, I wouldn't spend too much time on this given this uncertainty. |
@foolip This is possible, but seems suboptimal to me because the archives of [email protected] would be split between two areas, and the public-whatwg archives would have a confusing mix of the CG list and [email protected]. |
Thanks @gosko for investigating! Since the volume on these lists is so low and the effort to keep them working indefinitely non-trivial, the new plan I'd like to propose is:
|
The list addresses auto-reply as suggested above. I've revised the plan for lists.whatwg.org a little bit, however:
|
I like that idea. I might even encourage folks to file an issue on whatwg/meta if they encounter such a broken link so we can help them out. |
This is done :) |
This is all that remains of #7.
Search the issue for "mail" for some previous attempts/discussion.
The text was updated successfully, but these errors were encountered: