On 11 Jan 2015, at 13:45, Benny Kjær Nielsen wrote: > On 11 Jan 2015, at 13:38, Bram Heerink wrote: > >> On 11 Jan 2015, at 13:30, Benny Kjær Nielsen wrote: >> >>> Complex HTML emails are best handled using “Message ▸ Forward as >>> Attachment” or “Message ▸ Redirect”. Part of the reason is that MailMate >>> only has a plain text composer and part of the reason is that forwarding >>> HTML emails inline is a bit of a trial-and-error problem (even for HTML >>> capable email clients). I do have a plan to improve the behavior of >>> MailMate to allow embedding the original HTML of the replied/forwarded >>> message, but apparently I keep postponing this -- probably because I'm >>> afraid it's going to be an infinitely big “can of worms” :-) >> >> Unfortunately, Forward as Attachment has the same issue(s). > > Then it sounds like a different issue. I have a (vague) recollection of iOS > Mail not always being able to show forwarded emails (forwarded as > attachments). I don't think I ever found out why that failed. It does not > fail with Mail on OS X. Could this be the problem you are seeing? If not, > what is the receiving email client?
I doubt this: The e-mail in my `Sent Items` looks the same (Forward vs FaA). But I think I found what triggers it. If I disable Signing of the e-mail on time MailMate does not scramble up the message. Regards, Bram
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mailmate mailing list mailmate@lists.freron.com http://lists.freron.com/listinfo/mailmate
