09-05-2011 08:02 PM
When printing an email, the time received is incorrect on the printed version, but correct within the email itself. As an example, below is the "sent" info from an Xfinity email from today. It was sent at 5:15pm, but the source code (also below) shows 21:15 (9:15pm) which is obviously incorrect since it is only 7:58pm EST. I am using the full version of XC. Any ideas? Thanks much.
|XFINITY Mobile App - BlackBerry Download Link|
Return-Path: firstname.lastname@example.org Received: from omta20.emeryville.ca.mail.comcast.net (LHLO omta20.emeryville.ca.mail.comcast.net) (126.96.36.199) by sz0169.wc.mail.comcast.net with LMTP; Mon, 5 Sep 2011 21:15:49 +0000 (UTC) Received: from app034-fnc ([188.8.131.52]) by omta20.emeryville.ca.mail.comcast.net with comcast id V9C91h01B0qh9zg8g9CCgn; Mon, 05 Sep 2011 21:12:16 +0000 X-CAA-SPAM: 00000 X-Authority-Analysis: v=1.1 cv=Fc3M3d7+feNawxPGmUhl+bjYyw1h8ahZ2YvbKbJMdoE= c=1 sm=1 a=ijMkI9SILtQA:10 a=rl5eUP2J6s4A:10 a=rITDv7nW5hcA:10 a=IeuvsTkbp3w2ebjOMyDzug==:17 a=DLBGSgxYAAAA:8 a=C_IRinGWAAAA:8 a=6MyZ0KW2AAAA:8 a=ebjkH5-4w0poLw7nWF0A:9 a=R7TFgQCo6OfC9XcvWdoA:7 a=CjuIK1q_8ugA:10 a=tLKJx8WUvQ4A:10 a=U9NR-HKISwMq-xtgxzMA:9 a=Uqsr3L4gJ9T0RiDDoa4A:7 a=IeuvsTkbp3w2ebjOMyDzug==:117 Date: Mon, 5 Sep 2011 21:15:42 +0000 (UTC) From: XfinityMobileApp@comcast.net Reply-To: XfinityMobileApp@comcast.net
Solved! Go to Solution.
09-05-2011 10:58 PM - edited 11-28-2012 12:43 AM
Check your time zone setting in Xfinity Connect. Click Preferences / General / Version and select "Lite version". Then log out and back in again to access Xfinity Connect Lite.
In the Lite version, Click Preferences / Email / Timezone and select the correct time zone.
Then click Preferences / General / Version and select "Full version", and log out and back in again to return to Xfinity Connect Full.
If the email time zone setting was correct, check your computer's time zone setting. In Windows, you can reach "Date & Time Properties" through Control Panel, or by right-clicking the taskbar clock and selecting "Adjust Date/Time". Click the "Time Zone" tab, select the correct time zone setting, and click OK.
When done, try printing that email again and see if the problem is corrected. If the time is still wrong, please let us know.
09-06-2011 01:33 AM - edited 09-06-2011 01:50 AM
sewarddds wrote: ... It was sent at 5:15pm, but the source code (also below) shows 21:15 (9:15pm) which is obviously incorrect ...
Maybe not. The header says "Date: Mon, 5 Sep 2011 21:15:42 +0000 (UTC)". The "+0000 (UTC)" is the time zone, and as Beth says it means "Coordinated Universal Time", aka GMT or ZULU time. You didn't say what time zone 5:15pm was in. UTC is 4 hours ahead of Eastern Daylight time. If the message was sent at 5:15pm EDT, adding 4 hours to that gives us the 9:15pm UTC we see in the header. So if that 5:15pm was EDT, then the time and zone in the "Date:" line are valid -- it just looks a little weird. If that 5:15pm was not EDT, then there's a problem somewhere.
09-06-2011 03:00 AM - edited 09-06-2011 03:02 AM
One of the Comcast folks (I don't recall who exactly, sorry) posted a note awhile back that there was a bug when printing an email from Xfinity Connect. When you print a message, the code was getting and using the timezone setting from Xfinity Connect Lite, even when you were using the full version of Xfinity Connect. So if that timezone setting there was incorrect, even if your OS timezone setting was right, the timestamp on the printed email would be incorrect. The work around was to do exactly what Bruce mentions, switch to Lite, adjust the timezone setting to your local time zone, and then switch back to the Full version. The timestamp on printed emails should now be correct.
It's typical of most email systems to send messages with UTC timestamps (so everybody uses the same standard), and then the time is converted to a local time by the displaying client according to local timezone settings. So those headers look normal, if the messages was sent at 5:15 PM and the OP was in EDT. Now if the Lite timezone setting was something other that EDT, the printed message would have the wrong local timestamp due to the bug.
©2011 Comcast | Investor Relations | Press Room | Corporate Blog | Privacy Statement | Visitor Agreement | Comcast.com Feedback | Site Map