How do I send a file as an email attachment using Linux command line?

Question

I've created a script that runs every night on my Linux server that uses mysqldump to back up each of my MySQL databases to .sql files and packages them together as a compressed .tar file. The next step I want to accomplish is to send that tar file through email to a remote email server for safekeeping. I've been able to send the raw script in the body an email by piping the backup text file to mailx like so:

$ cat mysqldbbackup.sql | mailx [email protected]

cat echoes the backup file's text which is piped into the mailx program with the recipient's email address passed as an argument.

While this accomplishes what I need, I think it could be one step better, Is there any way, using shell scripts or otherwise, to send the compressed .tar file to an outgoing email message as an attachment? This would beat having to deal with very long email messages which contain header data and often have word-wrapping issues etc.

Pantry

Can you share the script that backup your MySQL databases? – Coign

Sorry, I haven't been doing this for a while now. I know it involved invoking mysqldump and then attaching the output to an email (with mutt). I may have even had a step that compressed the output to a zip/tar.gz as well... – Pantry

Purely curious, why email your backups vs scp or rsync them? – Loblolly

cat dados | mailx [email protected] worked perfectly for me inside a python program with dados being a file containing the results of the program. I wrote a function to catch the results of the program, "dados" then the line os.system(' cat dados | mailx [email protected]') has sent to my e-mail the file. Perfect! – Pulchi

Answer 1

None of the mutt ones worked for me. It was thinking the email address was part of the attachment. Had to do:

echo "This is the message body" | mutt -a "/path/to/file.to.attach" -s "subject of message" -- [email protected]

Countermark

I'm using mutt 1.5.21 (2010-09-15) and it requires -a parameter to be after recipient email – Thrombocyte

Worked for me using Mutt 1.5.24 (2015-08-30) on openSUSE Leap 42.1. – Participation

@fugitive means "end of options". Take a look at unix.stackexchange.com/questions/11376/… – Countermark

Is there a way to check for exceptions and retry sending? – Lallage

That's a complex follow-up question. Roughly speaking, there are two failure modes: mutt fails and you can pick up its exit code; or, sending succeeds but you get a delivery notification (bounce) eventually and then have to react to that. The latter is complex enough to handle properly that it's the business idea of several companies. – Lobation

This is all perfect, so long as SPF is not in place (like sending emails to Gmail in 2023, for example). Make sure you adjust your .muttrc to reflect the proper MTA settings. – Hiett

Answer 2

Or, failing mutt:

gzip -c mysqldbbackup.sql | uuencode mysqldbbackup.sql.gz  | mail -s "MySQL DB" [email protected]

Sirocco

This sends the uuencoded part inline and not as an attachment. Many mail-clients recognize this though and display the uuencoded part as an attachment. – Stranger

Don't use uuencode in this day and age. MIME is slightly more complex but a lot more user-friendly. – Lobation

@DavidGiven: See for example (by quick glance) all the other answers to this question. – Lobation

None of them use mail! – Supplicant

Then e.g. #3317674 and replace text/html with whatever MIME type makes sense for your attachment. (For this concrete example, I guess application/gzip.) – Lobation

Answer 3

Depending on your version of Linux it may be called mail. To quote @David above:

mail -s "Backup" -a mysqldbbackup.sql [email protected] < message.txt

or also:

cat message.txt | mail -s "Backup" -a mysqldbbackup.sql [email protected]

Clara

Both solutions doesn't work for me. I received the email with outlook 2013 and the mail only contains the filename – Brief

@nickel715: could it be that mail on your system is aliased to anything? – Clara

my manpage reads: -a, --append=HEADER: VALUE append given header to the message being sent – Dreamworld

@Dreamworld and Nathan, what system are you on with this mail program and where does it come from? In Ubuntu the "mail" program is the GNU mail program from mailutils, which doesn't have a -a option to attach a file. manpages.ubuntu.com/manpages/lucid/en/man1/mail.1.html – Chapman

@Chapman Mine also only has an option to append a header with the -a option. Also on Ubuntu using mailutils. – Dreamworld

Nathan, it looks like your quote from David is wrong - he used the mutt command, not mail. Also as others have pointed out, mutt now seems to require a -- argument before the address. And I see that @Dreamworld and I actually agree on what the -a option in mail does - I got confused there for a minute ;) – Chapman

instead of -a you should use -A: -a, --append=HEADER: VALUE append given header to the message being sent -A, --attach=FILE attach FILE – Broomcorn

