You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
may attributes of header fields use quoted-printable encoding? How do different mail clients deal with this? This is addressed in RFC2231, but I'm not sure how widely this has been implemented.
I noted this in #55 with suggested DecodeWords fix.
The only issue would be if filename really contains "=?" but that is very unlikely right?
However, The example filename in this case should work fine if accessed with mail.Attachments ?
(since the .NET Attachment class do decoding of filename)
Http is a different beast, and it is not quite the same on mail.
Will revisit, but wanted to note this down while I have it in fresh memory.
Filename could be encoded as QP, same way as Subject. I think that it should be decoded in
BodypartFromMIME()
.Example:
The text was updated successfully, but these errors were encountered: