See my announcement to the Encryption forum.

[quote user="tigershark"]

Thanks for your answer,

As you mentioned, only GPG 2.x supports S/MIME and I'm not able to get GPGrelay

running with a GPG version > 1.4.x.

It also look's like, that development has stopped on GPGrelay for almost three years now.

 greetings

On my wishlist is a build-in S/MIME and GPG(PGP) support, without the

need of any additional plugins. I've many contacts using S/MIME certificates,

so it would be usefull, if Pegasus would support this.

I don't expect this to be available in the next releases, but I hope i could

be added to the "far future" roadmap of development.

Pegasus Mail does support S/Mime via the PMPGP extension. http://www.pmpgp.de/pmpgp/indexen.htm. Once you buy your own S/Mime certificate you can send or receive anyone else's S/Mime processed messages.  Of course you need a current version of PGP to start with.

Martin 

Thanks for your answer.

I know this extension for Pegasus, but I'm using GPG for years know and I don't want to change to PGP :-)

So it would be good, if Pegasus could support this regardless whether you are using GPG or PGP.

How about using GPGrelay http://sites.inka.de/tesla/gpgrelay.html: You don't need any Pegasus Mail extension, GnuPG (since v2.x) supports S/MIME, and if it doesn't satisfy your needs its developer should be the most proper person to ask for more.

Hello!

As far as I can see, GPGrelay is a great tool - it makes encryption avalaible to anyone, no matter whether one's e-mail program can or cannot handle that. However, there is an issue concerning your e-mail messages (i.e., the e-mail messages saved on your machine): GPGrelay encrypts outside of your e-mail program, so any message that you save, copy, move etc. within your favourite e-mail program is not encrypted.

This is the usual workflow for sending a message when GPGrelay is installed: Pegasus Mail -> GPGrelay -> SMTP-server -> ... other servers ... -> recipient's POP3-sever -> recipient. A message to be sent will be encrypted / signed by GPGrelay, i.e. after you wrote and sent the message and after you saved a copy-to-self of that message. So, the copy-to-self is not encrypted or signed.
When receiving an encrypted message, you see a similar behaviour: GPGrelay handles the encryption of an incoming message before Pegasus Mail is getting the message, so Pegasus Mail will get that message not encrypted. If you want to save, copy, move etc. that message, you will have an unecrypted version of it.

In other words: the messages are encrypted only as long as long as they are on their way on the internet. However, your local copies of incoming and outgoing mail are not encrypted. You have to decide for yourself whether you accept that.

First of all: Pegasus Mail doesn't store copies to self in encrypted form no matter whether using an extension or not, so this argument is meaningless; secondly you can simply store your whole mailbox on an encrypted disk or partition: e.g. using TrueCrypt http://www.truecrypt.org/. This way you can even keep all your email communication encrypted ...

Thanks for your answer,

As you mentioned, only GPG 2.x supports S/MIME and I'm not able to get GPGrelay

running with a GPG version > 1.4.x.

It also look's like, that development has stopped on GPGrelay for almost three years now.

 greetings