3490
Comment: Revamp, add migration instructions
|
3001
List admin needs to change the host_name setting
|
Deletions are marked like this. | Additions are marked like this. |
Line 7: | Line 7: |
/!\ '''This page is currently in flux.''' We are still figuring out the details of how we want DomTool to interact with Mailman. |
|
Line 11: | Line 9: |
If you would like a mailing list managed by our global [http://www.gnu.org/software/mailman/ Mailman] [https://lists.hcoop.net/ listinfo installation], you must first [https://members2.hcoop.net/portal/list place a request on the portal]. | If you would like a mailing list managed by our global [http://www.gnu.org/software/mailman/ Mailman] [https://lists.hcoop.net/listinfo installation], you must first [https://members2.hcoop.net/portal/list place a request on the portal]. |
Line 15: | Line 13: |
You then have a choice between doing list management at [https://lists.hcoop.net/admin/LISTNAME https://lists.hcoop.net/admin/''LISTNAME''] or at your own domain. | You then have a choice between doing list management at [https://lists.hcoop.net/admin/LISTNAME https://lists.hcoop.net/admin/LISTNAME] or at your own domain. |
Line 38: | Line 36: |
mailmanWebHost "VHOST.DOMAIN"; end; |
mailman "VHOST"; |
Line 41: | Line 38: |
(* This has to be its own subdomain, if you want to be able to *) (* provide the alias "mailman@VHOST.DOMAIN", which is advertised *) (* on http://VHOST.DOMAIN/listinfo. Alas, there is no way to *) (* change that alias to "mailman@DOMAIN", short of patching *) (* Mailman. Otherwise, you could get by with a dnsIP line. *) (* Perhaps this is something best generated automatically by *) (* Domtool. *) domain "VHOST.DOMAIN" with nameserver "ns1.hcoop.net"; nameserver "ns3.hcoop.net"; dnsDefault "69.90.123.67"; |
(* Do the following if you want the email address given on *) (* http://VHOST.DOMAIN/listinfo to work. *) |
Line 57: | Line 45: |
The list admin web interface then will be available at {{{http://VHOST.DOMAIN.TLD/admin/LISTNAME}}}. | The list admin web interface then will be available at {{{http://VHOST.DOMAIN/admin/LISTNAME}}}. /!\ Be sure to change the '''host_name''' setting for the list using the list admin web interface, or messages sent to that list will come from the wrong domain! |
This page describes how to set up and manage mailing lists on your domain.
Request a Mailing List
If you would like a mailing list managed by our global [http://www.gnu.org/software/mailman/ Mailman] [https://lists.hcoop.net/listinfo installation], you must first [https://members2.hcoop.net/portal/list place a request on the portal].
Setup Instructions
You then have a choice between doing list management at [https://lists.hcoop.net/admin/LISTNAME https://lists.hcoop.net/admin/LISTNAME] or at your own domain.
Using https://hcoop.net/ for the web interface
If you are fine with using the main hcoop.net site for your list's web interface, then there is nothing left to do except wait for the list to be created.
You can then access your list at https://hcoop.net/admin/LISTNAME, where LISTNAME is the name of your list.
Using your own domain for the web interface
If you would like the web interface to be at your own domain, then you must do some simple domain configuration.
LISTNAME is the name you gave your list,
DOMAIN is your domain,
VHOST is the virtual subdomain you would like the web interface to be accesible from.
USER is your HCoop username.
If you want to access the site from your domain with no subdomain, then use the default virtual host for VHOST (in other words, "www").
domain "DOMAIN" with (* Other configuration stuff... *) mailman "VHOST"; (* Do the following if you want the email address given on *) (* http://VHOST.DOMAIN/listinfo to work. *) handleMail; emailAlias "mailman" "USER"; end;
The list admin web interface then will be available at http://VHOST.DOMAIN/admin/LISTNAME.
Be sure to change the host_name setting for the list using the list admin web interface, or messages sent to that list will come from the wrong domain!
Hosting Domains Elsewhere
You can host mailing lists with us that use your own domains, even if your domain is primarily hosted elsewhere.
The best way of doing this is for you to point your domain's MX record to deleuze.hcoop.net. If you want to use the Mailman webinterface on a subdomain, then point that subdomain at deleuze.hcoop.net, as well.
Migrating an Existing List
If you previously hosted a mailing list on Fyodor, our old machine, then file a request at [https://bugzilla.hcoop.net/enter_bug.cgi Our bug-tracker], using the Mailman component. Be sure to tell us what the name of your list is.
If you haven't hosted a mailing list with us before, it is still possible to migrate a list over to our machines, provided that you have an mbox file containing the archives, and the file config.pck containing your settings. File a request at [https://bugzilla.hcoop.net/enter_bug.cgi Our bug-tracker], using the Mailman component, and we will help you out.