https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6048
--- Comment #31 from Sidney Markowitz <[email protected]> 2009-01-23 11:53:16 PST --- (In reply to comment #29 and comment #30) If the problem is a small percentage of installations that are super high volume and not getting or ignoring attempts to reach them, I don't see how they can count on the admin email address being set correctly or the admin responding to the email. And that still leaves the policy question at the heart of this bug report, which is do we allow a default enabled setting of a RBL that has this particular policy. Regarding the 127.0.0.1 suggestion, given that each child process is independent and all the DNS queries are sent out at once to be checked asynchronously as the replies come in, how would that work? Won't we have to have an additional 127.0.0.1 query per RBL and then wait for the reply before sending the actual queries, and wouldn't that make every process have to wait the extra time for the replies to that query, and wouldn't that only reduce the load from those very high volume users by a factor of the the average number of URLs queried per message (because they still get one 127.0.0.1 query per message) which might not be enough to solve the problem from them anyway? Or is that last issue not a problem because you can make the response to 127.0.0.1 have a very large TTL? -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
