You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
I've run into an issue with Apple Mail. Generally speaking, sending rich text emails works. However, if I send a simple text-only email without any formatting (aka no lists, no emphases, etc.) Apple Mail sends out a plaintext message instead of a rich text message resulting in garbled signatures when my recipients reply to these particular emails because their respective mail clients will inadvertently choose to respond with a plaintext instead of a rich text or HTML message.
Is there a hidden setting to force Apple Mail to always send out rich text emails regardless of content and simplicity thereof?
Check your settings:
"To use the same format for all of your messages, choose Mail > Preferences, click Composing, then choose a message format. If you want to use a different format for replies, select “Use the same message format as the original message.”
Thanks. That's the first place I checked, and I have it set to Rich Text already. Toggling the "Use the same message format as the original message" doesn't do anything in this case because it happens when I start composing a new message, not when I am replying to one.
The bottom line is this: when I compose a message without any formatting, just plain text, Apple Mail will send that email out as plaintext regardless of my preferences. Enabling "Rich Text" under Message format will allow me to add some formatting to my message, at which point it is then successfully sent out as rich text instead of plaintext message. I need Mail to always send out rich text regardless of contents.
Here's a web page from someone that knows a lot more than me. As you can see at the bottom, they're resigned to the fact that some formatting must be done in the message in Apple Mail and don't have a client-side fix.
This article explains why and how to avoid plain text messages when sending from iOS/Android and other mobile devices as well as from Apple devices such as Mac.
www.codetwo.comYou could use an email template that already has some formatting but that might be more trouble than just making some format change every time…although if you got into the habit of using a template you might be less likely to forget.
In this post (and accompanying video) I will show you an easy way to create reusable email templates in the latest version of Apple Mail. And I have to say, I like this way even better than my old way of using stationery. And, it will work with any version of Apple Mail. UPDATE Oct […]
ericleeclark.com
Or can do as they are doing in the CodeTwo link: create a signature in Mail that has minimal formatting (eg. one's name in bold) and include it in the email.
Tried to get this to work with an empty signature: no luck, needed something that would trigger HTML to be generated.
Or can do as they are doing in the CodeTwo link: create a signature in Mail that has minimal formatting (eg. one's name in bold) and include it in the email.
Once I saw the trouble that a formatted email signature can cause my recommendation to folks was to do just that.
. Apple Mail sends out a plaintext message instead of a rich text message resulting in garbled signatures when my recipients reply to these particular emails because their respective mail clients will inadvertently choose to respond with a plaintext instead of a rich text or HTML message.
How exactly is this a problem on YOUR side?I will try adding a formatted signature, thank you.
@posguy99 It's not a problem at first, but once they respond to my initial message the entire conversation thread remains plain text resulting in either completely garbled or, even worse, entirely missing HTML email signatures. That's fine for personal email conversations but can become an issue with business emails when trying to get in touch with a client or vendor by phone or means other than email. That's how I noticed this was an issue with Mail in the first place.
So, again, how is this an issue with *Mail* other than with the broken email client on the other end?
Because it is not an issue of a broken email client on the other end. The issue is that Mail isn't behaving as expected. If I tell it to always send messages as Rich Text I expect it to send them as Rich Text no matter what. Instead, sometimes it will send out emails as plain text. This is clearly an issue with Mail. If, for example, you tell your word processor of choice, be it Pages, LibreOffice or Word, to save all your documents as ODF files you expect it to do so no matter what and not to automatically revert to TXT files for documents that you haven't formatted yet without giving you proper notice, thereby preventing you from ever formatting those particular documents in the future.
FYI, the other end's behavior is as expected: when responding to a message use whatever format the original message came in. Mail will do that too ("Use the same message format as the original message", see screenshot in post #3) and destroy HTML signatures along the way.
Either way, using the trick referred to by @BrianBaughn and @NoBoMac worked. Using a formatted email signature will force Mail to always send out messages as Rich Text regardless of content.
Last edited: Sep 21, 2020Because it is not an issue of a broken email client on the other end. The issue is that Mail isn't behaving as expected. If I tell it to always send messages as Rich Text I expect it to send them as Rich Text no matter what.
Semantics. That box doesn't say "always". What you're actually complaining about is that it doesn't waste space including the other MIME type (since it always includes the plain-text), if it doesn't need to (ie there's no enhanced text present). Your "work-around" just means there's always enhanced text present.
The responding client is still the broken one if it does not include the right MIME type if it's including enhanced text.
Semantics. That box doesn't say "always". What you're actually complaining about is that it doesn't waste space including the other MIME type (since it always includes the plain-text), if it doesn't need to (ie there's no enhanced text present). Your "work-around" just means there's always enhanced text present.
The responding client is still the broken one if it does not include the right MIME type if it's including enhanced text.
If the OP goes through his original scenario and uses Mail to send the email to himself and reply…and the result is how he describes…what cllent is broken?
If the OP goes through his original scenario and uses Mail to send the email to himself and reply…and the result is how he describes…what cllent is broken?
I don't know if that was tested. I read through the entire thread again and I still don't know. But I would assume it does not break. If the OP sent a message that was entirely plain-text, then that would also mean it didn't have an enhanced signature. Mail.app would then receive it, and reply in the same format as the original message, and append again the non-enhanced signature, leading to a non-enhanced message.
Myself, I don't use Mail.app any longer on macOS, I'm not interested in Apple's weird ideas about how font sizes are supposed to work. But IMO, a client that does not send both a plain-text MIME-part and an enriched MIME-part when there is enriched text is broken. If there is no enriched text, then sure, only send a plain-text part. But if they're both there it should be up to the receiving client which to pay attention to.
I have been digging into this a whole day since I noticed that my clients receive a veeeery different looking emails than I thought I have been sending (Mac Mail Version 12.4).
I started out with one very useful tip from one guy on lifewire (https://www.lifewire.com/text-formatting-images-os-x-mail-1172889) to build my signature via HTML editor and then paste the text into Mac Signatures. After some more digging I went further and placed the created HTML (with my logo hosted on my webpage's server) right into the signature file (https://www.daretothink.co.uk/html-email-signature-in-apple-mail/)
After this fiddling around I have managed to get my signature to look the way I expect also on the other end, yay.
..And her comes the BUT I can't yeat solve:
When I compose an email with my new HTML signature, Mac Mail sends out my signature as expected (Calibri font), but the actual message is undefined text and lends at e.g. Gmail as Arial (I also see that in the raw source of the message in Mac Mail outbox).
IF I format all message (including the new html signature) as Calibri, whole message gets stripped to plain text and lends in whatever format the receiving mail client desires! (yes - Message format is Rich Text..)
What on earth is that.
How can I permanently apply certain format to all of my outgoing messages? (And probably code way as it seems that Mail>Format> Show Fonts is like piss in the wind..)
