[plasmashell] [Bug 370608] XAUTHORITY env variable changes in the middle of the night

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370608

--- Comment #6 from kolAflash  ---
Found what's happening and it's definitely not KDE's fault.

Thanks for the help!

--

If interested, here's the follow up bug report for openSUSE.
https://bugzilla.suse.com/show_bug.cgi?id=1006239

It's the file /etc/tmpfiles.d/tmp.conf and systemd-tmpfiles-clean.timer which
are deleting the file /tmp/xauth-1000-_0 periodically. And
/etc/tmpfiles.d/tmp.conf is always being created (probably by mistake) when
updating from openSUSE 13.1 to 42.1.

I don't know if there's also a bug-report or fix for Arch Linux. (maybe it's
even a totally different thing on Arch - I didn't test it).
https://bbs.archlinux.org/viewtopic.php?id=193273

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370608] XAUTHORITY env variable changes in the middle of the night

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370608

--- Comment #5 from kolAflash  ---
I used auditctl / ausearch as suggested, but got only this line after the file
was deleted:

type=CONFIG_CHANGE msg=audit(10/21/16 13:06:51.010:163) : auid=unset ses=unset
op="updated_rules" path=/tmp/xauth-1000-_0 key=(null) list=exit res=yes

I'm having no idea what type=CONFIG_CHANGE should indicate. Guess normally
ausearch should give me the program's name or pid.
The only thing I was able to find by that message was this bug report, which
has a similar ausearch result.
https://bugzilla.redhat.com/show_bug.cgi?id=567914

type=CONFIG_CHANGE msg=audit(1270141789.105:19355): auid=500 ses=5 op="updated
rules" path="/home/kavol/.Xauthority" key=(null) list=4 res=1

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370608] XAUTHORITY env variable changes in the middle of the night

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370608

--- Comment #3 from kolAflash  ---
New findings:
If the bug "happends", the file /tmp/xauth-1000-_0 had been deleted (will be
recreated on next login).

1 Million dollar question: Which process deletes that file???

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370608] XAUTHORITY env variable changes in the middle of the night

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370608

kolAflash  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|INVALID |---

--- Comment #2 from kolAflash  ---
New fact (tested on openSUSE):
The variable XAUTHORITY is already set directly after login to the value
"/tmp/xauth-1000-_0", which it still has when the bug start appearing (usually
some hours after logging in).
But XAUTHORITY is only set if using SDDM as display manager. If using KDM as
display manager, XAUTHORITY doesn't get set.


So "unset XAUTHORITY" and "XAUTHORITY=~/.Xauthority" only seem to be
workarounds.
And the actual bug is probably something else. My current guess is, that the
file "/tmp/xauth-1000-_0" becomes broken somehow. But I'll have to wait for the
bug to appear again to verify.

Both systems I'm experiencing the bug on had been updated from KDE 4 (openSUSE
13.1) to KDE/Plasma 5 (openSUSE 42.1). I'm not experiencing the bug on any
systems which had been set up from scratch using KDE 5.
But XAUTHORITY is also set to /tmp/xauth-1000-_0 on those newly set up systems.
So that variable should probably really have that value.

And please keep in mind: The bug appears on Arch Linux and openSUSE, so there's
some chance it's by KDE.
(yes, it could also be an systemd bug - I'm keeping that in mind)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370608] New: XAUTHORITY env variable changes in the middle of the night

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370608

Bug ID: 370608
   Summary: XAUTHORITY env variable changes in the middle of the
night
   Product: plasmashell
   Version: 5.5.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kolafl...@kolahilft.de
CC: bhus...@gmail.com, plasma-b...@kde.org

I'm experiencing exactly this bug, described by "jbaum".
Except, that I'm having this bug on openSUSE 42.1 and jbaum seems to have it on
Arch Linux.

https://bbs.archlinux.org/viewtopic.php?id=193273

| So after about 24 hours, I start being unable to open graphical applications.
| 
| Running something from console, I get this:
| $ xterm
| No protocol specified
| xterm: Xt error: Can't open display: :0.0
| $ ls $XAUTHORITY
| ls: cannot access /tmp/xauth-1000-_0: No such file or directory
| adam@t420a:~$ XAUTHORITY=~/.Xauthority xterm
| [launches successfully]

A question which may help to find out what's going on:
How can an environment variable be re-set to a different value, globally in all
KDE applications (e.g. a konsole and krunner), >>>while those applications are
already running<<< ?

Reproducible: Sometimes

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 332167] KMail is failing to encrypt PGP/Inline for non-signed key

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=332167

--- Comment #8 from kolAflash  ---
I'm using openSUSE 42.1 default software (KMail and GnuPG).

