Skip to content

Conversation

gudmundurg74
Copy link

This allows the user to specify if the content of a node is already correctly encoded, skipping the encoding part in build().

@felixhammerl
Copy link
Contributor

Hi! Sorry for the late response, I've just gotten here while cleaning up the emailjs libraries.

What's the specific encoding capabilities you're missing?

@nifgraup
Copy link
Contributor

This feature is valuable when building a new mime tree from an existing one, to skip unnecessary decode & encode. (Think forwarding mail with an attachment).

@nifgraup nifgraup reopened this Jun 20, 2018
@gudmundurg74 gudmundurg74 force-pushed the isEncoded branch 2 times, most recently from 18707c8 to b1ccba2 Compare October 3, 2018 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants