#3169: mutt -H ignores Content-Type:
------------------------+----------------------
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: closed
Priority: minor | Milestone:
Component: mutt | Version: 1.5.18
Resolution: fixed | Keywords:
------------------------+----------------------
Changes (by kevin8t8):
* status: new => closed
* resolution: => fixed
Old description:
> Forwarding from http://bugs.debian.org/434235
>
> ---
>
> Hi,
>
> I prepared with a script a few mail templates containing attachments. I
> tried to send these using option -H of mutt.
>
> Nevertheless I noticed that mutt ignores
> Content-Type: multipart/mixed; boundary="1yeeQ81UyVL57Vl7"
> and displays all attachments as part of the mail body.
>
> Even using E to edit the message inclusing headers fails because it
> doesn't contain a Content-Type: I could change.
>
> I use the following workaround:
> I send the mail with all attachments as part of the body to
> me@localhost. Once I recieved the mail I'm able to edit the header
> including the wrong Content-Type:. I also have to recode the file from
> latin1 back to UTF-8 (by :set file-encoding=utf-8|:wq) since the encoding
> was destroyed during the first send (encoding base64 was used
> initially). Now I can bounce it to the wanted address.
>
> This works really well ...
>
> I attached a sample email template.
New description:
Forwarding from http://bugs.debian.org/434235
---
Hi,
I prepared with a script a few mail templates containing attachments. I
tried to send these using option -H of mutt.
Nevertheless I noticed that mutt ignores
Content-Type: multipart/mixed; boundary="1yeeQ81UyVL57Vl7"
and displays all attachments as part of the mail body.
Even using E to edit the message inclusing headers fails because it
doesn't contain a Content-Type: I could change.
I use the following workaround:
I send the mail with all attachments as part of the body to
me@localhost. Once I recieved the mail I'm able to edit the header
including the wrong Content-Type:. I also have to recode the file from
latin1 back to UTF-8 (by :set file-encoding=utf-8|:wq) since the encoding
was destroyed during the first send (encoding base64 was used
initially). Now I can bounce it to the wanted address.
This works really well ...
I attached a sample email template.
--
Comment:
Looks like I missed this ticket when committing changeset:a4d885bb36ab
That changeset added the "-E" flag, but also changed -H to be able to read
multipart emails, which should fix this bug.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3169#comment:2>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
