Hello,
I’ve noticed a discrepancy in the time displayed in the ticket body when an transaction is entered via e-mail. Looking at the SMTP headers directly from the RT GUI it shows the time as being correct in the “Received:” sections of the header however the “Date:” field shows the time in GMT.
Environment:
RT v 3.8.5 soon to be upgraded to latest version running on RHEL4 x32 w/Apache, MySQL and FastCGI
E.g.
Correct time is:
Mon, 15 Apr 2013 17:57:38 -0700 as noted in the “Received” sections of the mail header.
Incorrect time shows as:
Tue, 16 Apr 2013 00:57:34 +0000 in the actual ticket Date: field of the message body.
What’s confusing is that the transaction header shows properly:
Mon Apr 15 17:25:51 2013 joe.schmoe - Ticket created
Then follows the CC:, Subject: and Date: where the date appears as GMT instead of local time.
The RT_SiteConfig.pm file config is set to:
Set($Timezone , ‘US/Pacific’);
I checked the Linux server time config and it points to America\Los Angeles using UTC.
Where else can I look to ensure that this “Date:” field reports the correct time zone?
Thank you in advance for any pointers.
~Pete_Jibe
Disclaimer: This electronic message may contain information that is Confidential or legally privileged. It is intended only for the use of the individual(s) and entity named in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from your computer. Do not deliver, distribute or copy this message and do not disclose its contents or take any action in reliance on the information it contains.
Hi,
“Date: …” you see in the history comes from email headers and RT doesn’t
change them. We wrote code to deal with this, but I don’t know if it’s in
4.0 or if it only would be in 4.2.On Wed, Apr 17, 2013 at 3:46 AM, Pete Beebe pete.beebe@jibeconsulting.comwrote:
Hello,
I’ve noticed a discrepancy in the time displayed in the ticket body when
an transaction is entered via e-mail. Looking at the SMTP headers directly
from the RT GUI it shows the time as being correct in the “Received:”
sections of the header however the “Date:” field shows the time in GMT.
Environment:
RT v 3.8.5 soon to be upgraded to latest version running on RHEL4 x32
w/Apache, MySQL and FastCGI
E.g.
Correct time is:
Mon, 15 Apr 2013 17:57:38 -0700 as noted in the “Received” sections of the
mail header.
Incorrect time shows as:
Tue, 16 Apr 2013 00:57:34 +0000 in the actual ticket Date: field of the
message body.
What’s confusing is that the transaction header shows properly:
Mon Apr 15 17:25:51 2013 joe.schmoe - Ticket created
Then follows the CC:, Subject: and Date: where the date appears as GMT
instead of local time.
The RT_SiteConfig.pm file config is set to:
Set($Timezone , ‘US/Pacific’);
I checked the Linux server time config and it points to America\Los
Angeles using UTC.
Where else can I look to ensure that this “Date:” field reports the
correct time zone?
Thank you in advance for any pointers.
~Pete_Jibe
Disclaimer: This electronic message may contain information that is
Confidential or legally privileged. It is intended only for the use of the
individual(s) and entity named in the message. If you are not an intended
recipient of this message, please notify the sender immediately and delete
the material from your computer. Do not deliver, distribute or copy this
message and do not disclose its contents or take any action in reliance on
the information it contains.
Best regards, Ruslan.
Thanks for the reply. I just checked the 4.0.10 version we have running in our dev environment and it appears the issue still exists on that version. I just noticed that v4.0.11 is now available, when I get a moment I’ll upgrade to that version and retest.
~Pete_JibeFrom: Ruslan Zakirov
Sent: Wednesday, April 17, 2013 12:50 AM
Subject: Re: [rt-users] RT ticket body shows GMT time instead of PST (GMT -7) in the Date: field
Hi,
“Date: …” you see in the history comes from email headers and RT doesn’t change them. We wrote code to deal with this, but I don’t know if it’s in 4.0 or if it only would be in 4.2.
Disclaimer: This electronic message may contain information that is Confidential or legally privileged. It is intended only for the use of the individual(s) and entity named in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from your computer. Do not deliver, distribute or copy this message and do not disclose its contents or take any action in reliance on the information it contains.
Hi Ruslan,
Upon further testing it seems that v4.0.10 does have this fix in place for new transactions, only.
It doesn’t appear that it corrects older RT records. Does that functionality sound correct to you?
Either way, it’s good to know that the newer release addresses this for new records.
Cheers,
~Pete_Jibe
Disclaimer: This electronic message may contain information that is Confidential or legally privileged. It is intended only for the use of the individual(s) and entity named in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from your computer. Do not deliver, distribute or copy this message and do not disclose its contents or take any action in reliance on the information it contains.