gpg2-2.0.24-5.1.x86_64
kmail5-15.12.3-18.5.x86_64

https://software.opensuse.org/package/gpg2
https://software.opensuse.org/package/kmail5

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 339087] you cannot encrypt to an expired OpenPGP certificate

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=339087

--- Comment #3 from kolAflash  ---
Another attempt to get this fixed.
https://bugs.gnupg.org/gnupg/issue2703

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 339087] you cannot encrypt to an expired OpenPGP certificate

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=339087

kolAflash  changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

--- Comment #2 from kolAflash  ---
Still valid for KMail 5.1.3 (KDE Frameworks 5.21.0 on openSUSE 42.1)

Related: https://bugs.kde.org/show_bug.cgi?id=369358

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 369358] New: you cannot encrypt to an expired S/MIME certificate

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369358

Bug ID: 369358
   Summary: you cannot encrypt to an expired S/MIME certificate
   Product: kmail2
   Version: 5.1.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: kolafl...@kolahilft.de

Same as https://bugs.kde.org/show_bug.cgi?id=339087 which is for PGP, but this
time for S/MIME.

KMail does not allow to encrypt to expired certificates. It is OK to warn about
that (and would be a failure not to do so) but not allowing to encrypt to this
key is a severe security failure because it does not make any sense and forces
the user to use a different key (if available, usually not) or to send the mail
unencrypted.

Reproducible: Always


Actual Results:  
Mail can't be sent.

Expected Results:  
Warning which can be overridden.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 369357] New: KMail refuses to use a technically untrusted S/MIME certificate/key (sender and receiver)

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369357

Bug ID: 369357
   Summary: KMail refuses to use a technically untrusted S/MIME
certificate/key (sender and receiver)
   Product: kmail2
   Version: 5.1.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: kolafl...@kolahilft.de

There's no way to use a X.509 certificate/key for S/MIME from a CA which
technically isn't trusted. Neither if it's your certificate (for sending /
signing the mail) nor if it's the receivers certificate (for encrypting the
mail.

Maybe you don't want to trust a whole CA. But you may know that a certain
certificate is trustworthy (e.g. by comparing the fingerprint or because you
created the private key and anyone else has a copy).
Sadly there's no way to technically mark a single X.509 / S/MIME certificate
trustworthy. That's only possible for CAs.
(maybe there should be such a possibility for single X.509 certificates -
something to think about for Kleopatra - but as far as I know that's not the
way X.509 works)
(yes I know, I should use PGP for that trust model, but my contacts sadly don't
share that view and I don't want to trust their whole stupid CA - nevertheless
I need to encrypt my emails to them)


If sending an email, using an technically untrusted certificate for yourself,
KMail will just say (a situation that may also occur if someone else needs you
to use a certificate from a CA you don't like): "Could not compose message: Not
trusted"
No further explanation what's not trusted.
Instead there should be a warning, that you own key isn't trusted. And there
should also be the possibility to say "send anyway". Because, as said, you know
that you can trust a single key (but you can't technically set that mark to a
single X.509 key), but you don't want to trust the whole CA.


Similar thing the other way around:
Send a message to a receiver who's key technically isn't trusted. KMail will
give you a short warning, saying:
|  One or more of the OpenPGP encryption keys or S/MIME
|  certificates for recipient "recipi...@example.com" is not
|  fully trusted for encryption.
You can click "Cancel" or "Continue" and you can also select "Do not ask
again".
But also if you choose "Continue" KMail will refuse to send the mail, telling
you: "Could not compose message: Not trusted"

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 322708] kmail should allow encrypting mails with keys of unknown/zero trust

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=322708

--- Comment #6 from kolAflash  ---
For PGP/MIME I can't reproduce this anymore. (can anyone?)

But for PGP/Inline this still seems to be valid, as explained here:

https://bugs.kde.org/show_bug.cgi?id=332167

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 332167] KMail is failing to encrypt PGP/Inline for non-signed key

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=332167

--- Comment #6 from kolAflash  ---
Still existing in Kontact 5.1.3 (KDE Frameworks 5.21.0 on openSUSE 42.1)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 368244] some PGP messages show: Not enough information to check signature validity

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368244

--- Comment #1 from kolAflash  ---
= Correction =

I still get the message after importing the key.

So:
1. KMail should provide more details about what's going wrong in general.
2. Fix this specific bug.

If you tell me where I can get some debug output (KMail doesn't seem to have an
"-v" verbose option) I'll happily provide it!

Maybe related:
https://bugs.kde.org/show_bug.cgi?id=323168

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 368244] some PGP messages show: Not enough information to check signature validity

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368244

