nobaloney
NoBaloney Internet Svcs - In Memoriam †
In the past the SpamBlocker Technology* exim.conf file offered to one of two choices for blocking mailservers known to send spam, by using RBLs (realtime block lists).
1) you could use a separate use_rbl_domains file and use realtime block lists to block mail only coming to certain domains hosted on your server.
2) you could make use_rbl_domains a link to the domains file, and use realtime block lists to block mail for coming to all domains hosted on your server.
Recently DirectAdmin administrators have expressed an interest in changing the default behavior of SpamBlocker Technology* to switch to an rbl_exceptions file. If we did that the options would be:
1) you could use a separate rbl_exceptions file and use realtime block lists to block mail coming in to all domains hosted on your server, except for the domains listed in the rbl_exceptions file.
2) you could use an rbl_exceptions file as a link to your domains file, and not use realtime blocklists at all, but continue to use the other features of the SpamBlocker Technology* exim.conf file.
That all said, making the change comes with its own set of issues:
The problem is that if I make the change, then everyone installing the new file need to rework their files. More work on install because the new file will simply not work unless you make the file change (exim won't run).
It's easy enough for me to make the change from the use_rbl_domains file to the rbl_exceptions file, but it's a lot of work to implement, especially if you still have separate domains and use_rbl_domains files, and even more so if you have a lot of servers.
It will make it a lot harder for DirectAdmin to use it as their new standard.
But it's probably much better moving into the future.
What do you think? Please answer the poll before posting.
Thanks!
Jeff
*SpamBlocker Technology is a trademark of NoBaloney Internet Services
for our exim.conf file for DirectAdmin. The exim.conf file itself is distributed
under the GNU GENERAL PUBLIC LICENSE, Version 2, June 1991.
1) you could use a separate use_rbl_domains file and use realtime block lists to block mail only coming to certain domains hosted on your server.
2) you could make use_rbl_domains a link to the domains file, and use realtime block lists to block mail for coming to all domains hosted on your server.
Recently DirectAdmin administrators have expressed an interest in changing the default behavior of SpamBlocker Technology* to switch to an rbl_exceptions file. If we did that the options would be:
1) you could use a separate rbl_exceptions file and use realtime block lists to block mail coming in to all domains hosted on your server, except for the domains listed in the rbl_exceptions file.
2) you could use an rbl_exceptions file as a link to your domains file, and not use realtime blocklists at all, but continue to use the other features of the SpamBlocker Technology* exim.conf file.
That all said, making the change comes with its own set of issues:
The problem is that if I make the change, then everyone installing the new file need to rework their files. More work on install because the new file will simply not work unless you make the file change (exim won't run).
It's easy enough for me to make the change from the use_rbl_domains file to the rbl_exceptions file, but it's a lot of work to implement, especially if you still have separate domains and use_rbl_domains files, and even more so if you have a lot of servers.
It will make it a lot harder for DirectAdmin to use it as their new standard.
But it's probably much better moving into the future.
What do you think? Please answer the poll before posting.
Thanks!
Jeff
*SpamBlocker Technology is a trademark of NoBaloney Internet Services
for our exim.conf file for DirectAdmin. The exim.conf file itself is distributed
under the GNU GENERAL PUBLIC LICENSE, Version 2, June 1991.