Hi Michael
This is what we use:
tls_certificate = /etc/exim4/ssl/${interface_address}.crt
tls_privatekey = /etc/exim4/ssl/${interface_address}.key
Then simply name your cert and key files according to your interface ip
addresses.
You should be able to use a lookup in a file with
On Fri, 15 May 2015 11:39:18 +0200 M. Piscaer wrote:
[ ... ]
I see settings like tls_on_connect_ports, tls_certificate and
tls_privatekey. That that uses only one TLS certificate. The problem I
have multiple IP addresses and multiple hostnames. So I need to clue it
all together
Put all the
Hi,
I'm replacing an postfix setup for exim4. This because exim has better
mail routing options then postfix. This server is used as an Smarthost
for its ISP customers.
In the current setup that we use, we have multible hostnames to connect
to the server.
All are TLS enabled, with postfix we
On Fri, May 15, 2015 at 11:39:18AM +0200, M. Piscaer wrote:
I'm replacing an postfix setup for exim4. This because exim has better
mail routing options then postfix. This server is used as an Smarthost
for its ISP customers.
I hope your migration goes smoothly. When you're all done, and
have
On 2015-05-14, Rob Gunther red...@gmail.com wrote:
Looks like I figured out part of the issue. The destination server is
refusing to accept mail from some of our Exim servers. They have their
Exchange connector locked down so we get this on some connections:
*421 4.3.2 Service not
