PH> It would be good if Mystic could detect the flooding of an echo by a
PH> node and if a threshold is reached stop the messages from continuing to
PH> be processed. Perhaps an auto delink from echo if x messages posted
PH> within x minutes plus a netmail alert sent to node + hub admin?
I am open to trying to build something like this, but I am not really sure how
well it would work. If a node spams connections to you that can be covered by
the BINKP auto blocking, but I realize that doesn't really address this
specific issue.
When talking about importing a packet it would be tough to determine when its a
flood if the message content is different each time. If we put a threshold in
for messages then it could backfire in situations where people are trying to do
rescans or maybe even for systems who only poll daily or whenever they feel
like reading (so they tend to get mail in larger clumps)...
I suppose in the case of a hub though, there wouldn't be many instances of a
rescan coming into the hub, so maybe the threshold could work but just be
disabled by default? Or set to something really high.
The tracking would be a bit difficult or at the very least annoying to do and
it would probably slow down tossing speed a bit since it would have to compare
every single message being tossed and it would have to save this sort of data
for every node between MUTIL execution.
How did these messages come in? Where they connecting to you every minute to
send a new message or did it come in clumps every so often? I think having a
clearer picture might help me think it through a little better.
... Some people have no idea what they're doing, and are really good at it!
--- Mystic BBS v1.12 A47 2021/11/06 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)
|
