MX records point to non-existent hosts

imiviortal

New member
Joined
Jun 28, 2009
Messages
4
hello,
im using directadmin, the newest version.
now, im trying to send emails, for some addresses ive got no problem and the email sent secessfully, though for some recipients the email isnt sent, and i get immediatley the following message :

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

[email protected]
all relevant MX records point to non-existent hosts or (invalidly) to IP addresses

------ This is a copy of the message, including all the headers. ------

Return-path: <[email protected]>
Received: from localhost ([127.0.0.1] helo=[195.189.140.107])
by server1.emath.co.il with esmtpa (Exim 4.67)
(envelope-from <[email protected]>)
id 1MKq1n-0005jo-JT
for [email protected]; Sun, 28 Jun 2009 11:46:23 +0300
Received: from 77.126.188.238
(SquirrelMail authenticated user [email protected])
by 195.189.140.107 with HTTP;
Sun, 28 Jun 2009 11:46:23 +0300
Message-ID: <[email protected]>
Date: Sun, 28 Jun 2009 11:46:23 +0300
Subject: =?iso-8859-1?Q?=F0=E9=F1=E9=E5=EF_=EE=E0=EE=E9=F8?=
From: [email protected]
To: [email protected]
Reply-To: [email protected]
User-Agent: SquirrelMail/1.4.19
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal

?????? ?????

it happends under every domain im trying to send through, and through every email account.

i tried sending the mail to the specific address (through gmail) and the email sent secessfully .

ive searched alot in google and in this forum and i think i should set the
allow_mx_to_ip to true, though ive no idea where to do that .

thanks for the help .
 
Your server may be seeing the wrong DNS information. Check the mx record for the domain from both your server, and from the outside. Is the domain hosted by you? If so, then also check the mx record in the zone file on your server. Check the contents of your /etc/resolv.conf file to see what nameserver(s) your local server is using for lookups, and check there as well.

Jeff
 
The /etc/resolv.conf file is found exactly where it says it's found.

The zone files for your domains are found as listed in /etc/named.conf.

Jeff
 
ok, in the file etc/exim.conf ive got this :

# DO HOST LOOKUP
# OPTIONAL MODIFICATIONS:
# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.

host_lookup = *

and this :

# Remote addresses are those with a domain that does not match any item
# in the "local_domains" setting above.

# This router routes to remote hosts over SMTP using a DNS lookup. Any domain
# that resolves to an IP address on the loopback interface (127.0.0.0/8) is
# treated as if it had no DNS entry.

lookuphost:
driver = dnslookup
domains = ! +local_domains
ignore_target_hosts = 127.0.0.0/8
condition = "${perl{check_limits}}"
transport = remote_smtp
no_more

how can it help me, does i need to write on this file allow_mx_to_ip=true ??

in addition the domain is hosted by me (i own dedicated server)

and i think that the mx records are configured well, cause most of the emails as i mentioned are sent.
 
RFC prohibits use of an IP address as MX record. The domain "focus-telecom.com" has an IP as MX records, therefore it won't work.
If the domain is yours, correct this. If it isn't, get in contact with the domain owner (the whois registry has a post address, a phone number and a working email address).

If you really want to support IP addresses as MX records as a temporary workaround you can set allow_mx_to_ip=true, but I strongly suggest you don't.
 
why not to do allow_mx_to_ip=true ?
The domain "focus-telecom.com" isnt mine, though when i sending an email through gmail for e.g ,to this address ,the email is sent successfuly! so the my problem is on my end ..
 
Last edited:
Of course GMail technicians don't have time to deal with RFC-related matters, and they allow the MX record to be an IP address... like I said, if you don't have time either just set it as a temporary workaround, but I must tell you: if everyone does that, the Internet won't be a better place; it will be a dirty mess, and everyone will have to pay for that.

Think about IE not following the W3C standards... how did that go? How exactly are the webmasters mad right now because of that? :D
 
Old thread, but just to inform that I had a similar issue with sending email to GMail-addresses. This turned up in the logs starting 14th October and not before.

The problem was that I had an IP address as well as the IP number in my /etc/resolv.conf:

Code:
nameserver 80.69.67.67 ns0.transip.nl

After deleting the name and restarting named everything seems to be working properly.
 
Back
Top