Mailman - Revision history

Admin at 16:26, 28 May 2011

2011-05-28T16:26:09Z

← Older revision		Revision as of 16:26, 28 May 2011
Line 274:		Line 274:
	$ /path/to/mailman/bin/config_list -i /path/to/mailman/var/data/sitelist.cfg mailman		$ /path/to/mailman/bin/config_list -i /path/to/mailman/var/data/sitelist.cfg mailman
	</source>		</source>

			{{Programs}}

Admin at 08:50, 8 April 2011

2011-04-08T08:50:21Z

← Older revision		Revision as of 08:50, 8 April 2011
Line 1:		Line 1:
	A guide to installing GNU Mailman and getting it working with an Apache web server and a Postfix ~~mail server~~.		A guide to installing GNU Mailman and getting it working with an [[Apache]] web server and a Postfix [[Mail Server]].

	=Installation=		=Installation=

Admin at 08:49, 8 April 2011

2011-04-08T08:49:56Z

← Older revision		Revision as of 08:49, 8 April 2011
Line 1:		Line 1:
			A guide to installing GNU Mailman and getting it working with an Apache web server and a Postfix mail server.

	=Installation=		=Installation=

Admin: /* Using Mailman */

2011-04-08T05:27:37Z

Using Mailman

@@ Line 203: / Line 203: @@
-=Using Mailman=
+=Mailing List Basics=
 Every new list will have a set of email addresses that can be used to interface with the mailing list.
@@ Line 238: / Line 226: @@
 * mylist-confirm@example.com - another email robot, which processes confirmation messages for subscription and unsubscription requests

Admin: /* Using Mailman */

2011-04-08T01:44:14Z

Using Mailman

← Older revision		Revision as of 01:44, 8 April 2011
Line 214:		Line 214:

	to administer/create mailing lists.		to administer/create mailing lists.



			Every new list will have a set of email addresses that can be used to interface with the mailing list.

			For a list called mylist@example.com, you have these addresses:

			* mylist@example.com - this is the email address people should use for new postings to the list.

			* mylist-join@example.com - by sending a message to this address, a new member can request subscription to the list (both the subject and body of the message are ignored)

			* mylist-subscribe@exmaple.com - alias for the -join address

			* mylist-leave@example.com - request unsubscription from the list (both hte subject and the body are ignored)

			* mylist-unsubscribe@example.com - alias for the -leave address

			* mylist-owner@example.com - email the list owners and moderators directly

			* mylist-request@example.com - emails the mail robot, which processes email commands that can be used to set member subscription options, as well as process other commands

			* mylist-bounces@example.com - receives bounces from members whose addresses have become either temporarily or permanently inactive; the -bounces address is also a mail robot that processes bounces and automatically disables or removes members as configured in the bounce processing settings; any bounce messages that are either unrecognized, or do not seem to contain member addresses, are forwarded to the list administrators

			* mylist-confirm@example.com - another email robot, which processes confirmation messages for subscription and unsubscription requests

Admin: /* Connecting Mailman with Web Server */

2011-04-08T01:32:24Z

Connecting Mailman with Web Server

← Older revision		Revision as of 01:32, 8 April 2011
Line 81:		Line 81:

	<syntaxhighlight lang="apache">		<syntaxhighlight lang="apache">
	~~<IfModule alias_module>~~

	~~[...]~~		# Add a script alias for mailman to run required cgi-scripts
			ScriptAlias /mailman/ "/path/to/mailman/cgi-bin/"
	# Add a script alias for mailman to run required cgi-scripts
	ScriptAlias /mailman/ "/path/to/mailman/cgi-bin/"

	~~[...]~~

	~~</IfModule>~~

	~~[...]~~

	<Directory "/path/to/mailman/cgi-bin">		<Directory "/path/to/mailman/cgi-bin">
	AllowOverride None		AllowOverride None
	Options ExecCGI		Options ExecCGI FollowSymLinks
	Order allow,deny		Order allow,deny
	Allow from all		Allow from all
Line 130:		Line 121:

	<syntaxhighlight lang="apache">		<syntaxhighlight lang="apache">
	~~<IfModule alias_module>~~		Alias /pipermail/ /path/to/mailman/var/archives/public/

	~~[...]~~		<Directory /pipermail/>
			Options FollowSymLinks
			AddDefaultCharset Off # <-- if your list archives will
			# contain international characters
			AllowOverride None
			Order deny,allow
			Allow from all
			</Directory>

	~~Alias /pipermail/ "/path/to/mailman/var/archives/public/"~~

	~~[...]~~

	~~</IfModule>~~
	</syntaxhighlight>		</syntaxhighlight>

	~~And to properly display international characters, add this:~~

	~~<syntaxhighlight lang="apache">~~
	~~<Directory "/path/to/mailman/var/archives/public/">~~
	~~AddDefaultCharset Off~~
	~~</Directory>~~
	~~</syntaxhighlight>~~


	==Connecting Mailman with Mail Server==		==Connecting Mailman with Mail Server==

