Dear Maintainer, when forwarding mails with neomutt it seems that they get altered: - When an email has html and text, the recipient gets only the text part - When an email has only html it happend that the recipient gets a text email including the html (terrible UX) - When using the `-F` flag in the hope that it will fix the above issues, the original email is attached as an eml file. This is a terrible UX in many email clients (e.g. k9/mobile thunderbird). I don't know exactly what neomutt is doing, but neomutt always got it right when forwarding emails. I recall this has something to do with mime support, but I am not sure about the details. Best regards Martin
Hi Martin, Features like this ought to be requested upstream rather than the debian package, and should be filed as bug reports there (than here). Have you done that? (When upstream implements this, it should just be a matter of updating the version on the Debian side.) Thanks, Nilesh
Hi Nilesh, thank you very much for your reply. I created an issue upstream now: https://todo.sr.ht/~rjarry/aerc/344 Best regards Martin
Re-reading this again - Do you mean aerc here? did you mean "what aerc is doing"? This is extremely confusing wording and you've forwarded the same to upstream too, so I suppose even upstream authors will be puzzled. Can you clarify what exactly is it that neomutt does and aerc /does not/ do?
Dear Nilesh, I was comparing the way aerc does it, to the way neomutt does it as the latter seems the correct way for me. Unfortunately I mixed it up one time and wrote neomutt instead of aerc. Exactly. No, here I actually meant neomutt as forwording in neomutt just works as I would expect it to work. Emails do not show html plaintext or show empty with an eml file attached. As I said, I am not sure about the details about how to properly send mail forwardings, therefore I might not use the right terminus. But I often stumbled about the mime term when searching for explanations why the forwarded mails work well, when forwarded by neomutt but not when forwarded by aerc. Unfortunately not. That's why I wrote the part in the issue. Best regards, Martin
Hi Martin, I see in https://todo.sr.ht/~rjarry/aerc/344 that you got a template which has got this working for you (with no code changes in the package). Consequently, I believe this bug report can be closed and thus I am doing so. If you think this is still not solved, feel free to re-open with an explanation. Thanks! Nilesh