Many different things come to mind when I hear the word “Cloud.” To be honest, the first thing that I think of is this classic Homer Simpson audio clip. My co-founder Frank Addante often said I should write a book and base every milestone or event in my life on some clip from The Simpsons (I guess that is why the show it still going strong after all these years).

In any case, back to reality. Don’t get me wrong, I think the cloud idea is fantastic. Utility computing, capacity on demand, real-time scalability are all great ideas that allow maximum flexibility, provide massive cost savings and allow companies to maximize the computing power amassed over time. The one thing I don’t like about the cloud is that it seems a lot of people are very confused about the concept. I think this is quickly being pushed into the same category as “Web 2.0” and other classics.

My opinion is that simply offering your solution as a SaaS (or Software as a Service) does not constitute “being in the cloud.” While this is an important component to this relatively new way to offer software products today and adoption rates are very high, this is not the sole concept of the cloud. I think the company rPath does a good job at laying out the base components needed for adoption of the cloud computing model.

Here's the moral to my post. Whether we have the terminology right or wrong, the goal of the cloud is extremely promising. Being an infrastructure guy, I salivate at the opportunity to architect, deploy and manage such systems. I love scale, high capacity, on-demand access and repeatability/reusability. It is also exciting to keep pushing our own technology to allow our customers more flexibility when they deploy (whether software, hardware or virtual appliance).

I read an article today about how email addiction can be a sign of mental illness. This was certainly an interesting article that I enjoyed for several reasons:

1. It shows that people are relying more on email communications than ever before as a means of keeping in touch
2. It showcases the importance of the right message at the right time (quality of the message not quantity of messages)
3. I think Frank and I picked the right business to be in!

In all seriousness, mental illness of any kind is tragic. However, the article does demonstrate the impact the email has on our everyday lives. I can tell you first hand that email is addictive. While I don’t personally experience withdrawal symptoms when I'm away from email, I am usually glued to my mobile device, and I am always online. Mental illness aside, the article reinforced my belief that email is never a game of “more is better.” Content is king, but it has to be meaningful and sent to the right audience. Otherwise, it’s just a bunch of data moving from one hard drive to another.

As you may know, email is thirty years old and its underlying infrastructure was never built with security and accountability in mind. No one ever thought that email would become as widely used as it is today, that the Internet itself would be subject to so much abuse.

The original email and Internet systems that we know today weren't invented by Al Gore, but by our own government missile defense system group called the Advanced Research Projects Agency (ARPA), whose primary job was to handle research for all space and strategic missile research. NASA was then formed, and the activities of ARPA moved away from aeronautics and focused mainly on computer science and information processing.

One of ARPA's goals was to connect mainframe computers at different universities around the country so that they would be able to communicate using a common language and a common protocol. Thus the ARPAnet -- the world's first multiple-site computer network -- was created in 1969. In order to have an account on these systems you simply asked for one and they just gave it to you almost without ANY questions, completely overlooking security and accountability.

Well, obviously, as time went by and the systems got larger and more interconnected, some people figured out the vulnerabilities and started to send out the first of many billions of unsolicited messages now known as SPAM. The question now comes down to how we can possibly patch a hole this big. Email authentication technologies like DKIM (DomainKeys Identified Mail) are a start.

DKIM is a signature/cryptography-based sender authentication protocol developed in order to address the problem of forged email messages (missing security and accountability) and to allow an organization or individual to take reasonability for the message it sends, which has given rise to the concept of email reputation. Now, I won't bore you with the details of email reputation and authentication, but I do want to focus on why we got involved in this early on.

Email is now about as mainstream as any technology can be, yet the viability of email is continually being threatened by viruses, spam, spoofing, and phishing. All of these threats are shaking the confidence in email as a viable tool for communications and conducting business, and StrongMail is committed to help protect it. We have been participating in the DKIM standard since day-one, and we are proud to have our own employees acknowledged for their hard work in the standard.

StrongMail was the first technology provider to integrate support for all emerging authentication protocols into its outbound email products to simplify compliance with whatever standards are mandated. DKIM has since gained a lot of traction, and AOL, GMAIL, and Yahoo! now use it successfully in production.

Unless you're a member of the CIA, a Matrix super fan, or a cryptographic expert, signature-based authentication can be difficult to understand. In StrongMail, you don't have to think about any of that stuff, since we make it as easy as 1-2-3 with our step-by-step interface, which will either create, upload, or use the existing keys needed to properly sign and verify any email.

In fact, StrongMail is specifically designed to make it easy to work in the complex and ever-changing world of email standards. You even have the ability to apply authentication to certain email streams or campaigns based on your needs. Our offering is so simple that anybody with a mouse, keyboard, and monitor can institute email authentication.

Overall, DKIM brings accountability to the sender, establishes a reputation and confirms whether they should be sending email from a certain domain. By doing this, receivers can better separate mail streams from those who are good and those who are bad, which enables better anti-spam technologies and reduces false positives.

I read an article the other day that referenced StrongMail, and the topic was around sending speed. While it is true that you can send over 1 million messages per hour with StrongMail, you also have to realize that with great speed comes great responsibility. I’ll get to this last point in a second.

First, I agree with many of the points in the article. It is very important to have an email platform in place that is capable of not only sending but generating millions of dynamic and personalized messages for rapid-response situations such as alerts, quotes, notifications, reminders, ecommerce, etc. For those applications, you need to have a system that will allow rapid and dynamic scale when needed without having to add a lot of extra iron in the data center.

On the other hand, if you’re sending millions of messages really fast, you need to understand that your delivery is largely (if not solely) based on your sender reputation and how the ISPs view you at the time of send. This is why it is critical to have a Message Transfer Agent (or MTA) that gives you the ability to adhere to the sending rules the ISP’s have in place at any given moment in time.

When we built the StrongMail platform, we knew that in addition to speed, we needed to build in the control to follow best practices and send email in the way ISPs like to receive it. Offering both together allowed us to provide companies with the flexibility, control and visibility they need to see in real-time what is happening to their email streams and act accordingly.

Let’s face it; the reason companies send email is because, when done properly, it is a very effective and immediate communications medium that can create valuable customer relationships. However, when done improperly, email can cause brand degradation and reduce customer loyalty.

That’s why when it comes to email, it’s important to act responsibly. Just because you can send a million messages an hour, doesn’t mean you should.

It has been great times over the past 5+ years since founding StrongMail. I found out that Frank is now an aspiring actor. I often wonder “is there anything he can’t do?” so I thought I would share this great little vignette about his new company called The Rubicon Project. Enjoy.