Admin at 01:29, 8 April 2011

2011-04-08T01:29:37Z

@@ Line 53: / Line 53: @@
 $ ./runconfigure.sh
 $ make -j2
-$ /usr/bin/sudo -u mailman make install # <-- must be run as sudo because creating/modifying directories owned by "mailman" user
+$ /usr/bin/sudo -u mailman make install # <-- must be run as sudo because
 </pre>
@@ Line 215: / Line 217: @@
 $ /usr/bin/sudo -u mailman crontab /path/to/mailman/cron/crontab.in
 </pre>

Admin at 01:06, 8 April 2011

2011-04-08T01:06:33Z

@@ Line 23: / Line 23: @@
 ./configure \
      --prefix=${HOME}/pkg/mailman/2.1.14 \
-     --with-var-prefix=${HOME}/pkg/mailman/var
+     --with-var-prefix=${HOME}/pkg/mailman/var \
 </syntaxhighlight>
 Before I ran configure, I had to run
@@ Line 75: / Line 84: @@
      # Add a script alias for mailman to run required cgi-scripts
-     ScriptAlias /mailman/ "/path/to/apache/cgi-bin/"
+     ScriptAlias /mailman/ "/path/to/mailman/cgi-bin/"
      [...]
 </IfModule>
 </syntaxhighlight>
@@ Line 108: / Line 127: @@
 This can be set up to be accessed via the web:
-<syntaxhighglight lang="apache">
+<syntaxhighlight lang="apache">
 <IfModule alias_module>
@@ Line 133: / Line 152: @@
 See [[Mail Server]] for details on how to set up a mail server.
-I use postfix mail server
+I use postfix mail server.

Admin at 21:29, 7 April 2011

2011-04-07T21:29:15Z

← Older revision		Revision as of 21:29, 7 April 2011
Line 102:		Line 102:
	(default values for most stuff is defined in Defaults.py).		(default values for most stuff is defined in Defaults.py).

	==Setting Up Pipermail==		===Setting Up Pipermail===

	Pipermail is a feature of Mailman that archives all of the mailing list's activity and makes it available to users. This is basically what's being put in <code>/var/mailman</code> (or, in case you used the <code>--with-var-prefix</code> configure option above, <code>/path/to/mailman/var</code>).		Pipermail is a feature of Mailman that archives all of the mailing list's activity and makes it available to users. This is basically what's being put in <code>/var/mailman</code> (or, in case you used the <code>--with-var-prefix</code> configure option above, <code>/path/to/mailman/var</code>).
Line 127:		Line 127:
	</Directory>		</Directory>
	</syntaxhighlight>		</syntaxhighlight>


			==Connecting Mailman with Mail Server==

			See [[Mail Server]] for details on how to set up a mail server.

			I use postfix mail server

Admin at 21:27, 7 April 2011

2011-04-07T21:27:00Z

← Older revision		Revision as of 21:27, 7 April 2011
Line 30:		Line 30:
	<pre>		<pre>
	$ mkdir -p ${HOME}/pkg/mailman/var		$ mkdir -p ${HOME}/pkg/mailman/var
	$ /usr/bin/sudo chown mailman ${HOME}/pkg/mailman		$ /usr/bin/sudo -R chown mailman ${HOME}/pkg/mailman
	$ /usr/bin/sudo chgrp mailman ${HOME}/pkg/mailman		$ /usr/bin/sudo -R chgrp mailman ${HOME}/pkg/mailman
	$ /usr/bin/sudo chmod 02775 ${HOME}/pkg/mailman # <-- the "02" sets UID and GID permissions		$ /usr/bin/sudo -R chmod 02775 ${HOME}/pkg/mailman # <-- the "02" sets UID and GID permissions
	</pre>		</pre>

	(for more info on setting UID and GID permissions, see http://en.wikipedia.org/wiki/Setuid)		(for more info on setting UID and GID permissions, see http://en.wikipedia.org/wiki/Setuid)

			'''NOTE''': I acknowledge that using <code>--with-var-prefix</code> is more complicated, but the advantages are, (1) this keeps mailman self-contained, and (2) it is easy to upgrade mailman by installing the new version to <code>${HOME}/pkg/mailman/X.Y.Z</code>.

	Once you've created this directory with the correct permissions, do the usual thing:		Once you've created this directory with the correct permissions, do the usual thing: