# 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:** Product 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:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@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")

</div>

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: <https://example.com/unsubscribe/opaquepart>
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.

---

_[View the full topic](https://meta.discourse.org/t/bulk-email-sender-changes-requirements-at-major-email-providers/291818)._