 | |
| Original author(s) | Philip Hazel |
|---|---|
| Developer(s) | The Exim Maintainers |
| Initial release | 1995; 30 years ago (1995) |
| Stable release | 4.98.1[1]  / 21 February 2025 |
| Repository | |
| Written in | C |
| Operating system | Unix-like |
| Platform | Cross-platform |
| Type | Mail transfer agent |
| License | GPL-2.0-or-later[2] |
| Website | www |
Exim is amail transfer agent (MTA) used onUnix-like operating systems. Exim is afree software distributed under the terms of theGNU General Public License, and it aims to be a general and flexible mailer with extensive facilities for checking incominge-mail.
Exim has beenported to most Unix-like systems, as well as toMicrosoft Windows using theCygwin emulation layer. Exim 4 is currently the default MTA onDebianLinux systems.[3]
Many Exim installations exist, especially withinInternet service providers[4] and universities in the United Kingdom. Exim is also widely used with theGNU Mailman mailing list manager, andcPanel.
In March 2023 a study performed by E-Soft, Inc.,[5] approximated that 59% of the publicly reachable mail-servers on the Internet ran Exim.
The first version of Exim was written in 1995 byPhilip Hazel for use in theUniversity of Cambridge Computing Service’s e-mail systems. The name initially stood forEXperimentalInternetMailer.[6] It was originally based on an older MTA,Smail-3, but it has since diverged from Smail-3 in its design and philosophy.[7][8]
Exim, likeSmail, still follows theSendmaildesign model, where asingle binary controls all the facilities of the MTA. Exim has well-defined stages during which it gains or losesprivileges.[9]
Exim's security has had a number of serioussecurity problems diagnosed over the years.[10] Since the redesigned version 4 was released there have been four remote code execution flaws and one conceptual flaw concerning how much trust it is appropriate to place in therun-time user; the latter was fixed in a security lockdown in revision 4.73, one of the very rare occasions when Exim has brokenbackwards compatibility with working configurations.
Exim is highly configurable and therefore has features that are lacking in other MTAs. It has always had substantial facilities for mail policy controls, providing facilities for the administrator to control who may send or relay mail through the system. In version 4.x this has matured to anAccess Control List based system allowing very detailed and flexible controls. The integration of a framework for content scanning, which allowed for easier integration ofanti-virus andanti-spam measures, happened in the 4.x releases. This made Exim very suitable for enforcing diverse mail policies.
The configuration is done through a (typically single) configuration file, which must include the main section with generic settings and variables, as well as the following optional sections:
The configuration file permits inclusion of other files, which leads to two different configuration styles.
There are two main schools of configuration style for Exim. The native school keeps the Exim configuration in one file and external files are only used as data sources; this is strongly influenced by Philip Hazel's preferences and notes on performance as the configuration file is re-read at every exec, which happens post-fork for receiving inbound connections and at delivery.
The second commonly encountered style is theDebian style which is designed to make it easier to have an installed application automatically provide mail integration support without having the administrator edit configuration files. There are a couple of variants of this andDebian provide documentation of their approach as part of the packages. In these approaches, a debconf configuration file is used to build the Exim configuration file, together with templates and directories with configuration fragments. The meta-config is tuned with macros which have names startingDC_. When the supervisor for exim is invoked it re-processes the configuration files producing a single-file configuration that the exim binary uses.
Because the Debian approach diverges significantly from the Exim one it is common to find a lack of support for the Debian approach on the regular Exim mailing-lists, with people advised[11][12] to ask Debian questions on the Debian-managed mailing-list. The Ubuntu packaging[13] still advises users to use the Debian mailing-list.
Exim has extensive and exhaustive documentation; if a feature or some behaviour is not documented then this is classed as a bug. The documentation consists of The Exim Specification and two ancillary files: the experimental specification for features that might disappear and "NewStuff", which tracks very recent changes that might not have been fully integrated into the main specification. The Exim Specification is available in multiple formats, including online in HTML and in plain-text for fast searching. The document preparation system ensures that the plain-text format is highly usable.
Exim has been deployed in busy environments, often handling thousands of emails per hour efficiently. Exim is designed to deliver email immediately, without queueing. However, its queue processing performance is comparatively poor when queues are large (which happens rarely on typical low-traffic sites but can happen regularly on high-traffic sites).
Unlikeqmail,Postfix, andZMailer, Exim does not have a central queue manager (i.e. an equivalent ofqmail-send,qmgr, orscheduler). There is thus no centralized load balancing of queue processing (leading to disproportionate amounts of time being spent on processing the same queue entries repeatedly). System-wide remote transport concurrency is unlimited by default (leading to a "thundering herd problem" when multiple messages addressed to a single domain are submitted at once) but can be limited by the configuration. In Philip Hazel's own words:[14]
In 1997, Hazel replaced Exim'sPOSIXregular expression library written byHenry Spencer with a new library he developed calledPCRE (Perl Compatible Regular Expressions).Perl regular expressions are much more powerful than POSIX and other common regular expressions, and PCRE has become popular in applications other than Exim. In 2021 (after the 4.95 release)Exim transitioned to PCRE2.
Historically, Exim used a peculiar version numbering scheme where the first decimal digit is updated only whenever the main documentation is fully up to date; until that time, changes were accumulated in the file NewStuff. For this reason, a 0.01 version change can signify important changes, not necessarily fully documented.[15] In 2005, changes to Exim's version numbering were on the table of discussion.[16]
In more recent times, the document preparation system for Exim has been overhauled and changes are much more likely to just go immediately into The Exim Specification. The 4.70 release just followed on naturally from 4.69 and the 4.6x releases had up-to-date documentation.
Philip Hazel retired from the University of Cambridge in 2007 and maintenance of Exim transitioned to a team of maintainers. Exim continues to be maintained actively, with frequent releases.
| Open source |
|  | ||||
|---|---|---|---|---|---|---|
| Proprietary | ||||||
| Related technologies | ||||||
| Related articles | ||||||
| International | |
|---|---|
| National | |
