[MlMt] Inline CSS Error
info at techworkspro.com
Fri Aug 19 05:52:02 EDT 2022
As Bennie says, MM is trying to help the inlining process sort it out for non-HTML users receiving text-only messages. In the case of my signature, I edited it in a dedicated editor (BBEdit), before adding the signature to my MM app. Sanitized, as you said. Hence no issue, either way - original release, new or old Test Build - in MM.
In the case of adding HTML while composing, I can see how it would change for you depending on the version of MM Test Builds.
Henry Seiden, Founder
W: <https://www.techworkspro.com/> https://techworkspro.com
C/T: Call/Text <tel:95425342125>
E: <mailto:info at techworkspro.com> <mailto:info at techworkspro.com> <mailto:info at techworkspro.com>info at techworkspro.com
> On Aug 19, 2022, at 04:08, Benny Kjær Nielsen <mailinglist at freron.com> wrote:
> On 19 Aug 2022, at 1:42, Simon Kaplan wrote:
>> In the last few versions of MM I’ve been getting the following error as I compose:
>> Warning: CSS inlining unexpectedly failed
>> And I get a bright orange header bar as I’m composing that says
>> External command failed: sanitize-html
>> Any ideas, anyone?
> The change in MailMate causing this is that MailMate now inlines CSS in your HTML signature before embedding it in the HTML of the message itself. This is actually MailMate trying to help you because a signature should not contain a stylesheet. (I've yet to see an example where someone did this on purpose. It's usually the result of using an entire HTML document as a signature.)
> That said, there might still be a MailMate bug/issue since the inlining failed. You are welcome to send me your signature (off list) and I'll see if I can reproduce it. If I can then I'll look into possible workarounds or a more graceful way of failing.
> mailmate mailing list
> mailmate at lists.freron.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mailmate