Sendmail: Theory and Practice
Author: Frederick M. Avolio & Paul A. Vixie
Publisher: Digital Press
Reviewer: Phil Hughes
Many of us who have had to configure Sendmail think of it as something similar to fixing the plumbing in our house - it has to be done, we sort of know how to do it and we wish we could ignore it and it would go away. Yes, Sendmail is powerful and, for most systems, necessary, but it is complicated. To make matters worse, you don't have to make changes often enough so that you actually learn how to do it right and remember it.
When Eric Allman's book on Sendmail was published, I got a copy and was immediately intimidated. Eric is the author of Sendmail and his book is thorough - tipping the scales at almost 800 pages. Yes, the answer is there, but the book is more than many people need or want to get into - sort of like reading the National Electrical Code book to find out how to replace a fuse.
If this same thing happened to you, Sendmail: Theory and Practice may be the right answer. In 262 pages Avolio and Vixie address just what the book title says: theory and practice. It takes the fear out of Sendmail configuration by first explaining the practical considerations involved in electronic mail transfer and then goes on to show how to configure Sendmail to accomplish the tasks.
The first 90 pages cover practical information about addressing over networks, including the problems of mixed-type addresses (that is, a combination of a uucp address and domain address). These pages also cover mail user agents, their interface to Sendmail and how aliases work in Sendmail. Or, more correctly, how to use Sendmail aliases to do what you need in a reliable and secure fashion. Again, the emphasis is on practical application.
The next chapter offers the basics of macros and rules. This is presented in a practical and non-threatening manner with an emphasis on what you need rather than a lengthy look at all the capabilities.
The next chapter addresses the IDA Kit extension to Sendmail. It does a good job of showing how the DBM tables of the IDA kit tie into the rules in the sendmail.cf file. While I personally had hoped I didn't need to know this, the book gives enough information to help you understand this without getting bogged down in theory.
Even if you have what looks like a working Sendmail, the chapter on “Maintenance and Administration” will help you feel a lot better about your relationship with Sendmail. After going through all the files related to Sendmail and all the command line options, it looks at things you can check, why you might want to check them, and how to check them. For example, a section on queued mail offers five steps to help identify why mail is remaining in the queue and what to do to get it on its way.
The book ends with a series of appendicies that offer resources or pointers to resources that you need. These include summaries of the options and mailer flags for the sendmail.cf file, sample sendmail.cf files, logging and debugging information, and even the form to be sent in to the InterNIC to register a domain.
The main shortcoming of the book is that it does not address Release 8 of Sendmail. The authors claim that the philosophy of R8 is the same as R5. Certainly the added functionality in R8 is not covered. They may be absolutely right in their decision, however. This book contains plenty to keep you thinking, and adding complications of R8 could have detracted from the book's usability.
If you are afraid of Sendmail but have to deal with it, this is the right book to get. It doesn't tell you everything but it does tell you more than most systems administrators need to know and it is presented in a very practical manner from the point of view of two people who see Sendmail as a tool and have learned to use that tool to accomplish their tasks.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Returning Values from Bash Functions
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Rogue Wave Software's Zend Server
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide