PE>> Yeah, well you posted 38 messages today, which means the
"seconds"
PE>> field wrapped around in your version of PQWK, and could have created
PE>> dupes.  PQWK211 is a drop-in replacement for PQWK202, and will have
PE>> at least given you a fighting chance for messages 30-59.

RS> True, its a problem. But 211 drops these {at}EOT turds everywhere and
RS> many people see them in the mail.

PE> I don't for starters.

'many people see them' allows for some like you who dont.

PE> It's a problem for PQWK users,

And non PQWK users too.

PE> because it doesn't strip the kludge lines (it should, and it will as
PE> soon as I get answers to my questions).

OK< but that wont fix the problem with the non PQWK users who see them.

RS> Corse real MSGIDs in the outgoing PKT would fix the dupe problem even
RS> better.

PE> How many times do I have to tell you Rod?

You can tell me as often as you like Paul, if you are wrong the first
time, repeating it isnt going to change anything.

PE> It doesn't matter a toss if you put in a MSGID.

Yes it does. If you have a MSGID you eliminate the statistical
possibility of some dork dupe checking on the header data alone and
falsely detecting a dupe.

PE> The moment it goes through a squish system, it will do a crc on from,
PE> to + subject, and get the "time" field, and do a dupe check on that.

And the statistical possibility of those fields being duplicated in a
pair of messages in a single packet in all except the seconds field is
remote. And there is bugger all practical difference between a 1 and 2
second increment in the seconds field in that case.

Squish systems can be set to dupe check on MSGID too.

PE> It is important to make that unique, and PQWK211 does, and PQWK202
PE> doesn't.

And it aint that simple coz even with a one second increment in the time
field, you have only just improved the chances. MSGID almost completely
eliminates the problem cos THEN you only have the utterly remote prospect
of a change in mail software reusing a MSGID in 3 years. Utterly remote.
And even that utterly remote possibility is avoidable with a system like
PQWK that you have control over the software of.

--- PQWK202