exim releases, and may sometimes trail versions by a few days or
even weeks</i></li>
<li>
- Exim version 3.35 and 4.02 have both been released. These
- are bug fix releases over the previous versions.
- </li>
- <li>
- Exim Version 4.00 is available - see the <a
- href="mirrors.html">availability</a> 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.
- </li>
- <li>
- <a href="http://www-tus.csx.cam.ac.uk/courses/exim/">Exim
- course at Cambridge</a> on 24-26 June, 2002.
- </li>
- <li>
- Exim Version 3.34 is available - see the <a
- href="mirrors.html">availability</a> 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.
- </li>
- <li>
- Printed copies of the <a href="http://www.bsdmall.com/emexmailtran.html">
- Exim 3 documentation</a> are available from BSDMall as part of Prime
- Freeware's <a href="http://ptf.com/dossier/">Dossier</a>
- project</a> (NB this is a printed form of
- documents bundled in electronic form with Exim).
- </li>
- <li>
- The information on the <a href="maillist.html">Mailing
- Lists</a> also now contains a search form.
- </li>
- <li>
- A <b>Generic Windows Executable Content</b> filter is
- available at <a href="ftp://ftp.exim.org/pub/filter/">
- ftp://ftp.exim.org/pub/filter/</a> or <A
- HREF="system_filter.exim">here</A>. 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 <A
- HREF="http://www.securityfocus.com/frames/?content=/templates/article.html%3Fid%3D61">
- BugTraq article</A>). It is not infallible, but many sites
- may find it useful. The file contains installation
- instructions. <b>NB this is no longer being maintained.</b>
+ Current Exim versions are <b>3.36</b> and <b>4.05</b>, both of
+ which are bug fix releases over the previous versions.
</li>
</ul>
<hr>
<address><a href="mailto:Postmaster@exim.org">Nigel Metheringham</a></address>
<!-- Created: Sun May 16 21:43:01 BST 1999 -->
- <h6>$Id: home.html,v 1.19 2002/03/07 21:56:36 nigel Exp $</h6>
+ <h6>$Id: home.html,v 1.20 2002/03/26 14:08:11 nigel Exp $</h6>
</body>
</html>
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
- <title>HOWTO - Using exim and mailman together</title>
+ <title>HOWTO - Using exim and Mailman together</title>
</head>
<body bgcolor="#FFFFFF" text="#00005A" link="#FF6600" alink="#FF9933" vlink="#990000">
- <h1>HOWTO - Using exim and mailman together</h1>
+ <h1>HOWTO - Using exim and Mailman together</h1>
<p>Mailman is a list manager with web front end and built in
archiving functions. Details can be found at <a href="http://www.list.org/">http://www.list.org/</a></p>
<h2>Mailman configuration</h2>
- <p>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
+ <p>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.</p>
<h2>Exim configuration</h2>
<p>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.</p>
<p>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</p>
<p>The configuration file segments included are to be built on top
<tt>mailman-admin</tt> (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 <b>not</b> need to put per-list
+ being piped into Mailman. You do <b>not</b> 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
<p>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</p>
+ may also need tailoring to your Mailman configuration</p>
<h4>Main config file section</h4>
<pre>
## 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
</pre>
for a list. If you delete lists by foul means, be aware of
this.</li>
- <li>If you are getting exim or mailman complaining about user ids
+ <li>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
<b>not</b> have aliases in the main alias file for the list.</li>
</ul>
<h2>Other Tweaks</h2>
<p>One solution passed to me for handling virtual domains was -
- <i>Since I use mailman in a virtual domain configuration with a
+ <i>Since I use Mailman in a virtual domain configuration with a
separate installation for each virtual domain, I did a slight
modification like this:</i></p>
##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
<hr>
<address><a href="mailto:Postmaster@exim.org">Nigel Metheringham</a></address>
<!-- Created: Mon Aug 25 15:46:41 BST 1997 -->
- <h4>$Id: mailman.html,v 1.1.1.1 2000/05/22 19:54:43 nigel Exp $</h4>
+ <h4>$Id: mailman.html,v 1.2 2000/05/30 19:59:57 nigel Exp $</h4>
</body>
</html>
<body bgcolor="#FFFFFF" text="#00005A" link="#FF6600" alink="#FF9933" vlink="#990000">
<h1>Versions of exim</h1>
- <p>The latest release is <b>4.02</b>. This is a major upgrade
+ <p>The latest release is <b>4.05</b>. 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. <b>4.02</b> and
- <b>4.01</b> are a bug fix releases over <b>4.00</b></p>
+ rewritten (there are tools to help with this). This release is a
+ recommended bug fix update over earlier <b>4.0x</b> versions.</p>
- <p>The latest 3.x release is <b>3.35</b>. This is the latest bug fix
+ <p>The latest 3.x release is <b>3.36</b>. 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
<hr>
<address><a href="mailto:Postmaster@exim.org">Nigel Metheringham</a></address>
<!-- Created: Mon Aug 25 15:46:41 BST 1997 -->
- <h4>$Id: version.html,v 1.11 2002/03/07 21:56:36 nigel Exp $</h4>
+ <h4>$Id: version.html,v 1.12 2002/03/26 14:08:11 nigel Exp $</h4>
</body>
</html>
git://git.exim.org / exim-website.git / commitdiff