Skip to content

Add support for RFC 2231: "MIME Parameter Value and Encoded Word Extensions" #628

@rlebeau

Description

@rlebeau

When an email uses RFC 2231, eg:

Content-Transfer-Encoding: base64
Content-Type: application/octet-stream;
 name*0*=utf-8''A10090110721%2Epdf
Content-Disposition: attachment;
 filename*0*=utf-8''A10090110721%2Epdf

this useless encoding is not supported and the attachment name is empty.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Element: MIMEIssues related to MIME handlingStatus: ReportedIssue has been reported for reviewType: EnhancementIssue is proposing a new feature/enhancement

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions