Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature: Expand email builder API to support forced content Content-Transfer-Encoding for attachments, like quoted-printable, base64, 7BIT and others #405

Closed
bbottema opened this issue Jul 15, 2022 · 1 comment
Closed

Feature: Expand email builder API to support forced content Content-Transfer-Encoding for attachments, like quoted-printable, base64, 7BIT and others #405

bbottema opened this issue Jul 15, 2022 · 1 comment
Labels
enhancement Priority-Low
Milestone
7.3.0

Comments

@bbottema
Copy link
Owner

#399 added support for Content-Transfer-Encoding on body content level (so plain text, HTML text and iCalender), but we can go further and enforce transfer encoding for attachments as well. This way we can make sure plain text is stored as base64 in the resulting EML for example.
@bbottema bbottema added this to the 7.3.0 milestone Jul 15, 2022
bbottema added a commit that referenced this issue Jul 15, 2022
@bbottema
#404, #405: Added support for Content-Transfer-Encoding and Content-D…
c8b32ed 
…escription for attachments
@bbottema bbottema changed the title Feature: Expand email builder API to support forced content encoding for attachments, like quoted-printable, base64, 7BIT and others Feature: Expand email builder API to support forced content Content-Transfer-Encoding for attachments, like quoted-printable, base64, 7BIT and others Jul 15, 2022
bbottema added a commit that referenced this issue Jul 15, 2022
@bbottema
#405: Another CLI fix for Content-Transfer-Encoding for attachments
01d444f
@bbottema
Copy link
Owner Author

Released in 7.3.0

bbottema added a commit that referenced this issue Jul 19, 2022
@bbottema
#404, #405: Added missing toString entry for Content-Transfer-Encodin…
4932bc1 
…g value
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Priority-Low
Projects
None yet
Milestone
7.3.0
Development

No branches or pull requests
1 participant
@bbottema