Send bounces from powermta back to interspire

I have had a few requests from clients that use interspire with a rotating IP script and then switched over using Interspire with powerMTA.
They all ran into the same issue – Bounce notifications were not being sent back to the bounce address interspire used.

In order to send bounces back to Interspire that occur in powerMTA you have to add the following to your PMTA config:

<domain *>
deliver-local-dsn YES
</domain>

This will ensure that emails get returned to your Email address that you have specified in you Interspire under your bounce email address.

We now have to tell Interspire’s bounce processor to process emails with the subject “Delivery Report”.
The file we need to edit is: bounce_rules.php and can be found in your Interspire installation directory. /admin/resources/
If you do not add this to your interpsire bounce_rule.php interpsire will simply ignore that email and delete it after the bounce processing has run.
Round about line 68 you will find this line:

$GLOBALS['BOUNCE_RULES_SUBJECT'] = array(

Just below that we add:

'Delivery report',

Save the file.

Now go ahead and create a test list in interspire.
Add an email that you know will bounce.
Send a test campaign and see if the email gets marked as bounced after Interspires bounce has run.
In order to speed up the bounce run you can manually run the bounce process in interspire.
If the email does not get marked as bounced you can always debug the bounce process to see why it ignored the email. To debug, simply follow this guide on interspires website.

If Interspire is not marking the email as bounced and you have activated debug mode and you receive something like this:

Line 883; Date: Thu, 22 May 2013 10:45:25 +2
Line 884; Processing emailid: 20; listid: 1024
Line 471; the email headers werent returned properly. See if they have a utf-8 byte-order-mark in them.
Line 891; no proper email headers found. Returning ignore

Then add this to your powerMTA configuration:

<domain *>
     ignore-8bitmime true
</domain>