Internal flow

The following figure displays a flow: email delivery -> email bounce -> parsing bounces -> accumulating parsed data -> using parsed data, by using bounceHammer in your network. Your email delivery system or website can be linked with bounceHammer if your system can read YAML/JSON data.

You may not use all the function of bounceHammer, For Example, if you have installed bounceHammer without WebUI/HTTP-API, Web server and Web-related functions and modules do not to need.

The following figure displays a flow with focus on commands: Parsing by mailboxparser, Accumulating by logger, Inserting data into DB by databasectl, Getting data by datadumper and WebUI).

You may not use all of the commands of bounceHammer If you want to get parsed data only, databasectl, tablectl, and datadumper command and database are not required.

The following figure displays a sample diagram of bounceHammer in your netowrk.

The vital points of the above figure are the following.

• Send bounced emails to the host which bounceHammer is running (in the above figure, using scp, fetchmail)
• Send parsed data(YAML/JSON) from the host which bounceHammer is running to other host

Because bounceHammer can work even if there is any bounced email, you can use ftp, rsync, smtp for sending a bounced email except scp.