Solved OL 2016: You will not believe this one!

[markg2]

Installed Office 365 several days ago just for (temporarily) OL 2016.

2 email accounts: Outlook.com and a Kerio Connect (a multi platform exchange type account) installed as IMAP for our domain name.

The Kerio account is the default.

My wife came upstairs last evening and said she issued an email from the Kerio account and the email appeared in the Outlook.com sent box. I said 'no way' and looked for myself.

The email in the the Outlook.com sent box clearly said 'from' the Kerio account.

I sent a test email myself from the Kerio account (it clearly said 'sending from 'KOC' at the top) and darn if it didn't also appear in the Outlook.com sent account.

I bet a nickel no one here has had this experience or has a clue as to why!

Mark

 

[Ranger4]

Apparently it's not an unheard of problem, so have a look at this MS website for a solution.

https://support.microsoft.com/en-us/kb/2391896

 

[markg2]

I really thought I was the only one

One would think if MS knew of this sporadic problem since OL 2007 they would have devised a solid fix by OL 2016.

Thanks,

Mark

 

[Ranger4]

Yes that's true, they don't always fix problems, which could be due to how many problem reports they get.

Anyway did you get it fixed?.

 

[markg2]

Wife's working on the machine so it'll have to wait till Tuesday a.m. I'll let you know if it 'doesn't' work.

 

[markg2]

I reviewed the directions anyway and now I'm not so sure they'll work since they were written before OL 2016.

They say for 2007 run scanost before adding back the second account. For 2010 redownload the ost file.

So it seems something needs to be done after redirecting the misdirected messages, removing Outlook.com and before adding Outlook.com back.

Maybe I should post this on the MS answers forum (which I've never had a ton of luck with).

 

[markg2]

Problem was not 365 or the Outlook.com account but the second account, Kerio Connect. My ISP apparently hadn't installed the latest version of Kerio's Connector which resolved the problem.

 

[Ranger4]

Thanks for getting back with the solution & glad to hear all is now working.