Nice catch. Actually that’s how it was in the message ( Content-Type: Type: text/plain; charset=“utf-8” ). After looking at it again, the unreadable messages do have a base64 encoding, should this be an issue?
> On Sep 13, 2022, at 08:58, Tassilo Philipp <tphil...@potion-studios.com> > wrote: > > not sure if related, but I noticed your line says "text:plain" instead of > "text/plain" (which should be used according to rfc2045) > > > On Mon, Sep 12, 2022 at 10:20:38PM -0700, Ethan Ongstad wrote: >> The messages I receive that have the line ‘ Content-Type: text:plain; >> charset="utf-8” ‘ are not readable, but it is human readable if the "utf-8" >> bit is capitalized or if there are no quotation marks. Is this a opensmtpd >> bug? >> >> section 2 of RFC 2047 makes it sound like capitalization should not be >> relevant. https://www.rfc-editor.org/rfc/rfc2047#section-2 >> <https://www.rfc-editor.org/rfc/rfc2047#section-2> >
