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

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

Only 58 made it through?

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

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

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...

Otherwise, I didn't check to see if any of the ones that actually went through were posted with new MSGIDs from their original or not, which
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.
---
* Origin: (1:3634/12.73)

Re: New Files At War Ensemble BBS
By: Nicholas Boel to Rob Swindell on Sun Nov 05 2017 07:22 am

That said, I'm not blaming your software.. but I originally pointed out that these dupes started the day he upgraded to the Oct 31 sources.

The spam/dupes I see in this echo appeared on Oct-3. In some other echoes, they appeared later (e.g. Oct-13), but not Oct-31. <shrug>


digital man

Synchronet "Real Fact" #77:
Rob Swindell still has dozens of BBS-related magazines in his possession. Norco, CA WX: 69.6°F, 57.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs

Hello Rob,

On Mon Nov 06 2017 12:40:38, Rob Swindell wrote to Nicholas Boel:

That said, I'm not blaming your software.. but I originally pointed
out that these dupes started the day he upgraded to the Oct 31
sources.

The spam/dupes I see in this echo appeared on Oct-3. In some other
echoes, they appeared later (e.g. Oct-13), but not Oct-31. <shrug>

Take another look at the timestamps of said "file report" messages that came from War Ensemble BBS. They were dated from Oct. 1 up until Nov 4th I believe. They were not marked as dupes because they were never (and should not have ever
been) posted here in the first place.

That said, the last I heard from him was it was a little more than a configuration issue, so you may have some config files coming your way.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Re: New Files At War Ensemble BBS
By: Nicholas Boel to Rob Swindell on Mon Nov 06 2017 05:52 pm

Hello Rob,

On Mon Nov 06 2017 12:40:38, Rob Swindell wrote to Nicholas Boel:

That said, I'm not blaming your software.. but I originally pointed
out that these dupes started the day he upgraded to the Oct 31
sources.

The spam/dupes I see in this echo appeared on Oct-3. In some other echoes, they appeared later (e.g. Oct-13), but not Oct-31. <shrug>

Take another look at the timestamps of said "file report" messages that came from War Ensemble BBS. They were dated from Oct. 1 up until Nov 4th I believe.

Yes, I see that now:
when_written 59D09271 412C Sun Oct 01 2017 12:00 am EST
when_imported 59F92032 C1E0 Tue Oct 31 2017 06:15 pm PDT

They were not marked as dupes because they were never (and should
not have ever
been) posted here in the first place.

That said, the last I heard from him was it was a little more than a configuration issue, so you may have some config files coming your way.

Yup, it was an SBBSecho bug introduced on Oct-27, unrelated to any new feature usage (now fixed). Apparently DaiTengu runs SBBSecho in a manner that is uncommon (handles both importing and exporting with every invocation) and the problem only occurred in that scenario. So no one else has encountered this issue, thankfully.

digital man

Synchronet/BBS Terminology Definition #58:
XPDEV = Cross-platform Development
Norco, CA WX: 66.8°F, 57.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs

Hello Rob,

On Mon Nov 06 2017 16:56:16, Rob Swindell wrote to Nicholas Boel:

That said, the last I heard from him was it was a little more than
a configuration issue, so you may have some config files coming
your way.

Yup, it was an SBBSecho bug introduced on Oct-27, unrelated to any new feature usage (now fixed). Apparently DaiTengu runs SBBSecho in a
manner that is uncommon (handles both importing and exporting with
every invocation) and the problem only occurred in that scenario. So
no one else has encountered this issue, thankfully.

Looks like Bill just got bit by it too, but glad to see it was found and fixed quickly!

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

On 11/06/17, Nicholas Boel pondered and said...

Looks like Bill just got bit by it too, but glad to see it was found and fixed quickly!

Agreed, got a dump of them across a number or echos from his system too.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)