Klaviyo DKIM signs the List-Unsubscribe header for several reasons, broadly categorized as compliance, security, and deliverability. Compliance involves meeting requirements set by RFC8058 (when implemented), "Yahoogle" (Yahoo & Google), and other email standards. Security is enhanced by preventing malicious actors from modifying the header, protecting against DKIM replay attacks, and generally maintaining the integrity of the unsubscribe process. Deliverability is improved by building trust with mailbox providers, confirming sender identity, reducing spam complaints, improving inbox placement, and complying with anti-spam regulations. Overall, DKIM signing the List-Unsubscribe header signifies a commitment to a secure and trustworthy email experience.
7 marketer opinions
Klaviyo DKIM signs the List-Unsubscribe header primarily for two key reasons: compliance with RFC8058 (when implemented) and ensuring the integrity of the unsubscribe process. DKIM signing protects the List-Unsubscribe header from tampering or modification by malicious actors, preventing redirection of unsubscribe requests. This practice is considered a best practice that builds trust with recipients and mailbox providers, confirms sender identity, improves email deliverability, and helps maintain a secure and reliable unsubscribe process, ultimately reducing the risk of spam complaints and improving inbox placement.
Marketer view
Email marketer from GlockApps explains that DKIM signing the List-Unsubscribe header helps improve inbox placement by demonstrating to mailbox providers that the sender is committed to providing a safe and trustworthy email experience. This can lead to higher engagement rates and better overall email performance.
13 Feb 2024 - GlockApps
Marketer view
Email marketer from Litmus explains that DKIM authentication, including signing of the List-Unsubscribe header, improves email deliverability rates by confirming the sender's identity and assuring mailbox providers that the email is legitimate. This reduces the likelihood of emails landing in the spam folder.
24 Jun 2021 - Litmus
3 expert opinions
Klaviyo DKIM signs the List-Unsubscribe header due to a combination of factors: It is a requirement driven by newer initiatives like the "Yahoogle" requirements, and it aligns with RFC specifications and industry best practices. Furthermore, DKIM signing protects against potential security threats, such as DKIM replay attacks, where malicious actors could manipulate the header.
Expert view
Expert from Spam Resource explains that the recent webinar covers everything about list-unsub, including RFCs and DKIM header requirements. This addresses the 'why' behind DKIM signing the List-Unsubscribe header – it's often a requirement from specifications and best practices.
5 Jul 2021 - Spam Resource
Expert view
Expert from Email Geeks shares that without DKIM signing the List-Unsub header, someone could modify the header to trick people into sending a sign of life via DKIM replay.
16 May 2022 - Email Geeks
3 technical articles
Klaviyo, like other email senders, DKIM signs the List-Unsubscribe header to comply with RFC 8058 (when implemented) and to enhance email security and deliverability. DKIM signing prevents malicious actors from modifying or spoofing the header. This strengthens the overall email authentication framework, building trust with mailbox providers (like Gmail and Microsoft) and reducing the risk of emails being flagged as spam, ultimately leading to improved engagement.
Technical article
Documentation from Google explains that robust authentication, including DKIM, is crucial for ensuring deliverability to Gmail users. Signing all relevant headers, including List-Unsubscribe, enhances trust and reduces the risk of emails being marked as spam.
9 Nov 2021 - Google
Technical article
Documentation from RFC Editor specifies that if the List-Unsubscribe header is implemented according to RFC 8058, it SHOULD be signed using DKIM to prevent modification or spoofing by malicious actors.
7 Jun 2024 - RFC Editor
Can DKIM be set up on a subdomain, and which domain should be used for signing?
Does the DKIM domain need to align with the List-Unsubscribe domain?
How can I verify if my company's emails have List-Unsubscribe headers correctly configured?
How do I find the DKIM selector for my domain in Dmarcian or Hubspot?
How to troubleshoot DKIM failures and which tools to use?
Should I include List-Unsubscribe headers in transactional emails and what are the DKIM best practices?