replacement for FreeBSD:
* Use an rc.subr start/stop script.
* Include contributed periodic scripts.
* Replace $PREFIX with the build-time value of PREFIX.
* Generate a default configure file if it doesn't exist at install-time.
* Remove the default configure file if it hasn't been modified at
deinstall-time.
* Install additional documentation.
* Move creation and removal of /var/log/exim to pkg-plist.
Bump PORTREVISION accordingly.
This paves the way for ports/56458, which teaches sysinstall about Exim.
Bug trhodes about that PR. :-)
PR: ports/56450
Submitted by: Oliver Eikemeier <eikemeier@fillmore-labs.com>
* Move the contents of pkg-message into POST-INSTALL-NOTES, which
gets installed in the !NOPORTDOCS case for future reference.
* Refer to POST-INSTALL-NOTES from pkg-message in the !NOPORTDOCS
case. In the NOPORTDOCS case, use POST-INSTALL-NOTES as the
pkg-message.
Bite the bullet _now_ and use MTA user exim instead. This means that
only early adopters of Exim-3.31 are affected, rather than lots more
folks further down the line.
I still think mailnull is better, but nobody in the Exim community
agrees with me. :-)
Bump PORTREVISION as appropriate.
utility supplied with Exim is intended for systems that don't have
something as nifty as newsyslog(8).
I'm tempted to remove the utility from the port/package, but this
delta to pkg-message is less controversial.
FreeBSD has shipped with mailwrapper(8), which facilitates the use of
drop-in replacements for sendmail. Retire exim.sh in favour of the
mailwrapper(8) approach.
Requested by: AMAKAWA Shuhei <sa264@cam.ac.uk>
Replace it with a patch against the distribution configure.default,
which changes as little as possible so that folks who are accustomed to
Exim on other platforms will not be astonished.
Install the file as configure.default instead of configure.sample, since
it's as close as damnit to the default Exim configuration file.
The only arguably unnecessary deviation from the default is:
* Accept SMTP relay from the loopback IP address. Too many applications
require this, and the window of abuse is arguably negligible.
``info exim'' would fail to descend into any of the 3 Exim info files
from the dir top branch.
While we're at it, add a pkg-message that
1) Points to the documentation
2) Explains how to get Exim started
