[MlMt] forwarding HTML emails

[Benny Kjær Nielsen]

On 18 Jan 2018, at 0:18, David Ledger wrote:

> On 17 Jan 2018, at 20:21, Tracy Valleau wrote:
>
>>
>> Why not "just" forward ALL that original source? The head, the 
>> tables, the divs, the body... That way  the recipient would see what 
>> I see.
>
> I’m not up to date with all the possibilities of modern emails, but 
> I would imagine that the problem will be the ‘Content-Type:’ 
> headers. They have to be in the right place for the text and HTML 
> parts to make sense. I believe a header still has to be before the 
> first blank line that isn’t part of the data for another header. If 
> you want to forward with added text it would require a bit of 
> juggling.
>
> I think redirecting an email sends a replica with HTML part intact.

This is correct. The only way do what Tracy asks for is to use 
“Message ▸ Redirect”.

And just to be clear. MailMate is able to do exactly what other email 
clients do *except* for editing the forwarded HTML.

* By default, MailMate embeds the HTML when needed just like other email 
clients. There are some preferences to control this (in the Composer 
preferences pane), but the defaults should be fine for most users.
* MailMate also offers “Message ▸ Forward as Attachment”. Some 
email clients, like MailMate, would still show such a message inline, 
but this is not true for all email clients. This type of forwarding has 
the advantage of being able to add a comment before the attachment while 
keeping all of the original message (and HTML) intact. Some services 
also require this type of forwarding, e.g., it might be required when 
sending an email to some spam-registering service (which might not 
handle redirected emails).

-- 
Benny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freron.com/pipermail/mailmate/attachments/20180118/d8acecad/attachment.html>