Thanks a lot Steffen, I'll check with your examples.

Missatge de Steffen Nurpmeso <[email protected]> del dia dt., 8 de gen.
2019 a les 19:42:

> Hello Joan.
>
> Joan wrote in <CAP4s+CGK3KsAM0H7MyoxCEP_m7=NVbcRYy=vAdjuDrzGqivW-g@mail.\
> gmail.com>:
>  |Hello, I've been using s-nail for some time as as a replacement for the
>  |mailx tool, now I wanted to use the flag -M so I can change the mime type
>  |of the email I'm sending.
>  |The reason is that I'm dealing with a software that can only read the
>  |multipart emails.
>  |I tried several things, also looking into the documentation but I haven't
>  |been able to send any email with this option:
>  |
>  |For any of the options I test I get the same error.
>  |echo "BODY"  | s-nail -M text/watch-html -s "Subject" [email protected]
>  |> s-nail: Could not find `mimetype' for -M argument: text/watch-html
>  |
>  |What would be a proper way to call it?
>
> This MUA warns that it does not know about the mimetype you have
> specified.  You need to specify it with the `mimetypes' command:
>
>   $ </dev/null mail -:/ -stest -M text/watch-html \
>     -X 'mimetype text/watch-html anything' \
>     -Sexpandaddr -
>   From steffen Tue Jan  8 19:26:49 2019
>   Date: Tue, 08 Jan 2019 19:26:49 +0100
>   Subject: t
>   User-Agent: mail v14.9.11
>   MIME-Version: 1.0
>   Content-Type: text/watch-html; charset=us-ascii
>
> We read, dependent upon the variable *mimetypes-load-control*
> (mind you, i use `command', *variable* and $ENVIRONMENT notation),
> several so-called "The mime.types files" (the name of the manual
> section) in order to learn about MIME types.  We also (by default)
> have a builtin set of such.  More types can be created with the
> `mimetype' command, as above.
>
> That is, yes, we put this burden on you, but it is also to protect
> you a bit.  If you would use -m in the same example, we would try
> to classify your "watch-html" file, and could not.  You would also
> need to give us a hint what it is.  MIME types have an official
> registry (IANA), and i would like to prevent users from sending
> out data which is not easily understood by receiving parties
> because of typos and the like.  If you have the special
> requirement of using an otherwise unknown (to the world) MIME
> type, it think it is for the better to keep this requirement.
>
> But i think i will have to add some documentation regarding this.
> Thanks for pointing this out!
> Hope this helps,
>
> --steffen
> |
> |Der Kragenbaer,                The moon bear,
> |der holt sich munter           he cheerfully and one by one
> |einen nach dem anderen runter  wa.ks himself off
> |(By Robert Gernhardt)
>

Reply via email to