Replying to a message of James Vahn to Darryl Gregorash:
 >> You realize, of course, that the BOFAQ is published by an
 >> independent echomail distributor? 
 JV> The only 'official' document I've ever seen is Policy4, and 
 JV> surprisingly it mentions very little about echomail.
P4 is not an echomail document. 
 JV> BOFAQ is a good document, fairly well maintained and
 JV> available from the same place we send in the elist updates,
 JV> at least in  Zone 1.
Yes, but it still describes the operating procedures of only one of many 
echomail distributors. When Jim Balcom made the suggestion to you, there was 
only one. I won't describe all the politics that led up to the formation of 
others (one of which Jim himself was one of the founders).
Handling large volumes of uuencoded material is probably a good way to get an 
echo thrown off any distributor's network, but one should nevertheless be 
wary of tying one's self to the rules of a single distributor. In this case, 
the cited BOFAQ references aren't a burden, and indeed might be what most 
would consider "common courtesy" (not all people wish to receive bags and 
bags of uuencoded binary files, particularly here, when we can just as easily 
send the source code).
Here is the FidoSpine's document corresponding roughly to the BOFAQ:
                   FidoSpine Distribution System Pledge
1. The FidoSpine Distribution System recognizes all echoes as listed in the
   Echolist for June 1, 1997 (ELIST706.*) along with their first-listed
   moderator as the Moderator-of-Record.
2. The FidoSpine Distribution System will initially carry all Fidonet Zone
   one echoes that appear in the June 1997 echo listing, plus some that are
   not. The FidoSpine Distribution System will use it's own echo
   distribution list, FIDONET.NOW. The FidoSpine Distribution System does
   not require echo listing renewals or minimum traffic levels for any
   echo(s).
3. The FidoSpine Distribution System recognizes the Moderator-of-Record as
   the "owner" of their echo. As such all moderator requests for feed cuts
   are honored, provided that the moderator follows the path from the
   'problem' system and works backwards.  Any FidoSpine Distribution System
   hub retains the right to not distribute any echo who's moderator's
   actions causes too much of a burden on their system or well being.
4. The FidoSpine Distribution System recognizes the validity of Fidonet
   Policy 4.07 in determining the legality and appropriateness of messages
   carried in echomail. Since the Moderator-of-Record is the "owner" of the
   echo, The FidoSpine Distribution System recognizes the moderator's
   responsibility in maintaining the legality and appropriateness of
   message traffic in their echo(es). The FidoSpine Distribution System is
   not responsible for the content of echomail traffic.
5. The FidoSpine Distribution System will work toward establishing
   SuperHubs in each zone and region. The FidoSpine Distribution System
   does not mandate any specific routing scheme, and allows each zone,
   region, and net to adopt and use their own methods. The FidoSpine
   Distribution System, where netmail and other traffic is concerned, will
   use routing charts provided by recognized Fidonet Coordinators (as
   indicated in the Fidonet Nodelist).
6. The FidoSpine Distribution System distribution system will not interfere
   with any traffic in any echo, aside from eliminating duplicate messages
   ("dupes") and adding necessary routing information in accord with
   Fidonet Technical Standards.
7. The FidoSpine Distribution System will accept input from any moderator
   as to a request to carry his/her echo. We will NOT require multiple
   requests from various NEC's and REC's to 'authorize' distribution of any
   echo.  All that is required is that the moderator have properly
   established an entry in the current Echolist, and make a request of the
   FidoSpine Distribution System to distribute his/her echo.
8. The FidoSpine Distribution System may, from time to time, establish, and
   distribute, technical criteria that messages must meet in order to be
   carried on FidoSpine. Such criteria may include, but not be limited to,
   definitions of character set, Origin Line length, age of messages,
   technical specifications of the SEEN-BY's, the PATH, the tearlines, and
   assorted control lines.
                Bob Seaborn, 1:140/1
                Ed Georgen,  1:2222/258
                Jerry Gause, 1:3651/9
                Jim Balcom,  1:13/25
                Peter Rocca, 1:2401/0
I am not sure where the file can be obtained, except by anonymous ftp from 
ftp.nwstar.com. Note that Jim Balcom is no longer a FidoSpine distribution 
site, and of all of the rest, the only one I am certain of is Bob Seaborn. I 
believe Ed Georgen is as well, but don't quote me on that.
Note also that paragraph 3 could be used to deny large volumes of uuencoded 
files being transferred, as well as any encrypted material. However, 
uuencoded material is not eliminated (nor, I think, even on the NAB) unless 
it becomes excessive.. in which case, the entire echo is no longer carried.
--- FleetStreet 1.21 NR
---------------