On Fri, Dec 18, 2009 at 7:52 PM, Wietse Venema <wie...@porcupine.org> wrote:

> D G Teed:
> > So, this is an uncontrollable setting.  The response from
> > host not found should be something we can configure,
> > not hardwired to defer.
>
> Postfix handles "host does not exist" as a permanent error.
>
> Postfix handles "no DNS reply" as a non-permanent error.
>
> It is a mistake to handle "no DNS reply" the same as "host not found".
>
>        Wietse
>

In your opinion.  In our practical situation, it would be a benefit
if there was flexibility, and we could decide how postfix
treats "no DNS reply".

I initially thought my example had no DNS record at the top
level registrar (CIRA), but I see it does.  Does it make
a difference if there are no DNS servers recorded for the domain?

Unfortunately there are people who register the typoed domains
but have no services running.

Due to the hardwired default of 450, all sent mail becomes sluggish
on the Exchange queue as hundreds of messages are retried
every few minutes (one mistyped domain in a mail list triggers this
behaviour in MS Exchange).

--Donald

Reply via email to