| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Dupes |
Niels, at 21:18 on May 15 1997, you wrote to David Drummond ... NP> If you have read my previous mail regarding dupes. the bad NP> news is that I turned Dupe checking ON and FMail didn't pick NP> up the dupes from Teddy and forwarded the whole lot on to NP> you and John. NP> I opened the Zip and deleted the packet of messages from NP> teddy (after checking that there was no mail from her NP> personally ) so you will not get another load of Dupes. NP> What I can't figure out is why it didn't detect ALL the NP> messages as dupes. I actually checked the MSG ID's and they NP> were identical to messages already in the message base. The NP> ones from Teddy must be altered in some way that defeats NP> FMAIL's dupe checking mechanism. NP> I.E It detects Dupes if I toss YOUR pkts twice NP> It won't detect the same messages as dupes after they come NP> back from Teddy. NP> SO........ NP> Seeing you had this problem between you and Bill G, what did NP> you do in your setup to stop your system sending the NP> messages from Bill back to BIll. NP> I know the software is different, but your answer may give NP> me a clue as to what it is that needs changing on TEDDY's NP> system to stop it sending her inbound mail from being sent NP> staraight back to me. NP> I will be studying the Docs in the meantime. We instituted a "fakenet" number and I sent all outbound stuff to it instead. I had this "fakenet" node routed to Bill's point number. I have a feeling that inbound stuff bounced back to him, but was killed by his dupechecker. I had a similar problem when you started feeding me. All inbound from you was immediately repacked as outbound to you. I have resolved this by NOT forwarding the echoes to your point number at all. I toss them to John T's node number. I have any outbound for John T routed via your point number. Inbound mail from you already has John's node in the seenby so it doesn't get re-tossed straight back at you. NP> If I can't get her end fixed, then I may have to setup NP> Christians system to NOT forward from the FMail Toss and NP> make WildMail forward Locuser & Sysop when the mail get NP> tossed into his WildCat message base NP> Even then I may still have the same trouble if the Wildcat NP> Dupe detection system gets fooled by the difference in the NP> existing messages and the returned messages. (whatever it NP> is) NP> I have learnt that Christians system ADDs the Node part of NP> his point address to the seenby line. This is why I can't NP> use the SEENBY's as then it won't forward anything :-( NP> While I was on his sytem I used his editor. It is real shit NP> after being used to this one.! NP> After the DOCS comes the FMAIL echo. NP> The other solution would be to make Christian a node ?? :-) You mean getting him nodelisted? Pretty scary stuff..... Another option is that I set up a direct link from here to John's system and feed the LOCwhatever echos direct to him, (though I don't think that will help Teddy at all - the problem is in her setup I think). David @EOT: --- Msgedsq/2 3.10* Origin: The JabberWOCky +61 7 3868 1597 (3:640/305) SEEN-BY: 640/305 670/213 711/934 712/610 @PATH: 640/305 712/610 711/934 |
|
| 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™.