You might also want to look at using ETRN if you have two mailhosts that are
not on the same network. You could queue the mail on the backup host and
then once the primary mailserver comes back up it can issue an ETRN command
to the secondary server telling it to unfreeze the mail in the queue for a
certain domain and attempt to deliver it.
I hope that makes sense. There is some documentation in the Exim FAQ if you
would like more information.
Hope that helps.
Spencer.
PS. Are we able to buy exim shirts yet? If so, I would be most interested
=>.
On Wed, May 31, 2000 at 07:54:08PM -0700, John W Baxter wrote:
> At 1:00 +0100 5/31/2000, Tim Bishop wrote:
> >3. Say Exim was the only backup MX, and the main MX server was down for an
> >extended period of time (say 24 hours). Will Exim queue the mail for that
> >domain normally and thus generate the usual "mail has not been delivered for
> >x hours" messages ? Surely from an end-user point of view when an e-mail is
> >delived to any MX server for a domain it's considered "received" ?
>
> The way we have Exim installed, testing shows that indeed a delivery
> delayed message is sent out if the primary MX is down for the 24 hours
> after the message arrives in the Exim-run secondary MX. There's no
> indication that Exim was serving a secondary role, unless one studies the
> To: address vs the identity of the Mailer-Daemon vs the MX records.
>
> Since today's typical mail sender merely faints when getting one of those
> messages, and calls tech support upon recovery, you can expect that few
> will study the message that closely.
>
> --JOhn
> --
> --
> John W. Baxter, Port Ludow, WA, USA jwbaxter@???
> I'm trying to think, but nothing happens.
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
