PMR0001
Member
- Outlook version
- Outlook 2016 64 bit
- Email Account
- Exchange Server
I previously used Exchange Active Sync, forwarding emails from a mydomain.com server to xxx@outlook.com (configured as an alias) and was able (I use Outlook 2016) to use yyy@mydomain.com as my sending address (i.e. someone receiving the email would see yyy@mydomain.com). To do this, outlook.com was configured with the appropriate server for mydomain.com.
Then funny things happened very recently. Previous emails disappeared and extra addressees were added to previous sent items. However, this was only on Outlook2016, outlook.com was fine. This also coincided with an email from microsoft announcing extra functionality for outlook.com. I believe servers changed at Microsoft.
I got round this by creating a new account on outlook2016, though unlike EAS, entering yyy@mydomain.com just led autodiscover to set up Outlook2016 with imap/smtp for mydomain servers. I got round this also by creating the account using xxx@outlook.com.
All well and good, until I discovered that whilst outlook.com sent emails from yyy@mydomain.com, outlook2016 was sending from either outlook_1VD2...@outlook.com or xxx@outlook.com. Try as I might, the best I could achieve was 'outlook_1VD2...@outlook.com sent on behalf of yyy@mydomain.com' which had to be entered for each and every email!
I have seen stuff about using DNS entries (CNAME or MX) but am unfamiliar with such things.
It is really disappointing that EAS worked fine and now has issues but the free Exchange, whilst it has extra functionality (e.g. draft folder no computer specific) cannot provide the correct send address in Outlook2016.
So, any ideas anyone, please.
Then funny things happened very recently. Previous emails disappeared and extra addressees were added to previous sent items. However, this was only on Outlook2016, outlook.com was fine. This also coincided with an email from microsoft announcing extra functionality for outlook.com. I believe servers changed at Microsoft.
I got round this by creating a new account on outlook2016, though unlike EAS, entering yyy@mydomain.com just led autodiscover to set up Outlook2016 with imap/smtp for mydomain servers. I got round this also by creating the account using xxx@outlook.com.
All well and good, until I discovered that whilst outlook.com sent emails from yyy@mydomain.com, outlook2016 was sending from either outlook_1VD2...@outlook.com or xxx@outlook.com. Try as I might, the best I could achieve was 'outlook_1VD2...@outlook.com sent on behalf of yyy@mydomain.com' which had to be entered for each and every email!
I have seen stuff about using DNS entries (CNAME or MX) but am unfamiliar with such things.
It is really disappointing that EAS worked fine and now has issues but the free Exchange, whilst it has extra functionality (e.g. draft folder no computer specific) cannot provide the correct send address in Outlook2016.
So, any ideas anyone, please.