Why can spamdyke automatically blacklist (or delay) servers that are rejected too many times?
Technically, this is not possible because spamdyke of the way spamdyke works. Without a long-running daemon to keep track of the statistics and “penalties”, each instance of spamdyke would have to perform the accounting work on its own. This would take too long and is very likely to be error-prone. However, even if it were possible, this kind of feature is very problematic, for several reasons. • The only way spamdyke could possibly decide to block a server would be to examine its rejection statistics (i.e. number of rejections per time period exceeds a threshold). However, if spamdyke is already rejecting messages, what is the purpose of blacklisting the server? In effect, that would enable two filters for blocking a server when one is already enough. • Innocent mistakes by users of large email systems could unfairly penalize every user of that system. For example, if an AOL user sends several messages that are rejected, an automatic blacklist might block all messages from all AOL use
Related Questions
- I know that I can inject time delay but when I type WAITFOR DELAY :0:5, I get a result after about two/three/four/… times later than my value set in the delay. Whats wrong?
- What is the time delay in between tee times for a PGA championship tour match?
- Why does the DVR system reboot automatically everyday at certain times?
