<story><title>Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs</title><url>https://www.mailgun.com/blog/deliverability/gmail-and-yahoo-inbox-updates-2024/</url></story><parent_chain><item><author>TheCycoONE</author><text>DKIM, SPF, and DMARC are old hat and implemented by anyone serious for years. What&amp;#x27;s buried in this article is the required &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;datatracker.ietf.org&amp;#x2F;doc&amp;#x2F;html&amp;#x2F;rfc8058&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;datatracker.ietf.org&amp;#x2F;doc&amp;#x2F;html&amp;#x2F;rfc8058&lt;/a&gt; support for one-click unsubscribe posts. I don&amp;#x27;t see many messages in my inbox yet with that.</text></item></parent_chain><comment><author>pests</author><text>I&amp;#x27;ve seen a perverse dark pattern on one click unsubscribe. The page you land at has a button that lets you resubscribe! It looks non-obvious you&amp;#x27;ve already unsubscribed and it looks like the regular two-click flow needing to enter your email address to confirm. Very sneaky.</text></comment>
<story><title>Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs</title><url>https://www.mailgun.com/blog/deliverability/gmail-and-yahoo-inbox-updates-2024/</url></story><parent_chain><item><author>TheCycoONE</author><text>DKIM, SPF, and DMARC are old hat and implemented by anyone serious for years. What&amp;#x27;s buried in this article is the required &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;datatracker.ietf.org&amp;#x2F;doc&amp;#x2F;html&amp;#x2F;rfc8058&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;datatracker.ietf.org&amp;#x2F;doc&amp;#x2F;html&amp;#x2F;rfc8058&lt;/a&gt; support for one-click unsubscribe posts. I don&amp;#x27;t see many messages in my inbox yet with that.</text></item></parent_chain><comment><author>jasonjayr</author><text>I understand that the request happens in the background by the MUA at the user&amp;#x27;s express consent, and the unsubscribe is not allowed to send back any ui&amp;#x2F;html&amp;#x2F;whatever to present to the user, but the RFC is missing any information about how a response ought to be handled, HTTP Status code wise?    Retry if 400&amp;#x2F;500?  Give user any affirmative or negative response that it succeeded or failed?</text></comment>