The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Exim 4.54

Discussion in 'General Discussion' started by bsasninja, Oct 25, 2005.

  1. bsasninja

    bsasninja Well-Known Member

    Sep 2, 2004
    Likes Received:
    Trophy Points:
    Does anybody knows when cpanel will update to the Exim 4.54 ??

  2. easyhoster1

    easyhoster1 Well-Known Member

    Sep 25, 2003
    Likes Received:
    Trophy Points:
    Been running it on all our servers for a few weeks now

    /scripts/eximup will get you the latest.
  3. movielad

    movielad Well-Known Member

    May 14, 2003
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    DataCenter Provider
    I'd imagine that's the non-Maildir version? The latest Maildir version of Exim appears to be 4.52 unless I need to update the backend scripts or something.


  4. anup123

    anup123 Well-Known Member

    Mar 29, 2004
    Likes Received:
    Trophy Points:
    This Planet
    exim (exim-4.52-15_cpanel_maildir)

    on 10.8.1 C 3

    So that's the latest apparently.

  5. chirpy

    chirpy Well-Known Member

    Jun 15, 2002
    Likes Received:
    Trophy Points:
    Go on, have a guess
    Why do you need to be running Exim v4.54?
  6. djalpha

    djalpha Active Member

    Jan 20, 2003
    Likes Received:
    Trophy Points:
    just info

    just info:

    Exim version 4.53
    TK/01 Added the "success_on_redirect" address verification option. When an
          address generates new addresses during routing, Exim will abort
          verification with "success" when more than one address has been
          generated, but continue to verify a single new address. The latter
          does not happen when the new "success_on_redirect" option is set, like
          require verify = recipient/success_on_redirect/callout=10s
          In that case, verification will succeed when a router generates a new
    PH/01 Support for SQLite database lookups has been added. This is another
          query-style lookup, but it is slightly different from the others because
          a file name is required in addition to the SQL query. This is because an
          SQLite database is a single file and there is no daemon as in other SQL
          databases. The interface to Exim requires the name of the file, as an
          absolute path, to be given at the start of the query. It is separated
          from the query by white space. This means that the path name cannot
          contain white space. Here is a lookup expansion example:
            ${lookup sqlite {/some/thing/sqlitedb \
              select name from aliases where id='ph10';}}
          In a list, the syntax is similar. For example:
            domainlist relay_domains = sqlite;/some/thing/sqlitedb \
               select * from relays where ip='$sender_host_address';
          The only character affected by the ${quote_sqlite: operator is a single
          quote, which it doubles.
          The SQLite library handles multiple simultaneous accesses to the database
          internally. Multiple readers are permitted, but only one process can
          update at once. Attempts to access the database while it is being updated
          are rejected after a timeout period, during which the SQLite library
          waits for the lock to be released. In Exim, the default timeout is set
          to 5 seconds, but it can be changed by means of the sqlite_lock_timeout
          Note that you must set LOOKUP_SQLITE=yes in Local/Makefile in order to
          obtain SQLite support, and you will also need to add -lsqlite3 to the
          EXTRALIBS setting. And of course, you have to install SQLite on your
          host first.
    PH/02 The variable $message_id is now deprecated, to be replaced by
          $message_exim_id, which makes it clearer which ID is being referenced.
    PH/03 The use of forbid_filter_existstest now also locks out the use of the
          ${stat: expansion item.
    PH/04 The IGNOREQUOTA extension to the LMTP protocol is now available in both
          the lmtp transport and the smtp transport running in LMTP mode. In the
          lmtp transport there is a new Boolean option called ignore_quota, and in
          the smtp transport there is a new Boolean option called
          lmtp_ignore_quota. If either of these options is set TRUE, the string
          "IGNOREQUOTA" is added to RCPT commands when using the LMTP protocol,
          provided that the server has advertised support for IGNOREQUOTA in its
          response to the LHLO command.
    PH/05 Previously, if "verify = helo" was set in an ACL, the condition was true
          only if the host matched helo_try_verify_hosts, which caused the
          verification to occur when the EHLO/HELO command was issued. The ACL just
          tested the remembered result. Now, if a previous verification attempt has
          not happened, "verify = helo" does it there and then.
    PH/06 It is now possible to specify a port number along with a host name or
          IP address in the list of hosts defined in the manualroute or
          queryprogram routers, fallback_hosts, or the "hosts" option of the smtp
          transport. These all override any port specification on the transport.
          The relatively standard syntax of using a colon separator has been
          adopted, but there are some gotchas that need attention:
          * In all these lists of hosts, colon is the default separator, so either
            the colon that specifies a port must be doubled, or the separator must
            be changed. The following two examples have the same effect:
              fallback_hosts = host1.tld::1225 : host2.tld::1226
              fallback_hosts = <; host1.tld:1225 ; host2.tld:1226
          * When IPv6 addresses are involved, it gets worse, because they contain
            colons of their own. To make this case easier, it is permitted to
            enclose an IP address (either v4 or v6) in square brackets if a port
            number follows. Here's an example from a manualroute router:
               route_list = * "</ []:1225 / [::1]:1226"
          If the "/MX" feature is to be used as well as a port specifier, the port
          must come last. For example:
               route_list = *  dom1.tld/mx::1225
    PH/07 $smtp_command_argument is now set for all SMTP commands, not just the
          non-message ones. This makes it possible to inspect the complete command
          for RCPT commands, for example. But see also PH/45 below.
    PH/08 The ${eval expansion now supports % as a "remainder" operator.
    PH/09 There is a new ACL condition "verify = not_blind". It checks that there
          are no blind (bcc) recipients in the message. Every envelope recipient
          must appear either in a To: header line or in a Cc: header line for this
          condition to be true. Local parts are checked case-sensitively; domains
          are checked case-insensitively. If Resent-To: or Resent-Cc: header lines
          exist, they are also checked. This condition can be used only in a DATA
          or non-SMTP ACL.
          There are, of course, many legitimate messages that make use of blind
          (bcc) recipients. This check should not be used on its own for blocking
    PH/10 There is a new ACL control called "suppress_local_fixups". This applies
          to locally submitted (non TCP/IP) messages, and is the complement of
          "control = submission". It disables the fixups that are normally applied
          to locally-submitted messages. Specifically:
          (a) Any Sender: header line is left alone (in this respect, it's a
              dynamic version of local_sender_retain).
          (b) No Message-ID:, From:, or Date: headers are added.
          (c) There is no check that From: corresponds to the actual sender.
          This feature may be useful when a remotely-originated message is
          accepted, passed to some scanning program, and then re-submitted for
          delivery. It means that all four possibilities can now be specified:
          (1) Locally submitted, fixups applies: the default.
          (2) Locally submitted, no fixups applied: use control =
          (3) Remotely submitted, no fixups applied: the default.
          (4) Remotely submitted, fixups applied: use control = submission.
    PH/11 There is a new log selector, "unknown_in_list", which provokes a log
          entry when the result of a list match is failure because a DNS lookup
    PH/12 There is a new variable called $smtp_command which contains the full SMTP
          command (compare $smtp_command_argument - see PH/07 above). This makes it
          possible to distinguish between HELO and EHLO, and also between things
          like "MAIL FROM:<>" and "MAIL FROM: <>".
    TF/01 There's a new script in util/ which extracts sending
          rates from log files, to assist with choosing appropriate settings
          when deploying the ratelimit ACL condition.
    PH/13 A new letter, "H", is available in retry parameter sets. It is similar
          to "G" (geometric increasing time intervals), except that the interval
          before the next retry is randomized. Each time, the previous interval is
          multiplied by the factor in order to get a maximum for the next interval.
          The mininum interval is the first argument of the parameter, and an
          actual interval is chosen randomly between them. Such a rule has been
          found to be helpful in cluster configurations when all the members of the
          cluster restart at once, and may synchronize their queue processing
    PH/14 The options never_users, trusted_users, admin_groups, and trusted_groups
          are now expanded when the configuration file is read.

    Exim version 4.54
    There was a problem with 4.52/TF/02 in that a "name=" option on control=
    submission terminated at the next slash, thereby not allowing for slashes in
    the name. This has been changed so that "name=" takes the rest of the string as
    its data. It must therefore be the last option.

Share This Page