Out of curiosity, I just checked what all the fuss is about. It turns out that someone reads mail with a non-RFC compliant client, and thus fails to read mime parts. Screw it, update your client. The other problem seemed to be with the list archive. It turns out that at least one archive has no problem at all (*). If other archives have mime problems, they can update themselves or just delete the mail. http://openbsd-archive.7691.n7.nabble.com/OT-protonmail-mail-body-td322547.html Sent from ProtonMail Mobile
On Thu, Jul 13, 2017 at 2:39 PM, Bryan Steele <bry...@gmail.com> wrote: > On Wed, Jul 12, 2017 at 10:09:11AM +0200, Alarig Le Lay wrote: > Hello, > > > It's just Base64 Content-Transfer-Encoding, and it's part of rfc2045. > > https://tools.ietf.org/html/rfc2045#section-6.8 > > So, the problem is on > marc.info side. Moreover, it's working on > mutt and on mail-archive: > > https://www.mail-archive.com/misc@openbsd.org/msg154853.html > > -- > alarig > The mailing lists have very simple rules, messages should be in English, > plain/text and generally not be MIME. Attachments should be avoided and sent > inline, unless accepted by the list. https://www.openbsd.org/mail.html > "ProtonMail" does not meet these requirements, by defalt. It's not just > marc.info archives, I suspect anyone using mail(1) is ignoring all of your > mails. -Bryan.
