1. Debian Exim4 User FAQ

This is work in progress, so it is probably not yet very helpful.

?TableOfContents

1.1. Questions not categorized yet

1.1.1. When I try to deliver a message via SMTP to my Exim, I get "550 relay not permitted"

Answer not yet fleshed out.

• dc_relay_nets
• If client host is on dynamic IP, SMTP AUTH
• ISP blocking tcp/25

1.1.2. I cannot connect to my Exim from my home connection. From internet hosts, it works

Answer not yet fleshed out.

• ISP blocking tcp/25
• Use ISP Smarthost
• Use tcp/587

• ISP blocking incoming tcp/25 => no chance to have an MX there

1.1.3. I am trying to have exim forward mail to some internal hosts, but all I am getting is "all relevant MX records point to non-existent hosts"

A probeble cause for this might be that all MX records for the offending domain point to site local or link local IP addresses, which are ignored by the dnslookup router to protect from misconfigured external domains. The default configuration has relaxed checking for domains that the local system is configured to allow relaying to, so adding the offending domain to dc_relay_domains will most probably help.

Please note that no domain on the public Internet should have MX records pointing to site local or link local IP addresses, so you might check your externally visible MX records.

If this doesn't help, try analyzing the output of exim -d -bt some.local.part@the.offending.domain.example

[http://www.exim.org/eximwiki/FAQ/Routing_to_remote_hosts/Q0302 Upstream Exim FAQ Q0302] might help as well.

1.1.4. What do "lowest numbered MX record points to local host" or "remote host address is the local host" mean?

This is covered in [http://www.exim.org/eximwiki/FAQ/Routing_to_remote_hosts/Q0301 Upstream Exim FAQ Q0301.] The Debian default configuration has the hubbed_hosts router mentioned there already defined. Its configuration file is /etc/exim4/hubbed_hosts, and some documentation can be found in /etc/exim4/conf.d/router/150_exim4-config_hubbed_hosts.