From cad98b98badf9e9b061c07f42e0915b401faf9e0 Mon Sep 17 00:00:00 2001 From: nigel Date: Fri, 14 Jun 2002 10:42:15 +0000 Subject: [PATCH] minor updates --- home.html | 47 +++------------------------------------------- howto/mailman.html | 34 ++++++++++++++++----------------- version.html | 12 +++++------- 3 files changed, 25 insertions(+), 68 deletions(-) diff --git a/home.html b/home.html index d136603..b6bd8be 100644 --- a/home.html +++ b/home.html @@ -30,49 +30,8 @@ exim releases, and may sometimes trail versions by a few days or even weeks
  • - Exim version 3.35 and 4.02 have both been released. These - are bug fix releases over the previous versions. -
  • -
  • - Exim Version 4.00 is available - see the availability pages to get hold of a - copy. This is a major new release with some major changes - from version 3.x, as such it should be treated with care. -
  • -
  • - Exim - course at Cambridge on 24-26 June, 2002. -
  • -
  • - Exim Version 3.34 is available - see the availability pages to get hold of a - copy. Documentation has been patially updated to match. - Version 3.34 fixes an exploitable (in rare configurations) - security bug - upgrading is strongly recommended. -
  • -
  • - Printed copies of the - Exim 3 documentation are available from BSDMall as part of Prime - Freeware's Dossier - project (NB this is a printed form of - documents bundled in electronic form with Exim). -
  • -
  • - The information on the Mailing - Lists also now contains a search form. -
  • -
  • - A Generic Windows Executable Content filter is - available at - ftp://ftp.exim.org/pub/filter/ or here. This is an exim system - filter which attempts to detect executables including the - types responsible for the Windows/Outlook mail worms, and also - the recent bugs with header length checking (see this - BugTraq article). It is not infallible, but many sites - may find it useful. The file contains installation - instructions. NB this is no longer being maintained. + Current Exim versions are 3.36 and 4.05, both of + which are bug fix releases over the previous versions.
  • @@ -85,6 +44,6 @@
    Nigel Metheringham
    -
    $Id: home.html,v 1.19 2002/03/07 21:56:36 nigel Exp $
    +
    $Id: home.html,v 1.20 2002/03/26 14:08:11 nigel Exp $
    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 @@ - HOWTO - Using exim and mailman together + HOWTO - Using exim and Mailman together -

    HOWTO - Using exim and mailman together

    +

    HOWTO - Using exim and Mailman together

    Mailman is a list manager with web front end and built in archiving functions. Details can be found at http://www.list.org/

    Mailman configuration

    -

    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.

    Exim configuration

    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

    Main config file section

    @@ -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. -
  • If you are getting exim or mailman complaining about user ids +
  • If you are getting exim or Mailman complaining about user ids when you send mail to a list, check that the MAILMAN_UID and - MAILMAN_GID match those of mailman itself. Also make sure you do + MAILMAN_GID match those of Mailman itself. Also make sure you do not have aliases in the main alias file for the list.
  • Other Tweaks

    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
    Nigel Metheringham
    -

    $Id: mailman.html,v 1.1.1.1 2000/05/22 19:54:43 nigel Exp $

    +

    $Id: mailman.html,v 1.2 2000/05/30 19:59:57 nigel Exp $

    diff --git a/version.html b/version.html index 01a1835..d623026 100644 --- a/version.html +++ b/version.html @@ -7,14 +7,12 @@

    Versions of exim

    -

    The latest release is 4.02. This is a major upgrade +

    The latest release is 4.05. This is a major upgrade over the 3.x versions which will require configuration files to be - rewritten (there are tools to help with this). As an early - release of a major new version cautious users may wish to test - carefully before moving to production services. 4.02 and - 4.01 are a bug fix releases over 4.00

    + rewritten (there are tools to help with this). This release is a + recommended bug fix update over earlier 4.0x versions.

    -

    The latest 3.x release is 3.35. This is the latest bug fix +

    The latest 3.x release is 3.36. This is the latest bug fix release in the 3.3x series. They are an incremental upgrade over the 3.2x series with a few new features. There is a security issue (rare but exploitable) with versions previous to 3.34 @@ -43,6 +41,6 @@


    Nigel Metheringham
    -

    $Id: version.html,v 1.11 2002/03/07 21:56:36 nigel Exp $

    +

    $Id: version.html,v 1.12 2002/03/26 14:08:11 nigel Exp $

    -- 2.30.2