Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Debian machine running Exim4.

However, when checking the Exim log, I noticed this issue when mailing my own domain:

2010-12-14 09:20:01 1PSQ77-0005mG-9w ** all relevant MX records point to non-existent hosts
2010-12-14 09:20:01 1PSQ77-0005mJ-CH ** all relevant MX records point to non-existent hosts

And when checking MX in dig:

# dig mx
;            IN  MX

;; ANSWER SECTION:     3600    IN  MX  50     3600    IN  MX  10

;; ADDITIONAL SECTION: 2082    IN  A   2382 IN  A

;; Query time: 1 msec
;; WHEN: Tue Dec 14 09:21:22 2010
;; MSG SIZE  rcvd: 126

Yet I am able to ping and telnet the Barracuda server:

# ping
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=64 time=5.17 ms
64 bytes from icmp_seq=2 ttl=64 time=0.647 ms

--- ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 5066ms
rtt min/avg/max/mdev = 0.647/2.910/5.174/2.264 ms

# telnet 25
Connected to
Escape character is '^]'.
220 ***************************************************************

Any clue what might cause Exim to spit out those errors?


share|improve this question
up vote 2 down vote accepted

the problem is that the MX records are in the RFC1918 private range. By default exim refuses to connect to private IPS. Take a look in your config for a line like this:

ignore_target_hosts = : : : : :

and modify it to suit your needs.

share|improve this answer
solved it -- thanks – Tuinslak Dec 14 '10 at 13:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.