[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1193
  • Last Modified:

URGENT URGENT You receive a read receipt that contains incorrect time information from Exchange 2010

OUTLOOK 2007 and Outlook Anywhere is working really fine with our Exchange 2010 server
in our Windows 2008 R2 Compaq Server ..

But we have a little problem on :
************************************************************
Request a read receipt for this message
(Outlook clients request read receipt from each other ON THE SAME LAN
IN THE SAME OFFICE ROOM)

Your message was read on Tuesday, April 06, 2010 7:31:11 PM UTC.

**************************************************************
BUT THERE IS A TIME HOUR PROBLEM  
Message was sent 10:30 PM UTC

but  the SENDER gets

Your message was read on Tuesday, April 06, 2010 7:31:11 PM UTC.

3 hours difference problem (EVEN THEY ARE IN THE SAME OFFICE )
**************************************************************
I did check the server time , time zone  and outlok clients time and time zone
they are all the same  (UTC +02:00) Athens ,Istanbul
and date and clock settings are also same..
Automaticly adjust clock for Daylight Saving Time also checked on server
and on outlook clients ...
**************************************************************

Wishing you nice day and hoping to get direct step by step solution for this problem ...
0
hnetsupport
Asked:
hnetsupport
  • 11
  • 10
  • 6
1 Solution
 
AkhaterCommented:
there from the following it seems right

the message was sent at 10:30PM in your time zone (Athens is currently at GMT +3) and not UTC

so in UTC it will be 10:30PM - 3hours = 7:30PM UTC

am i missing somehting ?
0
 
hnetsupportAuthor Commented:
Hi Akthater ..

This Istanbul utc +2  at server and clients ..they are all same and same clock settings ...

Look at please the following link : Microsoft solved the same problem in Exchange 2007 ...


Here is the link what they did in exchange 2007 ..

http://support.microsoft.com/kb/940259

CHEERS
0
 
AkhaterCommented:
When was the email sent ? at 10:30pm local time ?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
hnetsupportAuthor Commented:
Here is a new email  which is sent right now with read receipt request

Subject :Time Problem Mail  sent  at  Wednesday, April 07, 2010 6:18 PM

Your message was read on Wednesday, April 07, 2010 3:20:08 PM UTC.
0
 
hnetsupportAuthor Commented:
How come Microsoft is fixing same problem in Exchange 2007 by giving
Update Rollup 5 for Exchange Server 2007 ..

http://support.microsoft.com/kb/940259

ANY UPDATE ROLLUP  for exchange 2010 ?
0
 
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
0
 
AkhaterCommented:
My friend this is correct


Subject :Time Problem Mail  sent  at  Wednesday, April 07, 2010 6:18 PM

Your message was read on Wednesday, April 07, 2010 3:20:08 PM UTC.


The email was sent at Athens' time 6:18 PM and it was read at 3:20:08 PM UTC (UTC = GMT) so it was read 3:20 + 3 6:20pm
0
 
hnetsupportAuthor Commented:
Right Now I am installing

Update Rollup 2 for Exchange Server 2010 (KB979611)

I hope it works ...
0
 
AkhaterCommented:
did you ream my comment?
0
 
hnetsupportAuthor Commented:
I did not get what you  say : did you ream my comment?

So what is the solution my friend  ? what to do ? play with clients local time  even they are in the same office as with server ... they have all the same  time zone   utc +2 ...

I am really going crazy now ? it is really Exchange 2010 server's   nonsense
0
 
AkhaterCommented:
well this is by design, I am not aware of anyway to change it sorry
0
 
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
Do you have all roles in one Exchange 2010 server? Check time for all exchange servers and also... more important.. check time zone of your Domain controllers and global catalogs used by exchange.
0
 
hnetsupportAuthor Commented:
HOW COME AS EXPERT YOU EXPECT THIS AS BY DESIGN ...

You are sending email to your friend at sales department at 1 st floor ..  You are in the same building at 5 th
floor and you are getting 3 hours read receipt  ** incorrect time information from Exchange 2010 server

How come ?

Any how..... cheers All my best wishes goes to you  ... Take care my friend ...
0
 
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
Chill out hnetsupport.. you are right.. you are having a problem you should not have.. like i said check the time zone on your global catalog servers and on all exchange 2010 servers (hub in particullary) and also post the result of upgrade to roolup 2.. we'll dig this up.. :)
0
 
AkhaterCommented:
GreatVargas this is by design, in Exchange 2007 the read receipt time zone was based on the server's time zone and this was leading to confusion when clients were in different time zones, so in E14 (i.e. exchange 2010) it is now based on the UTC time zone

so it is not a bug
0
 
hnetsupportAuthor Commented:
Hiii GreatVargas

I did installed the  roolup 2 and started the server ... Same same crazy result ..Negative ..

I did check the time zone on the server ... IT IS THE ONLY ONE server  in the company .. This exchange server is in hub transport role ...

Time zone of server is
I did check the server time , time zone  and outlok clients time and time zone
they are all the same  (UTC +02:00) Athens ,Istanbul
and date and clock settings are also same..
Automaticly adjust clock for Daylight Saving Time also checked on server
and on outlook clients ...
********************************************    
0
 
AkhaterCommented:
:o) ok when you decide to believe me let me know
0
 
