Messages from EAS senders have date/time stamp of when received, not sent
Problem reported by Paul R - November 2 at 7:38 AM
Resolved
Head scratcher here.  Person uses Outlook but DOES NOT use EAS.  Closes Outlook at 5 pm and goes home for the night.  Arrives the next morning and opens Outlook, which downloads all new emails.  

Emails sent by non-EAS users on the same domain arrive with their date/time stamp (as displayed in Outlook) reflecting when the message was originally sent.  That's good.

Here's the problem.  Emails sent specifically by EAS users on the same domain arrive with their date/time stamp (as displayed in Outlook) reflecting when the message was received that morning.  So a message sent at 6:00 p.m. the night before displays a date/time stamp in Outlook of 8:00 a.m. the next morning when it's retrieved.  Recipient has no way of knowing when the message was actually sent.  That's bad, because he's a high-level manager and needs to know when employees are actually sending the messages.

Again, this only seems to affect messages sent by EAS users.

Ideas?

5 Replies

Reply to Thread
0
Robert Emmett Replied
Employee Post
Paul, thank you for reporting this.  I have added it to our bugs list for further investigation.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Paul Blank Replied
Which versions of SM are affected, please?
0
Paul R Replied
We're seeing the problem on SM Enterprise 16.3.6870.
0
Andrea Rogers Replied
Employee Post Marked As Resolution
Hello, 

The fix for this issue was included in last night's release of SmarterMail 16.3.6885:
Fixed: Messages from EAS senders have date/time stamp of when the message was received, not sent.

Please upgrade SmarterMail and let us know if the issue persists. 

Andrea Rogers
Communications Specialist
SmarterTools Inc.
(877) 357-6278

www.smartertools.com

1
Paul R Replied
Hello,

We applied 16.3.6885 and it fixed the problem, but ONLY FOR senders using Microsoft Outlook.  Messages sent via the mail client on MacOS still show a timestamp when the user receives it.  So whatever fix you applied to EAS apparently needs to be applied to the EWS environment also.

 

Reply to Thread