#3886: provide the Content-Type when piping an attachment
--------------------------+----------------------
Reporter: vinc17 | Owner: mutt-dev
Type: enhancement | Status: new
Priority: major | Milestone:
Component: mutt | Version: 1.7.0
Resolution: | Keywords:
--------------------------+----------------------
Comment (by vinc17):
Replying to [comment:1 kevin8t8]:
> This is complicated by $attach_split and $pipe_split.
>
> If #3773 can be fixed, would that be sufficient?
With #3773 fixed, the command can now get the charset with {{{locale
charmap}}}. But getting the Content-Type could still be useful. If
multiple attachments are concatenated, I don't think that Mutt should
provide any Content-Type information, as this doesn't always make sense.
To give an example, the problem I had is when piping a HTML attachment to
my browser (Firefox): it didn't recognize this particular attachment as
HTML; I don't know exactly why, but as Content-Type sniffing is just a
heuristic, the browser can be wrong (and if the browser can be wrong, I
suppose that I could also be wrong if I tried to do this myself). And I
sometimes pipe other attachment types than HTML, so that forcing HTML on
my side would not be a solution.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3886#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
