-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22.07.15 06:25, Geordon VanTassle wrote:
I just set up PGP encryption from Facebook, and I know it works,
based on successful results from Mailvelope. However, I can't
figure out how to configure Postboox and Enigmail to work
correctly. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20.07.15 11:02, François Patte wrote:
Le 18/07/2015 15:52, Ludwig Hügelschäfer a écrit :
On 17.07.15 16:55, François Patte wrote:
Bonjour,
I can't send signed mail with enigmail 1.8.2 and tb 31.5 or
31.7: no dialog box is opened to ask
- Originale Nachricht -
Von: daniel Azuelos dan+moz...@pasteur.fr
Gesendet: 20.07.2015 - 17:56
An: enigmail-users@enigmail.net
Betreff: Re: [Enigmail] Enigmail with Keepass2 on Linux
Patrick Brunschwig écrivait (wrote) :
| Actually, that's the interesting thing. Thunderbird does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19.07.15 04:22, Palloy wrote:
Ubuntu 14.04, Thunderbird 31.7.0, Enigmail 1.8.2 (20150416-1748)
When I generate a key with a 63 character passphrase, it appears
to work OK. But when I then send an email containing my Public Key,
I am asked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/14/2015 05:36 PM, Patrick Brunschwig wrote:
On 14.07.2015 14:09, Kai Michaelis wrote:
This patch extends the save/restore profile function so that it
saves the contents of pgpRules.xml too. When restoring a saved
profile all existing per
On 14.07.2015 14:09, Kai Michaelis wrote:
This patch extends the save/restore profile function so that it saves
the contents of pgpRules.xml too. When restoring a saved profile all
existing per-recipient rules are _deleted_ and replaced with the ones
in the saved profile.
Hi Kai
From what I
On 10.07.2015 09:59, Daniel Kahn Gillmor wrote:
Apparently, Mac OS X /bin/date treats -d entirely differently than GNU
/bin/date. This should work no matter what /bin/date you have
installed.
Thanks, committed. I hope it will also work on Mac OS X.
-Patrick
signature.asc
Description:
On 10.07.2015 12:14, Kai Michaelis wrote:
This patch adds two buttons to the preferences dialog. One on the Basic tab
for loading Enigmail settings from a file and another on the Advanced tab
for saving the current settings into a file.
The settings are (de)serialized as a single JSON
On 10.07.2015 12:26, Daniel Kahn Gillmor wrote:
On Thu 2015-07-09 18:13:26 -0400, Patrick Brunschwig wrote:
On 09.07.2015 06:35, daniel Azuelos wrote:
Is it possible within Enigmail when including one's public key
to have the usual feedback that this attachment is done?
What I would like
On 09.07.2015 12:38, Daniel Kahn Gillmor wrote:
On Wed 2015-07-08 18:38:53 -0400, Patrick Brunschwig wrote:
On 08.07.2015 11:41, Daniel Kahn Gillmor wrote:
If the environment variable $SOURCE_DATE_EPOCH is set, use that as the
build date. otherwise, use the current date.
See https
On 03.07.2015 17:07, daniel Azuelos wrote:
Hello,
Where may I get an official logo of Enigmail ?
This is for a lecture on information security.
You can get it from me. I'll send it to you by separate email.
-Patrick
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23.05.15 19:03, Elias Assmann wrote:
Hi List,
I recently installed Enigmail 1.7.2 (Thunderbird 31.7.0) and
imported a new keypair. However, it seems that Enigmail is still
trying to use an old keypair. When editing a new message, trying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21.05.15 19:56, Philip Jackson wrote:
On 18/05/15 14:06, Philip Jackson wrote:
On 18/05/15 08:32, Patrick Brunschwig wrote:
And how could enigmail display an alertbox which contained
no
message ?
I think because of this (which is issued
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17.05.15 20:11, Philip Jackson wrote:
On 17/05/15 17:31, Patrick Brunschwig wrote:
On 16.05.15 21:10, Philip Jackson wrote:
On 16/05/15 16:22, Patrick Brunschwig wrote:
On 16.05.15 14:50, Philip Jackson wrote:
enigmail 1.8.2 Thunderbird
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16.05.15 21:10, Philip Jackson wrote:
On 16/05/15 16:22, Patrick Brunschwig wrote:
On 16.05.15 14:50, Philip Jackson wrote:
enigmail 1.8.2 Thunderbird 31.6.0 UbuntuStudio 1404, gnupg
2.0.22
Selecting the next message in a new thread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18.05.15 06:32, Beckert wrote:
Hello,
SeaMonkey: 2.33.1 Enigmail: 1.8.2 GnuPG: 2.1.1
if I decrypt a mail, the message window shows a green header with
encrypted message, correct signature from ..., but below the
decrypted message isn't
bingnBADEI439.bin
Description: PGP/MIME version identification
encrypted.asc
Description: OpenPGP encrypted message
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
:
Hi Patrick--
On Sat 2015-05-09 11:09:49 -0400, Patrick Brunschwig wrote:
Today I committed several changes that removed all binary
components from Enigmail. That is, it is no longer required to
create _any_ binary libraries for Linux/Unix systems. Any build
will now run on all platforms
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Today I committed several changes that removed all binary components
from Enigmail. That is, it is no longer required to create _any_
binary libraries for Linux/Unix systems. Any build will now run on all
platforms supported by Thunderbird (probably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06.05.15 23:11, Philip Jackson wrote:
On 06/05/15 18:05, Patrick at wrote:
On 03.05.15 13:54, Philip Jackson wrote:
using enigmail 1.8.2 with Ubuntu 1404 and Thunderbird 31.6.0
A signed incoming email had displayed below the text a colon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03.05.15 13:54, Philip Jackson wrote:
using enigmail 1.8.2 with Ubuntu 1404 and Thunderbird 31.6.0
A signed incoming email had displayed below the text a colon
separated sub-listing ( about 250 lines) of some parts of my public
keyring.
Sure, send me the logs.
Patrick
- Original Message -
From: Philip Jackson philip.jack...@nordnet.fr
Sent: 03.05.2015 - 14:54
To: Enigmail user discussion List enigmail-users@enigmail.net
Subject: [Enigmail] strange unrequested display of signatures
using enigmail 1.8.2 with Ubuntu 1404
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22.04.15 15:34, AV wrote:
Hello,
Im using enigmail with Thunderbird and I have with some emails from
some users which I'm receiving the problem that they will not be
decrypted automatically when I select the email.
In order to decrypt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18.04.15 14:15, Daniel Kahn Gillmor wrote:
On Sat 2015-04-18 12:43:07 +0200, Alexander Buchner wrote:
Are there reasons against using HSTS for the whole site?
Nope, i don't think there are any reasons for enigmail.net to avoid
HSTS. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16.04.15 20:24, Daniel Kahn Gillmor wrote:
package/enigprefs-service.js mentions that it is dual-licensed
MPL-1.1 or GPL, but it doesn't indicate which version of the GPL.
Other dual-licensed parts of the codebase are explicitly GPL 2 or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17.04.15 12:24, Onno Ekker wrote:
On Fri, Apr 17, 2015 at 11:30 AM, Patrick Brunschwig
patr...@enigmail.net mailto:patr...@enigmail.net wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
On 16.04.15 20:24, Daniel Kahn Gillmor wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17.04.15 16:08, Kosuke Kaizuka wrote:
On 2015/04/17 22:06, Patrick Brunschwig wrote:
Enigmail is not Mozilla, nor a product by Mozilla. It's (still)
MPL 1.1 licensed. To change the license would require to contact
_all_ contributors - going
not respond
to this mail.
- -Patrick
On 15.04.15 21:24, John Dose wrote:
Hi, THAT was the solution, i set my own key to ultimate trust
(from unknown) and the problem is gone :-) Thansk!
On 04/15/2015 09:04 PM, Patrick Brunschwig wrote:
This _is_ the improved error message. GnuPG does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm happy to announce the availability of Enigmail v1.8.2 for
Thunderbird 31, and SeaMonkey 2.29 and newer.
Changes
===
This is a bugfix release.
Important Note
==
Enigmail v1.8.x is the last branch of Enigmail to support GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15.04.15 15:19, Ian Mann wrote:
Under OpenPGP - Preferences, check Override with and put in the
following in the link next to it:
/usr/bin/gpg2
This is actually NOT required. It's fully sufficient to install
gnupg2. If both gpg2 and gpg are
This _is_ the improved error message. GnuPG does not report more details,
therefore there is nothing more specific for Enigmail to report.
You have to check in the key manager if the key you specified in the accout
settings for Enigmail is valid, fully trusted and not expired.
Patrick
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14.04.15 10:25, Anthony Papillion wrote:
Hello Again Everyone,
This problem started with 1.7.x and seems to persist into the new
beta. It might be something wrong with one of the keys I'm
encrypting to but I can't figure out which key it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12.04.15 14:39, Jan-Peter Rühmann wrote:
Am 12.04.2015 um 10:52 schrieb Ludwig Hügelschäfer:
On 12.04.15 10:13, Jan-Peter Rühmann wrote:
Am 11.04.2015 um 21:57 schrieb Ludwig Hügelschäfer: Thanks for
the Answer
But it seems you have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03.04.15 15:31, Daniel Kahn Gillmor wrote:
On Thu 2015-04-02 12:32:47 -0400, Patrick Brunschwig wrote:
I fixed a few bugs over the last couple of days. As some of the
changes were not straight forward, I have uploaded a new beta
version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I fixed a few bugs over the last couple of days. As some of the
changes were not straight forward, I have uploaded a new beta version
for public testing.
The fixed bugs mainly cover message composition, saving (encrypted)
drafts and improvements to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31.03.15 13:08, Daniel Krebs wrote:
Hi, I just installed Enigmail Version 1.8.1 (20150323-1740) on
Linux. In my gpg.conf I wrote:
keyserver hkps://hkps.pool.sks-keyservers.net
Enigmail doesn't recognize this. After installing, I had to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29.03.15 17:53, li...@datenritter.de wrote:
Hi!
Enigmail 1.8.1 causes me and users I support some pain at the
moment.
I don't want to ignite any (probably futile) usability
discussions. Still I would like to suggest a few things:
1.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28.03.15 15:59, Blaise Pascal wrote:
Hi,
using Linux Mint 17 / Thunderbird (24.4.0) / Enigmail 17.2 with
gpg2... Once deciphered, Enigmail (or gpg-agent) keeps the
passphrase forever in memory although I have a
.gnupg/gpg-agent.conf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26.03.15 14:44, Anna F J Morris wrote:
On 26/03/15 12:21, Anna F J Morris wrote:
Hi, I have increasingly serious and bizarre problems since the
new version, does anyone have time to help me on IRC? It's going
to take some time to untangle I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25.03.15 20:36, Doug Barton wrote:
On 3/25/15 4:44 AM, Patrick Brunschwig wrote:
On 25.03.15 09:04, Doug Barton wrote:
I was reading some list mail today and came across the
attached with 1.8.1.
Is this a new thing that Enigmail is doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25.03.15 09:04, Doug Barton wrote:
I was reading some list mail today and came across the attached
with 1.8.1.
Is this a new thing that Enigmail is doing? If so, how do we make
it go away?
Yes it's new and no, it's not new. The new thing
I'm happy to announce the availability of Enigmail v1.8.1 for
Thunderbird 31, and SeaMonkey 2.29 and newer.
Changes
===
This is a bugfix release addressing some disturbing regressions
introduced in the last release.
Important Note
==
Enigmail v1.8.x is the last branch of
Done.
I'm the only one who can do this.
-Patrick
On 22.03.15 14:28, Charly Avital wrote:
Ludwig pls unsubscribe me, I am hospitalized and cannot do it myself, thanks
Charly
Sent from Charly's iPhone
___
enigmail-users mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21.03.15 10:57, Olav Seyfarth wrote:
Hi Bob,
Deletion was a shade more complex as two old Thawtes keys had
private keys, but all is now well. Thanks again,
So, how did you solve that? I also had two secret keys, now
removed. I'd like to
On 20.03.15 15:52, Matthew Woehlke wrote:
The signature verification/warning banner at the top of messages is
illegible when using a light-on-dark color scheme; see attached.
Hard-coding the foreground color as well as the background color would
be an improvement, but please note that some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I pushed a number of changes that remove support for GnuPG 1.x from
Enigmail. The main objective was to remove anything concerning
passphrase handling from Enigmail, as GnuPG 2.x does this by itself.
Given the many places I had to touch in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18.03.15 15:53, Robert J. Hansen wrote:
But what percentage of overall enigmail users are they, and how
likely are they to blindly send their key to a keyserver rather
then blindly click a button to attach their public key?
[...]
If you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18.03.15 06:39, Doug Barton wrote:
On 3/17/15 8:00 PM, Daniel Kahn Gillmor wrote:
On 18/03/15 12:43, Doug Barton wrote:
Were the buttons for encrypt and sign moved up to their own
toolbar instead of the old icons at the bottom because the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17.03.15 22:25, Daniel Kahn Gillmor wrote:
hi enigmail folks--
after running make in 1.8, i see the contents below in
unused.txt.
Many of these do indeed seem to be unused. Would a series of
patches that clean them up be welcome, or are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18.03.15 01:07, Daniel Kahn Gillmor wrote:
hi enigmail folks--
I see that there are now test suites in the enigmail source!
Well yes, we have _very_ few of them; currently only to test the
concept. Details can be found here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04.03.15 18:27, Patrick Brunschwig wrote:
I created a survey open for everybody to find out if we should set
the default in Enigmail to inline-PGP or PGP/MIME. The survey is
open until March 14.
https://www.surveymonkey.com/s/H53J2LD
I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm happy to announce the availability of Enigmail v1.8 for
Thunderbird 31, and SeaMonkey 2.29 and newer.
Major Changes
=
* Improved user interface for message composition
* Simplified setup wizard
* Possibility to permanently decrypt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14.03.15 17:39, Philip Jackson wrote:
On 14/03/15 15:22, Patrick Brunschwig wrote:
On 13.03.15 20:06, Philip Jackson wrote:
On 13/03/15 17:16, Patrick Brunschwig wrote:
On 13.03.15 15:45, Philip Jackson wrote:
For this spontaneous change
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14.03.15 17:39, Philip Jackson wrote:
sent to you at your address.
Apart from the Thunderbird peculiarity of turning the address field
red (even though the address is already in my address book since
years), it looks like the tick box
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12.03.15 18:40, Philip Jackson wrote:
I receive a signed message from a friend and it has a pink Enigmail
header that the signature verification has failed. I am curious as
to which key he used so I click 'Details' and the Enigmail Alert
box
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12.03.15 20:38, Philip Jackson wrote:
Using Thunderbird 31.5.0 with Enigmail version 1.8a1pre
(20150312-0013) on linux.
Recently, I've been paying a lot of attention to the new interface
in enigmail especially the enigmail toolbar when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13.03.15 15:45, Philip Jackson wrote:
For this spontaneous change to occur, one needs these factors
to exist :
1. the 'To' field is in red type (with a red cursor) 2. the
'To' field must be completed and not left blank 3. the
spontaneous
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12.03.15 18:13, Philip Jackson wrote:
In enigmail's key manager,
1. select someone else's public key (one which has a photoID) 2.
view the key properties 3. click 'select action' and select photoID
- photoID is displayed 4. In photoID
Patrick Brunschwig 7/03/15 19:07 -from Ian Mann 7/03/15 19:25
(containing a quote from Patrick's mail) -from Ludwig Hugelschafer
7/03/15 19:57 (containing a quote from Ian Mann)
Pass from Ludwig's mail to Ian's and with Ian's mail open, you can
get offers to see a key which turns out to be Ludwig's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09.03.15 22:28, Philip Jackson wrote:
Hi Patrick :
On 07/03/15 19:13, Patrick Brunschwig wrote:
Most of the translations for Enigmail v1.8 are still very
incomplete.
Please help improving the translations on
http://beta.babelzilla.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.03.15 00:15, Philip Jackson wrote:
Using Sunday's nightly (Enigmail version 1.8a1pre (20150308-0013))
Thunderbird 31.5, linux.
Two manifestations of undesirable behavior.
1. When writing an email, I click on the icons to get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09.03.15 02:06, Ian Mann wrote:
Is this version close to release? Love what I see in the Nightly
version, especially the User Interface changes, thanks for all the
hard work
Yes. I still have to fix some small bugs and improvements, and I'm
with technical french. But I can try.
How would I start if that would be of use?
guillaume
On 07/03/15 01:13 PM, Patrick Brunschwig wrote:
Most of the translations for Enigmail v1.8 are still very
incomplete. Here is the current status for all incomplete
translations:
Dutch94
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06.03.15 17:05, Philip Jackson wrote:
On 03/03/15 18:27, Philip Jackson wrote:
On 03/03/15 15:44, Robert J. Hansen wrote:
Really easy:
1. The Help button beside Convenient encryption settings
is sometimes unresponsive. I saw this bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01.03.15 22:07, Philip Jackson wrote:
Hi Patrick :
On 26/02/15 18:36, Patrick Brunschwig wrote:
I have created the first *beta* release of Enigmail v1.8. It
contains many changes to the user interface, especially message
composition
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03.03.15 15:44, Robert J. Hansen wrote:
1. The Help button beside Convenient encryption settings is
sometimes unresponsive. I saw this bug with my own two eyes
(thanks, Dmitri!) and can confirm it.
Could it be that the help window was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I created a survey open for everybody to find out if we should set the
default in Enigmail to inline-PGP or PGP/MIME. The survey is open
until March 14.
https://www.surveymonkey.com/s/H53J2LD
- -Patrick
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27.02.15 11:48, Onno Ekker wrote:
Can you please add 1.8beta1 to the list of versions for which we
can report bugs? At the moment it is only possible to specify
either version 1.7.2 or nightly...
Use nightly, I don't consider it an official
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27.02.15 13:52, Daniel Kahn Gillmor wrote:
On Thu 2015-02-26 12:36:44 -0500, Patrick Brunschwig wrote:
I have created the first *beta* release of Enigmail v1.8. It
contains many changes to the user interface, especially message
composition
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have created the first *beta* release of Enigmail v1.8. It contains
many changes to the user interface, especially message composition,
and quite a lot of bugs were fixed.
I would appreciate to get as many bugs reported as possible such that
we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17.02.15 02:06, Robert J. Hansen wrote:
Yes, I am. Bad idea? :-/
puts on official Enigmail hat
Although we're happy GnuPG has released version 2.1, new users
should continue to use 2.0 for the time being. Enigmail 1.7.2 was
released on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16.02.15 17:51, Rainer Blome wrote:
Hi everyone!
Recently I have, for at least the third time in my life, made an
effort to use PGP (open implementations).
With two correspondents, I have managed to send encrypted mails
back and forth,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.02.15 15:02, Philip Jackson wrote:
On 11/02/15 13:14, Patrick Brunschwig wrote:
On 10.02.15 23:51, Philip Jackson wrote:
Running Enigmail version 1.8a1pre (20150202-0013) with
Thunderbird 31.4.0 and linux
Incoming message causes yellow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12.02.15 15:07, Besnik Bleta wrote:
Hello,
I would appreciate if someone gives a bit of help about the
following strings:
1. Error - No valid armored OpenPGP data block found
Does armored refer to some specification or is just kind
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.02.15 15:25, Dimitri Dhuyvetter wrote:
On 11-02-15 14:36, Patrick Brunschwig wrote:
On 11.02.15 14:17, Dimitri Dhuyvetter wrote:
As of lately it has become impossible for me to sign outgoing
messages or decrypt incoming messages. Sending
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.15 23:51, Philip Jackson wrote:
Running Enigmail version 1.8a1pre (20150202-0013) with Thunderbird
31.4.0 and linux
Incoming message causes yellow enigmail header to appear (Part of
the message signed with unknown key; click on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.02.15 14:17, Dimitri Dhuyvetter wrote:
As of lately it has become impossible for me to sign outgoing
messages or decrypt incoming messages. Sending encrypted messages
seems to still work, but saving an encrypted message as draft
resulted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06.02.15 23:30, Doug Barton wrote:
[...]
By that same token, what compelling use case does 2.0.x provide
that 1.4.x does not? The gpg-agent is interesting, and potentially
useful for heavy command line PGP users; but for Enigmail's
purposes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07.02.15 00:24, Doug Barton wrote:
On 2/6/15 3:05 PM, Robert J. Hansen wrote:
By that same token, what compelling use case does 2.0.x provide
that 1.4.x does not?
Werner has several times made various noises about stopping work
on 1.4, as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06.02.15 00:33, Doug Barton wrote:
On 2/5/15 3:26 PM, Ian Mann wrote:
With old equipment can the user remain on 1.x with an old version
of enigma?
No, that's the point of this exercise, to remove 1.x support
altogether. :)
I'd formulate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05.02.15 21:02, Doug Barton wrote:
On 2/4/15 11:01 PM, Patrick Brunschwig wrote:
The question is not so much the effort - you won't get a figure
from me. The main concern is code complexity, which makes things
hard to read, understand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05.02.15 16:46, Philip Jackson wrote:
On 04/02/15 18:13, Patrick Brunschwig wrote:
My plan is as follows: * Enigmail 1.8.x will still support GnuPG
1.4.x. However, if Enigmail detects GnuPG 1.4.x, a message will
be displayed saying that GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05.02.15 09:49, Besnik Bleta wrote:
Hello,
There’s a typo in enigmail.dtd:
specifiy
instead of specify.
I'd say you looked at some older version of enigmail.dtd? I cannot
find this on master; I think it was fixed already.
- -Patric
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05.02.15 17:11, Koszta Dániel wrote:
I'd say you looked at some older version of enigmail.dtd? I
cannot find this on master; I think it was fixed already.
It appears to be present in some files.
$ grep -Rl 'specifiy' .
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As my current key will expire at the end of this year, I have created
a new key pair:
Key ID: 0xDD5F693B
Fingerprint: 4F9F 89F5 505A C1D1 A260 631C DB11 87B9 DD5F 693B
I will switch to using my new key with immediate effect. My old key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29.01.15 09:09, Kosuke Kaizuka wrote:
Hi,
I am using Thunderbird 34.0b1, Enigmail 1.8a1pre (2015-01-28),
GnuPG 2.0.26 (Gpg4win 2.2.3 Light) on Windows 7 x64 Pro SP1. I can
see Patrick's, Ludwig's and Olav's photo IDs from View OpenPGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28.01.15 19:27, Pascal Winkelmann wrote:
Am 28.01.2015 um 19:11 schrieb Patrick Brunschwig:
Why can you not see the photo ID on Windows? Is the View OpenPGP photo
ID menu no active for your key, or is there no visible reaction from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28.01.15 16:42, Pascal Winkelmann wrote:
Hi,
I recently attached a photo id to my key but I can't see it if I'm using
a windows machine. If I boot up my Ubuntu system everything works fine.
Is this a problem with my public key or enigmail ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21.01.15 22:53, Stefan Koch wrote:
I have thought some time about the user interface / user experience
of Enigmail, because in my environment I see that many normal
users struggle to work with enigmail - even if they'd like to.
I looked a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.01.15 12:42, Anne Wilson wrote:
On 10/01/2015 14:38, Besnik Bleta wrote:
Më 01/10/2015, 04:11 PM, Bryant Evans shkroi:
Thanks guys for the quick response. Maybe someone in the future
could jump start such a program. Unencrypted mails on
that's the same root cause...
Cheers Felix
On Thu, Aug 28, 2014 at 9:09 AM, Patrick Brunschwig
patr...@enigmail.net wrote: This surprises me. I thought that
Enigmail gets decoded content from Thunderbird. But I'll check
this, and if not, I'll fix it.
-Patrick
On 28.08.14 08:46, Felix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06.01.15 15:23, Philip Jackson wrote:
On 06/01/15 13:07, Ian Mann wrote:
I am going to stick with ver 1.8 because of the graphics in
write mode.
The fact that you can see the large padlock alerted me to the
issue I was experiencing.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05.01.15 00:58, Robert J. Hansen wrote:
An argument, why your policy is based on one irrational human
would be nice. It may be the case, that people don't want
intelligence people on software, but as far as it's public, you
are not. There
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31.12.14 17:54, Kristy Chambers wrote:
[...]
With all due respect on the work of Enigmail and its developers,
it's just terrible. Maybe you ask, if I haven't complained earlier.
Yeah it is bad, and I'm too lazy to report bugs, but I also think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28.12.14 14:44, 894nevada wrote:
Hello all, I would like the images that accompany email sent to me
displayed along with the text of the email message. How might I go
about changing my settings to allow this?
You'll have to switch to HTML
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21.12.14 14:18, Ludwig Hügelschäfer wrote:
On 21.12.14 13:30, Ludwig Hügelschäfer wrote:
Hi,
On 16.12.14 16:43, terrygal...@mailbolt.com wrote:
The actual test is:
You did not configure this identity for using Enigmail
security. Send
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20.12.14 23:05, Doug Barton wrote:
Another feature I really like (in fact I think I was one of the
ones that suggested it a while ago) is the ability to automatically
sign a response to a signed message. I don't routinely sign stuff,
but if I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21.12.14 21:09, Philip Jackson wrote:
On 21/12/14 16:33, Patrick Brunschwig wrote:
This seems to be a bug, as Enigmail obviously tries to save the
message encrypted but cannot find the required public key -
as it isn't configured yet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20.12.14 15:01, Ludwig Hügelschäfer wrote:
Hi Philip,
On 20.12.14 13:30, Philip Jackson wrote:
Using Thunderbird 31.3.0 with linux UbuntuStudio 1404 and
enigmail version 1.8a1pre (20141208-0013) :
the 'photo id' buttons do not work in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.12.14 14:14, Onno Ekker wrote:
With Enigmail 1.7.2 enabled in Thunderbird 36.0a2 Aurora, going to
Tools - Account Settings shows all accounts as 'invalid account
email address'. The following message is logged in the error
console:
501 - 600 of 697 matches
Mail list logo
