[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] MX Records and failover servers
- Subject: Re: [cobalt-users] MX Records and failover servers
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Thu May 23 14:02:04 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
JL> Date: Thu, 23 May 2002 10:53:24 -0700
JL> From: Jeff Lasman
JL> > Does this mean that the primary mailserver can send an ETRN
JL> > message to the raq, and the raq would respond to this by
JL> > sending the messages in its queue to the primary mail
JL> > server?
JL> ETRN is better suited for (and I believe designed for)
JL> servers that are intended to be offline more than they are
JL> online, and to get email from a higher-priority server.
Yep. For secondard MX, we don't bother with ETRN. We _do_ use
it for the situation that you described.
IIRC, Sendmail 8.10.x was the first version that had a check_etrn
rule built in. Handy to prevent random people from trying to
tickle the queue.
--
Eddy
Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.