thru RFC\-2049. Currently
.B mhbuild
only supports encodings in
-message bodies, and does not support the encoding of message headers as
+message bodies, and does support the encoding of message headers as
specified in RFC\-2047.
.PP
If you specify the name of the composition file as `-',
.PP
.RS 5
.nf
-#audio/basic |raw2audio -F < /usr/lib/sound/giggle.au
+#audio/basic |raw2audio \-F < /usr/lib/sound/giggle.au
.fi
.RE
.PP
An example entry might be:
.PP
.RS 5
-mhbuild-compose-audio/basic: record | raw2audio -F
+mhbuild-compose-audio/basic: record | raw2audio \-F
.RE
.PP
Because commands like these will vary, depending on the display
#
This third part will be text/plain
#audio/basic [silly giggle] \\
- |raw2audio -F < /usr/lib/sounds/giggle.au
+ |raw2audio \-F < /usr/lib/sounds/giggle.au
#image/gif [photo of foobar] \\
/home/foobar/lib/picture.gif
.fi
Then send it.
There used to be a
.B \-nocontentid
-switch to prevent Content-ID headers to be inserted, but as it was considerd
+switch to prevent Content-ID headers to be inserted, but as it was considered
wrong to complicate all other MUAs instead of forcing the developers and users
of broken MUAs to fix or change their software, it was removed.