Random problem of replacing recipients
Problem reported by Jean-Guy Dubois - March 17, 2017 at 3:10 AM
I opened a support ticket two month ago about this problem. Without correction for the moment.

Since upgrading from v14.x to v15.x, Some Outlook 2013 users have seen their recipients replaced by others in the messaging domain.
For example : jerry@mydomain.com becomes john@mydomain.com
The replacement occurs when sending.
It seems that the wrong recipient is always the next item in the Gloable Address List
The wrong recipient appears in the sent items and the server logs show that Outlook has requested sending to the wrong recipient.
The problem was reproducible with the same recipients.

I understood that Outlook's autocompletion played a role. Emptying the cache eliminated the problem. But not its reappearance in a random way, for random recipients.
As a result I have disabled the auto completion of Outlook.

The frequency of the problem was reduced but I had new cases since.
This time the problem was not reproducible. A second sends, to the replaced recipients the first time, was done correctly.

Without autocompletion, users rely on the global address book that is synchronized through sharepoint link.
We encounter the problem only between addresses of the only domain managed by the server. Addresses that are in the GAL.

We have never had such a problem for years, until the update of v14.x to v15.x

Has anyone else got the problem?
If yes, what info did I not show?

Thank you.

12 Replies

Reply to Thread
Yes, we know this issue well and it's happened to us 3 times since we "upgraded" from v14 to v15 last October.  We've had a number of tickets opened and SmarterTools has been pretty unresponsive about getting this fixed now that all of the devs appear to be working on v16.  Overall the situation sucks and we're looking at moving to Exchange. 
We've supplied ST support with lots of info including videos that show the problem, screenshots that show duplicate entries in the Outlook GAL SharePoint list, errors we've found in the GAL SharePoint list using MFCMAPI (https://mfcmapi.codeplex.com/), etc. but have seen little to nothing in return. This is a completely unacceptable bug with significant confidentiality issues. We've had the wrong staff receive salary and compensation communications. And the worst part is that it's completely unpredictable--we're at the point where we have ZERO confidence in the product.  Other than the "sorry for the inconvenience" token response, support has done little more than to tell us there's nothing they can do because all of the devs are working on getting v16 out the door.
We've been a happy customer since 2008 and it's pretty disappointing to get kicked to the curb this way.
Hello All,
   Any update about this?
   I've found this issue on both SM15 and SM16. This will be happened  when you create GAL
via sharepoint service (Add to Outlook feature), and then you doing version upgrades
for some times. 
    You will need to remove the current GAL sync, then re-create it. And you don't know when
it will be happened if you upgrade your SmarterMail again and again. (happened randomly)
    I believe this will kill us for some important and confidential emails...............
Juan Lai
Hello There, we have the same problem at one of our customers side and this is very big problem as there some emails went the wrong way :-( ! Marco.
I am a little late to this thread but I have the same issue - and it is unacceptable. It is causing confidential emails to be sent to the wrong recipients. I have opened a ticket. 
Frankly, the fact that SmarterTools can't be bothered to take the time to post any form of reply on this VERY serious issue sucks.  This problem is a ticking time bomb that will eventually affect anyone using SM with Outlook.  Just think of the consequences of having a random employee within your organization receive a very confidential email meant for someone else. 
It would be good to have a response from ST on this topic.
Tim Uzzanti Replied
Employee Post
We have had about 10 customers report the issue to our Technical Support team over the last year and we sent them the following updates:
After spending 100's of hours debugging the issue internally and on customers machines with custom builds etc... the result was a bug in Microsoft Outlook.
We opened a case with Microsoft and they said they are no longer updating the functionality in Microsoft Outlook.  This is the same answer we received related to Exchange ActiveSync.  Each and every update of Microsoft Outlook on Windows keeps hiding features and functionality.
We are currently working on a MAPI implementation that will available VERY shortly.  All Windows users using Microsoft Outlook will want to move to MAPI and all MacOS users using Microsoft Outlook with want to use our existing Exchange Web Services protocols.
In Microsoft's defense, these protocols are newer and / or more up to date and expose more Exchange functionality.  For example, many more sharing features and group features will be available etc!
The next couple months will be exciting!
Tim Uzzanti
SmarterTools Inc.
(877) 357-6278
Will SMv15 users benefit from these exciting couple of months, or just v16?
Tim Uzzanti Replied
Employee Post
Microsoft originally made EAS (Exchange ActiveSync) for mobile.  All mobile device manufacturers support EAS and its not going anywhere.  Its the perfect solution for mobile!
In Windows 10, Microsoft decided to offer EAS in the Windows Mail, Calendar and People applications and it works great.  These were all built from the ground-up with EAS in mind!
Then, Microsoft decided to integrate EAS into Microsoft Outlook which was great because we could then prioritize an EAS implementation over MAPI and that would allow our customers to license ONLY ONE protocol which their users could use on both mobile and desktop!  FYI, we pay Microsoft for every EAS license our customers use.  When you buy our add-on a majority of that goes to Microsoft!
EAS has been available in Microsoft Outlook for almost 2 years.  Microsoft has fixed most of the issues but because Microsoft Outlook is so legacy and really wasn't intended to work with a protocol like EAS, there are some cases, especially with REALLY LARGE mailboxes, where it could be a little problematic.
I personally use Microsoft Outlook 2016 with EAS on my 2 gigabyte mailbox.  It works perfect.  I also use EAS on my iPhone and Android phone.  I also have Windows Mail connected via EAS.  I then use Microsoft Outlook for Mac via EWS.
From time to time I use Mac Mail via EWS (Exchange Web Services) but Apple just blew up their Exchange integration with their most recent 10.13.2 release of MacOS.  We have already contacted Apple and provided information to their engineers.
Soon, we will be offering MAPI which will be primarily for Microsoft Outlook users on Windows!  This bugs me because now you need MAPI and EAS to provide full synchronization across desktop and mobile.  But, this is what Microsoft wants and my guess is most of their decisions are for financial reasons!  
Microsoft is even pulling functionality off Outlook.com and Google stopped supporting EAS on Gmail unless you are part of the G-suite.  Google moved to use DAV for synchronization to avoid paying Microsoft.
Its all a nightmare and we're trying to make it as seamless and cost effective as possible for our customers! 
Hope this helps, Tim
Tim Uzzanti
SmarterTools Inc.
(877) 357-6278
So is the thread about EAS and Outlook saying that it should fix the sending to incorrect recipient problem? If it is , I have to disagree. We have been switching users to EAS due to problems with our IMAP server. We are still having the problems with addresses being replaced at time of sending. Any more ideas? This is a huge problem.
Oh and if it is due to a bug in Outlook, why did it manifest itself in our case as well as others when upgrading from V14.x?
Tim Uzzanti wrote the problem is a bug in outlook.
But the problem has appeared with the upgrade of version 14 to 15 of smartermail !

Reply to Thread