On 2017 Nov 05 07:18:48, you wrote to me:

 ml>> one slightly educated wild-arsed guess is it is maybe related to the
 ml>> new adding of unconfigured echos... we haven't seen the code or
 ml>> updated in a few months and we're not sure what mike's configuration
 ml>> is/was on the echo side but it would explain the duplicated 58
 ml>> messages dumped in various echos on various days if maybe those echos
 ml>> were being newly added to his config... where and why the 58
 ml>> duplicated posts are coming from? no clue but obviously somewhere on
 ml>> his system as they were in order from the first of Oct to the end...

 NB> Only 58 made it through?

no, sorry... 58 in each area each time it spewed...

 NB> Well, I suppose it's a lot better than the 10,000+ my system stopped
 NB> here and didn't send on (anything over 30 days old, which was a lot).
 NB> ;)

oh wow! that may explain why i saw only Oct 1 thru 31 in each area they
appeared in... they were all this Oct's postings, too...

 NB> Otherwise, I didn't check to see if any of the ones that actually went
 NB> through were posted with new MSGIDs from their original or not, which
 NB> is also possible.

they were not caught here as dupes by HPT which is set to retain MSGIDs for
1100 days across all message areas carried... that only means that they were
not dupes in the areas they were posted in... HPT does dupe checking per area
instead of across all areas... that means that the same MSGID can be seen in
more than one area... other software doesn't check per area but over all
areas...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Misspelled? Impossible. My modem is error-correcting.
---