Home opinion-and-analysis Open Sauce LCA 2011 keynotes: Allman to focus on sendmail

Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

Anyone who has received an email in his or her lifetime has probably made use of Eric Allman's code at some time or the other.

 


Allman is the father of sendmail, the first mail transport agent for UNIX systems. He will be in Australia later this month as one of the keynote speakers at the forthcoming Australian national Linux conference in Brisbane.

Allman developed the precursor of sendmail, delivermail, in 1981 as an extension to the AT&T Unix code which was available at the University of California in Berkeley. He was studying for a computer science degree.

Sendmail was designed to deliver email over what was then a relatively small ARPANET which had several different smaller networks. Most of these networks had differing headers for email.

Allman's MTA soon became an important part of the Berkeley Software Distribution. It is still widely used on UNIX systems despite being difficult to configure. Alternatives like postfix (written by Wietse Venema), exim (written by Philip Hazel) and qmail (authored by Daniel Bernstein) have gained ground as they are much easier to configure.

But veterans still swear by sendmail. As far as GNU/Linux goes, Slackware, one of the older distributions still uses sendmail as its default MTA though Debian has moved to exim and Red Hat to postfix.

Though Allman, who now works at Sendmail Inc, a company he co-founded in 1998, has also authored software such as syslog (a standard for logging program messages) and several other programs, he is best known for sendmail given its degree of use and the fact that it was the first MTA.

Thus it is not surprising that in his keynote, he will focus on the software that has become synonymous with his name.

FREE - SYDNEY & MELBOURNE BUSINESS INTELLIGENCE EVENTS

The Holy Grail of the Business Intelligence (BI) industry – pervasive deployments and widespread end-user adoption – has remained an illusive dream for years. Until now!

REGISTER & SECURE YOU PLACE / BRING A FRIEND

Melbourne - venue Captain Melville’s CBD 2:30 – 6:00pm, Tuesday 28th April

Sydney - venue Redoak CBD 2:30 – 6:00pm, Thursday 30th April

DON'T MISS OUT - MELBOURNE REGISTER NOW!

DON'T MISS OUT - SYDNEY REGISTER NOW!

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect