X-Git-Url: https://git.exim.org/exim-website.git/blobdiff_plain/1c9ad1cfe19dce95ac0f38c4e214eb829a738641..b4f56e92b58c554309aad4132f059b2f867686e3:/howto/mailman.html diff --git a/howto/mailman.html b/howto/mailman.html index 4efb795..ac7068c 100644 --- a/howto/mailman.html +++ b/howto/mailman.html @@ -1,32 +1,32 @@
-Mailman is a list manager with web front end and built in archiving functions. Details can be found at http://www.list.org/
There is no mailman configuration needed other than the - standard options detailed in the mailman install documentation. - The exim configuration is transparent to mailman. The uid/gid - settings for mailman must match those in the config fragments +
There is no Mailman configuration needed other than the + standard options detailed in the Mailman install documentation. + The exim configuration is transparent to Mailman. The uid/gid + settings for Mailman must match those in the config fragments given below.
The exim configuration is built so that a list created within - mailman automagically appears to exim without the need for + Mailman automagically appears to exim without the need for additional alias files etc to be changed.
The drawback of this configuration is that it will work poorly on systems supporting lists in several different mail domains - - for that matter mailman itself has poor support for this right + for that matter Mailman itself has poor support for this right now. This may change in the future
The configuration file segments included are to be built on top @@ -44,7 +44,7 @@ mailman-admin (plus any other global contact addresses for the list master). These addresses point to a (or some - not necessarily the same for all of these aliases) human rather than - being piped into mailman. You do not need to put per-list + being piped into Mailman. You do not need to put per-list entries into the system alias file, and doing so will most likely break things since the user id used for delivery is likely to be incorrect or not set (which causes an exim delivery time config @@ -52,7 +52,7 @@
There are 3 config file sections below which need pasting into the appropriate parts of the main exim config file. The first one - may also need tailoring to your mailman configuration
+ may also need tailoring to your Mailman configuration@@ -60,11 +60,11 @@ ## Tailor these to fit your installation ## pretty much everything else should just fit... ## -# home dir for mailman +# home dir for Mailman MAILMAN_HOME=/home/mailman # wrapper script for mailman MAILMAN_WRAP=MAILMAN_HOME/mail/wrapper -# user and group for mailman +# user and group for Mailman MAILMAN_UID=exim MAILMAN_GID=exim@@ -170,16 +170,16 @@ you like receiving tons of mail when a host is down. for a list. If you delete lists by foul means, be aware of this. -
One solution passed to me for handling virtual domains was - - Since I use mailman in a virtual domain configuration with a + Since I use Mailman in a virtual domain configuration with a separate installation for each virtual domain, I did a slight modification like this:
@@ -232,7 +232,7 @@ delay_warning = 26h ##delay_warning_condition = "${if match{$h_precedence:}{(?i)bulk|list|junk}{no}{yes}}" # # Verify receipient addresses on everything except local injects -# DO NOT verify addresses from mailman - this would slow down +# DO NOT verify addresses from Mailman - this would slow down # the acceptance of messages dramatically receiver_verify_hosts = !127.0.0.1/8:0.0.0.0/0 sender_verify @@ -265,6 +265,6 @@ exim-users-admin@www.exim.org