Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    BATPOWER    |    Batch Language Programming    |    216 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 129 of 216    |
|    Nicholas Boel to Bill McGarrity    |
|    Re: Zone Blind...    |
|    06 May 14 20:08:00    |
      @MSGID: <5369862B.33570.sync_sys@vert.synchro.net>       On 05-06-14, Bill McGarrity said the following...                BM> Quick question if Imay.               Quick answer if I might!               BM> The issue is with Zone Blind toggle. If I don't want one network's        BM> addresses to appear in the seen-by and path lines of another, should        BM> that toggle be "enabled" or "disabled"? If enabled, that brings us to        BM> another issue that I was told to add a 4 at the end of the Zone_Blind in        BM> the sbbsecho.cfg file. I am assuming that means the first 4 zones        BM> should be considered as one. Over the past few weeks with the issues of        BM> the INTL kludge line in echomail (which was determined sbbsecho was not        BM> to blame) my head is spinning.... not that it doesn't normally spin        BM> anyway.              No need for your head to spin.              everyone would still get their echomail if there were duplicate nets.              For example, the last duplicate net was 250. There was a 1:250 anda 2:250.       the echomail, and vice versa.              Since there are no more duplicate nets in Fidonet, some have asked top stop       help in the matter. What he did was create the ZONE BLIND option. At first       this caused trouble if you carried multiple networks because any echomail for       node number, my Zeronet node number, etc, were all being stuffed into Fidonet       echomail, which wasn't good (just in case) there was a matching net/node       combination between Fidonet and one of those other networks.              So, going back to Rob.. he added an optional number afterthe ZONE_BLIND       option. This way you can do ZONE_BLIND 4 and zones 1 through 4 will keep all              In all reality, you *could* put ZONE_BLIND 6 but it really doesn't matter       anymore since there are no zones5 and 6 in Fidonet. Any other zones above 4       Agoranet is zone 46. Only zone 46 net/node combinations will be put into       echomail.              Also, The ZONE_BLIND 4 option helps those same people in Fidonet with dupe       be less dupes. By now you've probably gotten a chance to see what the       "fidoweb" is all about. Everyone links to everyone for the same echos, and       let the dupe detection sort everything out. This is why they'reasking to       across zones.              I'm sure Rob could have done it a better way, but this was a quick fix to       make the very few people in Fidonet happy, while noone else in other networks       have any issues sticking to the old ways of doing things.              Either way, it's tried and tested here, working great for Fidonet, and the       rest of the networks separately.              BTW, the INTL kludge stuffing wasn't any kind of scare except to the original       person that posted about it when they realized it was their own system. LOL!              --- Mystic BBS v1.10 A39 (Linux)        * Origin: Dark Sorrow | telnet://bbs.darksorrow.us (1:154/701)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca