started  an EchoMail conference of his own and began relaying EchoMail
between several systems, again routing it all through his network.

His Network Coordinator observed that network performance was becoming
seriously impaired.  The offending node was told to hold  it  down.  A
compromise  was  reached  whereby  much of the EchoMail traffic was no
longer routed through the network,  and routed EchoMail was limited to
twenty messages per night.  No appeals were made.



4.1.8   The Case of the Bouncing Board4.1.8   The Case of the Bouncing Board

A local user decided to establish a node to promote a worthy  charity.
The  machine  being  used  was  also used for various other activities
during the day,  and the sysop was often called  away.  His  coworkers
would  often  forget to bring the board up at the end of the day while
he was away,  so the node was often down  for  extended  periods.  The
Network Coordinator, on finding the node unable to receive mail, would
mark it as down.  The sysop would return,  restart the board,  and ask
to be reinstated as a node.

The Network Coordinator eventually decided that the sysop was not able
to maintain a reliable system,  and removed him  from  the  node  list
completely.  Future  requests  for  a  node number from the same sysop
were turned down.  No appeals were made.








FidoNet Policy and Procedures   *** PROPOSAL ***             Page 16