That seems reasonable. Ithink that what I did to make it work was change from the
options to gpg.conf files and restart KMail.
I think that what you are using is the IETF endorsed OpenPGP, which is described in
MIME Security with Pretty Good Privacy, RFC 3156.
S/MIME is proprietory and favoure
Hey,
Ok, think I see. Basicly the built in GnuPG support in kmail, can not handle
multi part message, SMIME. This is still true. But with the plugins it can.
When using the plugins, if you compose an email you are given the option of
which to use on the email.
I am using the plugins, so the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mark,
> Kmail does support gpg out of the box. What those plugins allow you to do
> is sign and encrypt all message parts. Which is something kmail has not
> been able to do before. It also can use certs.
I do not understand what has happened here
Kmail does support gpg out of the box. What those plugins allow you to do is
sign and encrypt all message parts. Which is something kmail has not been
able to do before. It also can use certs.
On Thursday 06 Feb 2003 11:47 pm, ray wrote:
> Mostly the 3.1 upgrade (I used the SuSE rpms) was easy a
Mostly the 3.1 upgrade (I used the SuSE rpms) was easy and worthwhile, BUT
KMail 1.5 caused a minor panic. It does not support GnuPG without a plug-in
that has to be installed and configured separately.
http://kmail.kde.org/kmail-pgpmime-howto.html
--
rayH
__
On Sunday 02 February 2003 3:45 pm, ray wrote:
> FYI
> On January 28th 2003, the KDE Project released KDE 3.1, a major feature
> upgrade to the successful KDE 3.0 series.
>
> http://www.kde.org
4 days now I have been waiting and still no Mandrake packagaes :) I'm not up
to compiling the bugger m
FYI
On January 28th 2003, the KDE Project released KDE 3.1, a major feature
upgrade to the successful KDE 3.0 series.
http://www.kde.org
--
rayH
___
Scottish mailing list
[EMAIL PROTECTED]
http://mailman.lug.org.uk/mailman/listinfo/scottish