hnetsupportAuthor Commented:
Akhater:
GreatVargas this is by design, in Exchange 2007 the read receipt time zone was based on the server's time zone and this was leading to confusion when clients were in different time zones, so in E14 (i.e. exchange 2010) it is now based on the UTC time zone

so it is not a bug

HOW COME AKHATER YOU ACCEPT THIS ..... IF  I WORK WITH YOU IN THE SAME COMPANY BUILDING IN THE MORNING I WILL SEND YOU EMAIL WITH URGENT READ RECEIPT FOR BUDGET MEETING ** AND I WILL ACCEPT THAT YOU  ALREADY DID READ IN YOUR SLEEP IN YOUR DREAMS   3 HOURS BEFORE THE MORNING COMES OUT ..

HOW COME MY FRIEND YOU ACCEPT THIS BY DESIGN AND SAY
so it is not a bug
0
 
AkhaterCommented:
:) well when I say "by design" it simply mean Microsoft decided to do it like this, they might change it in a future SP or Rollup update the fact is there is nothing you can do about it right now nor I can

You just need to accept that the read receipt is at GMT time so if you know that you are at GMT+3 just add to it 3 hours.

sorry again, nothing I can do with it you will need to "accept" it and move on for now
0
 
hnetsupportAuthor Commented:
Do you have exchange 2010 server ? Can you please test with read receipt request email with your outlook clients ?


Cheers to All ...
0
 
hnetsupportAuthor Commented:
SO  IF I ACCEPT TO LIVE WITH THIS  problem until the  SP1  comes out ..  HOW  AM GOING TO BE SURE THAT MICROSOFT GUYS will add the solution to SP1 .. what is the best way to inform them to trigger them..

 
0
 
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/9b420c52-77d7-4a5d-a9b2-974df4c2dc9c

Akhater is right.. as stupid as it can sound (the Microsoft reason of "server does not know in which time zone your client is" is also stupid concerning read receipts) Exchange 2010 always use UTC time zone and you cannot change it. Sorry for the misinformation but i'm on UTC time and this problem never occured... and like i said this is a very "by POOR design" feature...
0
 
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
the best way to informed then is:

Open one ticket in Microsoft to solve that issue.. they will tell you that is a by design feature and you can tell them that you will move to another mail system if it's not solved.. if many people do that the fixup can appear in a SP.. if not this will continue as is
0
 
AkhaterCommented:
@hnetsupport I supposed you trust that when I tell you the the RR is sent on UTC time it means that I have at least tested it myself ?

I just said Microsoft MIGHT change it honestly I doubt they will since they actually just changed it from the TZ of the server to UTC time but who am I to decide

0
 
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
Read receipts are generated by the client so in my oppinion there are better ways to solve the "client time zone" problems... but like Akhater i dont decide nothing :)
0
 
hnetsupportAuthor Commented:
As  we all come into result :
Shame on Microsoft Exchange 2010 Server Product Design Team for the time being ..We hope they fix this in a logical acceptable way ...

Many Many Thanks to All of  you ... I am going out to relax my mind now ...Cheers to ALL ..
0
 
AkhaterCommented:
"I am going out to relax my mind now"

you need it :D
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 11
  • 10
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now