Mail Sending Mistakes
A follow up on David Blank-Edelman Perl for System Administration tutorial on Tuesday.
David emphasized the 3 rules a sysadmin should respect when programming some script that reports by email to its master:- Beware of overzealous message sending: you don't want your mailbox to be flooded by the same message repeating itself
- Build delay functions into the code.
- send aggregate messages
- Do not waste the subject line of the message: it is made for quick, to the point, if short information.
- Make sure the message body is relevant: include the answers to following questions - who, where, when, what, why, what next.
I think we should add a fourth rule these days, that mitigates the third one some: do not assume you'll be the only person reading the message.
All SMTP traffic goes out in the clear, and is a prime target for any network sniffer. This is not paranoïa, this is renewed experience.
If your script report includes sensitive or revealing data, encrypt it (with GnuPG for instance, and Ashish Gulhati's Crypt::GPG module) before sending it, or store it on some restricted access web server, and include a link in the body of the message.
5:14:43 PM Google It!
|
|