Re: how to make an intermediate machine receive mail while the destination is down?

1998-06-20 Thread Joey Hess
Daniel Martin at cush wrote:
 Well, you'll need to modify your MX dns record to point to the new
 destination - you'll then need to tell the gateway machine that's
 holding the mail explicitly how to route it, or else the machine
 holding the mail will try to send it to itself, and mail will get
 caught in a loop.  How to do this depends on what mail software is on
 your gateway/dns machine.
 
 But why bother?  If your main server is only going to be down for one
 or two days, then there shouldn't be any problem in simply not having
 something to hold the mail - if the sites sending the mail can't get
 through to your mail server, they'll just hold it until they can get
 through.  Typically, what will happen is that people trying to send
 mail to your site will only even notice that something's odd if your
 server is down for three days (in that case, the person who sent the
 mail will get something from their mail server saying This message
 has been undeliverable for 3 days; we'll keep trying for another 9
 days), and all the mail will get through if your main server is down
 for less than twelve.

Unfortunatly, there are exceptions to this. For example, if you are
subscribed to debian-user through this machine, you will be unsubscribed
after a few days of downtime. This is a highly annoying feature of
smartlist.

-- 
see shy jo


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Re: how to make an intermediate machine receive mail while the destination is down?

1998-06-20 Thread Jason Gunthorpe

On Sat, 20 Jun 1998, Joey Hess wrote:

  has been undeliverable for 3 days; we'll keep trying for another 9
  days), and all the mail will get through if your main server is down
  for less than twelve.
 
 Unfortunatly, there are exceptions to this. For example, if you are
 subscribed to debian-user through this machine, you will be unsubscribed
 after a few days of downtime. This is a highly annoying feature of
 smartlist.

Also the list server is set to give up after only two days - we have alot
of mail that just gums up the works if that number is raised.

As for the question in the topic, the way to do this is with MX records.
We have the debian domain setup so that murphy is the primary, master is
the first backup and va is the third backup. Other hosts should try them
all before giving up.

Jason


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


how to make an intermediate machine receive mail while the destination is down?

1998-06-18 Thread Carlos Carvalho
I need to shutdown our main mail server for hardware changes, and I'd
like that another machine in our department receives the mail and hold
it until the main server is up again, and then sends the stored mail
to the server. How can this be done? The temporary holder can be our
gateway/dns, for example, so that packets already travel through it.

Carlos


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Re: how to make an intermediate machine receive mail while the destination is down?

1998-06-18 Thread Daniel Martin at cush
Carlos Carvalho [EMAIL PROTECTED] writes:

 I need to shutdown our main mail server for hardware changes, and I'd
 like that another machine in our department receives the mail and hold
 it until the main server is up again, and then sends the stored mail
 to the server. How can this be done? The temporary holder can be our
 gateway/dns, for example, so that packets already travel through it.
 
 Carlos

Well, you'll need to modify your MX dns record to point to the new
destination - you'll then need to tell the gateway machine that's
holding the mail explicitly how to route it, or else the machine
holding the mail will try to send it to itself, and mail will get
caught in a loop.  How to do this depends on what mail software is on
your gateway/dns machine.

But why bother?  If your main server is only going to be down for one
or two days, then there shouldn't be any problem in simply not having
something to hold the mail - if the sites sending the mail can't get
through to your mail server, they'll just hold it until they can get
through.  Typically, what will happen is that people trying to send
mail to your site will only even notice that something's odd if your
server is down for three days (in that case, the person who sent the
mail will get something from their mail server saying This message
has been undeliverable for 3 days; we'll keep trying for another 9
days), and all the mail will get through if your main server is down
for less than twelve.


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Re: how to make an intermediate machine receive mail while the destination is down?

1998-06-18 Thread Nathan E Norman
On Thu, 18 Jun 1998, Daniel Martin at cush wrote:

[ snip ]

: something to hold the mail - if the sites sending the mail can't get
: through to your mail server, they'll just hold it until they can get
: through.  Typically, what will happen is that people trying to send
: mail to your site will only even notice that something's odd if your
: server is down for three days (in that case, the person who sent the
: mail will get something from their mail server saying This message
: has been undeliverable for 3 days; we'll keep trying for another 9
: days), and all the mail will get through if your main server is down
: for less than twelve.

While I agree that it shouldn't be a big deal for a mailhost to be down
a few days, I feel obligated to point out that sendmail at any rate
defaults to 5 day timeouts for undeliverables.  I see very few machines
in this part of the world which queue mail for much longer than that.

--
Nathan Norman
MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD  57104
mailto://[EMAIL PROTECTED]   http://www.midco.net
finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)



--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]