nobaloney
NoBaloney Internet Svcs - In Memoriam †
SpamBlocker Version 2 for DirectAdmin has just been released.
SpamBlocker Version 2 is a highly recommended upgrade, as it fixes some bugs that were causing certain whitelists to be ineffective under some circumstances.
SpamBlocker implements the availability of port 587 for authenticated SMTP; a feature required so that your clients whose ISPs block port 25 may still use your server for outgoing email.
SpamBlocker Version 2 uses the following public blocklists:
SpamBlocker Version 2 uses the following locally maintained blocklists:
SpamBlocker Version 2 uses the following locally maintained whitelists:
When SpamBlocker Version 2 blocks emails it replies to the sending server with a complete error message specifying which blocklist, local or public, was used. RFC compliant servers will notify the original message senders so senders will know their email wasn't received, will know why it wasn't received, and will know how to get it unblocked so it will be received.
SpamBlocker Version 2 is fully functional on its own, but is also compatible with a soon-to-be-available commercially-distributed plugin to allow simplified management. Look for an announcement soon.
SpamBlocker Version 2 will be included in future releases of DirectAdmin and will be available from the DirectAdmin website as soon as it becomes an official part of DirectAdmin. Beginning immediately it may also be downloaded from the official SpamBlocker site here.
Note: If you do not make the mandatory changes noted in the README file, then SpamBlocker may not work for you, and may in fact completely stop your server from either receiving or sending email.
If you wish to upgrade to the latest SpamBlocker Version 2 file but do not feel comfortable making changes yourself please contact NoBaloney Internet Services (see my siglines below) to request our help.
It's my honest hope that SpamBlocker helps you in the fight against spam.
Jeff
SpamBlocker Version 2 is a highly recommended upgrade, as it fixes some bugs that were causing certain whitelists to be ineffective under some circumstances.
SpamBlocker implements the availability of port 587 for authenticated SMTP; a feature required so that your clients whose ISPs block port 25 may still use your server for outgoing email.
SpamBlocker Version 2 uses the following public blocklists:
- SPAMHAUS
- ORDB
- SORBS SMTP LIST
- SORBS IP LISTS
- SORBS NAME-BASED LIST
- SPAMCOP
- NJABL
- CBL
SpamBlocker Version 2 uses the following locally maintained blocklists:
- Blocking by Hosts
- Blocking by Domains
- Blocking by Senders
SpamBlocker Version 2 uses the following locally maintained whitelists:
- Whitelist Domains
- Whitelist Hosts
- Whitelist Senders
When SpamBlocker Version 2 blocks emails it replies to the sending server with a complete error message specifying which blocklist, local or public, was used. RFC compliant servers will notify the original message senders so senders will know their email wasn't received, will know why it wasn't received, and will know how to get it unblocked so it will be received.
SpamBlocker Version 2 is fully functional on its own, but is also compatible with a soon-to-be-available commercially-distributed plugin to allow simplified management. Look for an announcement soon.
SpamBlocker Version 2 will be included in future releases of DirectAdmin and will be available from the DirectAdmin website as soon as it becomes an official part of DirectAdmin. Beginning immediately it may also be downloaded from the official SpamBlocker site here.
Note: If you do not make the mandatory changes noted in the README file, then SpamBlocker may not work for you, and may in fact completely stop your server from either receiving or sending email.
If you wish to upgrade to the latest SpamBlocker Version 2 file but do not feel comfortable making changes yourself please contact NoBaloney Internet Services (see my siglines below) to request our help.
It's my honest hope that SpamBlocker helps you in the fight against spam.
Jeff