From: Simon Waters (simonwzynet.net)
Date: Wed Mar 01 2006 - 06:36:17 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wednesday 01 Mar 2006 11:58, cbaegerteuropeanservers.net wrote:
>
> I'm wondering if I could have done something differently to avoid this
> problem, but I don't have the answer for now. Any idea ?

Run "ntpdate" on the way up before running Postfix, no guarantee as ntpdate
can fail due to networking issue, if the box is up before the routers, but
worth trying, we do it on all the GNU/Linux boxes here.

> so I think it will be better if
> Postfix could handle this problem automatically whatever the admin mistakes
> !

I think a general sanity check on date might be useful.

I was stunned to discover Lotus Notes didn't have one of these for replication
when I started using it, even those it did date based document replication,
it only needs a few replications with weird dates before I started losing
hair and will to live, and I was just an end user. It was quite happy to
receive updates that were older than the originals.

Problem is figuring out what test - at least in the current behaviour email
was returned to sender - so nothing was lost or held in an unacknowledged
state. Where as what to do with email that is much older in queue than the
queue expiry when Postfix starts, perhaps one last ditch delivery attempt
before bouncing?!

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]