# Bulk Email Sender Changes / Requirements at Major Email Providers
**URL:** https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818
**Category:** Support
**Tags:** email
**Created:** [January 16, 2024, 6:06pm UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818 "2024-01-16T18:06:19Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Jose\_C\_Gomez](https://meta.discourse.org/u/Jose_C_Gomez)
#### Post date: [January 16, 2024, 6:06pm UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818/1 "2024-01-16T18:06:20Z")
I got a notification from AWS that Yahoo and Gmail are implementing a long list of new rules for “Bulk” email senders.
Discourse I think can fall into this category specially if you use Mailing List Mode (as we do)
Are there any plans (or maybe it already does this) to implement these new requirements in Discourse Emails?
The changes / requirements are outlined here
> **[An Overview of Bulk Sender Changes at Yahoo/Gmail | Amazon Web Services](https://aws.amazon.com/blogs/messaging-and-targeting/an-overview-of-bulk-sender-changes-at-yahoo-gmail/)**
>
> In a move to safeguard user inboxes, Gmail and Yahoo Mail announced a new set of requirements for senders effective from February 2024. Let’s delve into the specifics and what Amazon Simple Email Service (Amazon SES) customers need to do to comply...
Some of them are external like DKIM and SPF but there are some changes required also the body of the email
> Bulk senders are expected to include a mechanism to unsubscribe by adding an easy to find link within the message. The February 2024 mailbox provider rules will require senders to additionally add one-click unsubscribe headers as defined by [RFC 2369](https://datatracker.ietf.org/doc/html/rfc2369) and [RFC 8058](https://datatracker.ietf.org/doc/html/rfc8058). These headers make it easier for recipients to unsubscribe, which reduces the rate at which recipients will complain by marking messages as spam.
>
> There are many factors that could result in your messages being classified as bulk by any mailbox provider. Volume over 5000 per day is one factor, but the primary factor that mailbox providers use is in whether the recipient actually wants to receive the mail.
Thanks!
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [January 16, 2024, 6:32pm UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818/2 "2024-01-16T18:32:58Z")
> [@Jose\_C\_Gomez](#):
>
> there are some changes required also the body of the email
Discourse already generates unsubscribe links in the `List-Unsubscribe` header and in the body of the message. Have you reviewed these and found them insufficient?
---
### Author:  [@Jose\_C\_Gomez](https://meta.discourse.org/u/Jose_C_Gomez)
#### Post date: [January 16, 2024, 6:52pm UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818/3 "2024-01-16T18:52:02Z")
No I just wasn’t sure if these were the same as the RFC Requirements. Was trying to confirm if it already did it as described.
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [December 18, 2024, 12:35am UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818/4 "2024-12-18T00:35:05Z")
This came to my attention again recently, and I actually had the bandwidth to delve into the details.
We’ve had a `List-Unsubscribe` header for ages, but there’s a strong push for having an actual one-click unsubscribe _without a further confirmation step from the sender_.
This is accomplished using a new header [defined in RFC8058](https://datatracker.ietf.org/doc/html/rfc8058)
```plaintext
List-Unsubscribe:
List-Unsubscribe-Post: List-Unsubscribe=One-Click
```
Upon explicit user verification, activating this triggers a POST request from the mail client with content similar to:
```plaintext
POST /unsubscribe/opaquepart HTTP/1.1
Host: example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: 26
List-Unsubscribe=One-Click
```
We might need to add support for this.
---
### Author:  [@Jose\_C\_Gomez](https://meta.discourse.org/u/Jose_C_Gomez)
#### Post date: [December 18, 2024, 12:55am UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818/6 "2024-12-18T00:55:06Z")
I had an issue with something similar in a different mailing list the issue with single click unsubscribe is that a lot of mail clients and spam / virus filters will click / activate links to “investigate” them and it ends up unsubscribing someone so you definitely need a confirmation of some sort not just a link activation
We had a bunch of people specially those in enterprise / outlook that got auto unsubscribed
But maybe if it’s done via this header it is okay
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [December 18, 2024, 1:17am UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818/7 "2024-12-18T01:17:57Z")
This concern is specifically addressed by this RFC.
A GET request must not trigger the unsubscribe for exactly this reason, only a POST which has to be explicitly confirmed by the user.
---
### Author:  [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [January 7, 2025, 1:22pm UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818/10 "2025-01-07T13:22:32Z")
Hey @Jose_C_Gomez — I’ve got good news! We’ve updated our emails to support one-click / easy unsubscribes:
> [@Jose\_C\_Gomez](#):
>
> I had an issue with something similar in a different mailing list the issue with single click unsubscribe is that a lot of mail clients and spam / virus filters will click / activate links to “investigate” them and it ends up unsubscribing someone so you definitely need a confirmation of some sort not just a link activation
When I tested this in Gmail, there is a secondary confirmation but it happens from the mail client — so I believe this still meets the “easy unsubscribe” requirements without risking unintentional unsubscribes from mail client investigations:
---
### Author:  [@Jose\_C\_Gomez](https://meta.discourse.org/u/Jose_C_Gomez)
#### Post date: [January 7, 2025, 1:34pm UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818/11 "2025-01-07T13:34:47Z")
Amazing, thanks!!
---
### Author:  [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [January 9, 2025, 1:22pm UTC](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818/12 "2025-01-09T13:22:18Z")
This topic was automatically closed after 2 days. New replies are no longer allowed.