Are Cloud Servers Bad for Sending Email?

Published: May 2nd, 2011

Public cloud servers are great for many things; however, sending email is not one of them.

Why Cloud Servers are Bad for Sending Email

The IP address spaces used by the major public cloud vendors (i.e. Amazon, Rackspace, etc.) for their cloud servers are well known and are generally black- or gray-listed by anti-spam systems. Additionally, many of the IP addresses in use by these systems are already “polluted” from previous abusive use by spammers.  When you set up a new cloud server, you could be easily assigned a “bad IP”.  Even if you do not inherit a bad IP reputation from the previous user(s) of your new IP, your server is still in the general set of IP addresses of the cloud and thus considered a possible spam source.

We have investigated several services that claim to offer “Cloud-Based Outbound Email” and have found that many use cloud servers for things like scanning email messages for spam and viruses, but use physical non-cloud servers for the actual sending of email.  This is obviously not true for all companies, but it points to the fact that if everyone might be affected, the solution is to NOT send from the cloud (directly), and that many companies just use the word “cloud” for its marketing impact.

How Did Cloud Servers get a Bad Email Reputation?

The “utility computing” model of the cloud is to blame. In the interest of making these servers and services as cheap as possible and to be able to charge for “by the hour with no setup fee”, there are generally few bundled services included some of which are 1) zero customer support, 2) little pre-sales work, and 3) minimal, if any, validation of new customers. All that time would increase prices.  In short, you signup with a name and credit card and get going almost immediately.  All you have to do is agree to “terms and conditions” by checking a box (how much do spammers care about that?)

Spammers and fraudsters take advantage of this easy to buy, inexpensive service to setup servers for sending spam or performing other abusive actions.  They do not care if they get shutdown fairly quickly because:

  • they are using stolen credentials and payment information
  • it is so easy to setup a basic cloud server, that there is not much time lost, and
  • even if they get shut down “fairly quickly”, they have still done their damage, sent some of their spam, etc.

Once they get shut down, they go to another public cloud server provider somewhere else under another stolen identity and do it again.  They can even automate this signup process by using the available APIs to these services.

The above scenario contributes to the pollution of the reputation of IP addresses and the public cloud servers in general.

With physical dedicated and managed servers, you typically interact with a Sales staff, sign a real contract, and undergo some level of validation (even if that happens behind the scenes).  This serves to block most of the fly-by-night spammers and fraudsters who use these services and therefore keeps these IP address spaces much cleaner.  The more validation and attention that is offered by a sales and support staff before signing up their customers, the cleaner the IPs are.  This is why, for example, managed servers at Rackspace have an excellent reputation that generally exceeds that of dedicated servers offered by commodity server providers.

If you are sending important email from a cloud server, to avoid the risk of your emails getting blocked by spam filtering services due to poor IP reputation, you should consider smart hosting through LuxSci’s High Volume Outbound Email service.

One Response to “Are Cloud Servers Bad for Sending Email?”

  1. How to Avoid Public Cloud Server Email Blacklists | LuxSci FYI Says:

    […] Home » FYI Blog « Are Cloud Servers Bad for Sending Email? […]

Leave a Comment

You must be connected or logged in to post a comment. This is to reduce spam comments.

If you have not previously commented, you can connect using existing social media account, or register with a new username and password.