Dev.SN ♥ developers
Sections
Dev.SN
Jaruzel writes:
"I have an on-premises Microsoft Exchange system that hosts my families personal email, which has gone through several upgrades over the years. However Exchange 2013 is now too bloated for my needs, and I find myself wanting to migrate my email services to a cloud provider.
The kicker is that although I only have about 5 live accounts, I have over 200 email aliases attached to those accounts. Most of the cloud providers out there do not support this configuration, or charge per 'address' which makes the cost prohibitive for personal email.
Do any SoylentNewsers know of, or can advise the best way to migrate this lot out of my garage without losing all my aliases or having to pay through the nose?"
This discussion has been archived.
No new comments can be posted.
Migrating Local Email into the Cloud?
|
Log In/Create an Account
| Top
| 1000 moderator points
| 64 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I'm not a robot like you. I don't like having disks crammed into me... unless they're Oreos, and then only in the mouth.
-- Fry
(Score: 4, Interesting) by Anonymous Coward on Thursday March 20 2014, @05:34PM
I hope that everyone on "SN" knows that "cloud" is just bullshitese for "hosted".
If you want, deploy your own remotely hosted mail server (IMAP, POP3, SMTP, etc.) -- something like Webmin/Virtualmin or a webhosting control panel like CPanel makes this a bit easier, particularly if you are used to the Exchange GUI. This can work just fine on a $10 VPS.
There's a current article series on ArsTechnica that addresses doing this the hard way.
That said, I don't think Google Apps has any problem with that many aliases, and does not charge for them as long as there's only one mailbox. You won't find anything much cheaper or with better uptime.
(Score: 2) by Fluffeh on Thursday March 20 2014, @05:46PM
...knows that "cloud" is just bullshitese for "hosted"
Oh Anon, if only you weren't anon, I would be your best-est friend ever. That little snippet just made my entire day! Utter gold!
(Score: 0) by Anonymous Coward on Thursday March 20 2014, @05:56PM
Thanks Fluffeh. Some day I will get a real account and our forbidden love will... I'm making myself sick here. But we have already interacted positively here before, I think. Have a great week/weekend.
(Score: -1, Troll) by Anonymous Coward on Thursday March 20 2014, @06:24PM
(Score: -1, Troll) by Anonymous Coward on Thursday March 20 2014, @06:50PM
lol
(Score: -1, Flamebait) by Anonymous Coward on Thursday March 20 2014, @07:11PM
(Score: -1, Flamebait) by Anonymous Coward on Thursday March 20 2014, @07:13PM
The top fields for bullshitese clouding up information has always been politics and religion. When they take money for their promises the lists of promises generally goes to /dev/null and the delivery dates are some undetermined points in the future.
Don't forget, the buck stops at 127.0.0.1, whether you have the information and cash securely there or not.
If you have your head up in the clouds, your vision is going to be foggy.
One spin or another..
(Score: 3, Informative) by edIII on Thursday March 20 2014, @07:14PM
It's not just hosted. It implies redundancy in many use cases as well.
A simple hosted solution does not always have that. Is that VPS redundant? Is it with a provider that has live migration of running instances?
Amazon EC2 could be a place to start for something like that.
In this case though, I would be looking for a SAAS company that will provide some redundancy and data backups and just provide the service itself.
I myself would look into Zimbra. It's very extensible and relatively cheap. If you demand MS compatible technologies look into Appriver or equivalent to provide it. Both should allow you unlimited aliases, and a couple thousand is not huge. It's just an alias and represents no substantive impact on the infrastructure other than an initial lookup from the SMTP server.
The best part is that your costs of maintaining that Server 2013 should be large enough to get a very nice SAAS service someplace and not have to worry about it again.