In comp.sys.raspberry-pi, Adrian <
bulleid@ffoil.org.uk> wrote:
Eli the Bearded <*@eli.users.panix.com> writes
I just did some playing with mpack myself. The output is compliant with
mid-90s RFCs (eg RFC-2046), I am not up on more modern standards, but it
is very quirky looking compared to modern MIME encoding.
mpack -c image/jpeg -d /dev/null -o output_file <file>
gives :
Message-ID: <14058.1660767984@pi2>
Mime-Version: 1.0
Subject:
Content-Type: multipart/mixed; boundary="-"
This is a MIME encoded message. Decode it with "munpack"
or any other MIME reading software. Mpack/munpack is available
via anonymous FTP in ftp.andrew.cmu.edu:pub/mpack/
---
---
Content-Type: image/jpeg; name="image_202208172025.jpg" Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="image_202208172025.jpg"
Content-MD5: NhPEg4pgYEkaTbtZnOkNsg==
I'm assuming that the set of blank lines is the area for the
description.
You would be 100% correct. And the lack of headers on the description
part is a big "quriky" output.
BTW, if you just need a message composed with a single file of a known
type and no other frills, that's really easy to do via shell script. The benefits of mpack are slim for that small use case.
You print your headers, with some particular mime details, you include
your base64 encoded image, and done. This is a super-bare-bones untested version that has no multipart, just jpeg:
#!/bin/sh
file="$1"
if [ ! -f "$file" ] ; then
echo 'Usage:'
echo ' echo "To: foo@bar" > output'
echo ' echo "From: bar@foo" >> output'
echo ' echo "Subject: qux" >> output'
echo ' composer jpegfile >> output'
echo ''
echo 'Then send with eg, sendmail -oi < output'
exit 2
fi
# simple JPEG as body email
echo 'Mime-Version: 1.0
echo 'Content-Type: image/jpeg; name="'"$file"'"'
echo 'Content-Transfer-Encoding: base64'
echo 'Content-Disposition: inline; filename="'"$file"'"'
echo ''
base64 "$file"
echo ''
exit
And this is a multipart example:
#!/bin/sh
file="$1"
desc="$2"
if [ ! -f "$desc" ] ; then
echo 'Usage:'
echo ' echo "To: foo@bar" > output'
echo ' echo "From: bar@foo" >> output'
echo ' echo "Subject: qux" >> output'
echo ' multicomposer jpegfile description.txt >> output'
echo ''
echo 'Then send with eg, sendmail -oi < output'
exit 2
fi
# simple multipart with text and jpeg. The use of = and - means
# that the boundary string cannot occur in base64 or quoted
# printable content
boundary=--==randomness--$$==--
echo 'Mime-Version: 1.0
echo 'Content-Type: multipart/mixed; boundary="'$boundary'"'
echo ''
# each part starts with named boundary plus two hyphens
echo "--$boundary"
echo 'Content-Type: text/plain; charset="UTF-8"'
# echo 'Content-Transfer-Encoding: quoted-printable;
echo ''
# if you have it, consider "mmencode -q < $desc" to quoted-printable
# encode body
cat $desc
echo ''
echo "--$boundary"
echo 'Content-Type: image/jpeg; name="'"$file"'"'
echo 'Content-Transfer-Encoding: base64'
echo 'Content-Disposition: inline; filename="'"$file"'"'
echo ''
base64 "$file"
# final boundary is indicated with extra hyphens at end
echo "--$boundary--"
echo ''
exit
My mail software has a set of scripts evolved from Rnmail (in the rn/trn package) that does roughly this but includes a "vi $outfile" step before sendmail is used.
Elijah
------
added 'rnmail' as a command to the mailx he uses
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)