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.

Commercial Support

  • 1Setting Up Sisimai Your Server
  • 2Support developmenet using Sisimai
  • 3Support via Email
  • 4Support bounce management
  • 5Parsing your bounced emails

WebUI/Daily Updates


Daily Updates of Email Bounce

bounceHammer output parsed data as a YAML format, and databasectl command insert parsed data into a database.

Beginning with bounceHammer 2.5.0, DailyUpdates has been implemented. This function insert/update the number of bounce emails into the database (t_dailyupdates table) by databasectl command.

The inserted/updated values are useful to refer with summarizer --dailyupdates command, to output as a CSV format for analyzing or editing on a spreadsheet. The values also can be refered on WebUI/DailyUpdates page.

You may refer the values on WebUI/DailyUpdates if it is available. The values are displayed with graph except Internet Explorer.

Abount Each Field

thedate - Date

The thedate field is holding a date which a email has bounced, as the format: YYYY-MM-DD.

inserted - The Number of Inserted Records

The inserted field is holding the number of inserted (to the database) records of the day. bounceHammer distinguish the record of email bounce from other email bounce by the combination (MD5 Hash, we call it message token See the bottom of Data Structure) of Addresser (a sender's email address) and Recipient (a recipient's email address).

If the record which has the same Message Token does not exist on the database, bounceHammer will insert the record as a new record to the database.

updated - The Number of Updated Records

The updated field is holding the number of updated records of the day. If the record which has the Message Token exist on the database and the record on the database is older than the record in the log file, bounceHammer will update the record (increment the Frequency, update the Date and the Reason) on the database.

More information about Frequency and Bounced Date are available at Data Structure page.

skipped - The Number of Skipped Records

The skipped field is holding the number of skipped records of the day by databasectl command.

Why Does Not It Update ?

Inserting or Updating by databasectl command will not executed if one of either the following condition is true.

  1. The record in the log file which is dealt by databasectl command is older than the record on the database.
  2. The domain part of sender's email address in bounce email does not exist on the SenderDomains table.

The number of the skipped field is the amount of these.

failed - The Number of Failed to Update/Insert

The failed field is holding the number of failed to update/insert records by databasectl command. Usually, the value of this field is always 0. If the value of this field is greater than 0, It means that some error have occurred.

executed - The Number of Times the Command Executed

The executed field is holding the number of times databasectl executed. It is used for calculating the estimated amount of email bounces of the day (described later).

estimated - Estimated Amount of Email Bounce

The estimated field is holding the estimated amount of email bounces of the day. This field does not exist as a column on the database. The estimated amount is calculated by the following formula: inserted + updated + skipped / executed.

modified - Last Modified Date

The modified field is holding the last modified date of the record on the database.

At command line tools

bin/databasectl command with many -v option or -B(--batch) option will show the number of the following fields: inserted, updated, skipped, and failed.