Page 1 of 1

Some bounce clarifications...

Posted: Fri Jun 22, 2012 4:03 pm
by lesstra
Hi,

I read a lot of posts here in the "Bounce management" section, but some things are still unclear to me...
I'm using OpenEMM 2011 on Debian squeeze 6.
I didn't configure any additional bounce management (running it "out of the box").
  • How do the softbounces / hardbounces work in this case? Is there any number of softbounce retries before the recipient's status is set to "Bounced" (hard bounce)?
  • I found this post, mentioning softbounce.py script http://forum.openemm.org/bounce-managem ... c1890.html, so I'm wondering is this script running in the default OpenEMM bounce setup (for "synchronous bounces" as stated in the install manual)...
  • I've got a couple of hundreds of new bounced recipients during the last mailing, which weren't bounced during previous mailings. This was strange to me. Should I try and reset the user status directly in the database for these recipients?
  • Finally, is there any particular reason why there is no option for resetting the status for the group of recipients from the webapp?
Thanks in advance.
Less

Re: Some bounce clarifications...

Posted: Sat Jun 23, 2012 6:31 pm
by maschoff
First, see section "9.3 Softbounce Scoring" in the OpenEMM Install Guide.

New bounces can have different reasons: Either it is a real bounce (address no longer valid, mailbox full or receiving mailserver unavailable), or a bounce created by greylisting or a spam filter creates bounces to block you.

I do not understand would you mean by "resetting the status for the group of recipients".

Re: Some bounce clarifications...

Posted: Tue Jun 26, 2012 9:34 am
by lesstra
Thanks maschoff.
By option for "resetting the status for the group of recipients" I meant an option for changing back the status from "Bounced" (2) to "Active" (1), for all bounced recipients, not just reattaching one recipient at a time for particular mailing lists.
Although, I know it's possible to do that directly with update of user_status in the customer_1_binding_tbl.