kolAflash  changed:

   What|Removed |Added

Summary|some PGP messages without   |some PGP messages show: Not
   |pubic key: Not enough   |enough information to check
   |information to check|signature validity
   |signature validity  |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 368244] New: some PGP messages without pubic key: Not enough information to check signature validity

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368244

Bug ID: 368244
   Summary: some PGP messages without pubic key: Not enough
information to check signature validity
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: kolafl...@kolahilft.de

This is being displayed on some messages for which I don't have a public key:

"Not enough information to check signature validity."
Screenshot: http://picpaste.com/not_enough.png

German:
"Es sind nicht genügend Informationen zur Überprüfung der Signatur vorhanden."

Instead KMail should tell me that it misses the public key and give me the key
id of that key, so I can start searching for it.

Thunderbird+Enigmail handle the same email much better, telling me "Unverified
signature" and then there's a details button giving me the public key id.
(there's no details button in KMail)

Here's a copy of such an email without private details.
If someone needs an original copy for debugging (without blackened stuff) send
me an email and I'll send it to you. I just don't want to make the whole email
completly public because it wasn't written by me.

--
Return-Path: 
Delivered-To: [...]
Received: from localhost (cubox [127.0.0.1])
by [...] (Postfix) with ESMTP id [...]
for [...]; Tue,  9 Aug 2016 [...]
Received: from [...] ([127.0.0.1])
by localhost ([...] [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id [...] for [...]
Tue,  9 Aug 2016 [...]
Received: from [...] ([...] [[...]])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by [...] (Postfix) with ESMTPS id [...]
for [...]; Tue,  9 Aug 2016 [...]
Received: from [...] ([...] [[...]])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by [...] (Postfix) with ESMTPS id [...];
Tue,  9 Aug 2016 [...]
Received: from [...] (localhost [127.0.0.1])
by [...] (Postfix) with ESMTP id [...];
Tue,  9 Aug 2016 [...]
X-Original-To: mitglie...@lists.fux-eg.org
Delivered-To: [...]
Received: from [...] ([...]
 [[...]])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by h07.hostsharing.net (Postfix) with ESMTPS id 5227AC9436;
 Tue,  9 Aug 2016 [...]
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by [...] (Postfix) with ESMTPS id [...];
 Tue,  9 Aug 2016 [...]
Received: from [192.168.1.4] ([[...]]) by mail.gmx.com [...]
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
In-Reply-To: [...]
Date: Tue, 9 Aug 2016 [...]
Message-Id: [...]
References: [...]
To: [...]
X-Mailer: Apple Mail (2.1510)
X-Provags-ID: [...]
X-UI-Out-Filterresults: notjunk:[...]
Subject: [...]
X-BeenThere: mitglie...@lists.fux-eg.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Mitglieder der Fux Genossenschaft 
List-Unsubscribe: ,
 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: ,
 
From: [...]
Reply-To: [...]
Cc: fux Mitgliederliste 
Content-Type: multipart/mixed; boundary="===[...]=="
Errors-To: mitglieder-boun...@lists.fux-eg.org
Sender: "Mitglieder" 



--===[...]==
Content-Type: multipart/signed; boundary="Apple-Mail=_[...]";
protocol="application/pgp-signature"; micalg=pgp-sha512


--Apple-Mail=_[...]
Content-Type: multipart/alternative;
boundary="Apple-Mail=_[...]


--Apple-Mail=_[...]
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252

[...]
> ___
> Mitglieder mailing list
> mitglie...@lists.fux-eg.org
> http://lists.fux-eg.org/listinfo/mitglieder


--Apple-Mail=_[...]
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252


[...]=




___=
Mitglieder mailing 

[kleopatra] [Bug 322664] Result of file signature verification is misleading/confusing

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=322664

kolAflash  changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 340602] KMail puts PGP/MIME signed attachments twice into the same mail (doubling mailsize)

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340602

--- Comment #8 from kolAflash  ---
Looks like this got fixed in KMail 5.1.3 but the fix wasn't backported to 4.x.

At least for me the bug is gone since updating to KMail 5.1.3 and it returns
when downgrading to 4.14.10.
(all software used from openSUSE 42.1)

Can someone confirm? If yes, feel free to set status "RESOLVED".

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 366398] New: add "Delete Attachments" menu entry (complementary to "Save Attachments")

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366398

Bug ID: 366398
   Summary: add "Delete Attachments" menu entry (complementary to
"Save Attachments")
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: kolafl...@kolahilft.de

When right clicking on or into a message with multiple attachments, there's a
menu entry "Save Attachments" which will save all attachments at once into the
same folder.

Complementary to that, there should be an menu entry "Delete Attachments", to
give you the possibility to delete all attachments at once.

Currently, if there's a mail with multiple attachments, you'll have to right
click and delete every attachment separately, which can be very time consuming.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 366397] New: regression: attachment right click menu lost mnemonics

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366397

