# deny using safe.dnsbl.sorbs.net deny message = Email blocked by SORBS - to unblock see http://www.example.com/ hosts = !+relay_hosts domains = +use_rbl_domains !authenticated = * dnslists = safe.dnsbl.sorbs.net
# deny using safe.dnsbl.sorbs.net # deny message = Email blocked by SORBS - to unblock see http://www.example.com/ # hosts = !+relay_hosts # domains = +use_rbl_domains # !authenticated = * # dnslists = safe.dnsbl.sorbs.net
But the people that do would be pissed that their configuration got overwritten.lol I'm not a developer but it's a DA supplied file so I would assume it would just be an overwrite to a bas config file again. Not too many people mess with the exim config files on a standard server config.
thanks for taking the time to explain this...Floyd:
It's nice to see that Michelle has updated the site. I still believe we should no longer use Sorbs as there's no guarantee.
How we feel about transgender people is our own business. Please try to refrain from such expressions on the forums.
The DirectAdmin exim.conf file cannot be an all-purpose file; here are only some of the customizations required:
1) As supplied the official file from DirectAdmin only supports mbox; it needs to be modified (there's a script available) to use Dovecot/Maildir.
2) As supplied unofficial file from NoBaloney Internet Services only supports Dovecot/Maildir; it cannot be easily modified to use mbox.
3) As supplied neither file supports ClamAV. The unofficial file from NoBaloney Internet Services contains the code but one line needs to be uncommented, and several others uncommented.
4) As supplied neither file supports SpamAssassin; the code is in the file but must be uncommented to work.
5) As supplied neither file supports an offer to accidentally blocked senders to whitelist them; the current error message simply tells such senders to visit example.com.
Already answered.Just removed sorbs block list from by web control panel.
Just wondering what will happend if I do not remove the block list.
I'm pretty sure any RBL that isn't active would just timeout, and exim would continue on, skipping that check.
So the worst case, is email delivery may be delayed a few seconds while it waits for the timeout. I highly doubt that exim's logic would bounce an email if an RBL check failed.
SORBS2 is about to be released, some of you will already know about it,
some it will be a completely new concept. The database started
development back in 2004 and was almost coded in 2005, but due to lack
of funding and support it was never completed. Now with the help of
GFI, the basic code of SORBS1 and some new functionality is complete and
ready for the world, more on what's new further down.
To move from the SORBS1 database to the SORBS2 database we are going to
need to migrate some 23 million database rows in to the current 91
million rows in SORBS2. The migration will cause an outage of the SORBS
website and will cause a suspension of 'new and delisted' entries. This
means during the migration new spam whilst detected will not be
published to the website or the DNS zone files. Similarly no delistings
will happen during the migration.
We are expecting to start the migration sometime between 8pm GMT on the
6th August 2010 and 10am GMT on the 6th August 2010. The migration
tests have brought the expectation that it will take around 60 hours,
however the test hardware is different from the production hardware
(slower disks but faster CPUs) so we expect the tests to be a guide only
and are not a fixed time. The migration is dependent on successful
completion of the final tests (a full test migration) and as with all
best laid plans it is possible that something unexpected occurring in
the execution. If the migration has not started by 10am GMT it will be
postponed until next weekend Friday 13th August 2010 (I'm not
Why are we doing this you might ask? Well quite simply the SORBS1
database has very limited functionality and is very "you are listed" or
"you are not listed" and has no functionality to allow anyone but a
SORBS admin to update it. The SORBS2 database on release will include
the following new functionality:
- Self Delisting of Spam/Hacked/Proxy etc entries without needing to use
the IP listed if already authorised as an administrator of the network/IP.
- Removal of the SORBS Spam DB fine, to be replaced by a simple formula
that will allow self delisting based on the number of times we have seen
spam from your network* against the number of previous delistings and
the time elapsed since the last spam was recorded.
- Full integration between the SORBS support tickets and the SORBS2
database so you can quickly reference any support tickets logged as well
as seeing any status updates. This integration will also show the
status of tickets logged by other people about an entry whilst denying
access to the ticket contents.
- Creation of a common interface for SORBS staff, ISPs and end users alike.
- Requirement to register and verify the email address for any new
support tickets or delisting requests. **
- Cleaner and 'snappier' interface where more detail is shown in a less
confused and cluttered way.
- Network and Host lookups <- big change here - you can put in your
network '127.0.0.0/24' for example and it will show all entries in the
- The ability to publicly comment on listings - this will be monitored
closely for abuse, writing in support requests into comments will not
result in a delisting, comments may be deleted by administrators if
inappropriate. HTML will not be allowed. We expect people to make
comments like 'this network has been the bain of our lives and has sent
so much spam that it should be escalated' etc.. SORBS Admins will also
be able to make multi entry comments on listings that all can view that
will be in a similar vein.
- Access to the headers of spams and other data relating to listings if
appropriate access is given.
- Access to full original spam/logfiles/network traces (and captures)
for all abuse in a "write once read many table" for law enforcement
purposes. Law enforcement officials will have access to this data
without interaction from SORBS staff once the initial authorisation is
- An extensible interface and backend that can be extended to include
new data types with just the smallest of changes to the code base.
New funtionality that will be released soon after the migration.
- Network usage updates (not only DUHL, but also the new 'static',
'residential', 'business', 'co-location servers', "permitted to run mail
services" zones) will be updatable directly and instantly by any
authorized representative of the network (ie ISP) ***
- New zone files, including a new SORBS URI database and Malware database.
- Instant listing and delisting (we are moving to the ability for live
DNS information, meaning when the database is updated within seconds the
DNS will be updated, for both listings and delistings)
- Instant reports - new listings will send an email to a registered
administrator of your choice alerting about the listing, the reasons
behind it, and what caused it.
- Instant reports by SMS (subscription service), same as the instant
reports by email but will page any number you have registered with an
SMS alert so that in the event that email is not available (eg through
spammer overload) or not delivering for several hours due to network
outages you will get the message. This service, unless we find
sponsorship will be a 'premium service' that will require a subscription
to cover the costs.
- Reputation data, SORBS2 will 'know' what networks are sending lots of
"not spam" and adjust it's listing policy automatically based on the
quantities of "not spam", this will result in a lower occurrence of
otherwise good network providers getting listed.
SORBS' goal has been and always will be the eradication of abuse from
the Internet, to that end we are expanding our services to enable system
administrators and end users alike to have an external view of their
network. We want you the users to see what is being abused, how, and
why, and hopefully this will give you enough information to eradicate
abuse from your small corner of the Internet making the world a better
SORBS has always been a community project, but has not enabled many
people in the community to take an active role due to security
considerations, with the advent of SORBS2 we will be able to extend the
project to many people can become active participants whilst protecting
the integrity of the data.
Spread the word, SORBS is about to move spam fighting to a whole new level.