Hi Bill,

On 2017-11-07 19:40:26, you wrote to me:

 WV>> Bill said he updated his software. Around that time there was a batch
 WV>> of those  messages from his system. But that could have been
 WV>> generated just before he did the update. I haven't seen any comment
 WV>> from the other sysop involved. But there aren't any of those messages
 WV>> from his system either for a couple of hours. So  lets hope, that
 WV>> involved systems are fixed now and the "spamming" is over...

 BM> I normally update from the cvs every two days of so as sometimes I miss
the
 BM> announceents of any updates over in DoveNet.  That was the issue.
 BM> Everything after release 3.49 through r3.51 was affected.  I am now
running
 BM> R3.54 on all my systems and it seems to ahve resolved the issue.

An hour ago I got a little bunch from your system in my BAD area, because the
messages were too old. It were just 16 messages and they were posted in this
and the SYNCDATA area. Here are the kludges of 1 of them:

@MSGID: 5380.2ftscpubl@1:266/404 1e12a08f
@REPLY: 1:342/200 4b23792c
@TID: SBBSecho 3.02-Win32 r3.51 Nov  6 2017 MSC 1800
@DATE: 04 Sep 17  09:16:00


It says 3.51, so maybe they were held up somewhere?

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815