email - delivery retry timeouts

R. David Whitlock ryandav at
Thu Mar 29 14:36:40 PST 2001

I'm not sure about the timeouts on the mailers, because I'm assuming that
there's not really any set standard, but you might have one problem
already: If you haven't already turned down the TTL for your zonefile to
some more frequent value, you may not have time to propogate a new MX
record before the power cuts out...

Of course, you could start with one broad assumption that might help:
the most important mailer that needs to know the change is the UW's, so if
you make a change and then nicely ask the kind netops folk to manually do
a zone transfer, the UW's nameservers and thus mailers will have the
correct info asap.


"What you hear isn't necessarily what was said,
what you read isn't necessarily what was written."

On Thu, 29 Mar 2001, Mike wrote:

> This is only related to Linux in that I've got a Linux server running

> sendmail which will be out of service for about 1 day. The rest of my

> question is email specific. If this makes you unhappy, stop reading now.


> Tomorrow the power is going to be out at my apartment for about 8 hours

> (sh!t, due to construction across the street). Since I receive email via

> my "server" at home, the server will be unresponsive for that amount of

> time.


> I've only got one MX for my domain. My question is whether I should:


> A) try to put together a secondary (caching) MX for tomorrow's

> outage?

> OR

> B) will other email servers cache messages for me (as in get a bounce and

> wait to retry delivery) and redeliver them when I'm back online?


> I'm not sure which RFCs to read about this (if there is in fact a standard

> for redelivery timeouts), and finding out which one might be a painstaking

> process. Thanks to those who might offer assistance.


> ---------------------------

> -=<(| mike at |)>=-



More information about the Linux mailing list