Skip to content
This repository

Exim Mail Transport Agent - source, testsuite and documentation

Bail configuration on missing package

If we're configured to use pkg-config (or pcre-config) and the tool is
not available or does not know about the package we ask for, that should
be a fatal configuration error.

We should not silently ignore the missing package, then try to compile,
and have missing header warnings from the compiler.  Eg, if we're told
to support GSASL, we'll try to compile the client code, and without
compiler flags, we'll either fail to compile (missing headers) or fail
to link, which obscures the source of the errors.

This change will only break people who had builds set to have Exim
depend upon non-existent packages, and that _needs_ to break.
latest commit 14ea0bea67
Phil Pennock philpennock authored
Octocat-spinner-32 configs Remove obsolete $Cambridge$ CVS revision strings. June 29, 2011
Octocat-spinner-32 doc Add back deprecated SPF error conditions April 15, 2014
Octocat-spinner-32 release-process quickrelease: A dumb script for making source-only tarballs November 07, 2013
Octocat-spinner-32 src Bail configuration on missing package April 15, 2014
Octocat-spinner-32 test More care with headers add/remove lists. Bug 1452 April 09, 2014
Octocat-spinner-32 .gitignore Add gdb history file to git ignore July 12, 2013
Octocat-spinner-32 Readme.pod Rough readme mainly for benefit of github November 18, 2011

Exim Development Repository

This is the Exim (Mail Transport Agent) Development Repository. Please read the following information if you wish to use or contribute to the Exim development process - this is to prevent your or our time being unnecessarily wasted.

If you just want to use, build or get information on Exim then have a look at the pointers further down this file at "General Exim Information".

General Development Information

The general Exim development process and resources are documented in the wiki page at - although the wiki is likely to be moved and rehashed in the near future.

The sections below this duplicate much of the information form the wiki document.

Development Repositories

Exim development is kept within a git ( repository. The master repository is at git:// with a web interface giving change and source visibility at

There is a secondary repository on github at managed by the Exim Organisation - however this may currently fall out of synchronisation with the main one. We intend to manage this better in the future, but it is currently early days for our github repo.

Bug Tracking

Currently this is all done using Bugzilla at - please do not use github issue tracking.

Mailing List

Development issues are normally discussed on the exim-dev Mailing list - see

Exim Release Process

Some documentation on the realse process can be found at

General Exim Information

The best place to get general information is on the website at

You can find Download locations, Mailing list info and Full Documentation on that website.

If you are using a Linux or other freely available Unix like operating system it is very likely that your system will have Exim packaged for it already. In this case it is probably prudent to use these packages unless you have specialised requirements.

In any case you can always ask on the Exim Users mailing list for further information.


Something went wrong with that request. Please try again.