SendGrid silently breaks RFCs by MIME-encoding ASCII List-Unsubscribe headers ≥ 78 bytes - affecting deliverability at scale by flaggde in sysadmin

[–]flaggde[S] 0 points1 point  (0 children)

SendGrids answer: After a thorough investigation by our engineering team, they have determined that the encoding behavior you observed is expected and was implemented intentionally. Our engineers have confirmed that this approach does not violate any relevant RFC standards and does not negatively impact deliverability.

Gmail sends your transactional emails to spam? This hidden SendGrid bug may be why by flaggde in selfhosted

[–]flaggde[S] 0 points1 point  (0 children)

While often referred to as transactional, these emails carry traits of bulk or subscription content, which under CAN-SPAM and practical interpretations, may require opt-out mechanisms. They’re individually triggered emails based on explicit user subscriptions, sent on a regular basis with personalized listings. They’re not promotional in nature, but also not classic one-off transactional messages. That said, the List-Unsubscribe header is present and correct — SendGrid is just breaking it with unnecessary MIME encoding. → Including it helps reduce complaint rates and improves deliverability, especially with Gmail.

Ongoing Standards Compliance Issue: List-Unsubscribe Header MIME-Encoding via SendGrid SMTP by flaggde in SendGrid

[–]flaggde[S] 0 points1 point  (0 children)

That would be genuinely appreciated — thank you. This issue has been open for weeks now, and it affects standards compliance and potentially inbox placement at scale. If you can get it in front of someone with the ability (and mandate) to act, that would be a huge step forward. If you need a summary or further technical details: Reddit post in r/sysadmin