Feb 11 2018 08:52 AM
Feb 11 2018 08:52 AM
I need some clarifications between a few things :
For instance :
1- I can set up a personal email address (me@mydomain.com) in the settings to change the from-line of the composer. So I can use that email address to send an email within Outlook.com. And I can have those message sent to that email address forwarded to my Outlook.com account => FREE > That's what I'm doing
2- I can go premium with a custom domain and therefore send and receive messages from and to outlook.com => PAID (granted this includes several users, but this would only concern me)
3- I can use this same personal email address as an alias and, if I'm not mistaken, send messages from that address from Outlook.com => FREE
If someone can clarify all this.
Also If I do #1 and #3 could there be some conflicts by having a from-line similar to an alias?
Feb 11 2018 11:13 AM
Solution1 and 3; With a Connected Account, you are sending via the original SMTP server of the domain so it's less likely that the message will get marked as spam (and also offers the option to collect your mail). If you are sending it as a pure alias, you are using the SMTP servers of Outlook.com so it will more likely get marked as spam (since they don't host your mailing domain), or you are sending it "on behalf of your custom domain" and would actually use your outlook.com address (which is also visible to the recipient) and significantly reduces the risk of having your message marked as spam.
2; Discontinued service, although several Premium features are now part of an Office Home / Personal subscription.
Note that for proper custom (vanity) domain support, it is currently recommended to get an Office 365 for Business subscription which contains Exchange Online.
Feb 11 2018 11:55 AM
Feb 11 2018 12:46 PM
Outlook.com Premium as a separate product has indeed been discontinued.
See: https://premium.outlook.com/
And: https://blogs.office.com/en-us/2017/10/30/premium-outlook-com-features-now-available-to-office-365-s...
The Custom Domain feature (full hosting of the email domain for up to 5 addresses) is no longer being offered via Outlook.com but only via Office 365 for Business (supports much more addresses and features).
If you already have an Office 365 subscription or only want to use your mail via browser and/or on mobile mail apps, then Exchange Online is the most affordable solution being offered;
https://products.office.com/en-us/exchange/exchange-online
Feb 11 2018 01:28 PM
Feb 11 2018 01:54 PM
No, you don't have to but it makes the configuration slightly more complex.
Using forwarder in Gmail and a (Send Only) Connected Account in Outlook.com is indeed the recommended approach when you already have a custom domain mail hosting provider and don't want to make any additional costs.
Feb 11 2018 02:00 PM
Feb 11 2018 02:16 PM
It's called Internal Relay;
https://technet.microsoft.com/en-us/library/jj945194
In it's simplest form, you'd create a forwarder for your address from your Gmail custom domain to the <tenantname>.onmicrosoft.com address of Office 365 (or another alias), leave the MX records with Gmail and add an additional SPF definition for your domain to validate Office 365 as a sender for your domain or configure a Send Connector so that Office 365 routes all your mail via Gmail.
This is basically the same approach as in Outlook.com but then scalable for many more users (as you only need to configure the Send Connector once).
You can also do the reverse and make Office 365 the authoritative host for your domain and configure Gmail as a relay. You'd then configure Mail Users in Office 365 to forward the mails (no license is needed for Mail Users). This would make sense when the majority of your accounts is hosted at Office 365.
Feb 11 2018 02:25 PM
Feb 11 2018 02:31 PM
You're welcome! :)
Feb 11 2018 11:13 AM
Solution1 and 3; With a Connected Account, you are sending via the original SMTP server of the domain so it's less likely that the message will get marked as spam (and also offers the option to collect your mail). If you are sending it as a pure alias, you are using the SMTP servers of Outlook.com so it will more likely get marked as spam (since they don't host your mailing domain), or you are sending it "on behalf of your custom domain" and would actually use your outlook.com address (which is also visible to the recipient) and significantly reduces the risk of having your message marked as spam.
2; Discontinued service, although several Premium features are now part of an Office Home / Personal subscription.
Note that for proper custom (vanity) domain support, it is currently recommended to get an Office 365 for Business subscription which contains Exchange Online.