We plan to upgrade this weekend.

Updated, no issues so far...

We updated during last night... :-(

EWS-protocol at least in conjunction with eMClient v8.2.1659 could be kind of "broken" - we can receive and send emails and they are being synced but:
sender name is showing at beginning with "nobody@invalid.invalid" and then on behalf of "original from/sender". This started right after updating our SmarterMail intallation to Build 8083 (updated from Build 8055)

Webmail is ok, EAS is ok - currently only at eMClient/using EWS-protocol this strange/garbage in front of the sender-information. :-( Due to the fact that we have upto 100 eMClient with EWS-protocol users this is kind of "fatal" for us. :-(

Its an emClient / No sender issue.  We have a custom build for this. Open a ticket with support.

Tim:

Is it necessary for any servers with connected EMclient users to update to the custom build?

Thanks.

Its a display issue only.  If you want to change the behavior, you can request a custom build.

@Tim: good that you were able to figure it out and that a fix/custom build will be available.

We had issues with Spam / our main IP having entries in spamlists, so such "disply-issues" are now very irritating our employees... they think that such messages could be another kind of Spam or Fake - so it is necessary to have this fixed/being disklayed correctly. This issue started with Build 8083, so probably you fixed somd EWS-protocol issue - and this s not correctly implemented at eMClient and your dev-team now created a workaorund for affected eMClient versions?

What do I have to report to eMClient-team, what they need to fix in their mailclient? Or did you already contacted eMClient directly in case so that they know what they need to fix?

Thomas, contact support and install the build if it is a concern.  

@Tim: I already have a ticket open ( 147-29A65E06-0B07 ) - Probably I was one of the first who reported this issue (even before I posted it @community to see if already anybody else is seeing our strange behavior with eMClient/EWS.

Right now I am waiting until Tony has the downlaod-link to pass it to me - at first he was not able to reproduce my reported issues. Perhaps he used a different eMClient version/buld.

We love emClient... Anytime a user or Company wants away from Outlook, we point them to emClient, those that have gone with them are very very happy.

The custom build 8087 fixed the issues with nobody@invalid.invalid (on behalf off) for our systems (running eMClient v8.2.1659). Thank you very much.

and yes, I like eMClient / I suggest using the EWS-protocol for best results/feautres (mail, calendar, contacts, ...).
And I really hope that some missing/not yet supported "Exchange-features/'functions" will be coming with one of the next SmarterMail beta builds.

Thomas,

As Tim noted, we have been working closely with eM Client to make sure our systems work well together over EWS. The current versions of SmarterMail and eM Client provide a very comprehensive Exchange-like experience, and our coming beta and eM Client's current beta are going to be improving that.

What kind of Exchange-like capabilities do you feel are currently missing? I hope that most of them are already included in our coming beta, but if there's something we're missing, we'd like a chance to review it.

I didn't understand one thing though.

With emclient and smarteremail, it is better to use ews and / or imap

Is there any difference in performance between the two?

@ Sabatino:

EM Client and others desktop clients software that support it are ALWAYS better if used with EWS/MAPI.

On smartphone/tablets it's probably better to use EAS (some mobile client software can use EWS, but I'm not sure if they are better on it or on EAS)

IMAP is a limited protocol by it's design...

Can someone email the link to build 8087 (or later) to dave at tm dot net?  We only do upgrades on weekends and I don't want to upgrade to 8083 knowing it has this problem.  Thanks in advance.