Bug ID: 366397
   Summary: regression: attachment right click menu lost mnemonics
   Product: kmail2
   Version: 5.1.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: kolafl...@kolahilft.de

Right click an attachment and you'll get a menu. This menu used to have more
mnemonics.

Currently there's only a mnemonic for "Open With" but in KMail 4.14.9 there
used mnemonics for all menu entries!
(Open, Open With, View, Save As, Copy, Delete Attachment, Properties)

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaddressbook] [Bug 366199] New: KAddressbook 5.1.3 contact window has a bad layout in german

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366199

Bug ID: 366199
   Summary: KAddressbook 5.1.3 contact window has a bad layout in
german
   Product: kaddressbook
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kolafl...@kolahilft.de
CC: to...@kde.org

http://picpaste.com/kaddressbook5_contact_window_german-7vO1uAEO.png

The contact window is badly layouted in german translation. The fields on the
left site (e.g. "Name" and "Telefonnummern"/telephone numbers) are much too
short.

In english translation those fields are much wider.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=336369

kolAflash  changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

--- Comment #13 from kolAflash  ---
(In reply to Martin Gräßlin from comment #12)
> For the record: I'm currently working on a solution which would allow to
> bring suspend back in the next release. I hope I found a way to make it
> secure.

That would be great!
In KDE 4 i used to have widgets on my lockscreen, allowing me to suspend and
hibernate. But in KDE 5 / Plasma 5 this isn't possible anymore.


I don't like to configure my notebook to go to standby if the display is
closed. Because I like to put the notebook under my arm and go somewhere else,
while the notebook is for example compiling something.

But sometimes I lock my notebook when leaving the office-room without it. And
when I come back, I maybe just want to suspend it, because I'm going home with
it.
And it's ridiculous, that I have to enter my password just to put the notebook
into standby!

In a very general sense of security (NOT regarding the API infrastructure in
KDE): Everyone in the room can just take the battery and ac cable out of my
notebook to hardly shut it down. And suspend/hibernate are even less worse than
a cold shutdown. So there's really no security in protecting theses actions
with the users password.
Hibernating may even help if you're not in place and someone else needs to
unplug/replug the power cable of your desktop pc. So he can power it down
(hibernate) before he unplugs the cable.

Maybe in some scenarios, the ac cable / battery may be not accessible for a
user and you want to keep others from suspending/hibernating the machine. So
it's maybe wise to make this options configurable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 359138] KMail doesn't set "In-Reply-To" and "References" headers when forwarding

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359138

--- Comment #1 from kolAflash  ---
Looks like Thunderbird is also setting this reasonable additional header when
forwarding.
X-Forwarded-Message-Id: ...

So a header-template could look like this:
References: %OHEADER="References" %OHEADER="Message-ID"
In-Reply-To: %OHEADER="Message-ID"
X-Forwarded-Message-Id: %OHEADER="Message-ID"

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 148407] Specify custom headers in templates

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=148407

--- Comment #7 from kolAflash  ---
One more reason to solve this:
https://bugs.kde.org/show_bug.cgi?id=359138

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 359138] New: KMail doesn't set "In-Reply-To" and "References" headers when forwarding

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359138

Bug ID: 359138
   Summary: KMail doesn't set "In-Reply-To" and "References"
headers when forwarding
   Product: kmail2
   Version: 4.14.7
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: kolafl...@kolahilft.de

KMail version 4.14.9

When forwarding a message, KMail doesn't set the "In-Reply-To" and the
"References" headers.

Could anyone check this for the current KMail version? (4.15.x)

One workaround would be, to specify custom headers in the forward template. But
this would require this bug to be solved first.
https://bugs.kde.org/show_bug.cgi?id=148407

Then you could do something like:
References: %OHEADER="References" %OHEADER="Message-ID"
In-Reply-To: %OHEADER="Message-ID"

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 148407] Specify custom headers in templates

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=148407

kolAflash  changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 355195] date and time are ambiguous when replying to and forwarding messages (no timezone information)

[kolAflash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355195

--- Comment #2 from kolAflash  ---
Thanks for the comment Ben!

Actually I'd prefer to see the timezone offset (e.g. +0800). Especially because
I'm mailing with people in different timezones, this seems to be the better way
instead of recalculating everything to my local timezone without any attached
timezone information.

-- 
You are receiving this mail because:
You are watching all bug changes.