Conversation

Notices

1. Embed this notice
   Jonathan Kamens (jik@federate.social)'s status on Wednesday, 22-Jan-2025 07:10:00 JST Jonathan Kamens

   in reply to

   Why am I asking this? Because I have a filter which runs on my incoming email which decodes RFC 2047 encoding that didn't need to be encoded, and I just discovered that it's breaking the formatting of some emails from LinkedIn because these emails are including LF characters in the encoded text. I'm going to fix the filter to work around the problem, but I am curious to hear what other people think.

   • Embed this notice
     Jonathan Kamens (jik@federate.social)'s status on Wednesday, 22-Jan-2025 07:10:01 JST Jonathan Kamens

     Here's an interesting question for you:
     Can RFC 2047 encoded text in the Subject line of an email contain encoded line break characters (i.e.,, ^J, a.k.a. 0x0A)?
     I don't think they should, because the point of RFC 2047 encoding is to encode non-ASCII characters which would otherwise be legal in the Subject line, not to encode characters which would otherwise be _illegal_, which includes line breaks.
     RFC 2047 itself doesn't give a definitive answer.
     What do you think?
     #email #MIME #SMTP #SysAdmin

     Blaise Pabón - controlpl4n3 repeated this.