bounceHammer has been EOL'ed on February 29, 2016

EOL on February 29, 2016

bounceHammer have been downloaded and used by many users and companies since the first release on March 2010 and has been EOL: End Of Life on February 29, 2016. Thanks for using bounceHammer for a long time. We are now providing Sisimai (the successor of bounceHammer, more faster, more higher precision of analysis) as a bounce mail parser library in BSD 2-Clause License.

9. Create neighbor-domains file

 

Configuration file for classifying into custom group(provider)

Configuration file neighbor-domains is for classifying a destinaion domain (the domain part of a recipient address) into custom group ( provider name) at parsing by bin/mailboxparser command.

If you want to classify a destination domain into custom provider, create and edit neighbor-domains file. The file has been installed as INSTALL-DESTINATION/etc/neighbor-domains-example

bounceHammer will work properly if this configuration file DOES NOT EXIST.

Copy and Edit neighbor-domains

Configuration file neighbor-domains is a YAML formatted file. Note that If there is any syntax error in the configuration file, bounceHammer will not work properly.

In this description, You classify three domains: sns.example.jp, bbs.example.net, blog.example.org into the provider oursite, and classify two domains: example.com, example.co.jp into the provider ourcompany. The hostgroup which the domains will be classified into is neighbor.

# cd /usr/local/bouncehammer/etc
# /bin/cp neighbor-domains-example neighbor-domains
# vi neighbor-domains
 
oursite: [ 'sns.example.jp', 'bbs.example.net', 'blog.example.org' ]
ourcompany: [ 'example.com', 'example.co.jp' ]

If the destination domain (the domain part of a recipient) in the bounce email is example.co.jp, bin/mailboxparser command will classify like the followings: hostgroup = neighbor, provider = ourcompany.

Next, If you are interested in classifying famous domains in other country, proceed to 10. Create available-countries page.