Re: non-ascii email forwarding failures

[David Edmondson <dme@dme.org>]

On Tuesday, 2019-02-26 at 00:33:33 -05, Antoine Beaupré wrote:

> So I have no idea what's going on with mail forwards, but this is the
> kind of stuff that happens to me all the time and I can't describe
> correctly enough to file a bug.
>
> The gist of it is that, under some weird circumstances, notmuch-emacs
> (message-mode.el?) will screw up email forwards in a big time. I just
> forwarded (or did I just reply? not sure) that private email to the list
> to trigger that bug...
>
> I get that from time to time. I think the key is that it's an email I
> *sent* not *received*, which are somewhat different in their storage
> mechanism...
>
> The first symptom will be that, when sending, I'd get a prompt like
> this:
>
> Non-printable characters found.  Continue sending? (delete, replace, send, edit, ?): 

After looking at something related but not the same, I ended up with:

 ;; Do forward as MIME (the default), but don't show me the
 ;; MML.
 ;;
 ;; Showing the MML causes decoding and recoding problems, where the
 ;; headers of an message/rfc822 part end up being very long and
 ;; opensmtpd decides to wrap them via QP encoding. Unfortunately it
 ;; QP encodes the MIME separators as well. No idea who is actually in
 ;; the wrong here, but this fixes it so far.
 message-forward-as-mime t
 message-forward-show-mml nil

No idea if this will help with the problem you see.

dme.
-- 
I've still got sand in my shoes.