Taavi Eomäe
Taavi Eomäe
@vstakhov > Apparently rfc2047 allows to encode any header, including From, To and even Received. No. It's only allowed for the 'comment' or 'phrase' part of those headers, not the...
The end result is that letters to recipients with UTF-8 local parts will use UTF-8 in headers that can't be encoded RFC-compliant and that seems to be expected behavior. I...
@vstakhov I've censored the sender address to avoid bots scraping it, let me know if an uncensored version is needed. ``` Return-Path: Authentication-Results: zonemx.eu; spf=pass smtp.mailfrom=gmail.com; spf=pass (zonemx.eu: domain of...
I've encountered this with S/MIME (`smime.p7s`) generated by Outlook (Classic). The .p7s contains "DigiCert Assured ID Root G2", "DigiCert Assured G2 SMIME RSA4096 SHA384 2024 CA1" and one personal certificate...
Looking into this more it seems like Outlook S/MIME signing outputs a PKCS#7 structure with indefinite length `EncapsulatedContentInfo` even if no `eContent` is used in the `SEQUENCE`. The [CMS RFC](https://datatracker.ietf.org/doc/html/rfc5652)...
@mdecimus Even without an IETF standard published, it's rather massively deployed in practice. Though currently only Apple Mail supports any custom SMTP server supporting BIMI, if the current draft with...
@mdecimus I'm sure there are opponents to BIMI, the BIMI IETF mailing list exists basically exists to address these concerns. It would be apt to take a hard look at...
@mdecimus While it is indeed not necessary, it's a strong incentive. The bigger a company the more reluctant they are to make such changes. While a lot of vendors are...