Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple UNhold Bounce addresses not removed from suppressed addresses on SparkPost #96

Open
nc3man opened this issue Dec 25, 2020 · 0 comments

Comments

@nc3man
Copy link

nc3man commented Dec 25, 2020

The documentation seems to indicate that if you clear out a ON HOLD (Bounce) state for a contact, then it also removes the suppression record on the Sparkpost side. That works just fine for a single contact while viewing it. However, if you do a search and select multiple contacts and then execute action "Email unhold addresses" the ON HOLD (Bounce) state will clear on the Civi side but the emails remain suppressed on the Sparkpost side, which means on the next mailer the ON HOLD (Bounce) state returns because of SparkPost bounce code 25. I guess that's being somewhat smart to avoid massive suppression removals and damaging your email reputation. However, for us, we have a use case where over 3+ years we have ~140 contacts who have good emails and had evidently unintentionally unsubscribed on the Sparkpost side (sparkpost suppression type "List Unsubscribe" which is different than the CiviMail embedded UNsubscribe link in each mail). You can also not do a bulk removal of suppression recipients on the SparkPost side, only one at a time like in Civi, so you're either in for a couple hours of mouse clicks or asking SparkPost support to do it for you. It would be good if the SparkPost extension also would do the multiple emails suppression removal when multiple contacts are selected on a search via the SparkPost API https://developers.sparkpost.com/api/suppression-list/?no-cache=1#suppression-list-delete-delete-a-suppression . Is the current behavior intended?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant