On Thu, Dec 12, 2002 at 01:43:16PM +0000, Colin Watson wrote: | On Thu, Dec 12, 2002 at 01:26:57PM +0100, Robert Land wrote:
| > Derrick, please forgive me if this question sounds stupid ( I know
| > I have to reread a lot of network stuff), but I have the impression
| > that the high-availability server in Colins example acts somehow
| > as a relay mashine with a buffer feature added to it?
Yeah, more-or-less.
| > Does this mean the mashine of Colins friend does no verification,
| > filtering or whatever, just collects the debian-list messages and sends
| > the whole bunch on demand?
Colin said it doesn't. That doesn't mean that it couldn't. How you
set up the relay system is entirely up to you.
| > What is the exact definition of a high-availability server?
|
| One that you can deliver mail to reliably.
Agreed. A counter example may help make it clear : if the machine is
connect for a total of only one hour per day, then it is unlikely that
the sending servers will be able to connect to it and perform the
delivery. A connection like that is bad for a server-push protocol
like SMTP.
| A box on the wrong end of an ADSL link without a static IP address
| doesn't fit that description.
LOL! I'll give you one guess as to where mine is. It's worked well
for me, using DDTS for name resolution. YMMV.
-D
--
If your company is not involved in something called "ISO 9000" you
probably have no idea what it is. If your company _is_ involved in ISO
9000 then you definitely have no idea what it is.
(Scott Adams - The Dilbert principle)
http://dman.ddts.net/~dman/
msg18795/pgp00000.pgp
Description: PGP signature
