PowerMTA Support Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

PowerMTA 5.5r1 is out!!!!  Please contact support@port25.com for a license and download access.

Author Topic: Bounce Management  (Read 38891 times)

kstadwick

  • Guest
Bounce Management
« on: September 30, 2011, 02:17:52 PM »
1) We provide an email sending service. Our feeder application automatically makes all hard bounced emails INACTIVE so that the next time a client sends out a broadcast email it does not send.  However, the database is designed so that a client can update the email address and make it ACTIVE again.  Our issue is that in the past we had a client make ACTIVE the Hard Bounced addresses without changing the email addresses.  This was on a small scale and did not affect the email reputation.  When changing from INACTIVE to ACTIVE our clients have to do this manually one at a time.  However, we all have not so bright clients that will do this sort of thing.  Question is, do you believe we need to put in place a master hard bounce list that all emails will be scrubbed against before sending so that even if the client changes the hard bounced email to ACTIVE it will not send (or is that jsut going overboard)? 
Logged

CaLViN

  • Hero Member
  • *****
  • Karma: +43/-2
  • Posts: 1233
  • Hasan Kurtoglu
    • PowerMTA Administration Service
Re: Bounce Management
« Reply #1 on: September 30, 2011, 02:33:12 PM »
A few more bounces would not affect your overall reputation.However,filtering hard bounces is a must and keeping them in the block list for x days.
Logged

Professional PowerMTA Administrator - Deliverability Expert

Contact me for Consultancy needs!

kstadwick

  • Guest
Re: Bounce Management
« Reply #2 on: September 30, 2011, 02:45:09 PM »
Thanks for the reply.  All hard bounces are permanently filtered unless the client marks them ACTIVE again.  I don't think it is an issue, but we had master scrub list built into our old system before switching to port25.  Just wanted input on whether we should take the time to recreate it or if it is a non-issue.
Logged

daniel

  • Full Member
  • ***
  • Karma: +6/-9
  • Posts: 192
Re: Bounce Management
« Reply #3 on: September 30, 2011, 07:14:54 PM »
I would suggest more statuses than just ACTIVE and INACTIVE. If the status were to actually say Hard Bounced, and the reason why it is marked hard bounced, then your users may be less likely to change it to Active again. If you are running your response processing through PowerMTA you should be able to get a good specific reason about why something bounced, but you might want to add a more customer friendly reason to explain each type of bounces as well.
Logged