doc/doc-txt/IncompatibleChanges

   1 Preamble
   2 ========
   3
   4 Normally The Exim Maintainers ensure that a configuration which works
   5 with version N will work with version N+1, within a major version number
   6 (eg, 4).
   7
   8 Occasionally this will not be the case; usually, those changes will be
   9 at the end of a long notice period where admins have been encouraged to
  10 move away and even then, we are hesitant to fully break things without
  11 strong cause to move away.
  12
  13 This does not apply to "experimental" features, which can be withdrawn
  14 or changed with little notice, although we still endeavour to limit
  15 that.  We may choose to note those changes here too.
  16
  17 The most likely cause of a backwards-incompatible change is a security
  18 improvement, where the benefits for everyone strongly outweigh the needs
  19 of the few.
  20
  21
  22 Changes
  23 =======
  24
  25 Exim version 4.73
  26 -----------------
  27
  28  * The Exim run-time user can no longer be root; this was always
  29    strongly discouraged, but is now prohibited both at build and
  30    run-time.  If you need Exim to run routinely as root, you'll need to
  31    patch the source and accept the risk.  Here be dragons.
  32
  33  * Exim will no longer accept a configuration file owned by the Exim
  34    run-time user, unless that account is explicitly the value in
  35    CONFIGURE_OWNER, which we discourage.  Exim now checks to ensure that
  36    files are not writable by other accounts.
  37
  38  * ALT_CONFIG_ROOT_ONLY is no longer optional and is forced on; the Exim
  39    user can no longer use -C/-D and retain privilege.
  40
  41  * The system_filter_user option now defaults to the Exim run-time user,
  42    rather than root.  You can still set it explicitly to root and this
  43    can be done with prior versions too, letting you roll versions
  44    without needing to change this configuration option.
  45