Repository navigation
Conversation
This was referenced Apr 20, 2016
Collaborator
|
Squashed 7812a77 |
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
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.
So I tried to build the following email:
An alternative part (plain + HTML) followed by a .txt attachment.
The resulting email was structured this way:
Starting with the attachment looked like a bug to me, so I dug a bit. I found about
Mail::Body#sort_parts!and the default@part_sort_order, so I tried disabling the sorting altogether by passingMail::Body#set_sort_orderan empty array (seeFIXMEcomment above).It did not work, because
Mail::Message#ready_to_send!does a hard-codedparts.sort!with the default order, effectively makingMail::Body#set_sort_orderuseless.This patch contains the fix. The example above now produces the following structure: