|
|
|
||||||||||||
 |
|||||||||||||
 |
 |
||||||||||||
|
|
|||||||||||||
| BLComp © 2004 BLComp is a utility for COMParing Mailwasher blacklist files and spam lists |
|||||||||||||
|
Mailwasher
is a product of Firetrust,
a
commercial package that offers multiple strategies for the effective
control of SPAM.
|
||||||||||||
|
|
|||||||||||||
| Press the Play button for some soothing music | |||||||||||||
| BLComp |  |
Use
BLComp to compare your Blacklist with * another users blacklist * published spam lists * your backup copies * and check the actions of third party tools |
|||||||||||
| BLComp
is a utility to
compare a Blacklist file against another
Blacklist file or against a blacklist entry/email address list (any
combination is
permissible). BLComp is an option within BLScanPlus. This page documents the BLComp utility and it makes no difference whether you're using the Classic or Pro version of BLScanPlus unless otherwise specified. |
|||||||||||||
|
|
|||||||||||||
| BLComp |
 |
||||||||||||
The
BLComp
utility has only one function, that is to compare two files. The input
files
can be any
combination of;
If one of the input files is a Blacklist file, BLComp will compare the entries within the blacklist section or the whitelist section of that file. If one or both input files are a list of email addresses, BLComp requires a simple sequential list, with one entry per line e.g.; name6@domain33
name2@domain2 This is a comment *@domain3 38246 name3@*.domain1 name4@domain4 38239 etc. As shown above, the Mailwasher date code can also be present in the file. The date code however is not considered as part of the comparison process, so two entries which are the same, but with different date codes, are considered identical. BLComp will only process lines that contain an '@' character, so comment lines or gaps are permitted, provided they do not include an '@' of course. This point does not apply to a Mailwasher blacklist file, where all entries are read regardless of whether an "@" is present. When BLComp is run, the entries unique to each file are determined. If there are differences, then BLComp will create an output file with a list of address unique to the first file and a second list of addresses unique to the second file. (The first and second sets of unique entries will be separated, either by a textual message or by a dummy domain name of "break@blcomp.com"). Note that if you have any duplicate entries in your Blacklist file, Mailwasher will remove them. So do not spend time manually searching through a spam list to separate out entries that you already have in your Blacklist file. Just run your Blacklist and the spam list through BLComp, look at the differences and cut/paste the ones you want back into your Blacklist. BLComp produces one output file; |
|||||||||||||
| BLComp | This is the output file and carries a concatenated list of the unique entries found in the first and second files. | ||||||||||||
|
|
|||||||||||||
| BLComp |  |
||||||||||||
Having
described what BLComp does, the intended purpose is described below;
The main value of exchanging a blacklist is to gain wildcard entries for spam domains, so ideally you only want to 'deal' in wildcard entries. BLScan features an exchange file option that does exactly this. The exchange file produced by BLScan during 'Scan' separates out your blacklist wildcards (not individual addresses) less any country specific wildcards that use the two letter country code. As always it should be noted that blacklisting a domain will cause any incoming email from any user name at that domain to be subject to the Blacklist options you set in Mailwasher. So be careful not to mask out sources of legitimate email. |
|||||||||||||
| BLComp |  |
BLComp is included with BLScanPlus |
|||||||||||
|
The version
history is given below;
|
|||||||||||||
|
|||||||||||||
| Back to top | |||||||||||||
|
|
|||||||||||||
|
|||||||||||||
|
|
|||||||||||||
|
|
|||||||||||||
