| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | you bastards |
RS> Squish systems can be set to dupe check on MSGID too. BG> In fact, Squish 1.10 can be *told* to check dupes using MSGID, BG> Header, or both, but due to an acknowledged bug, regardless of what BG> you tell it, Squish will always check dupes by MSGID regardless (i.e. BG> it can't be turned off, unless dupe checking is disabled completely). Yeah, I realised that and saw the announcement of it quite some time ago now. BG> However, despite this bug, in the 3 months I've been using 1.10, it BG> has *never* falsely detected a dupe here. Yeah, Paul has had a brain fart on this one. Yes its possible to have the To: From: Date: and Subject: fields identical, BUT you also have to have the Time field identical too to have a problem. Even when the message is coming from a QWK system which has no seconds field, the chances are pretty remote. Possible, coz you can get that if you proof read the mail, you can edit two in the same minute, but remote. And the 2 second increment in the early PQWKs is good protection against that. THEN the only thing which will bite you is proof reading those two messages and changing them BOTH in the SAME minute, and they must ALSO be PRECISELY 30 messages apart in the REP too. Very very unlikely. Your test isnt actually that conclusive coz by definition the vast bulk of false dupes would have got dropped before they got to you. BG> Therefore, I can see no valid reason for Paul not to be generating BG> MSGIDs in his software. None at all. Just a fundamentally extremist and fascist state of mind |-) --- PQWK202* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 @PATH: 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™.