Recently I've been seeing this message when sending email with an attached
.mp3 file:
mhbuild: extraneous information in message /home/smw/Mail/drafts/1's
Content-Type: field
(/octet-stream)
I've appended the Fcc copy of a typical message, in which the Content-Type:
field for the attachment is
Content-Type: audio/mpegapplication; name="session2.mp3"
I'm quite sure this isn't nmh's fault, but rather an error in the MIME
configuration on my Manjaro Linux machine. I'm hoping for a hint about
where to look for the config file responsible for "audio/mpegapplication;".
Thanks,
- Steven
8<----------------------------- cut here ---------------------------->8
To: smw@smwonline.ca
Subject: testing testing testing
From: Steven Winikoff <smw@smwonline.ca>
Reply-to: Steven Winikoff <smw@smwonline.ca>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"
Content-ID: <408771.1620805880.0@mort>
Date: Wed, 12 May 2021 03:51:21 -0400
Message-ID: <408773-1620805881.053161@ksVt.GHQA.IA-w>
------- =_aaaaaaaaaa0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <408771.1620805880.1@mort>
- Steven
--
___________________________________________________________________________
Steven Winikoff | "There are millions of chords. There are
Montreal, QC, Canada | millions of numbers. And everyone forgets
smw@smwonline.ca | the one that is a zero. But without the
http://smwonline.ca | zero, numbers are just arithmetic. Without
| the empty chord, music is just noise."
| - Terry Pratchett
------- =_aaaaaaaaaa0
Content-Type: audio/mpegapplication; name="session2.mp3"
Content-Description: session2.mp3
Content-Disposition: attachment; filename="session2.mp3"
Content-Transfer-Encoding: base64
SUQzBAAAAAAAI1RTU0UAAAAPAAADTGF2ZjU4Ljc2LjEwMAAAAAAAAAAAAAAA//tUAAAAAAAAAAAA
[many more lines of base64 encoding deleted to save electrons :-)]
------- =_aaaaaaaaaa0--
8<----------------------------- cut here ---------------------------->8