./mimesender -t to@mail.com -T "To Name" -f frommail -F "From Name" -b body.txt -s "TEST Subject" -X body.txt

Thats the body!--=== This is the boundary between parts of the message. ===--
Content-Type: text/plain; name="body.txt"
Content-Transfer-Encoding: x-uue
Content-Disposition: attachment; filename="body.txt"

begin 0 body.txt
05&AA=',@=&AE(&)O9'DA#0``
`
end

DEBUG: Debug Mode is on...no mail will be sent
DEBUG: pwentry = root:!:0:0::/:/usr/bin/ksh
DEBUG: myaddr = root
DEBUG: myname =
DEBUG: Attachment 0 body.txt X body.txt
DEBUG: PIPELINE = cat body.txt| sed "s/$/${CR}/"|uuencode body.txt
DEBUG:
DEBUG:
DEBUG: mta arg = to@mail.com
DEBUG:
DEBUG: start of mail
DEBUG: From: From Name <frommail>
DEBUG: Sender:  <root>
DEBUG: To: To Name <to@mail.com>
DEBUG: Subject: TEST Subject
DEBUG: X-Mailer: mimesender 0.0
DEBUG: Mime-Version: 1.0
DEBUG: Content-Type: multipart/mixed;
DEBUG:     boundary="=== This is the boundary between parts of the message. ===--"
DEBUG:
DEBUG:
DEBUG:         This message is in MIME format.  But if you can see this,
DEBUG:         you aren't using a MIME aware mail program.  Some parts of
DEBUG:         of this message have been uuencoded for transport.  On a Unix
DEBUG:         system, the program uudecode should be used to restore the file.
DEBUG:
DEBUG: --=== This is the boundary between parts of the message. ===--
DEBUG: Content-Type: text/plain; charset=US-ASCII
DEBUG:
DEBUG: Thats the body!--=== This is the boundary between parts of the message. ===--
DEBUG: Content-Type: text/plain; name="body.txt"
DEBUG: Content-Transfer-Encoding: x-uue
DEBUG: Content-Disposition: attachment; filename="body.txt"
DEBUG:
DEBUG: begin 0 body.txt
DEBUG: 05&AA=',@=&AE(&)O9'DA#0``
DEBUG: `
DEBUG: end
DEBUG:
DEBUG: --=== This is the boundary between parts of the message. ===----
DEBUG: end of mail