@Victor Perov I'm pretty sure that is wrong, at least in current flavours of mutt... -A <alias> : expand an alias, -a <filename> [<filename>...] : attach a file to a message – Hanleigh

Worked for me as is on RHEL 7.9 where mail is symlinked to mailx – Figueroa

Like my answer explains, there are several incompatible implementations of mail/mailx which no doubt adds to the confusion here in the comments. – Lobation

Answer 4

From looking at man mailx, the mailx program does not have an option for attaching a file. You could use another program such as mutt.

echo "This is the message body" | mutt -a file.to.attach -s "subject of message" [email protected]

Command line options for mutt can be shown with mutt -h.

Rosellaroselle

Thanks! That did the trick, I was having trouble getting mutt to do the action silently. – Pantry

See answer below (https://mcmap.net/q/99229/-how-do-i-send-a-file-as-an-email-attachment-using-linux-command-line) because apparently the syntax changed for mutt which now requires a --. – Wormwood

See my answer for a more in-depth explanation of why man mailx is not really well-defined. – Lobation

Answer 5

I use SendEmail, which was created for this scenario. It's packaged for Ubuntu so I assume it's available

sendemail -f [email protected] -t [email protected] -m "Here are your files!" -a file1.jpg file2.zip

http://caspian.dotconf.net/menu/Software/SendEmail/

Pupil

I believe, it should be "sendEmail" instead of "sendemail" in your example. – Homogamy

Yes and no - the source (caspian) uses an uppercase E, while this is uncommon naming strategy for command line tools (in the Unix world), at least the Ubuntu packaging of this software provides both sendemailand sendEmail in /usr/bin/. – Pupil

My Xubuntu 14.04.3 not have installed SendEmail – Sneed

"sudo apt install sendemail" to install sendemail and add "-f [email protected]" a mandatory from field for the command to work. sendemail -f [email protected] [email protected] -m "Here are your files!" -a file1.jpg file2.zip – Skedaddle

Probably the best option in Ubuntu: no mess with the different mail/mailx/Mail packages, can attach files and can specify a custom From address (instead of the ugly default [email protected]) – Timon

the link to the sendemail docu is dead. – Furnace

well, the configuration caspian.dotconf.net is broken - if you go to the "root" of the domain, and then back, the page loads fine :-/ – Pupil

Answer 6

I use mpack.

mpack -s subject file [email protected]

Unfortunately mpack does not recognize '-' as an alias for stdin. But the following work, and can easily be wrapped in an (shell) alias or a script:

mpack -s subject /dev/stdin [email protected] < file

Confide

This could work in bash for stdin. I don't have mpack, so I have not tried: mpack -s subject /dev/stdin [email protected] <(stdout_generating_program) – Educator

Answer 7

 echo -e 'Hi, \n These are contents of my mail. \n Thanks' | mailx -s 'This is my email subject' -a /path/to/attachment_file.log -b [email protected] -c [email protected] -r [email protected] [email protected] [email protected] [email protected]

Burcham

This should be the accepted answer. Uses default mailx and works perfectly. Mutt v1.5.21 refuses to send >1MB attachments when using cron. – Catamaran

I was looking for something which works in EC2 and this worked fine. – Maple

mailx is not properly standardized. Any answer which recommends it should point out this caveat. There are at least three incompatible variants in common use. – Lobation

(Also, anything which uses echo -e should probably not receive upvotes, though I'm not upset enough to downvote just for that.) – Lobation

Answer 8

I once wrote this function for ksh on Solaris (uses Perl for base64 encoding):

# usage: email_attachment to cc subject body attachment_filename
email_attachment() {
    to="$1"
    cc="$2"
    subject="$3"
    body="$4"
    filename="${5:-''}"
    boundary="_====_blah_====_$(date +%Y%m%d%H%M%S)_====_"
    {
        print -- "To: $to"
        print -- "Cc: $cc"
        print -- "Subject: $subject"
        print -- "Content-Type: multipart/mixed; boundary=\"$boundary\""
        print -- "Mime-Version: 1.0"
        print -- ""
        print -- "This is a multi-part message in MIME format."
        print -- ""
        print -- "--$boundary"
        print -- "Content-Type: text/plain; charset=ISO-8859-1"
        print -- ""
        print -- "$body"
        print -- ""
        if [[ -n "$filename" && -f "$filename" && -r "$filename" ]]; then
            print -- "--$boundary"
            print -- "Content-Transfer-Encoding: base64"
            print -- "Content-Type: application/octet-stream; name=$filename"
            print -- "Content-Disposition: attachment; filename=$filename"
            print -- ""
            print -- "$(perl -MMIME::Base64 -e 'open F, shift; @lines=<F>; close F; print MIME::Base64::encode(join(q{}, @lines))' $filename)"
            print -- ""
        fi
        print -- "--${boundary}--"
    } | /usr/lib/sendmail -oi -t
}

Bismuthic

On GNU/Linux, one may use base64 command instead of perl for encoding – Marilla

Answer 9

You can use mutt to send the email with attachment

mutt -s "Backup" -a mysqldbbackup.sql [email protected] < message.txt

Consuetudinary

At least as of mutt 1.5.21 (Ubuntu trusty), you need to put the -a option after the recipient: mutt -s "Backup" [email protected] -a mysqldbbackup.sql < message.txt, or use the -- option before the recipient as shown in rynop's answer. – Chapman

Answer 10

Send a Plaintext body email with one plaintext attachment with mailx:

(
  /usr/bin/uuencode attachfile.txt myattachedfilename.txt; 
  /usr/bin/echo "Body of text"
) | mailx -s 'Subject' [email protected]

Below is the same command as above, without the newlines

( /usr/bin/uuencode /home/el/attachfile.txt myattachedfilename.txt; /usr/bin/echo "Body of text" ) | mailx -s 'Subject' [email protected]

Make sure you have a file /home/el/attachfile.txt defined with this contents:

<html><body>
Government discriminates against programmers with cruel/unusual 35 year prison
sentences for making the world's information free, while bankers that pilfer 
trillions in citizens assets through systematic inflation get the nod and 
walk free among us.
</body></html>

If you don't have uuencode read this: https://unix.stackexchange.com/questions/16277/how-do-i-get-uuencode-to-work

On Linux, Send HTML body email with a PDF attachment with sendmail:

Make sure you have ksh installed: yum info ksh

Make sure you have sendmail installed and configured.

Make sure you have uuencode installed and available: https://unix.stackexchange.com/questions/16277/how-do-i-get-uuencode-to-work

Make a new file called test.sh and put it in your home directory: /home/el

Put the following code in test.sh:

#!/usr/bin/ksh
export MAILFROM="[email protected]"
export MAILTO="[email protected]"
export SUBJECT="Test PDF for Email"
export BODY="/home/el/email_body.htm"
export ATTACH="/home/el/pdf-test.pdf"
export MAILPART=`uuidgen` ## Generates Unique ID
export MAILPART_BODY=`uuidgen` ## Generates Unique ID

(
 echo "From: $MAILFROM"
 echo "To: $MAILTO"
 echo "Subject: $SUBJECT"
 echo "MIME-Version: 1.0"
 echo "Content-Type: multipart/mixed; boundary=\"$MAILPART\""
 echo ""
 echo "--$MAILPART"
 echo "Content-Type: multipart/alternative; boundary=\"$MAILPART_BODY\""
 echo ""
 echo "--$MAILPART_BODY"
 echo "Content-Type: text/plain; charset=ISO-8859-1"
 echo "You need to enable HTML option for email"
 echo "--$MAILPART_BODY"
 echo "Content-Type: text/html; charset=ISO-8859-1"
 echo "Content-Disposition: inline"
 cat $BODY
 echo "--$MAILPART_BODY--"

 echo "--$MAILPART"
 echo 'Content-Type: application/pdf; name="'$(basename $ATTACH)'"'
 echo "Content-Transfer-Encoding: uuencode"
 echo 'Content-Disposition: attachment; filename="'$(basename $ATTACH)'"'
 echo ""
 uuencode $ATTACH $(basename $ATTACH)
 echo "--$MAILPART--"
) | /usr/sbin/sendmail $MAILTO

Change the export variables on the top of test.sh to reflect your address and filenames.

Download a test pdf document and put it in /home/el called pdf-test.pdf

Make a file called /home/el/email_body.htm and put this line in it:

<html><body><b>this is some bold text</b></body></html>

Make sure the pdf file has sufficient 755 permissions.

Run the script ./test.sh

Check your email inbox, the text should be in HTML format and the pdf file automatically interpreted as a binary file. Take care not to use this function more than say 15 times in a day, even if you send the emails to yourself, spam filters in gmail can blacklist a domain spewing emails without giving you an option to let them through. And you'll find this no longer works, or it only lets through the attachment, or the email doesn't come through at all. If you have to do a lot of testing on this, spread them out over days or you'll be labelled a spammer and this function won't work any more.

Clover

For me it worked the other way round. (echo 'Email Body'; uuencode filename filename) | mailx -s 'Subject' [email protected] – Jar

uuencode is not properly an attachment. It simply embeds a oomputer-readable blob of text in the middle of some other text. It used to work fine when there wasn't any better mechanism, but that was 20+ years ago. – Lobation

None of the code here seems to use any ksh features. If you have something which doesn't work with POSIX sh, probably prefer Bash over ksh, which often uses the same syntax anyway. – Lobation

Answer 11

There are several answers here suggesting mail or mailx so this is more of a background to help you interpret these in context. But there are some practical suggestions near the end.

Historical Notes

The origins of Unix mail go back into the mists of the early history of Bell Labs Unix™ (1969?), and we probably cannot hope to go into its full genealogy here. Suffice it to say that there are many programs which inherit code from or reimplement (or inherit code from a reimplementation of) mail and that there is no single code base which can be unambiguously identified as "the" mail.

However, one of the contenders to that position is certainly "Berkeley Mail" which was originally called Mail with an uppercase M in 2BSD (1978); but in 3BSD (1979), it replaced the lowercase mail command as well, leading to some new confusion. SVR3 (1986) included a derivative which was called mailx. The x was presumably added to make it unique and distinct; but this, too, has now been copied, reimplemented, and mutilated so that there is no single individual version which is definitive.

Back in the day, the de facto standard for sending binaries across electronic mail was uuencode. It still exists, but has numerous usability problems; if at all possible, you should send MIME attachments instead, unless you specifically strive to be able to communicate with the late 1980s.

MIME was introduced in the early 1990s to solve several problems with email, including support for various types of content other than plain text in a single character set which only really is suitable for a subset of English (and, we are told, Hawai'ian). This introduced support for multipart messages, internationalization, rich content types, etc, and quickly gained traction throughout the 1990s.

(The Heirloom mail/mailx history notes were most helpful when composing this, and are certainly worth a read if you're into that sort of thing.)

Current Offerings

As of 2018, Debian has three packages which include a mail or mailx command. (You can search for Provides: mailx.)

debian$ aptitude search ~Pmailx
i   bsd-mailx                       - simple mail user agent
p   heirloom-mailx                  - feature-rich BSD mail(1)
p   mailutils                       - GNU mailutils utilities for handling mail

(I'm not singling out Debian as a recommendation; it's what I use, so I am familiar with it; and it provides a means of distinguishing the various alternatives unambiguously by referring to their respective package names. It is obviously also the distro from which Ubuntu gets these packages.)

• bsd-mailx is a relatively simple mailx which does not appear to support sending MIME attachments. See its manual page and note that this is the one you would expect to find on a *BSD system, including MacOS, by default.
• heirloom-mailx is now being called s-nail and does support sending MIME attachments with -a. See its manual page and more generally the Heirloom project
• mailutils aka GNU Mailutils includes a mail/mailx compatibility wrapper which does support sending MIME attachments with -A

With these concerns, if you need your code to be portable and can depend on a somewhat complex package, the simple way to portably send MIME attachments is to use mutt.

If you know what you are doing, you can assemble an arbitrary MIME structure with the help of echo and base64 and e.g. qprint (or homegrown replacements; both base64 and qprint can easily be implemented as Perl one-liners) and pipe it to sendmail; but as several other answers on this page vividly illustrate, you probably don't.

( printf '%s\n' \
    "From: myself <[email protected]>" \
    "To: backup address <[email protected]>" \
    "Subject: Backup of $(date)" \
    "MIME-Version: 1.0" \
    "Content-type: application/octet-stream; filename=\"mysqldbbackup.sql\"" \
    "Content-transfer-encoding: base64" \
    ""
  base64 < mysqldbbackup.sql ) |
sendmail -oi -t

This assumes that sendmail is on your PATH; sometimes it's not (and of course, sometimes it's simply not installed at all). Look in /usr/lib, /usr/sbin, /usr/libexec or etc; or query your package manager. Once you find it, you might want to augment your PATH in the script, or hardcode the full pathname to sendmail (and ditto for any other nonstandard binaries which may or may not be installed on your system).

This still does not attempt to provide any solution for situations where you need to send non-ASCII Unicode text or lines longer than what SMTP allows, etc etc etc. For a robust solution, I would turn to an existing tool like mutt, or a modern scripting language like Python; https://docs.python.org/3/library/email.examples.html has examples for many common use cases.

Lobation

I originally posted this as an answer to a moderately popular duplicate question #903091 – Lobation

For a quick and dirty intro to MIME structures, perhaps see #48563435 – Lobation

The simple example shell script allegedly doesn't work with Outlook; my recommendation would be to get rid of Outlook in that scenario, but if you can't, try adding a useless text part before the attachment. – Lobation

Answer 12

Another alternative - Swaks (Swiss Army Knife for SMTP).

swaks -tls \
    --to ${MAIL_TO} \
    --from ${MAIL_FROM} \
    --server ${MAIL_SERVER} \
    --auth LOGIN \
    --auth-user ${MAIL_USER} \
    --auth-password ${MAIL_PASSWORD} \
    --header "Subject: $MAIL_SUBJECT" \
    --header "Content-Type: text/html; charset=UTF-8" \
    --body "$MESSAGE" \
    --attach mysqldbbackup.sql

Shanney

This is absolutely brilliant. It's the only solution which in the end allowed me to use the smtp.gmail.com server and an app password (support.google.com/accounts/answer/185833#app-passwords) to send emails from the command line. A lot has changed since the early 90s, apparently, when I last used to send email from CLI. – Hiett

Answer 13

Mailutils makes this a piece of cake

echo "Body" | mail.mailutils -M -s "My Subject" -A attachment.pdf [email protected]

• -A file attaches a file
• -M enables MIME, so that you can have an attachment and plaintext body.

If not yet installed, run

sudo apt install mailutils

Uncinate

Answer 14

metamail has the tool metasend

metasend -f mysqlbackup.sql.gz -t [email protected] -s Backup -m application/x-gzip -b

Bullfighter

This used to be installed almost everywhere, but almost never used. Because it was unmaintained for a long time (and still is AFAIK) it has been removed from the de facto standard toolset on many platforms. – Lobation

Answer 15

I usually only use the mail command on RHEL. I have tried mailx and it is pretty efficient.

mailx -s "Sending Files" -a First_LocalConfig.conf -a
Second_LocalConfig.conf [email protected]

This is the content of my msg.

.

Hubey

Answer 16

I used

echo "Start of Body" && uuencode log.cfg readme.txt | mail -s "subject" "[email protected]" 

and this worked well for me....

Basso

The echo is useless here; it will output the text to the terminal, not into the pipe to mail. As in other similar answers here, uuencode is not "an attachment", although some email clients will helpfully hide the ugliness so that it appears to be one if you don't look closely. – Lobation

Answer 17

From source machine

mysqldump --defaults-extra-file=sql.cnf database | gzip | base64 | mail [email protected]

On Destination machine. Save the received mail body as db.sql.gz.b64; then..

base64 -D -i db.sql.gz.b64 | gzip -d | mysql --defaults-extra-file=sql.cnf

Achernar

This gets the data across, but lacks the MIME headers to tell the user what to do with it. Unless they know what it is, they will probably not be able to figure out how to use it. A proper MIME structure would at least display the base64 data as an attachment instead of as the actual message text. – Lobation

You got me there @Lobation - I was not really considering using such a mechanism for third parties. Most people I know wouldn’t know what to do with it even if they did have Mime headers to help them. – Achernar

Answer 18

using mailx command

 echo "Message Body Here" | mailx -s "Subject Here" -a file_name [email protected]

using sendmail

#!/bin/ksh

fileToAttach=data.txt

`(echo "To: [email protected]"
  echo "Cc: [email protected]"
  echo "From: Application"
  echo "Subject: your subject"
  echo  your body
  uuencode $fileToAttach $fileToAttach
  )| eval /usr/sbin/sendmail -t `;

Cotten

sendmail is nice example, glad I found it here. – Mond

Note that you need an empty line at the start of "your body", otherwise the body will disappear into the headers, or possibly break the message entirely. Also see notes elsewhere about avoiding uuencode in favor of MIME. – Lobation

And the monstrous eval and the mystery backticks around the whole contraption are completely unnecessary here. – Lobation

Answer 19

Just to add my 2 cents, I'd write my own PHP Script:

http://php.net/manual/en/function.mail.php

There are lots of ways to do the attachment in the examples on that page.

Blasted

Not every server may have PHP installed. If you really want to go down the "write your own script" path, then perl or python are much better suited as they are usually available by default. – Dreamworld

sh is even more ubiquitous. There are duplicate questions with answers with good examples; here is mine. – Lobation

Answer 20

mailx does have a -a option now for attachments.

Expunction

The "-a" option is for headers – Flapdoodle

man mail[x], version 12.5 of 10/9/10 (a few years ago) clearly says -a file Attach the given file to the message.` – Bisayas

some versions of mailx do. I believe there are two implementations. On one -a is for attachments, on the other it is for headers. – Dreamworld

The version of mailx in Ubuntu comes from GNU and there -a means add a header. manpages.ubuntu.com/manpages/lucid/en/man1/mailx.1.html Which system and which mailx does an attachment? – Chapman

In new implementation "-a" is for Headers and "-A" is for attchments – Lanceted

It's not old vs new, it's just different heritages. – Lobation

Answer 21

Not a method for sending email, but you can use an online Git server (e.g. Bitbucket or a similar service) for that.

This way, you can use git push commands, and all versions will be stored in a compressed and organized way.

Wirehaired

Answer 22

the shortest way for me is

file=filename_or_filepath;uuencode $file $file|mail -s "optional subject" email_address

so for your example it'll be

file=your_sql.log;gzip -c $file;uuencode ${file}.gz ${file}|mail -s "file with magnets" [email protected]

the good part is that I can recall it with Ctrl+r to send another file...

Lottielotto

The braces won't do you much good but to be completely portable you should use double quotes around the variables. See also #10067766 – Lobation

Answer 23

This is how I am doing with one large log file in CentOS:

#!/bin/sh
MAIL_CMD="$(which mail)"
WHOAMI="$(whoami)"
HOSTNAME="$(hostname)"
EMAIL"[email protected]"
LOGDIR="/var/log/aide"
LOGNAME="$(basename "$0")_$(date "+%Y%m%d_%H%M")"

if cd ${LOGDIR}; then
  /bin/tar -zcvf "${LOGDIR}/${LOGNAME}".tgz "${LOGDIR}/${LOGNAME}.log" > /dev/null 2>&1
  if [ -n "${MAIL_CMD}" ]; then
  # This works too. The message content will be taken from text file below
  # echo 'Hello!' >/root/scripts/audit_check.sh.txt
  # echo "Attachment" | ${MAIL_CMD} -s "${HOSTNAME} Aide report" -q /root/scripts/audit_check.sh.txt -a ${LOGNAME}.tgz -S from=${WHOAMI}@${HOSTNAME} ${EMAIL}
    echo "Attachment" | ${MAIL_CMD} -s "${HOSTNAME} Aide report" -a "${LOGNAME}.tgz" -S from="${WHOAMI}@${HOSTNAME}" "${EMAIL}"
    /bin/rm "${LOGDIR}/${LOGNAME}.log"
  fi
fi

Wrinkle

Why are you defining WHOAMI and HOSTNAME twice? – Boggs

This has several shell coding style mistakes. shellcheck.net will point out some, but not all, of them. – Lobation

Using which to find a program on your PATH so you can call it with the full path is ... silly, and also not properly portable. Just use mail instead of ${MAIL_CMD} everywhere for for exactly the same effect, with better robustness and portability. The properly POSIX-compatible equivalent of which is command -v or type, but you don't need any of that here. – Lobation

Answer 24

If the file is text, you can send it easiest in the body as:

sendmail [email protected] < message.txt

Familiarity

This does not send it as an attachment, or even as the message body. Sendmail expects its input to be a complete, well-formed RFC5322 email message, and may fail in interesting ways if it isn't. – Lobation

Answer 25

If mutt is not working or not installed,try this-

*#!/bin/sh

FilePath=$1
FileName=$2
Message=$3
MailList=$4

cd $FilePath

Rec_count=$(wc -l < $FileName)
if [ $Rec_count -gt 0 ]
then
(echo "The attachment contains $Message" ; uuencode $FileName $FileName.csv ) | mailx -s "$Message" $MailList
fi*

Hourly

This has numerous coding errors which will make it appear to work with trivial examples, but break in real life. See shellcheck.net for some recommendations, though it will not tell you to avoid uuencode – Lobation