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 backup@email.com
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.
None of the mutt ones worked for me. It was thinking the email address was part of the attachemnt. Had to do:
echo "This is the message body" | mutt -a "/path/to/file.to.attach" -s "subject of message" -- recipient@domain.com
Or, failing mutt:
gzip -c mysqldbbackup.sql | uuencode mysqldbbackup.sql.gz | mail -s "MySQL DB" backup@email.com
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" recipient@domain.com
Command line options for mutt can be shown with mutt -h.
mutt opens the nano editor for me, to send the mail. - Jonas--. - Alexander Bird
Depending on your version of linux it may be called mail. To quote @David above:
mail -s "Backup" -a mysqldbbackup.sql backup@email.com < message.txt
or also:
cat message.txt | mail -s "Backup" -a mysqldbbackup.sql backup@email.com
-a, --append=HEADER: VALUE append given header to the message being sent - exhumamutt command, not mail. Also as others have pointed out, mutt now seems to require a -- argument before the address. And I see that @exhuma and I actually agree on what the -a option in mail does - I got confused there for a minute ;) - nealmcb-a, --append=HEADER: VALUE append given header to the message being sent -A, --attach=FILE attach FILE - Victor Perov
I use mpack.
mpack -s subject file user@example.com
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 loser@example.com < file
mpack -s subject /dev/stdin loser@example.com <(stdout_generating_program) - thomasa88
I use SendEmail, which was created for this scenario. It's packaged for Ubuntu so I assume it's available
sendemail -f sender@some.where -t receiver@some.place -m "Here are your files!" -a file1.jpg file2.zip
http://caspian.dotconf.net/menu/Software/SendEmail/
sendemailand sendEmail in /usr/bin/. - Fredrik WendtSendEmail - Vitaly Zdanevichsendemail -f mandatory@email.com-t to@some.one -m "Here are your files!" -a file1.jpg file2.zip - Sailendra Pinupolu
echo 'These are contents of my mail' | mailx -s 'This is my email subject' -a /path/to/attachment_file.log email_id@example.com
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. - tripleee
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
}
base64 command instead of perl for encoding - MestreLion
You can use mutt to send the email with attachment
mutt -s "Backup" -a mysqldbbackup.sql backup@email.com < message.txt
-a option after the recipient: mutt -s "Backup" backup@email.com -a mysqldbbackup.sql < message.txt, or use the -- option before the recipient as shown in rynop's answer. - nealmcb
(
/usr/bin/uuencode attachfile.txt myattachedfilename.txt;
/usr/bin/echo "Body of text"
) | mailx -s 'Subject' youremail@gmail.com
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' youremail@gmail.com
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
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="el@defiant.com"
export MAILTO="youremail@gmail.com"
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.
(echo 'Email Body'; uuencode filename filename) | mailx -s 'Subject' user@domain.com - Vickyuuencode 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. - tripleee
There are several answers here suggesting mail or mailx so this is more of a background to help you interpret these in context.
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.)
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 projectmailutils aka GNU Mailutils includes a mail/mailx compatibility wrapper which does support sending MIME attachments with -AWith 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.
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
metamail has the tool metasend
metasend -f mysqlbackup.sql.gz -t backup@email.com -s Backup -m application/x-gzip -b
I used
echo "Start of Body" && uuencode log.cfg readme.txt | mail -s "subject" "a@b.c"
and this worked well for me....
mailx does have a -a option now for attachments.
mailx do. I believe there are two implementations. On one -a is for attachments, on the other it is for headers. - exhuma
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 Recipient@myemail.com
This is the content of my msg.
.
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" ph.gachoud@gmail.com
the good part is that I can recall it with Ctrl+r to send another file...
From source machine
mysqldump --defaults-extra-file=sql.cnf database | gzip | base64 | mail me@myemail.com
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
using mailx command
echo "Message Body Here" | mailx -s "Subject Here" -a file_name user@example.com
using sendmail
#!/bin/ksh
fileToAttach=data.txt
`(echo "To: user@company.com"
echo "Cc: user@company.com"
echo "From: Application"
echo "Subject: your subject"
echo your body
uuencode $fileToAttach $fileToAttach
)| eval /usr/sbin/sendmail -t `;
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.
sh is even more ubiquitous. There are duplicate questions with answers with good examples; here is mine. - tripleee
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.
This is how I am doing with one large log file in CentOS:
MAIL="`whereis mail | awk '{print $2}'`"
WHOAMI="`whoami`"
HOSTNAME="`hostname`"
EMAIL"your@email.address"
LOGDIR="/var/log/aide"
LOGNAME="`basename "$0"`_`date "+%Y%m%d_%H%M"`"
# Arhiveerime ning kui hästi, saadame edasi:
/bin/tar -zcvf ${LOGDIR}/${LOGNAME}.tgz "${LOGDIR}/${LOGNAME}.log" > /dev/null 2>&1
if [ $? -eq 0 ]; then
cd ${LOGDIR}
# This works too. The message content will be taken from text file below
# echo 'Hello!' >/root/scripts/audit_check.sh.txt
# echo "Arhiivifail manuses" | ${MAIL} -s "${HOSTNAME} Aide report" -q /root/scripts/audit_check.sh.txt -a ${LOGNAME}.tgz -S from=${WHOAMI}@${HOSTNAME} ${EMAIL}
echo "Arhiivifail manuses" | ${MAIL} -s "${HOSTNAME} Aide report" -a ${LOGNAME}.tgz -S from=${WHOAMI}@${HOSTNAME} ${EMAIL}
/bin/rm "${LOGDIR}/${LOGNAME}.log"
fi
WHOAMI and HOSTNAME twice? - David C. Rankin
If the file is text, you can send it easiest in the body as:
sendmail recipient@example.com < message.txt
One more thing about mutt: by default it uses your address and name in "From:" field.
If it's not what you need, you can create alternative muttrc file containing a string like this:
set from="My mail daemon "
Use this file with -F command line option.
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*
mysqldumpand then attaching the output to an email (withmutt). I may have even had a step that compressed the output to a zip/tar.gz as well... - Kit Roed