Hey All,
Well, I believe I discovered why my system barfed mail originating here into a bunch of different fidonet echos (including this one).
I manually added an echo to areas.bbs and apparently typo'd the name, or tag, or something. Any time sbbsecho processed incoming mail that included an area with mail originating from my system, it would then send out all that mail to the echos that were imported.
I'm not really sure why, or exactly how, but I removed the offending line from my areas.bbs
Apologies for any nuisance I may have caused.
I'm not really sure why, or exactly how, but I removed the offending
line from my areas.bbs
Apologies for any nuisance I may have caused.
Do you have a "bad echo" area defined in your area file?
Are you executing SBBSecho with the 'r' (re-toss) command-line option?
Do you see entries in your SBBSecho log with regards to "Moving" messages?
mark lewis wrote to Digital Man on 11-06-17 20:42 <=-
On 2017 Nov 06 12:03:40, you wrote to DaiTengu:
I'm not really sure why, or exactly how, but I removed the offending
line from my areas.bbs
Apologies for any nuisance I may have caused.
Do you have a "bad echo" area defined in your area file?
Are you executing SBBSecho with the 'r' (re-toss) command-line option?
Do you see entries in your SBBSecho log with regards to "Moving" messages?
whatever the problem is, bill mcgarrity just got bitten by it... his system just spewed numerous posts that are at least 3 years old...
Are you executing SBBSecho with the 'r' (re-toss) command-line option?
Do you see entries in your SBBSecho log with regards to "Moving"
messages?
whatever the problem is, bill mcgarrity just got bitten by it... his
system just spewed numerous posts that are at least 3 years old...
I updated all my sbbsecho instances to yesterday's release. sbbbsecho v3.02 r3.51 I think.
Either way, shit happens. I guess according to alex I should get my
hand slapped.. lol!!
Either way, shit happens. I guess according to alex I should get my hand BM>slapped.. lol!!
did you miss the one in FTSC_PUBLIC that thought your node number should have already been removed within seconds of the huge spewage? he's a putz anyway and that's actually an insult to real putzes...
yeah, we larger distribution hubs are watching closely O:)
did you miss the one in FTSC_PUBLIC that thought your node number
should have already been removed within seconds of the huge spewage?
he's a putz anyway and that's actually an insult to real putzes...
I'm pretty sure he thought it was me again. I think I wound up
spamming FTSC_PUBLIC two or three times. Fortunately Nick's system filtered out most of my stuff, Bill wasn't so lucky.
mark lewis wrote to Bill McGarrity on 11-07-17 10:44 <=-
On 2017 Nov 07 08:33:00, you wrote to me:
Are you executing SBBSecho with the 'r' (re-toss) command-line option?
Do you see entries in your SBBSecho log with regards to "Moving"
messages?
whatever the problem is, bill mcgarrity just got bitten by it... his
system just spewed numerous posts that are at least 3 years old...
I updated all my sbbsecho instances to yesterday's release. sbbbsecho v3.02 r3.51 I think.
yeah, we larger distribution hubs are watching closely O:)
Either way, shit happens. I guess according to alex I should get my
hand slapped.. lol!!
did you miss the one in FTSC_PUBLIC that thought your node number
should have already been removed within seconds of the huge spewage?
he's a putz anyway and that's actually an insult to real putzes...
BTW: did you see the 290 spewed into SYNCDATA? ;)
Daryl Stout wrote to BILL MCGARRITY on 11-07-17 12:03 <=-
Either way, shit happens. I guess according to alex I should get my hand
slapped.. lol!!
30 lashes with a wet ethernet cable!! :P
mark lewis wrote to Bill McGarrity on 11-07-17 10:44 <=-
On 2017 Nov 07 08:33:00, you wrote to me:
Are you executing SBBSecho with the 'r' (re-toss) command-line option?
Do you see entries in your SBBSecho log with regards to "Moving"
messages?
whatever the problem is, bill mcgarrity just got bitten by it... his
system just spewed numerous posts that are at least 3 years old...
I updated all my sbbsecho instances to yesterday's release. sbbbsecho v3.02 r3.51 I think.
yeah, we larger distribution hubs are watching closely O:)
Either way, shit happens. I guess according to alex I should get my hand slapped.. lol!!
did you miss the one in FTSC_PUBLIC that thought your node number should have already been removed within seconds of the huge spewage? he's a putz anyway and that's actually an insult to real putzes...
Yes, I've relied to him and the echo over it.
BTW: did you see the 290 spewed into SYNCDATA? ;)
Yes, not sure where that came from other than from what Rob had stated the message pointers were screwed... even in a QWK area.
Either way, shit happens. I guess according to alex I should get my han BM>slapped.. lol!!
30 lashes with a wet ethernet cable!! :P
Hey, no auto-erotica here.. ;)
Digital Man wrote to Bill McGarrity on 11-07-17 17:49 <=-
Re: File Announcements from my system
By: Bill McGarrity to mark lewis on Tue Nov 07 2017 07:55 pm
mark lewis wrote to Bill McGarrity on 11-07-17 10:44 <=-
On 2017 Nov 07 08:33:00, you wrote to me:
Are you executing SBBSecho with the 'r' (re-toss) command-line option?
Do you see entries in your SBBSecho log with regards to "Moving"
messages?
whatever the problem is, bill mcgarrity just got bitten by it... his
system just spewed numerous posts that are at least 3 years old...
I updated all my sbbsecho instances to yesterday's release. sbbbsecho v3.02 r3.51 I think.
yeah, we larger distribution hubs are watching closely O:)
Either way, shit happens. I guess according to alex I should get my hand slapped.. lol!!
did you miss the one in FTSC_PUBLIC that thought your node number should have already been removed within seconds of the huge spewage? he's a putz anyway and that's actually an insult to real putzes...
Yes, I've relied to him and the echo over it.
BTW: did you see the 290 spewed into SYNCDATA? ;)
Yes, not sure where that came from other than from what Rob had stated the message pointers were screwed... even in a QWK area.
Well, to clarify, the "pointers" I was referring to were pointers (addresses) in the C programming language, not "message pointers" as in dates or message numbers that we're used to using/manipulating on a BBS
to tell us what messages are new or not.
In this case, the "pointers" were to message bases themselves (not messages) and they could get crossed-up where messages were being
exported from one msgbase when SBBSecho thought it was a different
message base. That was the bug.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495933:25:41 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,917 |