[prev in list] [next in list] [prev in thread] [next in thread]
List: postfix-users
Subject: NULL MX (was: Name service error)
From: wietse () porcupine ! org (Wietse Venema)
Date: 2006-07-31 14:18:08
Message-ID: 20060731141808.18665BC0BA () spike ! porcupine ! org
[Download RAW message or body]
Simon Waters:
> On Monday 31 Jul 2006 13:39, martin wrote:
> >
> > Jul 31 12:29:45 localhost postfix/qmgr[30804]: 747DCC60F11:
> > to=<recipient@some.other.address>, relay=none, delay=3984,
> > status=deferred (delivery temporarily suspended: Name service error for
> > name=pop-smtp1-f.bt.mail.vip.ird.yahoo.com type=MX: Malformed name
> > server reply)
>
> This is just down to Yahoo declaring the MX record as "." for
> pop-smtp1-f.bt.mail.vip.ird.yahoo.com.
>
> They do that for domain names that don't send email, so you should not get
> email addresses like "<anything>@pop-smtp1-f.bt.mail.vip.ird.yahoo.com"
Now I am confused. I thought that the purpose of the "empty" MX
record was to stop RFC compliant MTAs from doing A lookups (the
idea is that an empty MX record for example.com means don't connect
to the IP address listed in the A record for example.com).
But in this case they have a null MX record AND and A record.
Wietse
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic