Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!nic.MR.NET!shamash!nis!ems!datapg!sewilco
From: sewilco@datapg.MN.ORG (Scot E Wilcoxon)
Newsgroups: comp.mail.uucp
Subject: Re: some (hopefully) useful comments about mail routing
Message-ID: <1915@datapg.MN.ORG>
Date: 2 Oct 88 23:56:18 GMT
References: <433@manta.pha.pa.us>
Reply-To: sewilco@datapg.MN.ORG (Scot E Wilcoxon)
Followup-To: comp.mail.uucp
Organization: Data Progress, Minneapolis, MN
Lines: 43

In article <433@manta.pha.pa.us> brant@manta.pha.pa.us (Brant Cheikes) writes:
...
<Yet if we are to eliminate dynamic routing, the following problems (at
<least) need solutions:
<
<1. Sites must be able to maintain private links.  Just omitting the
...
<an authorization file?  Mail over unauthorized links should be bounced
<back to the originator.
<
<2. We have acknowledged that network topology is in constant flux.
...

Brant brings up several issues.

	Smail should allow local exceptions to mapped links.

Type of exceptions:

	Mail through an exceptional link.
	Mail to an exceptional link.

Possible actions for an exceptional link:

	1. Bounce mail.
	1a. Bounce all mail except that from certain sites.
	1b. Bounce only mail from certain sites.

	2. Reroute mail through an alternate path.
	2a. Reroute all mail except that from certain sites.
	2b. Reroute only mail from certain sites.

If "exceptional link" declarations allow date ranges, problems of known
duration can be entered once and automatically begin/expire.

(I could use "private link" support in smail as well, but don't need to
list it here as a "private link" is just an exceptional link with
actions 1a or 2a.)
-- 
Scot E. Wilcoxon  sewilco@DataPg.MN.ORG    {amdahl|hpda}!bungia!datapg!sewilco
Data Progress 	 UNIX masts & rigging  +1 612-825-2607    uunet!datapg!sewilco
   "When Hurricane Gilbert comes through, I'll stay here to experience it."
   CBS:"What if you experience death?" "Well, I'll worry about that later."