Xref: utzoo comp.mail.misc:5625 comp.mail.uucp:6729 news.admin:14758
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!wrdis01!mips!daver!tscs!tct!chip
From: chip@tct.com (Chip Salzenberg)
Newsgroups: comp.mail.misc,comp.mail.uucp,news.admin
Subject: Re: MBAS flags in map entries
Message-ID: <28445E21.17D4@tct.com>
Date: 30 May 91 02:06:25 GMT
References: <1991May22.040039.21721@iguana.uucp> <1991May22.141737.26521@sceard.Sceard.COM> <1991May24.230704.19188@skypod.guild.org>
Organization: Teltronics/TCT, Sarasota, FL
Lines: 35

According to scott@skypod.guild.org (Scott Campbell):
>In article <1991May22.141737.26521@sceard.Sceard.COM> mrm@Sceard.COM (M.R.Murphy) writes:
>>How about having the MBAS not abuse its downstream sites unless they are
>>masochistic enough to accept the abuse willingly.
>
>What about a new line in everyone's map entry stating whether they will
>forward MBAS mail?

Rather, a new line that enumerates those sites and/or domains to which
the given site is willing to forward MBAS mail.  For example, the
following map entry would be reasonable for a domain gateway that
accepts MBAS mail for its domain and two neighbor sites, but not for
the site "distant":

    #N     bigcorp
    #O     Really Big Corporation
    #...
    #M     *.bigcorp.com friend buddy
    #
    bigcorp   .bigcorp.com(0)
    bigcorp   friend(DIRECT), buddy(DIRECT), distant(POLLED)

>This would mean that MBAS's would have to start getting the map files (which 
>they probably don't have, being on the internet).

Small price to pay, IMHO.  If an MBAS wants to be sociable, it has to
know who's who in society.

>Anyone that REALLY wants to get MBAS mail can update their map entry and
>convince sites upstream to do so also.

I like it.
-- 
Chip Salzenberg at Teltronics/TCT     <chip@tct.com>, <uunet!pdn!tct!chip>
          perl -e 'sub do { print "extinct!\n"; }   do do()'