Microsoft Azure Websites - Custom domain mail

Question

Microsoft Live Custom Domains are now shutting down. I have been using this service for e-mail hosting for all my Microsoft Azure Websites, but now it is gone and no viable repl

Answer 1

You can install a Free Mail Server on a Virtual Machine on Azure like:

https://www.hmailserver.com/download

Answer 2

I just finished installing a mail server in Azure in a Linux virtual machine. So far seems ok.

The total cost of operation is about 10€ a month since neither Ubuntu (the OS) nor iredMail (the mail server) nor Postgres (the database) have any licensing fees.

Regarding the block on Azure IPs I do believe that most users saying that did not correctly configured their servers. And by that I mean that they didn't configured the PTR reverse DNS on Azure, which allows other mail servers to check if that IP is allowed to send and receive mail from that domain.

Also make sure you add the SPF DNS entry for your mail server. You can't blame a mail server to blacklist you if you don't minimize the risks of SPAM.

Hope this helped you.

Useful links:
IredMail Server - http://www.iredmail.org/
Reverse DNS in Azure - http://azure.microsoft.com/blog/2014/07/21/announcing-reverse-dns-for-azure-cloud-services/

Answer 3

you could run a Ubuntu VM in Azure and set up Postfix

Answer 4

Zoho provides a Google Apps like deal for 5 users for free: https://www.zoho.com/mail/zohomail-pricing.html

• Up to five users
• 5GB/User
• 25MB attachment limit
• Web access only
• Email hosting for single domain

Answer 5

Your cheapest option is to have one (single) google apps account which will cost you around $5 per month. Make it something very general like mail@yourdomain.com. Then in the google apps dashboard make it a catch all address. This will make the single inbox catch all email for accounts such as Sales@, support@ bob@ or whatever at your domain.

Then you can set Gmail filters to sort (label) each incomming message based on who it was sent to. For example you can have messages sent to frank@ automatically labeled as frank.

Next you want to create regular old gmail accounts for all of your individual users. I am going to follow the example of creating a box for frank@company.com for this instance.

1. Create Google Apps primary account (catch all) as mail@company.com
2. Create Gmail account for frank.company@gmail.com (regular gmail account)
3. Create filter rule on Google Apps account for all messages sent to frank@company.com to be forwarded to frank.company@gmail.com. You can further mark them as read or delete them upon forward.
4. In the frank.company@gmail.com create a sending alias as frank@company.com. Google will give you a 4 digit code, and now when logging in as frank.company@gmail.com i can both send as frank@company.com and recieve all email since its forwarded to this account.

Also make sure to set default reply:to addresses in case you send from the frank.company@gmail.com address.

Using the technique above you can get all the benefits of having a pro google apps account (dkim, spf, 25gb inbox) and with a little bit of configuration you can setup multiple gmail accounts which run off the single account. We use the technique above and it works flawlessly. The only thing that doesn't work is mailbox delegation, which is not that great.

If you wanted to save the $5 you could get away with using something like GoDaddy free email forwarding, but then you would be limited to godaddys 250 message limit per day.

The approach above just works.

Answer 6

I feel your pain. Had to have some tough talks with many of my customers when the free Google Apps option was discontinued.

I found two routes:

1. Find a hosted Exchange type solution. This has the advantages of any hosted solution. It is managed for you. You can get started with around 50 USD / user / year and services are provided by the likes of Microsoft, Google and Rackspace, like stated in the other answers.
2. (Which is the route I chose) Host your own Exchange server on AWS EC2 or Azure. Thanks to Microsoft License Mobility, you can install an Exchange license on a cloud server and provide email addresses for your customers` domains yourself. This will allow you to share the cost of the Exchange license between all your customers and if you reach the critical mass, this can save a lot compared to the pay-per-user-per-month models for most hosted solutions.

I am stil looking for a free alternative, but have yet to find one that can match the features that were available in the free version of Google Apps.

EDIT: I was thinking about this again last night and came up with another idea. I am not a Linux guy, so I would not be happy to do this for production mail server. For someone who is "bilingual" (i.e. ok with both MS and Linux solutions) or of a more adventurous nature than me, could take route 2 with a linux server and an open source mail server solution. I am sure this will lower the cost even more significantly, since you will not need to pay for the mail server licence and also per-hour instance costs for Linux servers are lower. This might even create a whole new revenue stream.