Author Topic: CiviMail - few suggestions on processing bounces (Read 948 times)

goran · October 25, 2010, 03:57:47 am

1. Looking for more information on bouces[/b]
The bounce messages are short, if we include first x lines from them in

civicrm_mailing_event_bounce it might be useful when going through the mailing reports. Especially for cases where the bounce could not be parsed.

Use case: While going over the bounce lists I can give access to the CiviMail/Processed to our end users, but these are not necessarily in the same order and finding the details about bounce is awkward.

2. Verified e-mail addresses
As there is an on-hold status for an e-mail, it might be interesting to have verified e-mail status (e-mails that had been opened, replied on or clicked-through) as this might be a way to distinguish between 'successful delivery' report (which is definitively not verified) and actual verified addresses.

Use case: We sometimes send very important messages using CiviMail and troubleshooting delivery from one end point to another is important for us. Having a central place where we can quickly establish if the intended recipient was ever verified could be useful and reduce the need for ad-hoc SQL queries.

xavier · October 25, 2010, 09:37:02 am

Quote from: goran on October 25, 2010, 03:57:47 am

1. Looking for more information on bouces[/b]
The bounce messages are short, if we include first x lines from them in
Code: [Select]
civicrm_mailing_event_bounce it might be useful when going through the mailing reports. Especially for cases where the bounce could not be parsed.

Use case: While going over the bounce lists I can give access to the CiviMail/Processed to our end users, but these are not necessarily in the same order and finding the details about bounce is awkward.

I'd suggest to
1) create a new activity type "bounced"
2) create a bounced activity for each bounced email, and put it here

Almost all the code is there already, as it manages the incoming emails anyway

Added benefit: you see it in the contact in the list of activities and you can see when it stopped being send emails

Quote from: goran on October 25, 2010, 03:57:47 am

1. Looki
2. Verified e-mail addresses[/b]
As there is an on-hold status for an e-mail, it might be interesting to have verified e-mail status (e-mails that had been opened, replied on or clicked-through) as this might be a way to distinguish between 'successful delivery' report (which is definitively not verified) and actual verified addresses.

Use case: We sometimes send very important messages using CiviMail and troubleshooting delivery from one end point to another is important for us. Having a central place where we can quickly establish if the intended recipient was ever verified could be useful and reduce the need for ad-hoc SQL queries.

Is there a hook on the process bounces ?
Might want to create a tag "verified" and tag the contact.

X+

xavier · October 30, 2010, 06:02:15 am

Hi,

started to collect all the suggestions there:

http://wiki.civicrm.org/confluence/display/CRMDOC32/Improvments+on+CiviMail

The goal being to gather enough people willing to contribute to improve civicrm. Would you ?

X+

CiviCRM Community Forums (archive)

News:

Author Topic: CiviMail - few suggestions on processing bounces (Read 948 times)

goran

CiviMail - few suggestions on processing bounces

xavier

Re: CiviMail - few suggestions on processing bounces

xavier

Re: CiviMail - few suggestions on processing bounces