bounceHammer 2.7.8 has been released. To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.7.8 and the previous version.

New functionality

• (EXPERIMENTAL IMPLEMENTATION): bin/mailboxparser detects some of FBL: Feedback loop message as a bounced email. Thanks to Gilles.

Fixed Bugs

• Fixed an issue that src/cgi/Makefile uses "/" as a temporary di- rectory when the "make" command is executed. Thanks to Hasegawa.
• Fixed an issue that Kanadzuchi::Address->canonify fails when the email header does not contain any space character like follwoing: "=?ISO-2022-JP?B?.....?=" . Thanks to Kanazawa.

Get the tarball of bounceHammer 2.7.8 release from Download page. If there is any patch for version 2.7.8, download patches and apply before running the progmam: configure, make.

To upgrade to bounceHammer 2.7.8 from the previous version or older, you overwrite the previous version like the following:

There is an issue that when you execute the command "make" for building bounce hammer, src/cgi/Makefile uses "/" as a temporary directory. This bug is caused that an undefined macro is used in the Makefile.

If you run the "make" command as a non-root user, the build will be failed with the message "cp: /api.cgi: Permission denied *** Error code 1". To fix the problem, download Patch(001_src-cgi-makefile.patch) and apply the patch before ./configure.

If you have already installed bouncehammer, please delete 2 files that may be remained at "/" directory: /api.cgi and /bouncehammer.cgi .

bounceHammer 2.7.7 has been released. To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.7.7 and the previous version.

New functionality

• New command line option for bin/mailboxparser, --save-failed-mesg is for save messages which are failed to parse.

Assorted improvements and code cleanup

• Update for commercial MTA modules(bouncehammer-nails).
• Improved analytical accuracy for bounce messages via Exim, qmail, Sendmail, Postfix, and au by KDDI. Thanks to Toyokawa.

Get the tarball of bounceHammer 2.7.7 release from Download page. If there is any patch for version 2.7.7, download patches and apply before running the progmam: configure, make.

To upgrade to bounceHammer 2.7.7 from the previous version or older, you overwrite the previous version like the following:

Bug information

There is an issue that when you execute the command "make" for building bounce hammer, src/cgi/Makefile uses "/" as a temporary directory. See Bug: 2.7.7-001 page to get detailed information and the patch.

bounceHammer 2.7.6 has been released. To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.7.6 and the previous version.

Assorted improvements and code cleanup

• @m.facebook.com is classified into Webmail/facebook .
• @verizon.net is classified into Smartphone/verizon..

Fixed Bugs

• Fix the 3rd argument of AC_PATH_PROG() macro in ./configure .
• Fixed an issue that bin/mailboxparser stops with the error message: ``Invalid mailbox list: ...'' if any ESC(0x1b) character is contained in a phrase part of a email header. Thanks to Toyokawa.

Get the tarball of bounceHammer 2.7.6 release from Download page. If there is any patch for version 2.7.6, download patches and apply before running the progmam: configure, make.

To upgrade to bounceHammer 2.7.6 from the previous version or older, you overwrite the previous version like the following:

bounceHammer 2.7.5 has been released. To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.7.5 and the previous version.

Assorted improvements and code cleanup

• Support a bounced email from BIGLOBE (****@***.biglobe.ne.jp, Japanese ISP) and Biglobe-compatible emails (tmtv.ne.jp,inacatv.ne.jp,ttv.ne.jp).
• Add some webmail domains of qip.ru (RU::WebMail).
• Add 81 webmail domains of Shtrudel M@il (US::WebMail).
• MTA Module list on the WebUI.

Fixed Bugs

• Fixed csv format bug ( multiple header fields are displayed ) in Kanadzuchi/Log.pm .

Get the tarball of bounceHammer 2.7.5 release from Download page. If there is any patch for version 2.7.5, download patches and apply before running the progmam: configure, make.

To upgrade to bounceHammer 2.7.5 from the previous version or older, you overwrite the previous version like the following:

bounceHammer 2.7.4 has been released. To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.7.4 and the previous version.

Assorted improvements and code cleanup

