Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id DAA02442; Sun, 4 Jun 1995 03:21:52 -0400
X-Resent-To: drums@CS.UTK.EDU ; Sun, 4 Jun 1995 03:21:52 EDT
Errors-to: owner-drums@CS.UTK.EDU
Received: from domen.uninett.no by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id DAA02434; Sun, 4 Jun 1995 03:21:50 -0400
From: <Harald.T.Alvestrand@uninett.no>
Message-Id: <199506040721.DAA02434@CS.UTK.EDU>
Received: from localhost.uninett.no by domen.uninett.no with SMTP (PP) 
          id <17775-0@domen.uninett.no>; Sun, 4 Jun 1995 09:21:01 +0200
X-Mailer: exmh version 1.5.3 12/28/94
To: Eric Thomas <ERIC@SEARN.SUNET.SE>
cc: drums@CS.UTK.EDU, Dave Barr <barr@math.psu.edu>
Subject: Re: getting started
In-reply-to: Your message of "Wed, 31 May 1995 22:00:06 +0200." <199505312010.QAA20373@CS.UTK.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sun, 04 Jun 1995 09:20:59 +0200
Sender: Harald.T.Alvestrand@uninett.no

Eric,
typical solutions in the "enclave with one gateway" situation:

- If message is returned with bounces, and headers are extensible, and
  the gateway can tell messages from bounces, stick it in the headers
  (aka errors-to) and let the gateway redirect the bounce

- If headers are not extensible, or are not returned, but some kind of
  message-ID is returned, keep a table around of message-id -> bounce
  address for the last hours/days of traffic, and redirect bounces
  appropriately

Of course, in cases where you can't tell bounces from messages, or where
there are multiple gateways into the same domain, so that bounces come out
at a different place from where they got in, and the writers of the software
at the two places don't know about each other, you *do* have a problem.

                Harald A