Index of /services/blockcracking

[ICO]NameLast modifiedSizeDescription

[PARENTDIR]Parent Directory   -  
[DIR]1.1/ 2014-12-24 00:24 -  
[DIR]1.2/ 2015-04-24 06:43 -  
[DIR]1.3/ 2015-05-15 05:56 -  
[DIR]1.4/ 2016-06-03 22:51 -  
[DIR]1.5/ 2016-08-26 11:59 -  
[DIR]1.6/ 2016-10-05 03:32 -  
[DIR]1.7/ 2017-09-27 19:33 -  
[DIR]1.8/ 2017-10-08 14:49 -  
[   ]exim.blockcracking-1..>2014-09-04 04:56 1.9K 
[   ]exim.blockcracking-1..>2014-11-03 03:59 1.9K 
[   ]exim.blockcracking-1..>2015-04-24 06:43 2.2K 
[   ]exim.blockcracking-1..>2015-05-15 05:56 2.2K 
[   ]exim.blockcracking-1..>2016-06-03 22:51 2.6K 
[   ]exim.blockcracking-1..>2016-08-26 12:00 2.6K 
[   ]exim.blockcracking-1..>2016-10-05 03:32 2.6K 
[   ]exim.blockcracking-1..>2017-09-27 19:48 2.6K 
[   ]exim.blockcracking-1..>2017-10-08 14:49 2.7K 


Credit to

this version has been modified for use with a DirectAdmin System.
It requires a minimum of exim.conf 4.3.3 and 23


See this guide for automated CustomBuild 2.0 install:


See the forum for issues or questions:


The idea BlockCracking is that spammers typically send masses of emails and a large number of those emails are invalid or no longer exists (spammers don't confirm them)
The BlockCracking code will keep count of these invalid deliveries and block the sender of the given type, if the limit is hit, within a period of time.

Sender Types:
- auth: an account who had authenticated with smtp-auth
- script: any script being delivered to exim via /usr/sbin/sendmail|exim commandline, including php mail();


You can use the /etc/exim.blockcracking/variables.conf.custom to override the default variables.(see below)
There are also DirectAdmin directadmin.conf options to control how DA handles the reports:

0 = script paths and E-Mails cannot be unblocked by DA.
1 >= emails and paths can be unblocked by the User*
2 >= Automatically unblocked after 'block_cracking_unblock_minutes' have passed, plus abilities from =1

*an E-Mail block must be done one-level up, eg: E-Mail unblocked by User. If User is blocked, unblocked by Reseller or via Lost Password tool.


-- variables.conf

If you want to customize the file, create your own file:
-- variables.conf.custom, and set only the values in this file as desired, and they'll override the defaults.
Use double equals in the variables.conf.custom, to override the varibles.conf

-- auth.conf

Contains the BlockCracking code to count and block smtp authenticated accounts.
Blocks to the file:

-- script.conf

Contains the BlockCracking code to count and block script paths.
Since exim has no way of knowing which script actually sent the message, this code will track and rate-lmiit based on the script's working path.
This will allow other possibly valid scripts in other paths to continue working.
Blocks to the file:

-- script.recipients.conf

Contains a "recipients" ACL for the scripts.conf to call, because the non-SMTP ACLs must figure out the recipients one-by-one (Credit to Lena for helping with this)

-- script.denied_paths.txt

Contains a list of nwildlsearch regex values to be compared against the current working directory for a sending script.
Will the cwd does not contain the filename, just the path it's under.
CustomBuild 2.0 will create this file for you, based on the scripts.denied_paths.txt.
If you want to customize it, create scripts.denied_paths.custom.txt, and CB will use this instead of the scripts.denied_paths.default.txt.

-- /etc/virtual/bc_skip_authenticated_users

Optional file, does not need to exist.
Contains list of smtp-auth email addresses which will be skipped / not scanned by BlockCracking

-- /etc/virtual/bc_skip_sending_hosts

Optional file, does not need to exist.
Contains hostlist of IPs or rDNS host addresses email addresses which will be skipped / not scanned by BlockCracking.
Wildcards may work on rDNS hostnames, but should be listed after any full IPs or ranges