Sending Files by E-mail
Often, we have files we wish to send colleagues and friends by e-mail. Depending on the type of file you wish to send, there is a Linux command to make the process easy for you.
The shell archive file command shar is very useful for combining plaintext files into one file, which can then be sent by e-mail. shar writes shell commands for unpacking the output file inside the file itself, as well as code to verify the content using an MD5 checksum. It is much easier to use than the archive command tar, whose complexities can trip up even an expert. All you have to do to run shar is type:
shar input_filenames > filename.shar
It will take all the input files and write them to the output file, embedding the unpacking commands as it goes. The extension conventionally used with shar output files is .shar. To unpack the file, you don't need to know the embedded commands or retrieve them from the file yourself. Instead, use the command sh. The first argument to uuencode is the input file name; the second is the name to put in the output file header. We will use the same name for both. Type:
sh filename.sharThe sh command will do the work for you by reading the file, extracting the commands and executing them to unpack the archive.
It is permissible to use wild cards in naming your shar input files, so you can easily pack all the files in one or more directories. Just remember, the files must all be plaintext—no binaries.
The purpose of the shar command is quite similar to that of tar. However, the command and its format are much easier to remember, and since the output is plaintext instead of binary, it does not need to be encoded to send it as e-mail.
Non-plaintext files such as binaries and graphics must be encoded before e-mailing them. First, pack and compress your files using tar, which outputs a binary file. We won't go into tar in detail here, since it has been discussed before: see “Tar and Taper for Linux” by Yusuf Nagree, Linux Journal, February 1996 (http://www.linuxjournal.com/lj-issues/issue22/1216.html). A simple command to pack and compress all the files in the current directory would look like this:
tar -cvzf tar_files.tgz *
Now, the tar file can be encoded using the command uuencode by typing:
uuencode tar_file.tgz tar_file.tgz > mail_fileThe output file can now be put into e-mail and sent off into the ether.
The recipient can save the e-mail (perhaps as mail.save) and decode the file easily—no need to even remove mail headers. Simply use the command uudecode by typing:
uudecode will do just what its name says: decode the mail file, leaving a file called tar_file.tgz in the current directory. To unpack the tar file, type:
tar -xvzf tar_file.tgzA single graphics file can be encoded and decoded in the same way, skipping the tar step since an archive file is not needed.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Three More Lessons
- Django Models and Migrations
- August 2015 Issue of Linux Journal: Programming
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Huge Package Overhaul for Debian and Ubuntu
- General Relativity in Python
- Embed Linux in Monitoring and Control Systems