Subj : Echomail
To : Mark Lewis
From : Daryl Stout
Date : Sat Mar 26 2016 06:45 pm
Mark,
ML>that's the way it is supposed to work but many don't understand these things
ML>and ignorantly break the system because they don't know... others break the
ML>system on purpose because they can... either way, it either works or it is
ML>broken because of someone specifically breaking it...
One of the differences with GT Power BBS software and the way it handled
network echomail or netmail (when the network was at its peak years ago), was
that certain systems could "sponsor" an echo...similar to "moderating" an echo
in FIDONet.
Network nodes would request the echo by an ID number, such as E00/103, via
netmail from their hub (similar to the way an Areafix is done in FIDONet), then
would set up their ROUTING.BBS file to get it from their hub, if they had it.
But, unlike FIDONet, all messages for the echo, originating on a BBS other
than the system sponsoring it, would go to the sponsoring system FIRST. That
way, the moderator/echo sponsor, could weed out any messages not considered
conducive to the echo (i.e. spam), and with various utilities, have those
messages deleted. All other messages would then echo out to the rest of the
network.
With FIDONet, systems that are linked to the echo, see posts from other
downlinks...sometimes before they get to the sponsoring/moderating system...and
before they are dealt with by a moderator. I've wondered though, that even with
a feed cut, would an offending poster try another way to get to the echo??
Daryl
---
* OLX 1.53 * X-Modem: A modem on the losing end of a lightning strike.
* PDQWK 2.53 #5
--- GTMail 1.26
* Origin: The Thunderbolt BBS - wx1der.dyndns.org - GT Power 20 (1:19/33.0)