• Support a bounced (blocked) email from @facebook.com and @groups.facebook.com.
• WebUI template and CSS tiny improvement.

Fixed Bugs

• Fixed an issue that the following warning message: ``Use of uninitialized value in pattern match (m//) at lib/Kanadzuchi/MTA/US/Google.pm line 194.''.
• Fixed an issue that could not parse an email which the last line does not end with LF.
• Fixed an issue that bin/mailboxparser cannot parse bounced emails in Maildir except the first email when bounced emails of the same pattern are continuous. Thanks to REALIT Co., Ltd.

Get the tarball of bounceHammer 2.7.4 release from Download page. If there is any patch for version 2.7.4, download patches and apply before running the progmam: configure, make.

To upgrade to bounceHammer 2.7.4 from the previous version or older, you overwrite the previous version like the following:

bounceHammer 2.7.3 has been released. This version is a bug fix version of the previous release (2.7.2) for a bounced email from au by KDDI (Japanese cellular phone provider). To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.7.3 and the previous version.

Fixed Bugs

• Fixed an issue that precision of analysis for a bounced email from au by KDDI (@ezweb.ne.jp: Japanese cellular phone provider) have dropped.

Get the tarball of bounceHammer 2.7.3 release from Download page. If there is any patch for version 2.7.3, download patches and apply before running the progmam: configure, make.

To upgrade to bounceHammer 2.7.3 from the previous version or older, you overwrite the previous version like the following:

bounceHammer require many Perl modules for working properly. Perl modules will be installed into /usr/lib/perl5 or /usr/local/lib/perl5 directory when you use cpan command or perl command for installing modules. But if you have no permission to write to these directories or you want to install perl modules which are required by bouncehammer into a certain directory, you may use cpanm command to install modules.

App::cpanminus

cpanm(App::cpanminus) is distributed at the following web site: http://search.cpan.org/dist/App-cpanminus/. If you have already installed cpanm command, skip to the next section ``Install perl modules''. In this article, we will install cpanm command into /usr/local/bin directory like the follwing operation:

Install perl modules

In this article, we will install perl modules (required by bounceHammer) into /usr/local/bouncehammer/lib directory. Perl script ./Modules.PL (you can find it at the top of the bouncehammer source directory) is usefull to install perl modules like the following operations:

When you run cpanm -l /usr/local/bouncehammer MODULE-NAME, required perl modules and dependent perl modules are installed into /usr/local/bouncehammer/lib/perl5 directory.

After installation

After installation of perl modules by cpanm command, Build bouncehammer like the following operations:

bounceHammer 2.7.2 has been released. To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.7.2 and the previous version.

Assorted Improvements and Code Cleanup

• WebUI template and CSS tiny improvement.
• Analytical accuracy of mailboxparser improvement for mailboxfull error from au by KDDI (Japanese cellular phone provider). Thanks to REALIT Co., Ltd.

Fixed Bugs

• Fixed an issue that libexec/mp-startup.pl does not work properry if bouncehammer was installed with --with-perl-extlib option.
• Fixed an issue that ``Illegal division by zero at mailboxparser line 462.''

Get the tarball of bounceHammer 2.7.2 release from Download page. If there is any patch for version 2.7.2, download patches and apply before running the progmam: configure, make.

To upgrade to bounceHammer 2.7.2 from the previous version or older, you overwrite the previous version like the following:

bounceHammer 2.7.1 has been released. To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.7.1 and the previous version.

Assorted Improvements and Code Cleanup

• New configure option --with-perl-extlib=dir, dir is the directory which contain required perl modules installed by cpanm -l.
• Support My Opera Mail's domain: @myopera.com
• Update syslog format of each command
• Update email domains of fastmail.fm, and Excite
• Update webmail domains of some countries in Europe and Southeast Asia.
• Support some smartphone domains of America and Indonesia.
• A bounced email which is rejected by AOL Phoenix Sender Filter will be classified into the reason 'filtered',and by Content Filter will be classified into the reason 'contenterr'.
• A bounced email which is rejected by @MAIL.RU's Filter will be classified into the reason 'filtered'.
• A bounced email which is rejected by @MAIL.RU with the message "We do not accept mail from dynamic IPs" will be classified into the reason 'notaccept'.

Fixed Bugs

• Fixed an issue that the following warning message is displayed: ``Use of uninitialized value in transliteration (tr///) at lib/Kanadzuchi/Address.pm line 147,148''.
• Fixed an issue that the following warning message is displayed: ``Use of uninitialized value in lc at lib/Kanadzuchi/MTA/US/Google.pm line 195''.
• Fixed an issue that when DBD::* driver module is missing, command line tools shows the following error message: ``Can't use string ("Failed to connect DB at /usr/loc"...) as a HASH ref ...''.
• Fixed an issue that --skip-norelaying option of bin/mailboxparser command does not work propery.

Get the tarball of bounceHammer 2.7.1 release from Download page. If there is any patch for version 2.7.1, download patches and apply before running the progmam: configure, make.

To upgrade to bounceHammer 2.7.1 from the previous version or older, you overwrite the previous version like the following:

bounceHammer can parse a bounced email from Gmail. But Gmail's bounced email format is difer from a bounced email which created by Sendmail, and Postfix, and qmail. In this article, we describe about 9 state values in bounced email from Gmail.

The format of Gmail's bounced email is difer from other open source MTAs. We found 9 state values from Gmail's bounced email while develop bounceHammer. In this article, these 9 state values are described. (See also lib/Kanadzuchi/MTA/US/Google.pm file if you have bouncehammer source code)

The following table show state value, SMTP command, bounce reasons detected by bounceHammer, Note about the error.

state 14 have 2 kind of messages

The state value is almost 14 or 18 in our sample bounced emails from Gmail.
But the state 14 have two bounce reasons: User Unknown and Mailbox Full. To find a correct bounce reason, you should read error messages too.

In the case of User Unknown

In the case of Mailbox Full

state 6

500 Remote server does not support TLS (state 6).

state 8

535 SMTP AUTH failed with the remote server. (state 8).

state 9

454 454 TLS missing certificate: error:0200100D:system library:fopen:Permission denied (#4.3.0) (state 9).

state 12

500 Remote server does not support SMTP Authenticated Relay (state 12).

state 13

550 550 5.7.1 <****@gmail.com>... Access denied (state 13).

state 14 (two kind of messages are observed)

550 550 5.1.1 <******@*********.**>... User Unknown (state 14).
550 550 5.2.2 <*****@****.**>... Mailbox Full (state 14).

state 15 (two kind of messages are observed )

550 550 5.7.1 SPF unauthorized mail is prohibited. (state 15).
554 554 Error: no valid recipients (state 15).

state 17 (two kind of messages are observed )

550 550 <****@***.**> No such user here (state 17). 550 550 #5.1.0 Address rejected ***@***.*** (state 17).

state 18

550 550 Unknown user *****@***.**.*** (state 18).

This article described 9 state values of Gmail's bounced email. But the following state values are not observed: 1,2,3,4,5,7,10,11,16,19 or larger.
We don't know that these values exist or not. If you found these values please send the bounced email to us

There are many bounce reasons which found by bounceHammer. When you scrub email addresses of your website users or mail magazine subscribers, You should decide whether to send an email again to a recipient which is already bounced at previous delivery.

In this article, we show our interpretation of each bounce reason for sending an email again. Note that the percentage of each bounce reason is our sensuous value.

It is almost impossible to send an email again to a recipient which is bounced by the following reasons. You should exclude the recipient email address from your list to delivery.

Unknown Host(hostunknown)

A domain part (the right hand side of @ sign) is misspelled, a domain name does not exist, or a domain name has been expired. If the user registration program working on your website checks an email address insufficiently, bounces by this reason will be occurred frequently.

Unknown User(userunknown)

A local part (the left hand side of @ sign) is misspelled or a recipient's mailbox does not exist. Several providers will reject SMTP connection from a host which is sending an email to unknown user continuously.

It is too difficult to send an email again to a recipient which is bounced by the following reasons.

Rejected by filter(filtered)

An email bounce by this reason is rejected by the header content of an email you sent. Mainly a recipient's mailbox exists but the recipient can not receive a email for any reason, or the recipient is rejecting an email, and so on.

Sender address rejected(rejected)

If you seen a bounced email which is returned by this reason, your envelope sender address (SMTP MAIL FROM:) is rejected by the remote host.
This reason mean the following things:

• A remote host considers you as a spammer
• A domain part of envelope sender address was not resolved with DNS

Mailbox has moved(hasmoved)

Recipient's mailbox has moved and recipient's email address has changed. But this bounce reason is not rarely seen. This reason means that recipient's email addres has changed but it is not forwarded automatically.

Security error(securityerr)

This bounce reason means that contents (include headers) of the email you sent violated remote host's security policy. For example, an email contains any virus, a source host's IP address is found DNS-Based blackhole list. But when a connection simply rejected, an email will bounce by this reason.

Alternative of "Unknown User" (userunknown)

Less frequency, some remote mail server returns an email with this reason as alternative of "User Unknown". When you seen a bounced email with this reason, you should investigate the maillog carefully.

The following bounce reasons mean that a destination mailbox could not be received an email temporarily. There are many reasons of temporary failure, a retransmission may be successful if you send an email some time after.

Mailbox is full(mailboxfull)

This bounce raason means that a destination mailbox is full or exceeds the limit of the server. If a bounced email often returns by this reason for long time, the destination mailbox has been neglected or no email is retrieved from the mailbox.

Delivery time expired(expired)

This bounce reason means that no response from a destination mail server or a domain part of a recipient email address did not resolve. A bounce message will returns like the following process:

• Send an email
• Cannot connect to the destination host
• Trying to connect or delivery several times for several hours
• Give up, your mta returns a bounce message to the sender

Problems on DNS or network

This bounce reason also means the followings:

• Your DNS server does not work properly
• Your gateway IP address is rejected or ignored by remote firewall

The following bounce reasons mean that an email bounce has been caused by a destination host (mail server), not a destination email address. In many cases, the destination host could not receive any email temporarily. You may retransmit an email after several hours.

Exceed limit (exceedlimit), Disk full (systemfull)

These bounce reasons mean that a destination mail host's disk is full. The destination host can not receive any email any more. You may send an email again after several hours (after the administrator resolved disk full problem).

Destination host does not accept an email(notaccept), Stopping temprarily (suspend)

These bounce reasons mean that a destination mail host does not accept an email temporarily due to high load or under the maintenance. You may retransmit an email after several hours.

Meanwhile, there is a destination host which returns bounce email by these reasons for a long time, the host may not receive an email forever.

Unknown mailer error (mailererror)

This bounce reason means that an error occurred for a mailer program bug on a destination host. The mailer program is a program which is called from MTA (such as aliases) like following:

register: "|/path/to/registration.pl"

If the mailer program exited on other than 0 or 75 (status code), a bounce message by this reason will return to a sender.

System error (systemerror)

This bounce reason means that some system error occurred like a configuration error on a destination host.

The following bounce reasons caused by an email content or email format.

Message too big (mesgtoobig)

When email size is too big (such as a big attachment file) for a destination host, a bounce message with this reason will return to a sender.

Mail content error (contenterr)

If a destination mail server could not parse or convert an email you sent, a bounce message with this reason will return to a sender.

bounceHammer 2.7.0 has been released. To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.7.0 and the previous version.

New Functionality

• UNIX syslog supported. Four commands: mailboxparser, databasectl, logger, tablectl (except --list mode), and WebUI send messages to syslog.
• A configuration name can be set in each etc/*.cf file.
• WebUI prints a configuration name on the top of each page.

Assorted Improvements and Code Cleanup

• Supprot vodafone/ blackberry's 35 domains: mobileemail.vodafone.* are classified into HostGroup/smartphone and Provider/vodafone .
• Support orange/ blackberry's 25 domains: blackberry.orange.* are classified into HostGroup/smartphone and Provider/orange .
• Ovi (ovi.com) has moved from Webmail to Smartphone (HostGroup).
• Support 2 domains of satellite phone: Globalstar and Iridium.
• Support cellular phone's domains or smartphone's domains of 87 countries in the world.

Fixed Bugs

• Minor bug fix for WebUI/Template.
• Fixed an issue that bin/databasectl fails with -Uv only.
• Fixed an issue that each command's progress bar fails in verbose mode when the standard-out is other command via pipe line.
• Fixed an issue that a lock file left when mailboxparser is called with -2(--two-way) option.

Get the tarball of bounceHammer 2.7.0 release from Download page. If there is any patch for version 2.7.0, download patches and apply before running the progmam: configure, make.

To upgrade to bounceHammer 2.7.0 from the previous version or older, you overwrite the previous version like the following:

And you should do the following works if you want to use the new features (UNIX syslog and Setting name) of version 2.7.0.

ToDos for New Functionarities

# Setting name
name: 'Default'

# UNIX syslog(3) configuration, Beginning with bounceHammer 2.7.0
# mailboxparser, logger, databasectl, and tablectl use this configuration
syslog:
  # By default, messages will not be sent syslog(3). If you want to
  # use syslog(3), set 1 to the value of enabled:.
  enabled: 1
  facility: 'local6'
		

Here is the new settings which are required by new functionalities of bounceHammer 2.7.0. So bounceHammer works properly unless these settings, if you don't want to use syslog and setting names, you don't need to configure these settings.
To use the new feature of this version, you should append these settings into INSTALLED-DIRECTORY/etc/bouncehammer.cf or merge etc/bouncehammer.cf-example with the current configuration file.

Setting Name(name:)

Beginning with Version 2.7.0, you can define a Setting Name in the configuration file. For example, you want to administer email bounces of two sites. When you want to keep parsed data of each site in a separate directory, to store parsed data of each site into a separate database, two configuration files (e.g. site-a.cf and site-b.cf) are requied.

syslog

Beginning with Version 2.7.0, Results of the following commands and WebUI(Browser based control panel) are written in syslog.

• mailboxparser
• logger
• tablectl
• databasectl

To write results of a command or operations on WebUI, please append above settings into configuration file: etc/bouncehammer.cf . If you configure enabled: 0 or the settings are omitted, bounceHammer does not use syslog. By default, a syslog facility is local6.

syslog.conf

The following setting is defined in INSTALLED-DIRECTORY/etc/syslog.conf-example file. You may configure syslog.conf on your system with referring etc/syslog.conf-example.

bouncehammer.jp server will be performed on Sunday, March 13th, 2011 between 02:00 and 03:00 JST. The server will stop for about an hour.Duruing the maintenance, all the pages on this site can not be viewed, ditribution files can not be downloaded. If you need to download distribution files, visit SourceForge.JP . Thank you for your patience.
Maintenance successfully completed (02:12 JST).

bounceHammer 2.6.4 has been released. To get the distribution files for this release, see Download page. RELEASE_NOTES[English] has a list of all changes between the version 2.6.4 and the previous version.

Assorted Improvements and Code Cleanup

• Support 4 AOL's Project Phoenix domains: 'games.com', 'love.com', 'wow.com', and 'ygm.com'. They will be classified into the hostgroup 'webmail'.

Fixed Bugs

• Fixed an issue that bin/mailboxparser command will exit successfully even if the command could not write to the temporary directory (e.g. /tmp) due to disk full (Thanks to CAREER DESIGN CENTER CO.,LTD.).
• Fixed an issue that working directory which is specified in etc/bouncehammer.cf is not used if the directory does not exist.
• Fixed an issue that Kanadzuchi::Address module cannot detect an email address from HTML formatted email ( Thanks to CAREER DESIGN CENTER CO.,LTD. ).

Get the tarball of bounceHammer 2.6.4 release from Download page. If there is any patch for version 2.6.4, download patches and apply before running the progmam: configure, make.

To upgrade to this version from the version 2.6.0 or later, you simply overwrite the previous version like the following steps: