Should I use blacklist or blocklist in email marketing?
Summary
What email marketers say13Marketer opinions
Marketer from Email Geeks says that the term “blocklist” had already been used plenty before now.
Email marketer from Mailjet Blog recommends switching to 'blocklist' to promote inclusivity and avoid potentially offensive language. This change reflects a broader movement towards more sensitive and respectful communication practices in the industry.
Marketer from Email Geeks shares that they’ve started using the terms block/deny list and allow/safe list.
Marketer from Email Geeks explains that even if deliverability teams start using a new terminology, not much changes until the mail filters or the lists themselves start changing the terminology.
Marketer from Email Geeks has been using the term blocklist.
Email marketer from Reddit explains that they have started replacing 'blacklist' with 'blocklist' in their email marketing materials due to increasing awareness of the negative connotations associated with the term 'blacklist'. They believe it's a small change that can make a big difference.
Email marketer from Stack Overflow explains that while both terms are understood, 'blocklist' is now the preferred terminology in many technical communities. They recommend using 'blocklist' for clarity and to align with current best practices.
Email marketer from Quora answers that they support the move to 'blocklist' because 'blacklist' can be unintentionally offensive. They also explain that this change helps create a more inclusive and sensitive environment within their marketing team.
Marketer from Email Geeks explains that stopping using "blacklist" is a good thing and probably only morons would laugh if you start using the proper term.
Email marketer from Litmus argues for the adoption of inclusive language like 'blocklist' in email marketing to foster inclusivity and avoid perpetuating harmful associations. This change is about respecting diverse audiences and creating a welcoming environment.
Marketer from Email Geeks explains that besides the "black" wording, "blacklist" can also be used to talk about a suppression list.
Email marketer from Sendinblue advocates for using inclusive terminology in all marketing communications. This includes replacing 'blacklist' with 'blocklist' as a more neutral and considerate alternative. The overall goal is to avoid language that could be seen as discriminatory.
Marketer from Email Geeks shares that they changed all their documentation from blacklist/whitelist to blocklist/allowlist and sees changes happening in the industry.
What the experts say3Expert opinions
Expert from Email Geeks shares that switching to using "blocklist" is sensible and there's a lot to be said for using "denylist", especially around security or enterprise IT people.
Expert from Email Geeks reveals that blacklist was a term invented by spammers to make what we were doing back at MAPS seem bad, but it became a term of art because people understood it better than blocklist.
Expert from Word to the Wise, Laura Atkins, explains the preference for 'blocklist' over 'blacklist' due to historical and ethical considerations, emphasizing inclusivity and avoiding harmful connotations.
What the documentation says4Technical articles
Documentation from OWASP advocates for using 'allow list' and 'block list' to promote inclusive language in cybersecurity and development. This change aims to avoid reinforcing negative stereotypes and promote a more equitable and welcoming environment.
Documentation from Google Developer Documentation Style Guide now recommends using 'blocklist' instead of 'blacklist'. They state the importance of inclusive language. This change is intended to reduce potential harm and promote a more welcoming environment for all users and developers.
Documentation from Red Hat indicates a shift towards inclusive language within their documentation, favoring 'blocklist' over 'blacklist'. This reflects a company-wide commitment to inclusive practices and responsible communication.
Documentation from Microsoft Style Guide confirms that they are actively updating terminology to be more inclusive, recommending the use of 'blocklist' instead of 'blacklist' in their documentation and products. This is part of a larger initiative to promote diversity and inclusion in technology.