On Mon, Feb 15, 1999 at 03:22:02PM +0100, Florent Guillaume wrote:
> > I belive richard means that the secondary mx will sit there uselessly
> > trying to deliver to the nonexistant primary mx.
> >
> > Which is why the secondary needs to be modified only to deliver when
> > primary is up.
>
> But isn't it possible to have the secondary MX be a near-clone of the
> primary, and do the delivery itself to the clients instead of sending
> the mails back to the primary when it comes back up ? This implies
> of course adequate configuration.
Definitely. But, depending on your network, you might as well have your secondary on
the same MX preference. If it's farther away netwise, keep it at a lower preference.
> Is it unadvisable ? If so why ? I'm asking because I about to install
> such a setup here.
No it would be very good, but be sure to keep them _in_sync_. I've had _way_ too much
trouble sending mail to ISPs where configurations like this were totally fucked up.
So.. go ahead, but _be_ _careful_.
Greetz, Peter.
--
.| Peter van Dijk | <mo|VERWEG> stoned worden of coden
.| [EMAIL PROTECTED] | <mo|VERWEG> dat is de levensvraag
| <mo|VERWEG> coden of stoned worden
| <mo|VERWEG> stonend worden En coden
| <mo|VERWEG> hmm
| <mo|VERWEG> dan maar stoned worden en slashdot lezen:)
