I would like to relay the body of an existing email, which should be ready to use with its 'multipart/mixed;boundary="_something_";' container. So I created a draft file for the -H option with headers MIME-Version, Content-Type, Content-Disposition and the ready-to-use body. But for some reason there is a call to mutt_remove_multipart_mixed in mutt_prepare_template, and as a result there is data loss in the mail. (I think this is the reason why it does not work)
I wonder what the rationale for that is? The commit messages from 2019 mean nothing to me. Should there be a way for a user to prepare an email upfront and let mutt just add From/To/Date/Message-Id etc as needed to the mail and be done with it? I think things might become tricky if the mails are automatically signed and/or encrypted. But that would be the responsibility of the user to provide a suitable muttrc for sending from command line. Olaf
pgpHg1NgM1CoU.pgp
Description: Digitale Signatur von OpenPGP
