How to get traditional email clients to send email which appears normal in Gmail?
A considerate friend informed me recently that emails I send (with Neomutt; could be Mutt or Gnus or Pine) look funny on his device:
Apparently Google doesn't invest much effort in properly formatting standard RFC 2822 text emails.
Given that Gmail has more than one billion monthly active users, it seems futile to blame them for the problem.
Is there something that I can do on my end to make my emails appear "normal"? I'm happy to use format=flowed which has somewhat unofficial support in Emacs; but apparently Gmail does not support it.
Another solution that comes to mind would be to pass my plain-text emails through some kind of Markdown parser, turning them into HTML and attaching this as an alternative format to outgoing emails. I haven't really thought this through, but it seems like it could work nicely because Markdown already supports
quoted text
and double-quoted text
using the standard >, >> prefixes. Perhaps the result would look even better than the emails that "normal" people send using their graphical email clients.
Do people do this? Can they do this (e.g. in Mutt/Neomutt)? What is the "standard" solution?
email mutt text-formatting markdown gmail
asked Oct 29 at 8:51
Metamorphic
26117
add a comment |
A considerate friend informed me recently that emails I send (with Neomutt; could be Mutt or Gnus or Pine) look funny on his device:
Apparently Google doesn't invest much effort in properly formatting standard RFC 2822 text emails.
Given that Gmail has more than one billion monthly active users, it seems futile to blame them for the problem.
Is there something that I can do on my end to make my emails appear "normal"? I'm happy to use format=flowed which has somewhat unofficial support in Emacs; but apparently Gmail does not support it.
Another solution that comes to mind would be to pass my plain-text emails through some kind of Markdown parser, turning them into HTML and attaching this as an alternative format to outgoing emails. I haven't really thought this through, but it seems like it could work nicely because Markdown already supports
quoted text
and double-quoted text
using the standard >, >> prefixes. Perhaps the result would look even better than the emails that "normal" people send using their graphical email clients.
Do people do this? Can they do this (e.g. in Mutt/Neomutt)? What is the "standard" solution?
email mutt text-formatting markdown gmail
asked Oct 29 at 8:51
Metamorphic
26117
add a comment |
A considerate friend informed me recently that emails I send (with Neomutt; could be Mutt or Gnus or Pine) look funny on his device:
Apparently Google doesn't invest much effort in properly formatting standard RFC 2822 text emails.
Given that Gmail has more than one billion monthly active users, it seems futile to blame them for the problem.
Is there something that I can do on my end to make my emails appear "normal"? I'm happy to use format=flowed which has somewhat unofficial support in Emacs; but apparently Gmail does not support it.
Another solution that comes to mind would be to pass my plain-text emails through some kind of Markdown parser, turning them into HTML and attaching this as an alternative format to outgoing emails. I haven't really thought this through, but it seems like it could work nicely because Markdown already supports
quoted text
and double-quoted text
using the standard >, >> prefixes. Perhaps the result would look even better than the emails that "normal" people send using their graphical email clients.
Do people do this? Can they do this (e.g. in Mutt/Neomutt)? What is the "standard" solution?
email mutt text-formatting markdown gmail
asked Oct 29 at 8:51
Metamorphic
26117
A considerate friend informed me recently that emails I send (with Neomutt; could be Mutt or Gnus or Pine) look funny on his device:
Apparently Google doesn't invest much effort in properly formatting standard RFC 2822 text emails.
Given that Gmail has more than one billion monthly active users, it seems futile to blame them for the problem.
Is there something that I can do on my end to make my emails appear "normal"? I'm happy to use format=flowed which has somewhat unofficial support in Emacs; but apparently Gmail does not support it.
Another solution that comes to mind would be to pass my plain-text emails through some kind of Markdown parser, turning them into HTML and attaching this as an alternative format to outgoing emails. I haven't really thought this through, but it seems like it could work nicely because Markdown already supports
quoted text
and double-quoted text
using the standard >, >> prefixes. Perhaps the result would look even better than the emails that "normal" people send using their graphical email clients.
Do people do this? Can they do this (e.g. in Mutt/Neomutt)? What is the "standard" solution?
email mutt text-formatting markdown gmail
email mutt text-formatting markdown gmail
asked Oct 29 at 8:51
Metamorphic
26117
asked Oct 29 at 8:51
Metamorphic
26117
edited Dec 13 at 3:59
asked Oct 29 at 8:51
Metamorphic
26117
asked Oct 29 at 8:51
Metamorphic
26117
asked Oct 29 at 8:51
Metamorphic
26117
26117
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
check out 'plainMail2HTML' which uses python's docutils to convert 'markdown' to 'HTML'. So far I've found the results to be encouraging. Find out more at the github repository.
Bye bye
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f478377%2fhow-to-get-traditional-email-clients-to-send-email-which-appears-normal-in-gmail%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
check out 'plainMail2HTML' which uses python's docutils to convert 'markdown' to 'HTML'. So far I've found the results to be encouraging. Find out more at the github repository.
Bye bye
add a comment |
check out 'plainMail2HTML' which uses python's docutils to convert 'markdown' to 'HTML'. So far I've found the results to be encouraging. Find out more at the github repository.
Bye bye
add a comment |
check out 'plainMail2HTML' which uses python's docutils to convert 'markdown' to 'HTML'. So far I've found the results to be encouraging. Find out more at the github repository.
Bye bye
check out 'plainMail2HTML' which uses python's docutils to convert 'markdown' to 'HTML'. So far I've found the results to be encouraging. Find out more at the github repository.
Bye bye
answered yesterday
user328196
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f478377%2fhow-to-get-traditional-email-clients-to-send-email-which-appears-normal-in-gmail%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
