[hcoop/zz_old/ikiwiki] / MailingListConfiguration.mdwn

Before continuing with this page, you probably want to read DomainTool to learn the basics of how we handle shared daemon configuration.\r
\r
If you would like a mailing list managed by our global [http://www.list.org/ Mailman] installation you must first [https://members.hcoop.net/portal/list place a request on the portal]. You then have a choice between doing list management at [http://hcoop.net/cgi-bin/mailman/admin/LISTNAME http://hcoop.net/cgi-bin/mailman/admin/''LISTNAME''] or at your own domain.\r
\r
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.\r
\r
''LISTNAME'' is the name you gave your list, ''DOMAIN'' is your domain, and ''TLD'' is the TLD (org, com, name, ...) of your domain, ''VHOST'' is the virtual subdomain you would like the web interface to be accesible from. If you want to access the site from your domain with no subdomain then use the default virtual host for ''VHOST''.\r
\r
 * 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.\r
 * Place the `Mailman` directive in the VirtualHostConfiguration at `/etc/domains/TLD/DOMAIN/VHOST`.\r
 * Run domtool\r
\r
Now the list admin web interface will be available at http://VHOST.DOMAIN.TLD/cgi-bin/mailman/admin/LISTNAME.\r
\r
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.\r
Commit	Line	Data
ee25310d	1	Before continuing with this page, you probably want to read DomainTool to learn the basics of how we handle shared daemon configuration.\r
	2	\r
	3	If you would like a mailing list managed by our global [http://www.list.org/ Mailman] installation you must first [https://members.hcoop.net/portal/list place a request on the portal]. You then have a choice between doing list management at [http://hcoop.net/cgi-bin/mailman/admin/LISTNAME http://hcoop.net/cgi-bin/mailman/admin/''LISTNAME''] or at your own domain.\r
	4	\r
	5	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.\r
	6	\r
	7	''LISTNAME'' is the name you gave your list, ''DOMAIN'' is your domain, and ''TLD'' is the TLD (org, com, name, ...) of your domain, ''VHOST'' is the virtual subdomain you would like the web interface to be accesible from. If you want to access the site from your domain with no subdomain then use the default virtual host for ''VHOST''.\r
	8	\r
	9	* 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.\r
	10	* Place the `Mailman` directive in the VirtualHostConfiguration at `/etc/domains/TLD/DOMAIN/VHOST`.\r
	11	* Run domtool\r
	12	\r
	13	Now the list admin web interface will be available at http://VHOST.DOMAIN.TLD/cgi-bin/mailman/admin/LISTNAME.\r
	14	\r
	15	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.\r