- What do lowest numbered MX record points to local host and *remote
- Why does Exim say all relevant MX records point to non-existent hosts
- How do I configure Exim to send all messages to a central server? I
- How do I configure Exim to send all non-local mail to a gateway host?
- How can I arrange for mail on my local network to be delivered directly
- How do I configure Exim to send all non-local mail to a central server
^foo$:^bar$ $domainin a manualroute
- I have a domain for which some local parts must be delivered locally,
- How can I configure Exim on a firewall machine so that if mail arrives
- If a DNS lookup returns no MX records why doesn't Exim just bin the
- When a DNS lookup for MX records fails to complete, why doesn't Exim
- Is it possible to use a conditional expression for the host item in a
- I send all external mail to a smart host, but this means that bad
- I have a really annoying intermittent problem where attempts to mail to
- I'd like route all mail with addresses that can't be resolved (the DNS
- I would like to forward all incoming email for a particular domain to
- What I'd like to do is have alternative smart hosts, where the one to be
- Exim won't route to a host with no MX record.
- I have some mails on my queues that are sticking around longer than the
- How can I arrange for all mail to
- How can I tell an Exim router to use only IPv4 or only IPv6 addresses
- How can I reroute all messages bound for 192.168.10.0 and 10.0.0.0 to a
Clone this wiki locally
Why does Exim say all relevant MX records point to non-existent hosts when MX records point to IP addresses?
MX records cannot point to IP addresses. They are defined to point to
host names, so Exim always interprets them that way. (An IP address is a
syntactically valid host name.) The DNS for the domain you are having
problems with is misconfigured. However, it appears that more and more
DNS zones are breaking the rules and putting IP addresses on the RHS of
MX records. Exim follows the rules and rejects this, but other MTAs do
support it, so the
allow_mx_to_ip was regretfully added at release
3.14 to permit this heinous activity.
- there may be rules ignoring hosts on the local network (e.g. 192.168.0.0/16).