![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
![]() |
Realtime Blackhole Lists (RBL's)
One of the best ways to fight spam is to use RBL's. RBL's are lists of servers that usually you don't want to talk to, sometimes they are lists of servers that are open relays or they are lists of servers that are proxies or maybe lists of servers that are dynamic ip's. There are many different types of RBL's out there so you might want to do some investigation before you deicde which ones to use. The idea is that when a server connects to your server SurgeMail will then check the RBL to see if the connecting server is listed, if it is then we can simply drop their connection or we can stamp the message to say its listed on a RBL and increase the ASPAM score. Using RBL's can dramatically decrease the amount of SPAM coming into your system and we highly recommend using them.
Here are some RBL's you can use.
Name of RBL What to enter in SurgeMail
(name section)Response Code General Information on RBL. spamhaus sbl.spamhaus.org 127.0.0.2 Very well known RBL, well recommended.
Direct UBE sources, verified spam services and ROKSO spammersspamhaus xbl.spamhaus.org 127.0.0.4-6 Illegal 3rd party exploits, including proxies, worms and trojan exploits spamhaus sbl-xbl.spamhaus.org 127.0.0.2-6 If you want to use both sbl and xbl then you can just enter this into SurgeMail. Domain Name System Real-time Black List (DNSRBL) dun.dnsrbl.net 127.0.0.2-9 List of IP addresses of machines that are either direct SPAM sources or Dial-up (dynamic address) pools which would never be a source of non-spam messages. RFC Ignorant (Whois) whois.rfc-ignorant.org 127.0.0.7 or 127.0.0.5 List of IP's that do not comply with RFC's.
(Careful about using this one) ?Not Just Another Bogus List (NJABL) dnsbl.njabl.org 127.0.0.2-9 List of known and potential spam sources (open relays, open proxies, open form to mail HTTP gateways, dynamic IP pools, and direct spammers). Spamcop bl.spamcop.net A very good RBL to use, quite reliable. ORDB relays.ordb.org Database of Open Relays
There are plenty more out there, but the above ones are well known and will probably do the trick
To add them into SurgeMail, click on global settings, then SPAM settings, and the RBL settings are at the top of that section.
![]()
Once you have clicked on Edit RBL's
So under the name section you add the domain of the rbl (eg bl.spamcop.net), then what action you would like to take (deny, accept, or stamp) and then in the stamp section you can add the stamp.
deny = connection is banned and sending server is sent the stamp message.
stamp = message will be allowed through but it will be stamped with stamp you set. The stamp is a message header and should normally start with X- eg X-RBL: Listed in SPAMCOP (||remoteip||)The RBL's are processed in the order they are listed and if the sending server is found on one of the RBL's the rest will not be checked to save processing power.
There are servers that you might not want to ever risk being denied, sometimes servers can accidentally get themselves on RBL's or the RBL's can add servers by mistake at times. In the first screen shot you can see the third option(exception list of IP's) allows you to add IP's that will never be checked by SurgeMail.You can also set the second option in the screenshot (do late disconnect....). This means that the your users are allowed to authenticate first and then the RBL checks are done, this means that if your users are on a RBL they will still be able to send messages through your server. This can also be used with the setting g_spf_skip_to which allows you to add recipients that will be bypassed for RBL checks, so you might add postmaster in here as everyone should be able to send to postmaster.
Editing surgemail.ini directly
For those that prefer to edit surgemail.ini directly here are the settings and some examples
g_orbs_list name="sbl-xbl.spamhaus.org" action="deny" stamp="Your ip ||remoteip|| is listed in the spamhaus RBL http://www.spamhaus.org"
g_orbs_list name="bl.spamcop.net" action="stamp" stamp="X-RBL: Listed in SPAMCOP"RBL Exceptions:
g_orbs_exception "ip,ip,ip"
g_orbs_late "true" - This makes the RBL checks happen after the authentication phase and allows you to also use g_spf_skip_to.
g_spf_skip_to "fred@mydomain.com" - This will make SurgeMail not use the RBL if the message is going to fred@mydomain.com and you also have g_orbs_late "true" activated.
g_spf_skip_from "fred@anotherdomain.com" - Will make SurgeMail skip RBL checks if the from address matches this, must have g_orbs_late "true" activated.