debian/exim4-config.NEWS

   1 exim4 (4.84.2-2) jessie; urgency=medium
   2
   3   As part of the fix for CVE-2016-1531 updated Exim versions clean
   4   the complete execution environment by default, affecting Exim and
   5   subprocesses such as routers calling other programs, and thus may break
   6   existing installations. New configuration options (keep_environment,
   7   add_environment) were introduced to adjust this behavior. Because of the
   8   possible breakage Exim will show a runtime warning if keep_environment is
   9   not set.
  10
  11   The Debian exim4 configuration does not rely on specific environment
  12   variables and therefore sets 'keep_environment =' (i.e confirm empty
  13   environment).
  14
  15   Users of custom Exim configurations will need to check whether their setup
  16   continues to work with the abovementioned upstream change and modify the
  17   Exim environment as needed otherwise. If the setup works fine with empty
  18   environment it is still necessary to set the main configuration option
  19   "keep_environment =" to quiet the runtime warning.
  20
  21   See <https://exim.org/static/doc/CVE-2016-1531.txt> for details.
  22
  23  -- Andreas Metzler <ametzler@debian.org>  Mon, 28 Mar 2016 17:58:09 +0200
  24
  25 exim4 (4.68-1) unstable; urgency=low
  26
  27     In order to fix #420217, the handling of incoming messages to
  28     system accounts has been changed once again. To allow system
  29     account mail addresses to be redirected via traditional
  30     /etc/aliases, system accounts are now processed later in the
  31     router chain.
  32
  33     This has made it necessary to change the default behavior of the
  34     real- prefix. real-foo is now only accessible for locally
  35     generated messages, such as the error message generated by the
  36     userforward router. If you need the old behavior back, set the
  37     macro COND_LOCAL_SUBMITTER=true. As a side-effect, you can
  38     entirely switch off the real- processing by setting
  39     COND_LOCAL_SUBMITTER=false.
  40
  41  -- Marc Haber <mh+debian-packages@zugschlus.de>  Thu, 04 Oct 2007 22:34:01 +0200
  42
  43 exim4 (4.67-6) unstable; urgency=low
  44
  45     acl_whitelist_local_deny was renamed to acl_local_deny_exceptions
  46     to avoid confusion. This means changes to ACLs, file names in
  47     /etc/exim4/conf.d/acl and the exception list file names themselves.
  48
  49     CONFDIR/local_host_whitelist and CONFDIR/local_sender_whitelist
  50     have been renamed to CONFDIR/host_local_deny_exceptions and
  51     CONFDIR/sender_local_deny_exceptions. The old files will continue
  52     to be honored for a transition period.
  53
  54     The old file conf.d/acl/20_exim4-config_whitelist_local_deny will
  55     get a .dpkg-bak suffix if it had local changes, and it will be
  56     removed if there were no local changes. In the case of local changes,
  57     you'll need to repeat these changes in the new file
  58     conf.d/acl/20_exim4-config_local_deny_exceptions.
  59
  60  -- Marc Haber <mh+debian-packages@zugschlus.de>  Wed, 05 Sep 2007 21:22:22 +0200
  61
  62 exim4 (4.67-5) unstable; urgency=low
  63
  64     The macro generation in update-exim4.conf has been changed once
  65     more. update-exim4.conf now looks for the (non-commented!)
  66     definition of the exim configuration macro UPEX4CmacrosUPEX4C to
  67     an arbitrary, non-empty value, and inserts the generated macro
  68     definitions right after this line, without changing it.
  69
  70     update-exim4.conf looks for commented UPEX4CmacrosUPEX4C (which
  71     used to be the place marker in earlier 4.67-x versions) and barfs
  72     if it finds them anywhere in /etc/exim4/exim4.conf.template or
  73     recursively /etc/exim4/conf.d. This check - as a feature - also
  74     includes files that would normally be excluded by
  75     update-exim4.conf, such as .dpkg-old and .dpkg-dist files.
  76
  77     If you insist on having a commented UPEX4CmacrosUPEX4C in your
  78     exim configuration and don't want update-exim4.conf to barf, set
  79     the exim macro UPEX4CmacrosOK_config_adapted to a non-empty value.
  80
  81  -- Marc Haber <mh+debian-packages@zugschlus.de>  Thu, 28 Jun 2007 08:29:36 +0200
  82
  83 exim4 (4.67-4) unstable; urgency=low
  84
  85     Since a lot of users did not read the docs while upgrading and
  86     filed bug reports about exim4-config failing to install due to a
  87     "malformed macro definition", update-exim4.conf.conf now checks
  88     for DEBCONFsomethingDEBCONF strings anywhere in
  89     /etc/exim4/exim4.conf.template or recursively /etc/exim4/conf.d
  90     and barfs if such strings are found. This check - as a feature - also
  91     includes files that would normally be excluded by
  92     update-exim4.conf.
  93
  94     It _is_ necessary to either accept the offered configuration file
  95     change _or_ to manually check a manually changed exim config. Exim
  96     will _NOT_ run if a configuration file of an older version is
  97     being used with a more recent exim4-config.
  98
  99     If you insist on having DEBCONFsomethingDEBCONF strings in your
 100     exim configuration and don't want update-exim4.conf to barf, set
 101     the exim macro DEBCONFstringOK_config_adapted to a non-empty
 102     value.
 103
 104  -- Marc Haber <mh+debian-packages@zugschlus.de>  Fri, 22 Jun 2007 12:50:38 +0200
 105
 106 exim4 (4.67-2) experimental; urgency=low
 107
 108     The symlink /etc/exim4/email-addresses caused data loss for people
 109     who had a local file named /etc/exim4/email-addresses. The Debian
 110     tools do not handle symlinks in /etc which are contained in
 111     packages very well, so we decided to simply remove it. Please
 112     submit a tested patch if you think that it would be a more elegant
 113     way to handle the transition from /etc/exim4/email-addresses to
 114     /etc/email-addresses.
 115
 116     There is now a possibility to modify handling of incoming messages
 117     to system accounts, identified by their UID (see
 118     conf.d/router/250_exim4-config_lowuid). If you want this, set the
 119     macro FIRST_USER_ACCOUNT_UID (which defaults to 0) to the UID of
 120     your first "real" user account. Incoming messages for an account
 121     with an UID below that value get routed according to the extra
 122     alias file /etc/exim4/lowuid-aliases. If an account does not have
 123     an alias there, it gets routed to the value of the macro
 124     DEFAULT_SYSTEM_ACCOUNT_ALIAS, which defaults to ":fail: no mail to
 125     system accounts" and gets the message rejected. You can use this
 126     mechanism to route all messages for system accounts to a single
 127     address, with exceptions. Locally generated messages are not
 128     processed by this facility.
 129
 130     Generation of the final exim configuration has changed. The
 131     configuration no longer has the DEBCONFsomethingDEBCONF
 132     placeholders. All data from Debconf are put into exim
 133     configuration macros by update-exim4.conf, which are then
 134     appropriately picked up by the configuration itself. There should
 135     be no visible change to people who have not modified their
 136     configuration, but customized configurations need to adapt.
 137
 138     We now do basic sanitizing of input read from
 139     update-exim4.conf.conf. If your update-exim4.conf complains about
 140     non-ascii values, you have found a bug. Please report it.
 141
 142  -- Marc Haber <mh+debian-packages@zugschlus.de>  Mon, 11 Jun 2007 14:09:24 +0200
 143
 144 exim4 (4.62-7) unstable; urgency=low
 145
 146     Bug #392993 says that 4.63-5 and -6 have overwritten manual
 147     setting of dc_local_delivery with one of the default versions if
 148     you have set dc_local_delivery to a value that is not either
 149     mail_spool or maildir_home. Please verify that your
 150     dc_local_delivery does still point to the transport you have
 151     chosen.
 152
 153     Please note that the debconf configuration only supports plain
 154     lists. Advanced features like "dsearch;" entered there may work
 155     today, but are not guaranteed to continue working in the future.
 156
 157     If you want to use such features, please use the macros made
 158     available for use in the configuration or edit the configuration
 159     itself.
 160
 161     This allows us to use semicolons as list delimiters consistently
 162     while still being backwards compatible to colon-separated lists
 163     without driving code complexity up too high.
 164
 165     Starting with this version, update-exim4.conf will print a warning
 166     if a dsearch lookup is found in the list of local domains,
 167     dc_local_domains since there is a HOWTO on the Internet that
 168     recommends doing this kind of things and this will _not_ work any
 169     more.
 170
 171  -- Marc Haber <mh+debian-packages@zugschlus.de>  Sun, 15 Oct 2006 10:00:15 +0000
 172
 173 exim4 (4.62-4) unstable; urgency=low
 174
 175     exim4-config has had its debconf templates re-worked. Basic
 176     functionality is unchanged, so you shouldn't expect a real
 177     difference. The priority of most questions has been lowered to
 178     medium, so that the Installer can install exim4 with no questions
 179     being asked. The default is local delivery only. Mail messages for
 180     root and postmaster are delivered to an mbox file in
 181     /var/mail/mail, make sure to read them.
 182
 183     You can do the full exim4 configuration by calling
 184     dpkg-reconfigure exim4-config as root.
 185
 186     It is now finally possible to configure exim4 to deliver outgoing
 187     mail to a smarthost on a port number different from 25 via debconf.
 188
 189  -- Marc Haber <mh+debian-packages@zugschlus.de>  Mon,  9 Oct 2006 14:12:25 +0000
 190
 191 exim4 (4.62-3) unstable; urgency=low
 192
 193     A template for SPF support is now provided.  It is disabled by
 194     default, and relies on external calls to spfquery(1) from the
 195     libmail-spf-query-perl package. For details, check README.Debian,
 196     and conf.d/acl/30_exim4-config_check_rcpt.
 197
 198  -- Robert Millan <rmh@aybabtu.com>  Fri, 28 Jul 2006 22:43:56 +0200
 199
 200 exim4 (4.62-1) unstable; urgency=low
 201
 202     Please note that the handling of update-exim4.conf.conf has
 203     changed with regard to dc_local_interfaces and dc_relay_nets: If
 204     the strings given there contain a semicolon, the string "<;" is
 205     now prepended to the value written to the configuration file to
 206     consider ; a list separator. This significantly helps writing down
 207     IPv6 addresses, but means that if you use complex things like
 208     lookups in update-exim4.conf.conf, you'll have to change your
 209     configuration to use the macros that directly interfere with the
 210     configuration.
 211
 212     127.0.0.1 and ::1 have been removed from the default hostlist
 213     relay_from_hosts - these addresses are now added by
 214     update-exim4.conf with the appropriate separator. If you set
 215     MAIN_RELAY_NETS manually, you'll need to add these two addresses
 216     to your local host list.
 217
 218  -- Marc Haber <mh+debian-packages@zugschlus.de>  Sat, 29 Apr 2006 22:36:31 +0000
 219
 220 exim4 (4.50-5) unstable; urgency=low
 221
 222     mailname, the local name of the system used to qualify senders and
 223     recipients is no longer a local domain by default. Having local
 224     delivery for that host name used to break satellite and smarthost
 225     setups where no local delivery was expected.
 226     /etc/exim4/update-exim4.conf.conf is modified automatically on
 227     upgrade from the appropriate earlier versions, so if you don't do any
 228     funky things with /etc/exim4/update-exim4.conf.conf, you should be fine.
 229
 230  -- Marc Haber <mh+debian-packages@zugschlus.de>  Sat,  2 Apr 2005 20:31:27 +0200
 231
 232 exim4 (4.43-3) unstable; urgency=low
 233
 234     /etc/exim4/email-addresses is ignored now, please use /etc/email-addresses!
 235     The last version of exim4 that shipped this file was uploaded on the
 236     19th of May 2003, and I really do not want to start sarge with cruft like
 237     that.
 238
 239  -- Andreas Metzler <ametzler@debian.org>  Mon, 10 Jan 2004 10:05:34 +0100
 240
 241 exim4 (4.34-1) unstable; urgency=low
 242
 243     Debconf will not ask for relay_domains if configuring smarthost or
 244     satellite-type systems. - This functionality was untested and could
 245     generate mail-loops.
 246
 247  -- Andreas Metzler <ametzler@debian.org>  Wed, 12 May 2004 13:42:23 +0200
 248
 249 exim4 (4.30-5) unstable; urgency=low
 250
 251     (Re)introduce /etc/exim4/exim4.conf.template as alternative to the
 252     multiple small files in /etc/exim4/conf.d/ and make it the default choice
 253     for fresh installations. This trades in a loss of comfort (you will again
 254     need to merge in each small change manually) for increased stability.
 255
 256  -- Andreas Metzler <ametzler@debian.org>  Sun, 11 Jan 2004 13:03:43 +0100
 257
 258 exim4 (4.20-2) unstable; urgency=low
 259
 260     Rewriting now uses /etc/email-addresses instead of
 261     /etc/exim4/email-addresses like exim v3 did. Please move the contents to
 262     the new file and delete the old one, when you have time to spare.
 263
 264  -- Andreas Metzler <ametzler@debian.org>  Tue, 15 Jul 2003 10:20:15 +0200