|
Size: 2211
Comment: Try to categorize a bit
|
Size: 3485
Comment: fix listinfo link
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| /!\ '''This page is currently out of date.''' We are still figuring out how to migrate mailing lists and set up Mailman. | /!\ '''This page is currently in flux.''' We are still figuring out the details of how we want DomTool to interact with Mailman. |
| Line 9: | Line 9: |
| = Request a mailing list = | = Request a Mailing List = |
| Line 11: | Line 11: |
| If you would like a mailing list managed by our global [http://www.list.org/ Mailman] 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 13: | Line 13: |
| = Setup instructions = | = Setup Instructions = |
| Line 15: | Line 15: |
| You then have a choice between doing list management at [http://deleuze.hcoop.net/cgi-bin/mailman/admin/LISTNAME http://hcoop.net/cgi-bin/mailman/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 17: | Line 17: |
| 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. If you would like the web interface to be at your own domain, then you must do some simple domain configuration. | == 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. |
| Line 21: | Line 29: |
| * '''TLD''' is the top-level domain (org, com, name, ...) of your domain, | |
| Line 23: | Line 30: |
| * '''USER''' is your HCoop username. | |
| Line 24: | Line 32: |
| If you want to access the site from your domain with no subdomain, then use the default virtual host for ''VHOST''. | 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"). |
| Line 26: | Line 34: |
| * Write `VHOST.DOMAIN.TLD` to `/etc/domains/TLD/DOMAIN/.mailman`. You must do this '''before''' requesting the list on the portal or it will have no effect. * Place the `Mailman` directive in the VirtualHostConfiguration at `/etc/domains/TLD/DOMAIN/VHOST`. * Run domtool |
{{{ domain "DOMAIN" with (* Other configuration stuff... *) |
| Line 30: | Line 38: |
| = Manage your mailing lists = | mailmanWebHost "VHOST.DOMAIN"; end; |
| Line 32: | Line 41: |
| The list admin web interface will be available at http://VHOST.DOMAIN.TLD/cgi-bin/mailman/admin/LISTNAME. | (* 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"; handleMail; emailAlias "mailman" "USER"; end; }}} |
| Line 34: | Line 57: |
| = Hosting domains elsewhere = | The list admin web interface then will be available at {{{http://VHOST.DOMAIN.TLD/admin/LISTNAME}}}. |
| Line 36: | Line 59: |
| Note that you '''can''' host mailing lists with us that use your own domains even if your domain is primarily hosted elsewhere. However, the best way we know of doing this is for you to point your domain's MX record to `mail.hcoop.net`. If you don't know what this means, then you probably shouldn't be trying anything so complicated as splitting a domain's hosting between several providers in the first place. | = 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. |
This page describes how to set up and manage mailing lists on your domain.
![/!\](/moin_static1911/moniker_bt/img/alert.png "/!\"){kind=small}
This page is currently in flux. We are still figuring out the details of how we want DomTool to interact with Mailman.
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... *) mailmanWebHost "VHOST.DOMAIN"; end; (* 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"; handleMail; emailAlias "mailman" "USER"; end;
The list admin web interface then will be available at http://VHOST.DOMAIN.TLD/admin/LISTNAME.
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.