NAME harcoderbl DESCRIPTION It's essentially the same plugin as rblchecks with the following differences: 1. It ignores the RBLSERVERS environment variable 2. It is hardcoded (thus the name), to use bl.spamcop.net and combined.njabl.org 3. It gives more informative errors to the sender, because it knows exactly what RBL it uses and knows the lookup pages for each: 451 NJABL Blocked, look at http://njabl.org/lookup?24.232.239.145 If the user is successfully authenticated, this plugin disables itself for the session. This is necessary because most home IP addresses are listed in one RBL or the other. This behaviour, may become configurable in the future. It could be used at the HELO command, but then you have no way to allow access for your authenticated users. REQUIREMENTS This plugin will add one or more DNS calls for every incoming connection, and one line of logging. Other than that, performance impact should be negligible. If the RBL servers you use are down, it will cause latency, but since that should never happen to authenticated connections, your users should never notice it. CONFIGURATION None possible. LOGGING It logs each accepted or rejected connection: hardcoderbl: pid 12345 - 451 NJABL Blocked, look at http://njabl.org/lookup?24.232.239.145 hardcoderbl: pid 12346 - Accepted 24.232.239.145 ERROR MESSAGES If the user is blocked by this plugin, he will get this kind of error message: 451 NJABL Blocked, look at http://njabl.org/lookup?24.232.239.145 This more descriptive error message is the only reason to use this plugin instead of rblchecks. SEE ALSO plugins-ra(8) Homepage: http://ralsina.blogsite.org/stories/39.html COPYRIGHT Copyright © 2006 Roberto Alsina Copyright (C) 2003-2004 Perolo Silantico For any questions please contact Roberto Alsina, because this version is heavily modified from Mr. Silantico's original. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.