Carlos Carvalho:
> Wietse Venema (wietse AT porcupine DOT org) wrote on 10 August 2007 20:55:
> >Carlos Carvalho:
> >> Messages have been getting stuck in the smtp queue because the
> >> destination doesn't have a MX record. Here's an example:
> >>
> >> Aug 9 07:49:34 hoggar postfix/smtp[7034]: 3B95232E1A4: to=<X AT example
> DOT com>, relay=none, delay=80142, delays=80142/0.02/0/0, dsn=4.4.3,
> status=deferred (Host or domain name not found. Name service error for
> name=example.com type=MX: Host not found, try again)
> >>
> >> The dns answer is "MX record currently not present".
> >
> >No that was NOT the DNS reply. "Host not found, try again" means
> >that no valid reply was received.
>
> What do you mean by "no valid reply"? Both host and dig say the
> nameserver answered but the answer section was empty. Here it goes
> with the real name, you can see it too:
No valid reply, as in: timeout (no reply), malformed (not valid), whatever.
It is entirely possible that other programs find an
answer because
- You run them at a different point in time.
- You run them as root, while Postfix does not and you screwed up
permissions.
- You don't use a chroot jail, while Postfix does and the jail
is screwed up.
And numerous others.
Wietse
|
