On Mon, 26 May 2003 12:30:00 -0500, "Cory Daehn" <cdaehn@???>
wrote:
>I e-mailed their ISP, the response was "You aren't receiving mail from
>mediaone.net because it is a defunct domain, and if you are having mail loops
>caused by that IP address, your mailer software was poorly written and should
>be able to recognize that as a bad IP address and halt the delivery attempt."
>
>I kinda agree on that one. Exim should be able to tell that 0.0.0.0 is an
>undeliverable IP address. I get a lot of mail frozen in the queue for mail
>servers with an IP lookup of 127.0.0.1 also. I really wish Exim would
>immediately kill these messages.
I thought you were talking about sending mail, not receiving??
I don't believe it is Exim, see below. I did -
exim -d -bt postmaster@???
and got debug result below, then a test mail which failed immediately.
The relevant (and correct) reply back from Exim was "all relevant MX
records point to non-existent hosts" because when Exim asks the SOA
responsible for the domain - zoneedit.com - for the MX zoneedit gives
the names *but not the A records*. So Exim says correctly (well my
Exim does)..."all relevant MX records point to non-existent hosts" and
stops delivery immediately.
If Zoneedit says the statement above I would say that they "should be
able to recognise that they are badly managing the domain DNS records
and get out of the business".
When you do digs for records like MX's you should first find the SOA
nameserver then query that server for the relevant information. As the
start of authority it is the final word.
So there are two problems here:
1) Why your Exim installation doesn't fail the message immediately and
2) The fact that Zoneedit are cowboys. Since we started this
discussion they have changed the MX records from mediaone.actwin.com
to mail.mediaone.com but they *still* haven't added the A records for
the host.
Not clear on why 1 is happening, the original message was a bounce. Do
you have alias for postmaster to a real account on your system? What
does your dnsrouter router section in Exim configure file say?
And finally - my favourite comment :-) I see you are using Exim 3.x is
there any reason why you cannot upgrade. Exim 4 really has many new
features.
Cheers
PS
=================
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
routing postmaster@???
--------> dnslookup router <--------
local_part=postmaster domain=mediaone.com
checking domains
mediaone.com in "mydomain.com"? no (end of list)
mediaone.com in "! +local_domains"? yes (end of list)
calling dnslookup router
dnslookup router called for postmaster@???
domain = mediaone.com
DNS lookup of mediaone.com (MX) succeeded
DNS lookup of mail.mediaone.com (A) succeeded
0.0.0.0 in "0.0.0.0 : 127.0.0.0/8"? yes (matched "0.0.0.0")
ignored host mail.mediaone.com [0.0.0.0]
fully qualified name = mediaone.com
host_find_bydns yield = HOST_FIND_FAILED (0); returned hosts:
mail.mediaone.com <null> 0 *
dnslookup router declined for postmaster@???
"more" is false: skipping remaining routers
no more routers
postmaster@??? is undeliverable:
all relevant MX records point to non-existent hosts
search_tidyup called
>>>>>>>>>>>>>>>> Exim pid=17551 terminating with rc=2 >>>>>>>>>>>>>>>>
=================
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:
devnull@???
all relevant MX records point to non-existent hosts
=================
