[Pkg-exim4-users] exim4, gmail and 550-5.7.1

Robert Steinmetz rob at steinmetznet.com
Fri Dec 18 16:09:28 UTC 2015

Based on the link I listed in my first post I have come up with a 
potential solution:

Can anyone comment on whether it should work or not?

I propose adding a new files in /etc/exim4/conf.d/main



domainlist ipv4_force_domains = \
gmail.com : \
googlemail.com : \
virgin.net : \
linkedin.com : \

Greping router for remote_smtp

I get

100_exim4-config_domain_literal: transport = remote_smtp
150_exim4-config_hubbed_hosts: transport = remote_smtp
200_exim4-config_primary: transport = remote_smtp
200_exim4-config_primary: transport = remote_smtp
200_exim4-config_primary: transport = remote_smtp_smarthost
500_exim4-config_hubuser: transport = remote_smtp_smarthost

So I propose adding a new file to /etc/exim4/conf.d/router called



driver = dnslookup
domains = +ipv4_force_domains
transport = ipv4_smtp
ignore_target_hosts = <; 0::0/0|

Finally adding a file in /etc/exim4/conf.d/transports


I'm a little puzzled by the one in the example.

driver = smtp
dkim domain = mydomain.co.uk
dkim_selector = x
dkim_private_key = /usr/exim/dkim.private.key
dkim_canon = relaxed
interface = <my.v4.ip.address>|

Why can't I simply use the existing smtp remote_smtp transport with
the some relatively simple edits? This example contains a directive
that limits it to using ipv4 by specifying the interface using an
ipv4 address. Seems like somewhere should be a directive like
disable_ipv6 = true or dns_ipv4_lookup = *

I also wonder if these dkim statements conflict with the rest of the
basic debian configuration.

More information about the Pkg-exim4-users mailing list