On Wed, Oct 29, 2014 at 10:39:05AM -0400, alan@??? wrote:
> I postulate a Linux box, with exim, and with three users,
> alan, ben, and charles. Let us suppose the name of this
> machine is abc.greatbox. Let us also suppose that Alan,
> Ben, and Charles have hired a professional mailserver,
> him.com, to act as a smart host, or relay host.
Switching gears for a moment:
http://www.postfix.org/BASIC_CONFIGURATION_README.html#relayhost
http://www.postfix.org/SOHO_README.html#fantasy
http://www.postfix.org/SASL_README.html#client_sasl
http://www.postfix.org/TLS_README.html#client_tls
give in combination (with example.net as the ISP's email domain,
and the local domain defaulting to the hostname).
/etc/postfix/main.cf:
# Often ISP outbound relays use port 587 with TLS and SASL,
# adjust as necessary:
#
# smtp_tls_security_level = verify
# smtp_tls_loglevel = 1
# smtp_tls_CAfile = /some/file/with/trusted/root/cas.pem
# smtp_sasm_auth_enable = yes
# smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
# relayhost = [smtp.example.net]:587
#
# The below is for a port 25 relay with no TLS or SASL.
#
relayhost = [smtp.example.net]
# Map internal domain to external:
#
smtp_generic_maps = hash:/etc/postfix/generic
# Externalize addresses when sending mail out.
#
/etc/postfix/generic:
alan alan@???
ben ben@???
charles charles@???
# If using port 587 with SASL, ...
/etc/postfix/sasl_password:
[smtp.example.net]:587 sasl-loginname:sasl-password
And now you're beginning to see why a naive expectation of a single
document that covers every combination of use-cases is unrealistic.
MTAs are complex systems with many separately tunable moving parts.
Describing every combination of settings is out of the question.
> Can some expert take the time to describe _exactly_ how to
> do this?
Only if you hire such an expert to build your system. Otherwise,
you'll have to read the documentation and map your requirements
onto the various supported features, checking the documentation
for each feature in turn.
--
Viktor.
