TIP: Click on subject to list as thread! ANSI
echo: crossfire
to: ROSS CASSELL
from: TOM WALKER
date: 2009-06-26 10:34:00
subject: If you use Docsplace BBS,

I Always edit out anything preceiding the Text and usualy edit the
Text and any thing following it.l
And at times I have accidnetly tested the Dupe scanner and it has
worked Perfectly each time!!  :-)



RC>Hello All!

RC>**IF YOU USE DOCSPLACE BBS TO POST FIDONET MESSAGES, THIS APPLIES TO YOU**

RC>Fidonet messages contain alot more info that gets used by the software to:

RC>* scan it out to the network

RC>* toss it in from the network

RC>But has no relevance to the average user.

RC>An example of this can be found by looking at the headers of any email messa
RC>there is alot more info than just from/to/subject.

RC>I am the uplink mailhub for DOCSPLACE, over the years I have noted that my
RC>system was trapping random messages from DOCSPLACE as duplicates that should
RC>have been flagged as such. When a message gets flagged as a duplicate, it go
RC>no further.

RC>With the help of Fellow Sysop Dale Shipp, he and I both believe we have foun
RC>the culprit, after all this time, the common denominator has been identified

RC>Part of the problem has to do with the message editor and QWK door of Docs B
RC>setup, which he cannot control, the other part has to do with the dupe check
RC>routines of my tosser.

RC>Fidonet messages contain header control lines, most of which begin
with an "
RC>sign. The ones involved in this issue help identify each message individuall
RC>with a unique identifying number, the originating system and the system that
RC>originated the message being replied to. It appears that nearly every false
RC>duplicate is indeed a message reply, not a new or original message.

RC>What is happening in the case of these false duplicates is that the person
RC>replying is including in the body of their message quotes, a few of the mess
RC>control lines of the message they are repling to.

RC>What is supposed to happen is the editor should change the {at} symbol to a
RC>different character such as a # sign or something other than {at}. However on t
RC>otherhand when this message reply gets to my system, my dupe checker should
RC>theory ignore the quoted control info because it is being prefixed with the
RC>usual quotation characters such as "->" or
"initials>".

RC>Because my system has seen the original message already, when it sees the
RC>quoted control info in this type of reply, it assumes it is a dupe.

RC>Preferably, the setup on Docs should alter the control character when it
RC>encounters it in a uploaded message from the QWK door or when a reply is bei
RC>authored by the user while online... A similiar preference is that my tosser
RC>should ignore control info that is prefixed by any character other than what
RC>supposed to be there.

RC>It is not a perfect world, the developer of Docs software hasnt done much wi
RC>the Fidonet side of it for years now and the developers of my tosser are als
RC>not as abundant, my tosser is open source, Docs is proprietary commercial.

RC>I will still attempt to contact someone whom might still be toying with the
RC>codebase for my tosser, most of it was done in Eastern Europe but Fidonet is
RC>much to code for when that group can concentrate on Rogue Security Software
RC>earn money.. :-/ Not saying that the same persons are involved, but it is th
RC>area where most of that stuff comes from now.

RC>The work around for this issue is pretty straight forward...

RC>When using Docsplace to reply to Fidonet Messages and you quote a message..

RC>DO NOT LEAVE WITHIN THE MESSAGE BODY OF YOUR MESSAGES, QUOTED OR NOT...

RC>Any line that begins with a "{at}"


RC>Examples: (Pretend # is {at})

RC>#MSGID ?:???/??? ????????
RC>#REPLYID ?:???/??? ????????

RC>The "?" can be any number and in the last octet also a letter.

RC>The best thing to do is not quote any control info back, do not include it i
RC>your quotes, it is irrelevant anyway from a users point of view.

RC>If you see any text that has a {at} sign in column one, edit that line out of y
RC>quotes.

RC>Excepting Test Messages to reveal this issue, I have noted false dupes writt
RC>by:

RC>JohnJWilson
RC>Wayne Chirnside

RC>Dont quote the control info and all will be well, there is no need to quote
RC>anyway unless specifically asked to do so.

RC>If I can get my tosser refined, I will let you know.

RC>==
RC>Ross
RC>Fidonet Feeds Or Fidonet In Your Newsreader: http://www.easternstar.info
RC>E-mail: ross(at)cassell(dot)us | Other Places: http://links.cassell.us
RC>Fidonet Netmail Routing Chart Z1 Only: http://netmail.fidonet4u.info
RC>... Democrat Is Code For Double Standards And Absolute Evil.
RC>--- GoldED+/LNX 1.1.5-b20060121
---
 þ SLMR 2.1a þ Typo Tom strikes agaoin
RC> * Origin: The Eastern Star - Spartanburg, SC USA (1:123/456)
* Origin: Doc's Place BBS Fido Since 1991 docsplace.tzo.com (1:123/140)
SEEN-BY: 10/1 3 11/331 34/999 120/228 123/500 128/2 187 140/1 226/0 236/150
SEEN-BY: 249/303 250/306 261/20 38 100 1381 1404 1406 1410 1418 266/1413
SEEN-BY: 280/1027 633/260 267 712/848 800/432 2222/700 2320/100 105 200
SEEN-BY: 5030/1256
@PATH: 123/140 500 261/38 633/260 267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.