Allow to set HTML Content-Transfer-Encoding based on UseMIMEfor 8bit - #8477
Closed
bojovyletoun wants to merge 1 commit into
Closed
Allow to set HTML Content-Transfer-Encoding based on UseMIMEfor 8bit#8477bojovyletoun wants to merge 1 commit into
bojovyletoun wants to merge 1 commit into
Conversation
… "Use MIME for 8bit" setting Allows to set Content-Transfer-Encoding for HTML part in similiar way as for Text part. (Based on Settings-Writing-Use MIME for 8bit) Previously it was hardcoded quoted-printable. If it is intentional (bugs in user agents...), please explain. According to my observations nearly everyone uses it and I think I should not be problematic, but I am not sure totally.
Member
|
A slightly modified version pushed. |
|
Hi, I've had to revert this in my installation because Mail_mime does not wrap lines when html_encoding is not quoted-printable or base64. My Exim server rejects emails where the lines are too long, they should not be over 998 octets. |
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
3 participants
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.
[Original name "Allow to set HTML Content-Transfer-Encoding by "Use MIME for 8bit config setting]
I modified Content-Transfer-Encoding for HTML parts. Previously it was hardcoded quoted-printable. Now it is determined in same manner as for Text part.
Is there any caveat in it? I have Settings-Composing-Advanced:Use MIME for 8bit obviously off so it is effectively 8bit.
Allows to set Content-Transfer-Encoding for HTML part in similiar way as for Text part. (Based on Settings-Writing-Use MIME for 8bit)
If it is intentional (bugs in user agents...), please explain. According to my observations nearly everyone uses it and I think I should not be problematic, but I am not sure totally.