Victor Duchovni wrote:
On Wed, Sep 17, 2008 at 08:51:48PM +0500, rihad wrote:
Sure enough, but I'm speaking of a single snapshotted value through a
single request ("transaction"). Besides its being more efficient,
caching makes for more consistent results: you wouldn't want Postfix to
first consider a delivery local (mydestination), only to suddenly change
its opinion and consider it remote.
Actually, you would want it to route correctly, based on the state of
the world at the time message delivery is attempted.
Sure, but every (retrial) attempt is a _different_ "transaction"! I was
speaking of a setting remaining the same within a _single_ attempt
(fractions of a second or more), which it doesn't, given that Postfix
test 4 times if @domain belongs to mydestination.
Postfix is *not* monolothic, and message delivery is not instantaneous.
Messages may sit in queues long enough to see the routing topology or
domain address classes change. This is fine.
Of course, and all those attempts are different transactions, as I
called them, so it's start afresh every time.
