[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#356: marked as done (signing messages with pgp fails)
From:       owner () bugs ! kde ! org (Stephan Kulow)
Date:       1999-04-18 18:48:00
[Download RAW message or body]

Your message dated Sun, 18 Apr 1999 20:44:31 +0200
with message-id <99041820450500.03792@beta>
and subject line Done
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 25 Jan 1999 13:40:32 +0000
From Matthias.Kiefer@stud.uni-karlsruhe.de Mon Jan 25 14:40:32 1999
Received: from nz40.rz.uni-karlsruhe.de ([129.13.197.4]:20233 "EHLO \
mailgate.rz.uni-karlsruhe.de" ident: "TIMEDOUT") by alpha.tat.physik.uni-tuebingen.de \
                with ESMTP id <106334-10203>; Mon, 25 Jan 1999 14:40:21 +0100
Received: from calvin (isdn216-75.rz.uni-karlsruhe.de [129.13.216.75])
	by mailgate.rz.uni-karlsruhe.de with smtp (Exim 2.04 #3)
	id 104mFT-0002FS-00; Mon, 25 Jan 1999 14:40:15 +0100
From:	Matthias Kiefer <Matthias.Kiefer@stud.uni-karlsruhe.de>
To:	submit@bugs.kde.org
Subject: signing messages with pgp fails
Date:	Sun, 24 Jan 1999 15:29:44 +0100
X-Mailer: KMail [version 1.0.11]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99012415485504.04105@calvin>
Content-Transfer-Encoding: 8bit
Return-Path: <Matthias.Kiefer@stud.uni-karlsruhe.de>
X-Orcpt: rfc822;submit@bugs.kde.org

Package: KMail
Version: 1.0.11

When signing messages with pgp5.0i the messages are sometimes not signed
correctly. When looking at the message in the outbox-folder there comes the
message that the signature is wrong. Same error happens if you save the message
and check it.

I have tried to find the problem why sometimes it happens and sometimes not.
But I couldn't find what causes the problem.


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic