[kmail2] [Bug 353627] better naming for attached PGP keys and merging all attached keys in one file

[kolAflash]

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

kolAflash <kolafl...@kolahilft.de> changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #4 from kolAflash <kolafl...@kolahilft.de> ---
Bug is still present exactly as described in:
- KMail-17.04.2/5.5.2 with desktop environment version 5.8.7 on openSUSE-42.3
- KMail-17.12.2/5.7.2 with desktop environment version 5.12.1 on
openSUSE-Tumbleweed-Snapshot20180221

Nothing changed about the bug description. So I'm not sure if this should be a
new bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 81781] An option to display all the months of the year in KOrganizer

[kolAflash]

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

kolAflash <kolafl...@kolahilft.de> changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

--- Comment #9 from kolAflash <kolafl...@kolahilft.de> ---
No progress on this!? :-/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 381596] kmail freezes with high cpu usage when reading pgp-signed messages with attachments

[kolAflash]

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

--- Comment #1 from kolAflash <kolafl...@kolahilft.de> ---
P.S.
Happens only on signed only emails.

Doesn't happen on non-signed or signed+encrypted pgp-emails.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 381596] New: kmail freezes with high cpu usage when reading pgp-signed messages with attachments

[kolAflash]

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

Bug ID: 381596
   Summary: kmail freezes with high cpu usage when reading
pgp-signed messages with attachments
   Product: kmail2
   Version: 5.3.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de
  Target Milestone: ---

When opening an pgp signed email with a big attachment (e.g. a 6 MB JPEG),
KMail will hang and need a pretty big amount of time (at least 30 seconds) to
open that email.

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 381579] New: add and handle Openpgp header

[kolAflash]

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

Bug ID: 381579
   Summary: add and handle Openpgp header
   Product: kmail2
   Version: 5.3.0
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de
  Target Milestone: ---

Please add a Openpgp header if the user has configured a PGP key.


E.g.:

Openpgp: id=01234567890ABCDEF01234567890ABCDEF012345;
url=https://dropbox.com/url/set/by/user.asc


Enigmail (PGP for Thunderbird) already does so.

https://enigmail.net

https://sourceforge.net/p/enigmail/source/ci/9f642b2286a38a06982fb3dd25dcff2b276e2fdb/tree/ui/content/enigmailMsgComposeOverlay.js#l4287

Enigmail already uses the described format, with one exception. There's a LF
before the url= part. I'm not sure why there is a LF and if KMail should copy
that.

Openpgp: id=01234567890ABCDEF01234567890ABCDEF012345;
 url=https://dropbox.com/url/set/by/user.asc


The first field id= can be automatically generated from the PGP key the user
has configured for this account. Please use the full key fingerprint, not just
8 or 16 characters.

The second field url= needs a configuration option, where the user can enter a
URL at which he has uploaded his key. If the user doesn't set this
configuration option, the url= field shouldn't be there. (not everybody uploads
his PGP key somewhere)


Second part happens on receiving an E-Mail. KMail should check for the Openpgp
header and offer the user to import the key from the given URL or via key-id
from the public keyserver. DON'T automatically import, but ask the user first.


--


I tried to manually add the header by the KMail settings->headers section. But
those headers are globally for all email accounts. And I'm using multiple email
accounts with different PGP keys.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

[kolAflash]

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

--- Comment #9 from kolAflash <kolafl...@kolahilft.de> ---
Still not working on openSUSE 42.2 with GnuPG-2.0.24 and KMail-16.08.2.

http://download.opensuse.org/source/distribution/leap/42.2/repo/oss/suse/src/gpg2-2.0.24-5.5.src.rpm

http://download.opensuse.org/update/leap/42.2/oss/src/kdepim-16.08.2-2.2.1.src.rpm

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 <kolafl...@kolahilft.de> ---
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 the assignee for the bug.

[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 <kolafl...@kolahilft.de> ---
Another attempt to get this fixed.
https://bugs.gnupg.org/gnupg/issue2703

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 <kolafl...@kolahilft.de> changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

--- Comment #2 from kolAflash <kolafl...@kolahilft.de> ---
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 the assignee for the bug.

[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-bugs@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 the assignee for the bug.

[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-bugs@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 the assignee for the bug.

[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 <kolafl...@kolahilft.de> ---
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 the assignee for the bug.

[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 <kolafl...@kolahilft.de> ---
Still existing in Kontact 5.1.3 (KDE Frameworks 5.21.0 on openSUSE 42.1)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 <kolafl...@kolahilft.de> ---
= 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 the assignee for the bug.

[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 <kolafl...@kolahilft.de> 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 the assignee for the bug.

[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-bugs@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 <kolafl...@kolahilft.de> changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 <kolafl...@kolahilft.de> ---
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 the assignee for the bug.

[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-bugs@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 the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[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-bugs@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 the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[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-bugs@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 the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[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 <kolafl...@kolahilft.de> ---
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 the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash via KDE Bugzilla]

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

kolAflash <kolafl...@kolahilft.de> changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[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-bugs@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 the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[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 <kolafl...@kolahilft.de> ---
One more reason to solve this:
https://bugs.kde.org/show_bug.cgi?id=359138

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[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 <kolafl...@kolahilft.de> ---
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 the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 355195] New: 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

Bug ID: 355195
   Summary: date and time are ambiguous when replying to and
forwarding messages (no timezone information)
   Product: kmail2
   Version: 4.14.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

When forwarding or replying to a message, the time zone information of the old
message is just thrown away.


When forwarding or replying to a message, a customizable standard template is
used.
See: Settings => Configure KMail => Composer => Standard Templates

For those you can use time and date values of the original mail such as:

%ODATE (Date)
%ODATEEN (Date in C Locale)
%ODATESHORT (Date in Short format)
%OTIME (Time)
%OTIMEEN (Time in C Locale)
%OTIMELONG (Time in Long Format)

To get something like:

On %ODATEEN, %OTIMELONGEN, %OFROMNAME wrote:

On a concrete mail this will expand to something like:

On Friday 02 November 2015, 09:17:44, Alice wrote:

Nevertheless Alice original mail said:
Date: Fri, 02 Nov 2015 09:17:44 +0800

So this is some very different time than 09:17:44 UTC for example.

So those %... variables should either always contains the time zone (e.g.
+0800) or there should be an additional variable for this.

Alternatively there should be variables offering a recalculated time, based on
the local time of the forwarding / replying persons computer.
Maybe the difference between %OTIME and %OTIMEEN was intended for this. But
actually I can't find any difference in the behaviour of these both variables.
Maybe broken!?!?
Additionally, a localized/non-localized version of the %OTIMELONG variable
would be needed.

I like the idea to recalculate to the forwarders/replyers local time and add
the time zone string, e.g. +0800
It's the same what KMail does when showing the Date of a normal email when
reading.


And don't forget, the %ODATE... variables are probably affected too
(date-borders).

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 353627] New: better naming for attached PGP keys and merging all attached keys in one file

[kolAflash]

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

Bug ID: 353627
   Summary: better naming for attached PGP keys and merging all
attached keys in one file
   Product: kmail2
   Version: 4.14.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

Lets give public keys a better naming when attaching them.

If you go to:
New (Message) => Attach => Attach Public Key
or
New (Message) => Attach => Attach My Public Key
it will attach your public key with a name like:

OpenPGP key 0x97EF7410FEC4DF7245A2D3F5C95E8EBD8258F706

or even worse when localized (e.g. German)

OpenPGP-Schlüssel 0x97EF7410FEC4DF7245A2D3F5C95E8EBD8258F706

Those names are far to long, including the whole fingerprint which has no real
use in this place.
And they lack a useful filename extension.


This is how Enigmail for Thunderbird names an attached public key:

0x8258F706.asc

And an even better choice could be this, including the primary mail
(j...@example.com) address of the key.

PGP-Key_john-AT-example.com_0x8258F706.asc

And please don't use localization on the filename. I think that just confuses
if you mail to people speaking other languages then your own localization.


Additionally we could consider merging multiple attached keys.
E.g if attaching your own public key and multiple other public keys with
Enigmail, you get a maximum of two files attached to the mail.

pgpkeys.asc
0x8258F706.asc

Where "0x8258F706.asc" is your own public key and "pgpkeys.asc" contains all
the other public keys. This makes life much more easier when sending someone
multiple publics keys he has two import. So he doesn't has to click every key
he wants to import.

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 353628] New: add option to always attach own PGP public key

[kolAflash]

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

Bug ID: 353628
   Summary: add option to always attach own PGP public key
   Product: kmail2
   Version: 4.14.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

In
Settings => Configure KMail => Identities => Modify => Cryptography
add an option to always attach the own public key by default.

There are some reasons people might prefer to send their public keys by mail
instead of publicly uploading them to keyservers. For those scenarios it's
pretty useful to have an option, to always attach the own public key by
default.

Enigmail for Thunderbird provides a similar option. For this go to:
(in Thunderbird)
Enigmail => Preferences => Display Expert Settings and Menus => OK
Account Settings => OpenPGP Security => Advanced => Attach my public key to
messages

Additionally KMail should name the attached key a little smarter. See
https://bugs.kde.org/show_bug.cgi?id=353627 for details.

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 353630] New: ask the user if all receivers public keys should be attached, if an encrypted PGP mail is send to multiple receivers

[kolAflash]

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

Bug ID: 353630
   Summary: ask the user if all receivers public keys should be
attached, if an encrypted PGP mail is send to multiple
receivers
   Product: kmail2
   Version: 4.14.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

If you send an PGP encrypted mail to multiple receivers, it would be pretty
convenient to ask (not fully automatically) the user if he wants to attach all
receivers public PGP keys.

Most users probably won't think of this problem in the first place, until
someone complains that he doesn't has all the other's public keys when trying
to "reply to all".

Guess this would be a great step forward to enable even less experienced users
to use PGP for mails in groups with multiple receivers.

Exception: When receivers are BCC, their keys probably shouldn't be attached.

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 353631] New: ask the user to import attached PGP keys

[kolAflash]

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

Bug ID: 353631
   Summary: ask the user to import attached PGP keys
   Product: kmail2
   Version: 4.14.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

When receiving a mail with attached PGP key(s), KMail should ask the user to
import those keys.

Don't auto-import those keys! That would be a (small) security problem.

But especially for inexperienced users it would be pretty helpful, if KMail
would tell them that the attached file(s) are actually PGP keys and ask the
user if they should be imported.

And, to do it the totally right way, KMail should not just say:

"There are PGP keys attached, should they be imported?"

but KMail should ask (imagine a popup window)


There are the following PGP keys attached. Please give those keys a mark that
you want to import:

[ ] j...@example.com
[x] al...@wonderland.net
[x] b...@test.org
[ ] e...@evil.tk

CancelOK


Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

kolAflash <kolafl...@kolahilft.de> changed:

   What|Removed |Added

Version|4.11.5  |4.14.7

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

kolAflash <kolafl...@kolahilft.de> changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|REMIND  |---

--- Comment #5 from kolAflash <kolafl...@kolahilft.de> ---
Bug still exists in KDE 4.14.9

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 351861] New: bad error message when S/MIME crl's are not reachable

[kolAflash]

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

Bug ID: 351861
   Summary: bad error message when S/MIME crl's are not reachable
   Product: kmail2
   Version: 4.14.7
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

If a message could not be encrypted and send, because the receivers S/MIME
certificate crls (certificate revocation lists) are not reachable, the only
error message is:
Could not compose message: Not found.
That's as unhelpful as possible!

Only way to workaround:
Kleopatra = Settings = Configure Kleopatra = S/MIME = check Never consult
a CRL

Two possible solutions:

1. Replace error message with something more precise for this situation. E.g.
Couldn't verify receivers S/MIME certificate, because it's revocation urls are
not reachable.

2. Additionally give the user the possibility, to ignore that the crls could
not be reached.

Those are the actual revocation urls used in the receivers S/MIME certificate.
If the original, full S/MIME certificate is helpful for you, tell me and I'll
ask the owner if I can publish it here.
http://cdp1.pca.dfn.de/haw-hamburg-ca/pub/crl/g_cacrl.crl
http://cdp2.pca.dfn.de/haw-hamburg-ca/pub/crl/g_cacrl.crl
http://cdp1.pca.dfn.de/haw-hamburg-ca/pub/cacert/g_cacert.crt
http://cdp2.pca.dfn.de/haw-hamburg-ca/pub/cacert/g_cacert.crt

Reproducible: Always

Steps to Reproduce:
1. Write an S/MIME encrypted+signed email to a receiver you have a S/MIME
certificate for, which crls are not reachable.

2. Click Send.

3. KMail may tell you:
One or more of the OpenPGP encryption keys or S/MIME certificates for
recipient ... is not fully trusted for encryption.
The following keys or certificates have unknown trust level: ...
Click Continue.

4. KMail will show you the Encryption Key Approval window. Click OK.

Actual Results:  
KMail will show you twice a message Could not compose message: Not found.

Expected Results:  
Send and encrypt message.

Bug also appears in another place.

1. Send an S/MIME encrypted email to an receiver you don't have an S/MIME
certificate for.

2. When sending, KMail will ask you:
There are conflicting encryption preferences for these recipients.
Encrypt this message?
Click Encrypt.

3. KMail will ask you for a certificate for the receiver. Now search for a
certificate which is valid but has non working crls.

4. Before you click the line containing the certificate, at the left there will
be an icon containing an question-mark.

5. Click at the certificate. The question-mark will change to a red X and
you'll not be able to click OK.

Also in this case, there should be an explanation what's wrong about the
certificate and maybe also an possibility to send+encrypt the email anyway with
that key.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

--- Comment #5 from kolAflash kolafl...@kolahilft.de ---
Confirming what Hauke reported.

Mail body is also added twice and bug still exists in 4.14.8.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 303109] Message-ID: field of kmail 4.8.4 exposes hostname

[kolAflash]

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

kolAflash kolafl...@kolahilft.de changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

--- Comment #5 from kolAflash kolafl...@kolahilft.de ---
But the hostname will expose some private information about you, which you
might don't want to share with everyone you're writing emails to.

Other mail-clients like Thunderbird or K9Mail also use the E-Mail domainname.
E.g. writing from j...@example.com will give you a message-id *@example.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

--- Comment #2 from kolAflash kolafl...@kolahilft.de ---
Still there in 4.14.3

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

kolAflash kolafl...@kolahilft.de changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |REMIND

--- Comment #4 from kolAflash kolafl...@kolahilft.de ---
Bug still exists in KDE 4.14.3

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328315] KMail doesn´t save changes when the column order in the messagelist is changed

[kolAflash]

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

--- Comment #15 from kolAflash kolafl...@kolahilft.de ---
 http://commits.kde.org/kdepim/e54fd2e1250f0a4b6bb958ea46e26b69c4438fa4
Works!

I tried the patch on the KDE 4.14.2 source-rpm of openSUSE 13.2.
http://download.opensuse.org/source/distribution/13.2/repo/oss/suse/src/kdepim4-4.14.2-1.1.src.rpm
Now column order and column size are properly restored after restarting KMail.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 329597] PGP/MIME signed messages not accepted by Thunderbird's Enigmail

[kolAflash]

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

kolAflash kolafl...@kolahilft.de changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

--- Comment #4 from kolAflash kolafl...@kolahilft.de ---
I reported a similar problem to the Enigmail bug-system. It's fixed in the
current nighties of Enigmail.
So maybe you can close this bug.

http://sourceforge.net/p/enigmail/bugs/332/

https://www.enigmail.net/download/nightly.php

@Martin Albrecht
Can you do a test with a current Enigmail nightly?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328315] KMail doesn´t save changes when the column order in the messagelist is changed

[kolAflash]

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

--- Comment #11 from kolAflash kolafl...@kolahilft.de ---
@Laurent Montel
This should be perfectly reproduceable for you:


Correct behavior:
Boot the Kubuntu 13.10 AMD64 livecd (including KDE 4.11.2) in VirtualBox (I
used VirtualBox 4.3.18).
If you run KMail, everything should be fine! You can move columns in KMail,
close KMail, reopen it and the columns should be right where you left them.

http://cdimage.ubuntu.com/kubuntu/releases/13.10/release/kubuntu-13.10-desktop-amd64.iso


Buggy behavior:
Boot the Kubuntu 14.04.1 AMD64 livecd (including KDE 4.13.2) in VirtualBox (I
also used VirtualBox 4.3.18 for this).
If you run KMail, first you'll have to enable columns (View = Message List =
Theme = Smart with Clickable Status).
Then you can move columns. But after closing and reopen KMail, it will put the
columns back to their default positions (specified by the Smart with Clickable
Status theme).

http://cdimage.ubuntu.com/kubuntu/releases/trusty/release/kubuntu-14.04.1-desktop-amd64.iso

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328315] KMail 4.11.97 doesn´t save changes when the column succession in the income box where changed - reproducable: every time!

[kolAflash]

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

--- Comment #6 from kolAflash kolafl...@kolahilft.de ---
Try Kubuntu 14.10 x86_64 with KDE-4.14.1

http://cdimage.ubuntu.com/kubuntu/releases/utopic/release/kubuntu-14.10-desktop-amd64.iso

Start the livecd, then start KMail. Don't set up an mail account. Just use
Local Folders.
On the first start KMail doesn't show a message list... don't know why. But on
the second start the Message List is there. If you rearrange the order of the
Message and Status columns, it won't last after closing and reopening
KMail.


Same with openSUSE 13.2 x86_64 livecd.
(just need to switch to Smart with Clickable Status message-list theme before
to get columns)

http://ftp4.gwdg.de/pub/opensuse/distribution/13.2/iso/openSUSE-13.2-KDE-Live-x86_64.iso


I'll see if I can get more information. Do you need anything specific?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328315] KMail 4.11.97 doesn´t save changes when the column succession in the income box where changed - reproducable: every time!

[kolAflash]

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

kolAflash kolafl...@kolahilft.de changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

--- Comment #3 from kolAflash kolafl...@kolahilft.de ---
Reproducible with openSUSE Linux.

openSUSE 13.1 with KDE 4.11.5 still saved column succession/order and size of
columns.

openSUSE 13.2 with KDE 4.14.2 forgets succession/order and size of columns.

Any updates on this bug-report?


It's very annoying for daily use of KMail.
I know, the column order can be changed by the Message List theme. But the
column size can't.

Additionally I was used (in 4.11.5) to have a Message List theme with a
message-column and a clickable status column (carrying icons for read/unread
and important). In the theme, the status-column was configured to be on the
right, because I wanted to have the message-tree (for message-thread groups) in
the message column.
In KMail (not in the Message List theme editor) I moved that status column to
the left. By that, the tree stayed at the message column. That's exactly the
way I like it!
In general, this still possible. But after restarting KMail the status column
is back at the right side :-(

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328315] KMail 4.11.97 doesn´t save changes when the column succession in the income box where changed - reproducable: every time!

[kolAflash]

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

--- Comment #4 from kolAflash kolafl...@kolahilft.de ---
Just a guess (I'm not very experienced in the KMail sourcecode):


Is this the file responsible for the message-list in KMail?

https://projects.kde.org/projects/kde/kdepim/repository/revisions/v4.11.97/changes/messagelist/pane.cpp

If yes, the problem might be caused by any of the changed between git revision
e2489368 (2013-08-11) and revision 7f9198c6 (2013-11-19)

https://projects.kde.org/projects/kde/kdepim/repository/diff/messagelist/pane.cpp?rev=7f9198c6710f2e1b05fd066ff6769db2f6a96cdbrev_to=e2489368898cee4b4c908cbc0d8c20cf58bb4a7b

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

kolAflash kolafl...@kolahilft.de changed:

   What|Removed |Added

Version|4.11.5  |4.14.2

--- Comment #1 from kolAflash kolafl...@kolahilft.de ---
First test was with KDE 4.11.5 (openSUSE 13.1 with latest distribution updates)

Now repeated the test with KDE 4.14.2 (openSUSE 13.2)

Same bug in both versions!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

Bug ID: 340602
   Summary: KMail puts PGP/MIME signed attachments twice into the
same mail (doubling mailsize)
   Product: kmail2
   Version: 4.11.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

When sending an PGP/MIME signed (and optionally also encrypted) mail, including
signed attachments, KMail puts every attachment twice into the mail.

This double's the size of the mail!

Example mail body, created by KMail. You'll see, that the (very small) file
blue-pixel.png has become attached twice. But I attached it only once to the
mail.

MIME-Version: 1.0
Content-Type: multipart/signed; boundary=nextPart1782944.DN5yU133gh;
micalg=pgp-sha1; protocol=application/pgp-signature
User-Agent: KMail


--nextPart1782944.DN5yU133gh
Content-Type: multipart/mixed; boundary=nextPart4748887.diooyAto5j
Content-Transfer-Encoding: quoted-printable

This is a multi-part message in MIME format.

=2D-nextPart4748887.diooyAto5j
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset=us-ascii

Small test mail.
=2D-nextPart4748887.diooyAto5j
Content-Disposition: attachment; filename=blue-pixel.png
Content-Transfer-Encoding: base64
Content-Type: image/png; name=blue-pixel.png

iVBORw0KGgoNSUhEUgEBCAYfFcSJBmJLR0QA/wD/AP+gvaeTCXBI
WXMAAA3XAAAN1wFCKJt4B3RJTUUH3gsDDREaJ+YAOQAAAB1pVFh0Q29tbWVudAAAQ3Jl
YXRlZCB3aXRoIEdJTVBkLmUHDUlEQVQI12NgyDj2HwADyAIu6/Hk0wBJRU5ErkJggg==

=2D-nextPart4748887.diooyAto5j--
This is a multi-part message in MIME format.

--nextPart4748887.diooyAto5j
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset=us-ascii

Small test mail.
--nextPart4748887.diooyAto5j
Content-Disposition: attachment; filename=blue-pixel.png
Content-Transfer-Encoding: base64
Content-Type: image/png; name=blue-pixel.png

iVBORw0KGgoNSUhEUgEBCAYfFcSJBmJLR0QA/wD/AP+gvaeTCXBI
WXMAAA3XAAAN1wFCKJt4B3RJTUUH3gsDDREaJ+YAOQAAAB1pVFh0Q29tbWVudAAAQ3Jl
YXRlZCB3aXRoIEdJTVBkLmUHDUlEQVQI12NgyDj2HwADyAIu6/Hk0wBJRU5ErkJggg==

--nextPart4748887.diooyAto5j--

--nextPart1782944.DN5yU133gh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

...%signature data%...
-END PGP SIGNATURE-

--nextPart1782944.DN5yU133gh--


Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kleopatra] [Bug 339385] New: Kleopatra (and KMail) need about 5 minutes to receive CRLs when CACert certificates are involved

[kolAflash]

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

Bug ID: 339385
   Summary: Kleopatra (and KMail) need about 5 minutes to receive
CRLs when CACert certificates are involved
   Product: kleopatra
   Version: 2.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de
CC: m...@kde.org

Load some CACert certificates into your Kleopatra.

http://www.cacert.org


Then configure Kleopatra to use CRLs instead of OCSP.
(This was actually the default on my system)

Settings = Configure Kleopatra = S/MIME
Check certificate validity every: hour
Validate certificates using CRLs: YES


Now completely quit Kleopatra (also the icon in the KDE Control-Bar).
Also quit KMail and every other application which might uses x509 certificates
at the moment (for me it was KMail and Kleopatra).

Then quit all dirmngr instances. For example by using:
pkill -e dirmngr

Then clear the dirmngr cache:
 dirmngr --flush

Kill dirmngr again, just to be sure it doesn't still uses any old cache-data.


If you now start Kleopatra, all certificate lists will be shown empty!!!

There is no information to the user why this is happening.
Actually in background dirnmgr is used to load the CRLs from CACert. If you
run:

 netstat -np | grep 'dirmngr'

you'll see a connection to 213.154.225.236 which is crl.cacert.org.
You can use tcpdump to see what it's doing:

 sudo /usr/sbin/tcpdump -n -v -i any host 213.154.225.236

For me it takes about 5 minutes until this process is finished. Until this
happens, no certificates are shown in Kleopatra at all.

After that time, all my certificates are back again in Kleopatra. None of them
has been lost, but it really looked like that for the last 5 minutes!


There should be a notification to the user!
For example:
 Your certificates have not been deleted! Just be a little patient, I'm 
 receiving Certificate Revocation Lists from the Server to find out if any 
 certificate became invalid.



KMail also suffers from that problem, if dirmngr is receiving the CRLs in
background (because the cache was flushed or the Check certificate validity
every ... time interval ran out).
If you read an S/MIME signed email, KMail will tell you:

 Please wait while the signature is being verified...

That's OK, but it should add: This may take several minutes, if CRLs have to
be refreshed from server.

If you answer a S/MIME signed+encrypted email, KMail will hang completly and
nothing will happen until dirmngr completed it's work.
There isn't even a message telling me, why KMail hangs.
And by the way my whole KMail is blocked for that time. I can't even work on
other emails, except I kill and restart KMail.

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

--- Comment #3 from kolAflash kolafl...@kolahilft.de ---
Tested it with openSUSE 13.1 + KDE 4.12.4 from this repo:

http://download.opensuse.org/repositories/KDE:/Current/openSUSE_13.1/

Result: Bug still exists in KDE 4.12.4 :-(

Console output using PGP/Inline:
==
$ kmail --nofork --composer
Enchant dict for en_US 0x2945f40 
Enchant dict for en_US 0x2eb52a0 
Enchant dict for en_US 0x2eb52a0 
kmail2(3789) ValidTrustedOpenPGPEncryptionKey: bad validity 0 
kmail2(3789) ValidTrustedOpenPGPEncryptionKey: bad validity 0 

** (process:3789): WARNING **: 1 dictionaries weren't free'd.
==

Console output using PGP/MIME:
==
$ kmail --nofork --composer
Enchant dict for en_US 0x10a3ba0 
Enchant dict for en_US 0x1621610 
Enchant dict for en_US 0x1621610 
kmail2(3836) ValidTrustedOpenPGPEncryptionKey: bad validity 0 
kmail2(3836) ValidTrustedOpenPGPEncryptionKey: bad validity 0 

** (process:3836): WARNING **: 1 dictionaries weren't free'd.
==

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

--- Comment #2 from kolAflash kolafl...@kolahilft.de ---
It's a little complicated for me, because my distribution (openSUSE 13.1) comes
with KDE 4.11.4 and I don't like to play too much around with that system.

I'll try to set up a whole vm with KDE 4.12.2. But I don't have much time for
gthat at the moment. (is there a ready-to-use KDE 4.12.2 livecd?)

Probably you could be much faster, trying what I described on your system. I'd
be very happy if you could do so.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

Bug ID: 332167
   Summary: KMail is failing to encrypt PGP/Inline for non-signed
key
Classification: Unclassified
   Product: kmail2
   Version: 4.11.5
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

I can't send an PGP/Inline email to a receiver with an key I didn't sign
before.

If I sign the receivers key before sending OR use PGP/MIME everything's working
fine.

Reproducible: Always

Steps to Reproduce:
1. Create a new email.
2. Encrypt the email and set the encryption-format to PGP/Inline.
3. Click Send.
Actual Results:  
KMail tells: It was not possible to create a message composer.

Expected Results:  
E-Mail should be encrypted and send using the PGP/Inline format.

I tried to find the bug searching in
messagecomposer/composer/keyresolver.cpp

https://projects.kde.org/projects/kde/kdepim/repository/revisions/6fce5eb967cc02398bcf9032959e48d0a3c64b78/entry/messagecomposer/composer/keyresolver.cpp


Line 547
ValidTrustedOpenPGPEncryptionKey ) != item.keys.end() ) {  // -= trusted?
looks suspicious. I tried replacing it with:
ValidOpenPGPEncryptionKey ) != item.keys.end() ) {

Same for line 1575
NotValidTrustedOpenPGPEncryptionKey ); // -= trusted (see above, too)?
I replaced with
NotValidOpenPGPEncryptionKey );

But both didn't helped. I just got another error telling me, that the key is
corrupt (it definitely isn't - I can use it for PGP/MIME and in Thunderbird it
also works for PGP/Inline).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kaddressbook] [Bug 331852] New: kaddressbook Template not found, contact.htmlTemplate not found, contact_embedded.html

[kolAflash]

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

Bug ID: 331852
   Summary: kaddressbook Template not found, contact.htmlTemplate
not found, contact_embedded.html
Classification: Unclassified
   Product: kaddressbook
   Version: 4.11.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de
CC: to...@kde.org

kaddressbook shows the error

Template not found, contact.htmlTemplate not found, contact_embedded.html

in the right contact-preview pane (in two and three columns mode) instead of
the contacts details. There are any further details why this happens.


Via strace I found out, that kaddressbook looks for the mentioned files in

~/.kde4/share/apps/kaddressbook/viewertemplates/

After deleting that directory, the preview pane works fine again. Don't know
why the directory was existing in the first place.


For any less experienced user this might be an unresolvable problem. And also
me it had cost some time. Please fix!

Either apply user-defined templates only if the html-file really exists (and
not just the directory). Of put more details on how to resolve the problem into
the error message shown by kaddressbook

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[kolAflash]

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

kolAflash kolafl...@kolahilft.de changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

--- Comment #3 from kolAflash kolafl...@kolahilft.de ---
I understand the bug in that way, that I got a private key which I'm not fully
trusting. Maybe because someone else stole a copy of that private key. Or it's
a private key I share with some people because we all get forwarded mails from
an alias address. Nevertheless KMail shouldn't deny to use the key but give a
clear warning.

Did some testing. (By the way: patch for bug #328311 doesn't fixes this bug)

KDE 4.11.4 (openSUSE 13.1)



When changing a OpenPGP key for a KMail identity
Settings = Configure KMail = Identities = Modify = Cryptography = Change
I can manually select a key for which I set the trust-level to anything less
then Ultimately (using Kgpg) for signing but I CAN'T select it for
encryption.

Same problem when changing the Your keys in the last step before sending an
encrypted E-Mail (dialog Encryption Key Approval).




If I set a full-trusted key as default for a KMail identity (Settings =
Configure KMail) and afterwards lower the trust-level KMail gives me this
message when trying to send a mail with that identity:

You have requested to encrypt this message, and to encrypt a copy to yourself,
but no valid trusted encryption keys have been configured for this identity.
Only choices:
Send unencrypted Cancel




Can't manually select a key in the Encryption Key Selection dialog which run
over it's date of validity. (created a key for testing by running a vm in Qemu
and set the time a few years back)

This is important! If someone forgot to create a new key or to send me a new
key I should be able so send him an encrypted email asking for that!


-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328311] KMail doesn't let me manually select a non verified PGP key which doesn't contains the receivers address

[kolAflash]

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

--- Comment #1 from kolAflash colafl...@gmx.net ---
Same bug appears if I have to manually select a key, because I got multiple
keys for the same email address in my key-chain.

Did anybody else experience this bug? Please tell!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328311] KMail doesn't let me manually select a non verified PGP key which doesn't contains the receivers address

[kolAflash]

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

kolAflash colafl...@gmx.net changed:

   What|Removed |Added

   Platform|unspecified |openSUSE RPMs
Version|4.11.2  |4.12

--- Comment #2 from kolAflash colafl...@gmx.net ---
For my initial bug report I used KDE 4.11.2

Later I got regular updates to 4.11.3 and then 4.11.4 from my distribution
(openSUSE 13.1).

Now I manually updated to 4.12.1 using this repository:
http://download.opensuse.org/repositories/KDE:/Release:/412/openSUSE_13.1/

Unfortunately none of this updates fixed the bug :-/

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328311] KMail doesn't let me manually select a non verified PGP key which doesn't contains the receivers address

[kolAflash]

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

--- Comment #3 from kolAflash colafl...@gmx.net ---
Did some debugging with KDbg. May this be the reason?


kdepim-4.12.1/messagecomposer/composer/keyresolver.cpp:1625
Method:
std::vectorGpgME::Key Kleo::KeyResolver::selectKeys(
  const QString person, const QString msg, const std::vectorGpgME::Key
selectedKeys ) const

  keys.erase( std::remove_if( keys.begin(), keys.end(),
  NotValidTrustedEncryptionKey ), // -= trusted?
  keys.end() );


Maybe it should be like this instead?

  keys.erase( std::remove_if( keys.begin(), keys.end(),
  NotValidTrustedEncryptionKey ), // -= trusted?
  keys.end() );


Because the method is called from

kdepim-4.12.1/messagecomposer/composer/keyresolver.cpp:1696

return trustedOrConfirmed( selectKeys(...


The method trustedOrConfirmed already checks if the key is trusted and may
ask the user what to do. But if selectKeys erases the key this won't happen.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328311] KMail doesn't let me manually select a non verified PGP key which doesn't contains the receivers address

[kolAflash]

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

--- Comment #4 from kolAflash kolafl...@kolahilft.de ---
Created attachment 84676
  -- https://bugs.kde.org/attachment.cgi?id=84676action=edit
Fix for KDE bug 328311. Should work at least for KDE 4.11.4 and 4.12.1.

My first KDE patch. Yhaaa! :-)

Please test it and if OK, commit! I'll be here if you've got any questions.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328311] KMail doesn't let me manually select a non verified PGP key which doesn't contains the receivers address

[kolAflash]

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

kolAflash kolafl...@kolahilft.de changed:

   What|Removed |Added

   Severity|normal  |major

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328311] New: KMail doesn't let me manually select a non verified PGP key which doesn't contains the receivers address

[kolAflash]

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

Bug ID: 328311
   Summary: KMail doesn't let me manually select a non verified
PGP key which doesn't contains the receivers address
Classification: Unclassified
   Product: kmail2
   Version: 4.11.2
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-bugs@kde.org
  Reporter: colafl...@gmx.net

I'm writing an email to a friend, who recently changed his email address. I got
his unverified!!! PGP key, which he hasn't updated with to his new email
address until now. When I try to send an encrypted email, KMail tells me:

 There are conflicting encryption preferences for these recipients.
 Encrypt this message?
 [Encrypt] [Do not encrypt] [Cancel]

That's all ok, because KMail can't autodetect the right key, because any key
contains my friends new email address.

I select [Encrypt]. The KMail gives me a dialogue to manually select a key I
want to use. I select my friends unverified key, which doesn't contains his new
email address (the one I set as receiver). But I know he can decrypt that key.
Then KMail gives me:

 It was not possible to create a message composer.

And I'm back in the composer window.
If I run KMail from shell, it gives me this message on the shell in exactly
that moment:
kontact(11836) ValidTrustedOpenPGPEncryptionKey: bad validity 0

This error only appears if the PGP key hasn't been trusted in the PGP
key-chain. If I repeat the scenario with a fully trusted key, everything is
fine. Looks like KMail forgets to bring up this dialogue, which normally
appears for non fully trusted keys.

 One or more of the OpenPGP encryption keys or S/MIME certificates for 
 recipient some-mail-addr...@example.com is not fully trusted for encryption.
 The following keys or certificates have unknown trust level: 
 some-mail-addr...@example.com
 [Continue] [Cancel]

P.S.
My Cryptographic Message Format is set to OpenPGP/MIME in KMail.
(relevant???)

Reproducible: Always

Steps to Reproduce:
1. Write an encrypted email to some address you don't have a PGP key for.
2. Click send and manually select some not fully trusted PGP key to encrypt
with.
Actual Results:  
KMail jumps back to composer window, tells you
 It was not possible to create a message composer.
and puts this to stdout:
kontact(*) ValidTrustedOpenPGPEncryptionKey: bad validity 0

Expected Results:  
Bring up this dialogue:

 One or more of the OpenPGP encryption keys or S/MIME certificates for 
 recipient some-mail-addr...@example.com is not fully trusted for encryption.
 The following keys or certificates have unknown trust level: 
 some-mail-addr...@example.com
 [Continue] [Cancel]

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs