Is there a way of getting Dkim working with Pegasus.

I've probably not got this right but as far as I can tell it seems the email client needs to sign the headers with a private key which can then be verified via the public key stored on the email server ?

[quote user="Euler GERMAN"]I think is worth mention that I found Pegasus Mail because I was after an e-mail client that could work with PGP. I'm a big fan of both. Maybe that's why I found the post at https://www.mailpile.is/blog/2016-12-13_Too_Cool_for_PGP.html much more palatable than that from Bruce Schneier. Note that I said "palatable". I'm in no way to contradict Bruce's expertise, but I prefer to disagree.[/quote]

Well, that's from three years ago, a pretty long time with regard to Internet and cryotography developments, and things haven't been getting better since then, unfortunately ... we would really need someone or something as good as and his (mostly unknown) co-workers when PGP started its world wide distribution in 1991.

Both updates provide a fix for working with the upcoming Pegasus Mail version 4.73 which introduces a security fix preventing Pegasus Mail from loading renamed malicious binary libraries.

PMPGP can be downloaded via and PMSM from the community's add-ons page (please check for your proper language version).

This sub-forum isn't limited to topics concerning Pegasus and Mercury, or even email as such, so from that point of view the post is acceptable. The advertising aspect is more debatable, but as the service in question is free it might be reasonable to inform about it.

Both updates provide a minor fix for using them with Pegasus Mail 4.7 and adjustments for dealing with Thunderbird's S/MIME shortcomings. 

PMPGP can be downloaded via and PMSM from the community's add-ons page (please check for your proper language version).

[quote user="zippes"]From a practical sense... which method have you folks found to be the most effective and the least hassle?

Thanks...

zippes[/quote]

Actually all of them so recipients may have the choice. The best way, though, would be attending a key signing party for directly verifying key ownership, see .

Hi there, 

after installing QDGPG and GPG4Win  I tried to encrypt emails but got got this error. I searched the internet for the phrase without finding hints so I just wanted to write down the solution here: 

I missunderstood the password field in the encryption dialog of pegasus. As the handbook of QDGPG (qdgnupg.chm) states: 

If you are encrypting only, leave the Password field empty. This

is very important.

Looks like spam to me, sorry ...

[quote user="radhx"]>7: Socket read error 2746.[/quote]

According to MSDN this translates to An existing connection was forcibly closed by the remote host.

[quote user="radhx"]The same forwarded mail goes through with "Encryption.." box checked.[/quote]

Since encryption modifies the contents seen by the server it must be something within the contents of the message causing the error.

[quote user="MikeSoja"]Something I subsequently read here last night seemed to indicate that it isn't possible to encrypt those copies to self in Pegasus.  Is that true?  Do any of the Pegasus plugins provide the encrypt to self functionality?[/quote]

Yes and no. As a workaround you may want to send yourself (permanent) BCC's - if QDGPG supports encrypting to BCC addresses which I don't know.

Both are based on a pair of private and public key.

The difference is, that with S/MIME the public key will be transformed by an certification agency (CA) to a certificate. This certificate (and not the public key) is, what you publish with your mails (i.e. in your mails signatures) and that someone, who wants to send a encrypted mail to you, uses to encrypt that mail. So you need a CA to get that certificate.

bye    Olaf

[quote user="Angus Scott-Fleming"]GPGRelay looks like overkill, as it encrypts EVERY outbound email.  Posting to lists and communicating with those who won't or can't use PGP/GPG would really be a problem... [/quote]

Thanks for your opinion on this, Angus!

The updated version may be retrieved from the , for changes see below: Please post your comments and suggestions to this forum.

Changes:

• Some more issues with AutoList address administration have been fixed.
• As usual some minor issues have been dealt with.

[quote user="idw"][quote user="rgl"]I have observed two strange behaviors regarding the automatic selection of private keys depending on the current mail identity. Both behaviors seem to be related. 

Before that I migrated from PMail 4.51 with PMPGP 6.2.7.1 on Windows XP SP3 32bit to

PMail 4.62 with PMPGP 6.2.7.4 on Windows 7 SP1 64bit, both Pegasus and PMPGP were the plain

english versions with no internationalization.[/quote]

Ok, tested on Windows 7 with PGP 10.0.3: No such issue, correct key is pre-selected and used. Maybe testing on XP with PGP 8.1 or 6.5.8 will reveal a different result.[/quote]

Testing on XP with PGP 6.5.8 (the regular one) doesn't fail either: It automatically preselects the proper (matching) key in the dialog using the cached passphrase for signing with exactly this (pre)selected key. Nothing I can do, sorry, there must be something else involed: Maybe using non-regular and heavily outdated PGP versions isn't the best idea ...

[quote user="radhx"]My S/MIME plugin is version 1.1.3.4 dt. 2011-01-04, 23:11:32,  916.8KB within the PMSMEn.zip, I hope that is the latest one.[/quote]It's the latest publicly available one, yes.

[quote user="radhx"](when I try to update S/MIME plugin using s/mime-frontend->About->Update option, I get error "Can not read internet data".)[/quote]

I never set up the required web site since the extension isn't really ready for broader public consumption because of all the "hacks" I needed to implement to get it working.

[...]

The colouring Expression rule lies somewhere in the middle of all the other Headers mails-to-folder rules.[/quote]

My extension isn't involved in any filterung and colouring at all (there's not need for colouring anyway unless you retrieve email other than via POP3 (IMAP, Mercury or the like)), IOW: There's probably something going wrong with your ruleset only you can figure out.

Just FYI, I've uploaded the most recent update to the .

[quote user="radhx"]I am having problem opening signed emails with double click after installing latest version 1.1.3.3. (previous version was opening the emails wilth valid signatures with double click)

One can open the same email with <RETURN> key after highlighting the same.

If I double click on a signed mail (valid signature or mismatched one), the following error pops up:[/quote]

Just a follow-up: I've implemented a workaround for this issue which I cannot really fix as it doesn't happen within the extension itself. It turned out that it existed with previous versions as well but only occurs in rather special situations which are not connected to the (double-click) scenario described above. If anyone needs the most recent version before I make it publicly available please contact me personally.

[quote user="A01"]I look in the "copies to self" folder. The message I sent does not have NewLines where I put them.[/quote]

On another note: Not displaying isn't the same as doesn't exist: You'd need to check the raw message data for telling whether there actually are linebreaks or not because there are several formatting options which may hide their existence: First of all if terminating a long line with a Return key may look like there actually isn't a line break depending on the line length used in the display window. Secondly it depends on the display options selected in your reader or preview windows (via context menu/right mouse click): If Wrap long lines or Reformat long lines are enabled Pegasus Mail may reflow the text. In general it's a good idea to insert two "Returns" if you want to reliably separate paragraphs from one another.

No idea.

Thanks for reminding me ;-) that I still need to update the installers of my encryption extensions, I've prepared some other fixes as well for them, watch out ...