On 07/09/2018 23:47, Patrick Chkoreff wrote:
> so Mr. Brunschwig has done great work in a very
> tricky domain.
Agreed. :-)
--
Mark Rousell
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subsc
Mark Rousell wrote on 09/07/2018 06:24 PM:
> I believe that 'PGP Tray' is part of Symantec's PGP email encryption
> software. Either that or it's a very old version of the PGP software. I
> vaguely seem to recall that PGP Tray was part of PGP Desktop before
> Symantec bought it. But that was a ver
I wrote:
> It still begs the question of why I can't Set Owner Trust on a newly
> imported key.
I fiddled around some more. This time I SIGNED the key, telling a lie
by saying that I had checked it very carefully. Then when I
right-clicked on the key the "Set Owner Trust" option appeared under
On 07/09/2018 22:58, Patrick Chkoreff wrote:
> Mark Rousell wrote on 09/07/2018 05:53 PM:
>
>> What mail client is Bob using? The first message part header you
>> quoted[1] is correct for PGP/MIME which I would have thought any modern
>> mail client should be able to decode.
> Oh, he's using Outloo
> Whenever I import a new key, the only way I can ever encrypt to it is to
> first go into Key Management and set "Owner Trust" to "Ultimate". I
> just now imported a key and when I right click on it, I see no menu
> option to set Owner Trust. I do see the option on keys I've already
> imported
Mark Rousell wrote on 09/07/2018 05:53 PM:
> What mail client is Bob using? The first message part header you
> quoted[1] is correct for PGP/MIME which I would have thought any modern
> mail client should be able to decode.
Oh, he's using Outlook or something. He uses the "PGP Tray" to decrypt
t
Whenever I import a new key, the only way I can ever encrypt to it is to
first go into Key Management and set "Owner Trust" to "Ultimate". I
just now imported a key and when I right click on it, I see no menu
option to set Owner Trust. I do see the option on keys I've already
imported.
So, when
On 07/09/2018 22:31, Patrick Chkoreff wrote:
>> Can anybody think of something more I can do to force Enigmail NOT to
>> set up one of those "encrypted.asc" file attachment things,
> OK I think I figured something out. I went into the Per-Recipient rules
> and set PGP/MIME to "Never". I sent a m
> Can anybody think of something more I can do to force Enigmail NOT to
> set up one of those "encrypted.asc" file attachment things,
OK I think I figured something out. I went into the Per-Recipient rules
and set PGP/MIME to "Never". I sent a message to my friend Bob and saw
this:
MIME-Versio
When I send a message to my friend "Bob", who uses a Windows system, he
sees a blank email with an attached encrypted file, which he has to save
out to decrypt instead of using the clipboard decryption in his Windows
"tray". I view the Message Source and sure enough I see this:
Content-Type: appl
Lachezar Dobrev wrote on 09/07/2018 10:59 AM:
> You can use 'Inline PGP' either from the Enigmail menu in the mail
> composer. You can also set it via a recipient rule to avoid doing that
> every time.
My Enigmail menu when composing already shows this option selected:
* Protocol: Inline PGP
Florian Knodt wrote on 09/07/2018 01:24 PM:
> Autocrypt sends your (automatically generated) public key in every mail.
> If the receiver also supports it it will automatically encrypt all
> messages to you. If the concept/implementation is a good or bad idea -
> well, let's say there are different
On 9/7/18 7:02 PM, Patrick Chkoreff wrote:
> I even went to Account Settings / OpenPGP Security and unchecked the
> option "Use PGP/MIME by default". Made no difference.
Autocrypt sends your (automatically generated) public key in every mail.
If the receiver also supports it it will automatically
Patrick Chkoreff wrote on 09/07/2018 01:02 PM:
> I guess I'll just have to live with this
> "Autocrypt" header thing, whatever that is.
On second thought, it really bothers me that even when sending a plain
text email, the email includes a big "Autocrypt" header. Why would
Enigmail insert that f
Lachezar Dobrev wrote on 09/07/2018 10:59 AM:
> You can use 'Inline PGP' either from the Enigmail menu in the mail
> composer. You can also set it via a recipient rule to avoid doing that
> every time.
My Enigmail menu when composing already shows this option selected:
* Protocol: Inline PGP
> I can't sign email with Enigmail 2.0.8 -v
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
You can use 'Inline PGP' either from the Enigmail menu in the mail
composer. You can also set it via a recipient rule to avoid doing that
every time. You can also disable 'Use PGP/MIME by default in the
Account preferences, in the 'OpenPGP Security' tab.
PGP/Mime is better suited to handle e-ma
I recently sent an encrypted email via Enigmail to a friend who does all
his crypto from the command line using gpg directly. He remarked that:
> I got your message. However, it was sent as an encrypted
> attachment in a blank MIME message. The message was not
> marked with the property "encrypte
On 09/07/2018 02:48 AM, Per Gunnarsson wrote:
> I can't sign email with Enigmail 2.0.8
>
>
I think I can.
--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key:166D840A 0C610C8B Registered Machine 1935521.
/( )\ Shrewsbury, New Jerseyhttp://linuxcounter.net
^^-
I can't sign email with Enigmail 2.0.8
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
20 matches
Mail list logo
