ALL NODES WHO ARE SWITCHING, OR PLANNING TO SWITCH, TO FTS In one network using FTS we saw an example of what can happen when a node switches to FTS (620 dupes). Before any QWK systems pipe up and say "see, told ya it's no good", I could do the same thing with QWK, so save the comments, this addresses preventing the dupes for FTS. I am not familiar with specifics for various front ends, only PCBoard, so I'll give a general method, and then a PCBoard specific method. ============================================================================== The #1 rule of thumb: Do NOT make the switch/addition until both the Hub AND the node sysops can be at their systems if you are at all unsure of things! Because a utility like IS.EXE can't be used with FTS packets, it's important to minitor the the first scanning for mail at both ends as this is when the dupes can occur. The #2 rule: Do NOT make the switch until you have stopped you QWK transfers. (Not applicable to new nodes, only those switching) The #3 rule: It's better to lose a few messages than dupe hundreds! Final Note: I "Know" how to read the Seen-by and Path lines and will track you down like carribou!! ============================================================================== General guidelines ------------------ 1: The hub sets up the nodes record and ONLY gives "access" to the appropriate conferences. Do NOT set the conference to be scanned. 2: The Node sets up the Hubs record with access and scanning. 3. Node sends an AREAFIX message to Hub to turn on the appropriate conferences. This should top off the message pointers, but the next steps will insure no dupes get through. 4. Hub Scans for outbound mail. If a packet is created, DELETE IT! Message pointers will be topped at the Hub at this point. 5. Node should also scan for outbound mail. If a packet is created, DELETE IT! Message pointers will be topped at the node at this point, and no dupes will get sent. It's better to lose a few messages than to flood the net with dupes. If things are done correctly, no packets should be created during 4 & 5. But if one is, deleting the packet will prevent the dupes. From this point on, everything should work automagically. ============================================================================== PCBoard-specific ---------------- Other mailers can use a similar technique, I just don't know the specifics If you are a Node: 1. Set up your Hub's ~FIDO~ record. Make sure that "Uplink" is marked 'Y' on the page with your Session and Areafix password settings. 2. Set the Registration flags for the appropriate conferences, by either: a. In PCBSM - set the RS flags for the conferences. You can also enter a high message pointer (like 100000) for those conferences (they'll be set to the high message number during the first outbound mail scan) b. Sysop Command 7 - Find the Hub's record, Select (C)hange, and when it asks about selecting conferences, choose Yes. Set the RS flags for the appropriate conferences. 3. This is crucial- From the Sysop Fido Menu (Alt-f at the WFC Screen) select "Scan for Outbound mail". After the scan is done, select "E-View/Modify Queue". Flip through the entries, and if there are any packets addressed to your Hub's address, select (D)elete this packet. 4. Create an AREAFIX message to you Hub to add the areas you are carrying. Scan for Outbound mail. This should be the only message scanned out. Send this message. Now it's up to the hub but you've done your part. If you are a Hub: [The first two can be done ahead of time, at your convenience] 1. In PCBSM, use Alt+A to add a record and et up the node's ~FIDO~ record with areafix & session passwords. 2. Set the conference registration flags to "R" ONLY!!! IF you enter an "S" the message pointer becomes fixed and an AREAFIX won't top the conference. The best method is to log in as the sysop, select 7 (sysop command for User Maintenance). Locate the Node's record, and select C to change it. Hit enter through the prompt til you get to Select Conferences? and enter a "Y". Now select the conferences (you can use ranges like 31-150) and enter "R" for the flags to set. [when the node is ready to add the conferences] 3. When the Node's AREAFIX message is received, after the message is imported select "Scan for Outbound Mail" from the sysops Fido menu. If everything has been setup correctly, you shouldn't see any messages get exported from the conferences for the new node. If you do (could happen if another node imported mail between the areafix and your outbound scan), delete the packet. This ensures absolutely no dupes get sent.