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: 2) by egcagrac0 on Friday March 21 2014, @02:40PM
I have seen a lot of people helpfully suggesting simple solutions. Many of the suggestions miss a few critical points.
Exchange is not just email. Exchange is a fairly full groupware system - in addition to email, there are also contacts, address lists (shared among multiple users, magically updated for everyone...), calendars (individual and shared), and there used to be some shared document capabilities as well. Anyone who installed it at home to get an understanding of it for work probably uses (or used) several of these features.
IMAP misses a lot of the features. IMAP can handle some client-server mailbox synchronization, if your client and server agree on the Right Way to Do Things. IMAP doesn't do diddly for contacts or calendars.
Google doesn't do ActiveSync anymore*. ActiveSync is extremely useful for mobile devices. ActiveSync does handle contacts and calendars.
I learned these things back when I was the new guy saying "Why are we paying for Exchange if we're trying to save money? Why not just run (postfix/qmail/dovecot etc) instead?" The quick answers from the people who kept paying the bills were "Shared contacts" and "Calendars that work". (The other part of the answer - "we can hire a consultant to fix it if in-house staff can't make it work" - probably doesn't apply for a family mailserver.)
As for me, I am running Google Apps. I only set up aliases when I need a new name to be forwarded to a mailbox (bar@.net also goes to foo@.net - for pseudonymity). For most mail filtering, foo+soylent@.net style mangles [blogspot.com] work just fine. I fully understand that they're reading everything, and try to keep my goat porn mundane enough so that it doesn't pique extra interest.
*Google maybe does ActiveSync if you're a paying customer for Google Apps. Maybe. (This may be a thing that they kept on for existing users that isn't available for new customers.)