Bug 317817 - Timezone set wrong in sending headers
Summary: Timezone set wrong in sending headers
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.10.1
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-04 11:05 UTC by Orion
Modified: 2017-01-07 22:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Orion 2013-04-04 11:05:00 UTC
If I set timezone to CAT (UTC +0200) Kmail inserts in header of sent mails that it is in fact UTC +0204 - adding 4 minutes from somewhere.
I was made aware of this by Ben Cooksley when I mailed some issues to KDEPIM developers mailing list. According to him this makes my sent mail to be seen as possible spam by many systems.
I can not see anywhere else in my system or using Thunderbird that the timezone gets +4 minutes added

Reproducible: Always

Steps to Reproduce:
1. Set timezone to Harare,Zimbabwe (CAT)
2. Start KMail, create a mail or reply, send it
3. Check headers in sent-mail, in headers you find (eg) Date: Mon, 11 Mar 2013 09:30:03 +0204
Actual Results:  
sent date set to +0204 instead of +0200, thereby creating problems with spam checking systems

Expected Results:  
sent date set to actual timezone value, +0200
Comment 1 Dhiraj 2014-04-15 09:56:51 UTC
I'm facing a similar problem in a different timezone. 
My timezone is set as Asia/Kolkata (+0530).However, any mail I send has the timezone set to +0630.
The date and time in any other widget/application I use shows the correct time.
Backtracking through my 'Sent-Mail' shows the problem had first occurred on 12th Feb 2014. All mail before that has the correct timezone.
That might be around the time I added the KDE backport repositories. I'm not absolutely sure, but it's definetly around the same time frame.

I'm using Kubuntu 13.10 with
Qt: 4.8.6
KDE Development Platform: 4.12.3
kde4-config: 1.0
Comment 2 phanisvara das 2014-05-10 07:16:47 UTC
same thing happens to me, with TZ 'Asia/Kolkata'. all emails sent are stamped (localtime - 1 hour).

i'm using archlinux with KDE 4.13.0, but the same thing happens on another machine, openSUSE 13.1 / KDE 4.11.5

on the arch machine system time is set == UTC, on the openSUSE box to localtime.

here's the output of timedatectl (arch box):
------------------
[root@phani phani]# timedatectl status
Local time: Sat 2014-05-10 12:32:51 IST
Universal time: Sat 2014-05-10 07:02:51 UTC
RTC time: Sat 2014-05-10 07:02:51
Time zone: Asia/Kolkata (IST, +0530)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: n/a
------------------

korganizer appointments & reminders are also off by one hour. this can sometimes be corrected by choosing 'floating' TZ in korganizer, but doesn't always work.
Comment 3 John Layt 2014-05-10 08:38:25 UTC
On the assumption that the 20 people who've voted for this bug are also experiencing the problem, can you please all post your current config so we can try find a common pattern.  Please post your distro and distro version, KDE version, the time difference you've noticed, if the difference is just in the email header or also in korganizer, and the output from running "timedatectl" in a terminal.  If you don't have "timedatectl" on your sytem then you need to manually list the output from "ls -l /etc/localtime" or for Debian/Ubuntu based systems "cat /etc/timezone", and state if teh system time is set to UTC or not.
Comment 4 phanisvara das 2014-05-10 09:57:12 UTC
misunderstanding: when i went to vote for this bug, i saw that i could choose up to 20 votes for it, which i did. i'm all those votes because this is driving me to use thunderbird now, while in all other respects i greatly prefer kmail.
Comment 5 Orion 2014-05-10 14:00:18 UTC
problem still persists in Kubuntu 14.40, KDE 4.13

from sent-mail header:
Subject: HI there
Date: Sat, 10 May 2014 15:55:31 +0204
Message-ID: <1519502.giisbihdPd@sinclair-hp>
X-KMail-Identity: 62776042
User-Agent: KMail/4.13 (Linux/3.12.15-031215-generic; KDE/4.13.0; x86_64; ; )
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nextPart1619318.Gbib8DB56r"
Content-Transfer-Encoding: 7Bit

Output of timedatectl status:
sinclair@sinclair-HP:~$ timedatectl
      Local time: Sat 2014-05-10 15:54:31 CAT
  Universal time: Sat 2014-05-10 13:54:31 UTC
        Timezone: Africa/Harare (CAT, +0200)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: n/a
sinclair@sinclair-HP:~$ timedatectl status
      Local time: Sat 2014-05-10 15:54:35 CAT
  Universal time: Sat 2014-05-10 13:54:35 UTC
        Timezone: Africa/Harare (CAT, +0200)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: n/a
Comment 6 Orion 2014-05-10 14:19:45 UTC
change timezone to Zambia/Lusaka (same timezone UTC+0200):
from KMail:
Date: Sat, 10 May 2014 16:03:54 +0200
Message-ID: <1991255.oNBM25R7Xn@sinclair-hp>
X-KMail-Identity: 62776042
User-Agent: KMail/4.13 (Linux/3.12.15-031215-generic; KDE/4.13.0; x86_64; ; )
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nextPart2590304.hvEY000s8D"
Content-Transfer-Encoding: 7Bit

output of timedatectl status:
Local time: Sat 2014-05-10 16:03:03 CAT
  Universal time: Sat 2014-05-10 14:03:03 UTC
        Timezone: Africa/Lusaka (CAT, +0200)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: n/a
sinclair@sinclair-HP:~$ timedatectl status
      Local time: Sat 2014-05-10 16:19:05 CAT
  Universal time: Sat 2014-05-10 14:19:05 UTC
        Timezone: Africa/Lusaka (CAT, +0200)
     NTP enabled: yes
NTP synchronized: no                                                                          
 RTC in local TZ: no                                                                          
      DST active: n/a
Comment 7 John Layt 2014-05-11 18:22:06 UTC
Thanks.  I've raised this on the pim list and it does appear to be an issue in KTimeZone which the maintainer is looking into.
Comment 8 Denis Kurz 2016-09-24 17:57:24 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 9 Denis Kurz 2017-01-07 22:15:36 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.