public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Marc G. Fournier <[email protected]>
Cc: Kevin Hunter <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: email is fast!
Date: Thu, 8 Feb 2007 09:29:46 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Wed, Feb 07, 2007 at 07:01:43PM -0400, Marc G. Fournier wrote:
> >> Just to follow up this one ... Kevin sent me an email including the full
> >> headers for one that took 12 hours to be delivered ... using the QUEUE ID, I
> >> checked the logs and it turns out that the mail server couldn't resolve the
> >> MX the first and second time it tried to deliver, but succeeded on the
> >> third ...
> >
> > This sounds scaringly close to the problem we had on wwwmaster with it
> > not delivering emails. Resolving separately looked fine, but sendmail
> > couldn't resolve.
> > Could it be symptoms of the same problem?
>
> Does postfix do any 'caching of results'? For instance, if it got a failed
> response, would it cache that and re-use that later, pending it timing out in
> its own cache? So try 1 failed, try 2 used cache and failed, try 3 was after
> cache timed out and re-tried, at which point the local DNS server had the right
> value ...
I don't beleive it does. The resolver library might do it though - some do, others don't.
//Magnus
view thread (11+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: email is fast!
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox