Home/ Questions/Q 7849755
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T18:37:35+00:00

I’ve been using mail -s here is a log file person@example.com < log/logfile.log Which

  • 0

I’ve been using 

 mail -s "here is a log file" "person@example.com" < log/logfile.log

Which used to come through with headers:

User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

But now the files are longer I’m getting noname attachments because with this:

User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: application/octet-stream
Content-Transfer-Encoding: base64

So if all else fails, check the manual man mail …

NAME
       mailx - send and receive Internet mail

SYNOPSIS
       mailx [-BDdEFintv~] [-s subject] [-a attachment ] [-c cc-addr] [-b bcc-addr] [-r from-addr] [-h hops]
              [-A account] [-S variable[=value]] to-addr . . .

None of these options seem useful so how can I force Content-Type: text/plain?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The man page is a good place to start! Keep reading until you get to the MIME TYPES section, and pay close attention the following:

    Otherwise, or if the filename has no extension, the content types
    text/plain or application/octet-stream are
    used, the first for text or international text files, the second for any file that contains formatting char‐
    acters other than newlines and horizontal tabulators.

    So, if your message contains “formatting characters” (which in general means control characters) other than newlines and tabs, it will automatically be classified as application/octet-stream. I bet that if you look closely at the data you’ll find some control characters floating around.

    You can work around this by…

    • Including the log file as an attachment (using -a) instead of the main message body, and set up your ~/.mime.types file to identify *.log files as text/plain.
    • Filter out control characters using something like tr.

    • Use another MUA such as mutt to send the mail. In fact, you could just craft a message yourself and send it directly to sendmail:

      (
  echo To: person@example.com
  echo From: you@example.com
  echo Subject: a logfile
  echo
  cat logfile.log
) | sendmail -t
    • 0