Allow custom media subtypes #103
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Is it possible to do this without modifying the current version? |
|
Fixed my issue of hmtl+text emails with embedded images using CID. Thanks a lot ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi.
I've added Message constructor argument to override default MIME subtype name (mixed for multipart, plain for text).
multipart/mixed subtype caused problems in some email clients when I tried to inline images using CIDs. As this RFC states CIDs are supposed to work if message content type is multipart/related which tells the client to assume that some parts are related to others. Otherwise all parts are assumed to be self contained and CID link may not work.
Thanks!