Hi @Eileenmcnaughton, that makes senes to me, though I'm unaware if there are any important reasons to not change the disallow list.
@bsisolak - what's your opinion on removing "marketing@" from the email blocking local prefix list?

Is this a major blocker for something @Eileenmcnaughton ?

No real person should have that as their email address, I would leave it and opt the user out.

Hmm - we did get a significant donation from that not-real-person....

I just checked - here are a couple more donors with that start
https://civicrm.wikimedia.org/civicrm/contact/view?reset=1&cid=521945
https://civicrm.wikimedia.org/civicrm/contact/view?reset=1&cid=43560023

• in the second one it does look like emails have gone out to that person (so the block doesn't seem to 100% prevent them being emailed from Acoustic - link in Acoustic https://civicrm.wikimedia.org/civicrm/a/#/omnimail/remote-contact?cid=43560023

For cid=43560023, their email address prefix has a "5" next to "marketing" so it's not triggering the block. I'm pretty sure all "marketing@" are disallowed from Acoustic.

I'm not sure if I'm the right person to make the call on this, so looping in @TSkaff here too since I'm going on vacation soon.

We may need to do more discovery to figure out how this change will influence other teams. So far this is what I'm understanding:

Pros:

• We have some real donors that have "marketing" in their prefix so they probably shouldn't be exempt from emails
• Allowing "marketing@" in Acoustic will unblock a project Eileen is working on

Cons:

• We don't know the scale of how many real donors that have "marketing" in their prefix
• Allowing "marketing@" in Acoustic for a few real donors will also allow all who are categorized under the "marketing@" prefix, which could result in poor sender reputation and a surge of complaint tickets for Donor Relations.

@KHaggard - there are 218 contacts in this category - they all have donations - which I think reflects the way contacts enter our database

https://civicrm.wikimedia.org/civicrm/admin/search#/create/Contact?params=%7B%22version%22:4,%22select%22:%5B%22id%22,%22display_name%22,%22Contact_Email_contact_id_01.email%22,%22wmf_donor.lifetime_including_endowment%22%5D,%22orderBy%22:%7B%7D,%22where%22:%5B%5B%22Contact_Email_contact_id_01.email%22,%22LIKE%22,%22marketing@%25%22%5D%5D,%22groupBy%22:%5B%5D,%22join%22:%5B%5B%22Email%20AS%20Contact_Email_contact_id_01%22,%22INNER%22,%5B%22id%22,%22%3D%22,%22Contact_Email_contact_id_01.contact_id%22%5D,%5B%22Contact_Email_contact_id_01.is_primary%22,%22%3D%22,true%5D%5D%5D,%22having%22:%5B%5D%7D

Ok, so it sounds like there's minimal contacts that apply to this. Is it just marketing@ that you're requesting to remove, or are there more prefixes to consider?

It's a pretty straightforward process to add/remove prefixes in the Acoustic UI. I think anyone with an Acoustic Admin account can make changes. https://cloud.goacoustic.com/campaign-automation/Settings/Administration/Email_blocking

Unfortunately, I'm not the one who can best advise on whether we should or shouldn't change the list. @bsisolak is our go-to for email best practices, risks, etc. Maybe a future meeting to discuss more would help?

@KHaggard - I just happened to hit one of the handful of contacts with marketing as a prefix - he is in the major gifts list they want to upload to Acoustic in a group to email - I don't know of any other prefixes but I'll try again to upload the list if I can get past that contact

@Eileenmcnaughton Not having an email in the upload should not have stopped the Contact List from being built. What API calls are you making and with what parameters?

As for which prefixes to allow, it's a long list with a lot that are clear no one wants (spam@, spamhole@, root@) but I could see you wanting to include some of the others. Someone will just have to go through the list and make a determination on each prefix. There are 37 prefixes.

While you are at it, take a look at the Domains and System Domains that are suppressed as well. I would not recommend removing any of those as those are mostly there for legal compliance reasons. You could at least mark those in Civi as undeliverable in some way.

https://cloud.goacoustic.com/campaign-automation/Settings/Administration/Email_blocking

I finished uploading @RLewis's group of 1500 contacts and 4 were rejected by Acoustic because the local parts of their emails were (respectively) 'marketing', 'support', 'service' and 'admin'

These are legitimate donors who have made donations > $1000

I believe we have been trying to upload these these contacts to Acoustic and to email them from there - but the nightly csv exports seem to quietly skip them. However, the AddRecipient api which is being used in this job returns an error which is why they have come up and we are now aware they are not in Acoustic - I think @RLewis & @DStrine probably need to think about this.