20,943,777 delivered and bounced emails
processed... and counting
What is InboxResponse.com?
InboxResponse.com (formerly BounceRemoval.com) is a powerful remote email marketing service toolset designed to help increase the return on your email marketing investment (ROI).

Services include tracking and logging of your successfully delivered email, removal of your undeliverable, or "bounced", email addresses from your mailing lists, and more. You can select from having InboxResponse.com downloading your email responses from your mail server or have it delivered directly to our servers.

InboxResponse.com requires no additional software to be installed on your home/office computer or your website hosting web server, no reconfiguration of your web server, no software updates or upgrades for you to install, can be used with most any mailing system, and best of all can be used remotely. Our service plugs into your existing mailing system.

How does it work?
How does this work?

When you send an email to your friend Bob, at his email address "bob@smith.com", the mail server which receives your email, on which Bob has an email account, can respond in one of three ways:

1) Successful Delivery (SUCCESS)

In order to receive "successfully delivered" email notifications from your MTA (mail transport agent), your MTA must be DSN (Delivery Status Notification) capable. Qmail (qmail.org) and Courier mail transport agents do not currently support DSN. Presently no option is available for Qmail or Courier users to receive "success" delivery notifications per this limitation in non-DSN capable mail transport agents.

2) Temporary Delivery Errors (DELAY)
3) Permanent Delivery Errors (FAILURE)

By default, the mail server that is receiving your email for your friend Bob will respond to both Temporary Delivery and Permanent Delivery Errors with an email to the sender (you), trying to explain the problem. If your friend Bob changed his email address, you may receive back a "bounced" email notification from Bob's old mail server. Below you will find an example of a permanent delivery error (also known as a "hard bounce") response from that mail server, sent back to you:

Example:

> Final-Recipient: rfc822; bob@smith.com
> Action: failed
> Status: 5.0.0
> Diagnostic-Code: X-Postfix; host
> inbound.server.domain.com[00.00.00.00] said: 550 RCPT
> TO:<bob@smith.com> User unknown (in reply to RCPT TO command)


This is an automated response, and when sending to one or two email addresses, this method is easy to manage manually.

Now imagine sending out a mailing to a large list of addresses, such as your customer mailing list of 5,000 email addresses. On average, 1 in every 10 emails are returned to the originating mail server. This means that at least 500+ bounced emails sent back to your inbox for you to sort through. "Soft" bounces, such as "Mailbox Full", can generate up to 5 email responses per email. That means you could receive up to 2,500 emails back for the 5,000 that you send.

When you use InboxResponse.com, all of these bounced emails get sent to our servers first. Our systems will automatically read through your incoming delivery status notificaiton emails, determine the disposition of the delivery attempt, then logs that information for you. All resulting information is then available for you in several different ways:

  1. Logged to your InboxResponse.com administration panel, with an easy "copy bounces" option available for your permanent delivery error emails.

  2. Email digest logs can be sent to you nightly, weekly, or monthly.

  3. InboxResponse.com can "post" the email addresses which receive permanent delivery error responses directly to your web server, if you are using a InboxResponse.com (also known as a BounceRemoval.com) supported email delivery program, such as Subscribe Me Professional, or using our "BounceBack Notification system". Supported email delivery programs can not only receive back the permanent delivery error addresses from InboxResponse.com, but also remove those addresses from the respective mailing lists, automatically.


But what if you want to know exactly which and how many of your mailings have reached their destination successfully and were accepted for delivery? Or if you would like to have a delivery confirmation to prove to your subscribers/customers that their email has been delivered? Mail servers do not, by default, send these kind of delivery response notifications. The mail server receiving your email must receive your email with a request to provide you with a successful delivery notification. Using the tools provided by InboxResponse.com, you will be able to make such a request within your mailings, and the hundred/thousands of responses you receive from these mail servers will be received and processed for you automatically, using your InboxResponse.com account.

Using our new detailed search tools, you will be able to look up your delivery status notifications by (but not limited to):

1) Delivery status
2) Date
3) Email address
4) Email domain
5) Server response
6) List number
7) Mailing/campaign ID.


Some of the things these tools can help you do/learn:

  1. Which hosts and/or individuals are blocking your mailings and are not accepting them, and why.

  2. Which email addresses have permanent delivery errors and should be removed from your mailing lists.

  3. Copy a list of email addresses with permanent delivery errors directly from your InboxResponse.com administration panel.

  4. Have all of your email addresses with permanent delivery errors "posted" back to a text file on your web server, so that you can manually or automatically remove those addresses from your mailing lists.

  5. Which email addresses have temporary delivery error, and why.

  6. Select the number of times within a particular time period that you wish to allow a temporary delivery error to occur to a specific email address before it is considered a permanent delivery error.

  7. Which of your emails have been delivered successfully.

  8. The time and date of deliveries/bounces.





Copyright ©2005 - 2016 Marketing Marvel, Inc.