The TZ is CEST. If I send an email at 19:00 CEST, it gets sent as "17:00 +0200". "Fancy headers" will show "17:00". "Brief headers" will show "19:00". This is utterly misleading. kmail2 should either use UTC time ( "17:00" ) or CEST time ("19:00 +0200"). Incoming email from people not using kmail will correctly suit this behaviour. Side note: it would be nice to see the TZ or the offset in Fancy headers/Brief headers, but probably this should be considered separately. Reproducible: Always Steps to Reproduce: 1.send an email 2.check the Date header on the sent email 3.the header is wrong Actual Results: Wrong date headers make difficult to track the mail order in e.g. a conversation with many short-timed replies Expected Results: Consistent, correct "Date" headers $ timedatectl Local time: mer 2016-04-06 07:48:14 CEST Universal time: mer 2016-04-06 05:48:14 UTC RTC time: mer 2016-04-06 05:48:14 Time zone: Europe/Rome (CEST, +0200) Network time on: no NTP synchronized: no RTC in local TZ: no
I'm in England (London). Unfortunately, my company sets up system to America/New_York and I don't have sudo rights to change it. So we use TZ=Europe/London to correct timezone. Every time I send an email using kmail, the mail is sent with twice the offset. Example : $ env | grep TZ TZ=Europe/London $ date jeu. nov. 17 09:37:53 GMT 2016 $ TZ=America/New_York date jeu. nov. 17 04:38:03 EST 2016 If I send a mail it is sent with time=14:38 (= 04:38 + 5h00 * 2, 5h00 = time lag between London and New York) I've played a little bit with TZ before sending an email with kmail. If I set TZ to America/New_York (-5), mail is sent with New York's time : correct If I set TZ to America/Halifax (-4), mail is sent with New York's time + 2 hours : incorrect (should be New York + 1 hour) If I set TZ to America/Sao_Paulo (-3), mail is sent with New York's time + 4 hours : incorrect (should be New York + 2 hour)
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!