Text 11185, 85 rader
Skriven 2005-07-20 20:24:12 av Ross Cassell (1:123/456)
  Kommentar till text 11184 av Matt Bedynek (1:106/1)
Ärende: Fidonews Echo Rules
===========================
Hello Matt!

20 Jul 05 18:55, you wrote to me:

 RC>> Bitching about dupes here and there is a waste of time, ..

 MB> If someone notifies another operator about looping conditions and
 MB> those other operators do nothing to correct the problem, that is being
 MB> lazy.

Well as you saw, I identified the cause of the loop and stated as such in here
a few days ago and the person has since netmailed me, although I do not know if
he has fixed it, I certainly cannot make him.

 MB>   I do not demand others run the software or implement the
 MB> methods here, but if I send you (example) a notification of a problem
 MB> and nothing is done that is plain sloppy. Maybe I outta whip something
 MB> up that will post notifications in fn_sysop to get some egg in the
 MB> face of those are involved.  :-)

Well I dont think you saw me jumping on that dupe bandwagon.

 RC>> .. forcedpath checking is strongarm operations because if the
 RC>> conventional wisdom is that we dont have the time to keep a ERN
 RC>> list then we certainly dont have time to keep a similiar database
 RC>> ..

 MB> Database?  I have five links in the forcepath setup.  That hardly
 MB> qualifies as a "database".  My last modification to the configuration
 MB> was when Grant unlinked with your node.  I probaly should have never
 MB> placed his link there in the first place since he is one of those that
 MB> plays musical links.

Grant didnt play musical links, he broke his mesh with Jack and I by unlinking
with me to /punish/ me for not thinking like he does.. Oh it was over that DNS
brouhaha, I had setup a DNS server on my laptop and I aliased his nodelisted
domain name to a sub-domain of mine, which of course was only accessible to
computers on /MY LAN/ I never exposed port 53 outside of the LAN to the WAN.

I could have done the same thing with a HOSTS file and it would have sent him
into orbit.

but anyway..

Forcepath checking would not have detected this particular loop, unless I
wanted to test the position 140/1 appeared in the path to me, which should
always be before 106/2000 (same with you). I would have no real reason to
validate 138/146's position in the path. I suppose I could forcepath check a
few things, but its not as rampant an issue like it was 3 to 5 + years ago.

Hopefully he will terminate the loop shortly?

 RC>> .. for echomail paths for forcedpath checking to really work and
 RC>> with echomail flow as it is, I dont want a message languishing on
 RC>> my system sidelined until I get up in the mornings or until I
 RC>> return home from work, because it came in all of a sudden from a
 RC>> different path. This method worked in busier times, I dont feel
 RC>> it is warranted any longer.

 MB> There are times when I do not login to the node for weeks at a time
 MB> and nobody has ever complained about a late or missing message.  They
 MB> have, however, complained elsewhere, where such methods of checking
 MB> are not even used.

The devil you know, to have messages or none, I was really talking about false
positives.

 RC>> The majority of my dupes appear to originate on 123/140 ..

 MB> If the message body is the same, hpt will detect those.

Its that damn PXWINS crap he runs, I am not sure he is running the same
versions that Shannon and Todd use, I see messages trapped as dupes that
shouldnt be and the only common denominator is that they all appear to be QWK
messages. I have even turned off dupe checking in POL_INC for this reason
because a majority of its users use his BBS.

==
Ross
Fidonet Feeds Or Fidonet In Your Newsreader! http://www.easternstar.info
Blog Or Discussion Forum: http://www.cassell.us
Email: ross[at]cassell[dot]us
... Some people are, through no fault of their own, sane.
--- GoldED+/LNX 1.1.5-30512
 * Origin: The Eastern Star - Spartanburg, SC USA (1:123/456)