-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.01.13 08:34, Remi Collet wrote:
Hi,
Is there any known incompatibility issue using both Enigmail 1.5
and Thunderbird Conversations extensions ?
I have report[1] of a user about thunderbird segfaulting, at
startup, when both are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19.02.13 05:33, John A. Wallace wrote:
I see a setting in the OpenPGPPreferences dialogue on the Basic
tab, a checkbox for“Never ask for any passphrase”. When might that
be useful? Setting it appears to create the effect
of“Error–signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It would seem to me that there could be a set of rules made from
the options in Thunderbird’s menu items at Tools | Account Settings
| OpenPGP Security, which might very well be different from a set
of rules made from the options in TB’s menu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03.03.13 04:15, Greg Jewell wrote:
This happened for me as well. I am running Thunderbird 17.0.3 on
Windows 7 (64-bit), with gpg4win-2.1.0 installed to C:\Program
Files (x86)\GNU\GnuPG. Enigmail started complaining that it cannot
find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06.03.13 14:28, Patrick Fleming wrote:
Jean-David Beyer jeandavid8 at verizon.net writes:
I run these and have no trouble at all.
thunderbird-10.0.7-1.el6.centos.x86_64
gnupg2-2.0.14-4.el6.x86_64 enigmail-1.4.4+15.0-33.29.1.x86_64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07.03.13 14:34, Patrick Fleming wrote:
I'm also not sure how Enigmail 1.4 is different from 1.5.1 in that
1.4 works on the CentOS system and 1.5.1 does not. (And I have no
problem on my Debian system with Enigmail 1.5.1, Thunderbird 17.0.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.03.13 02:00, Grant Olson wrote:
Ubuntu 12.10 Thunderbird 17.0.3 (ubuntu version) Enigmail 1.4.6
(ubuntu version) gpg2 2.0.17
When I try to do any signing actions, I get a No smartcard found
in reader error. I can use the card via the
On 12.03.13 23:46, Daniel Kahn Gillmor wrote:
Hi Enigmail folks--
The message i'm writing right now is not signed by me (please inspect
the source to verify). However, when viewed in enigmail, I believe it
will have a Good signature header if you already have my key.
This is because i've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23.03.13 17:44, Willi Mann wrote:
Hi!
In Debian bug http://bugs.debian.org/703112 a user reports that
enigmail fails to encrypt/decrypt messages. It seems that the
binary components do not get loaded. Can anyone give me some hints
how to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28.04.13 02:04, Sukhbir Singh wrote:
Hi,
So fixing the identifiable MIME boundaries is a necessary but
not sufficient step toward achieving the goals the Tor devs are
aiming for. If there are no downsides to making the change, it
would be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30.04.13 15:49, shar...@nym.hush.com wrote:
[...]
Symptoms:
The outgoing message, as encrypted for the intended recipients,
appears to get wrapped in another layer of encryption, keyed only
for the sender. The recipients get the error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02.05.13 02:40, Grant wrote:
On 05/01/2013 01:27 PM, Daniel Kahn Gillmor wrote:
Grant, if you can give us any hints about what the problem was
(or even better, what specific resolution you needed), that would
be a great help to anyone else
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07.05.13 13:08, Oystein Thorvaldsen wrote:
Whenever I forward an already signed email enigmail strips away
the existing signature, whether or not I add my own. I would very
much like to keep this existing signature, but I cannot find a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07.05.13 17:49, Doug Barton wrote:
On 05/07/2013 08:46 AM, Patrick Brunschwig wrote:
On 07.05.13 13:08, Oystein Thorvaldsen wrote:
Whenever I forward an already signed email enigmail strips
away the existing signature, whether or not I add my
On 05/29/2013 04:54 PM, Eduard Christian Dumitrescu wrote:
One way (as discussed in a private exchange with dkg and others) would
be to only show the signed parts of signed messages and ignore
whatever isn't signed. If a particular message doesn't display
properly, one only has to temporarily
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29.06.13 21:40, Doug Barton wrote:
On 06/29/2013 10:25 AM, Patrick Brunschwig wrote: | On 29.06.13
01:43, Yury Bulka wrote: | Dear Enigmail developers, | | I'd like
to translate Enigmail into Ukrainian. The Enigmail | website
instructs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02.07.13 23:02, Ludwig Hügelschäfer wrote:
On 02.07.13 22:56, Ludwig Hügelschäfer wrote:
No, and I can't reproduce it. Replying to encrypted mails works
well for me with todays 24.0a2 and todays Enigmail on Mac OS X.
Tested again: Only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have released Enigmail v1.5.2 for Thunderbird 17.x and newer, and
SeaMonkey 2.16.x and newer. The release fixes several bugs, issues and
regressions found in the past months. Furthermore, it ensures
compatibility with the latest releases of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21.07.13 20:15, Marius Stübs wrote:
my name is Marius, I'm from Hamburg, Germany, and as I'm new to
Enigmail development, I want to introduce myself. I've used
enigmail for several years, but some time recently I just stopped
using it. Since
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28.07.13 17:10, Kreuvf wrote:
Hi there,
since I upgraded my machine to Ubuntu 12.04 I experience weird
wrapping of long quote lines.
SOFTWARE SETTINGS Enigmail: 1.5.2 Thunderbird: 17.07
I use the following settings in Thunderbird:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06.08.13 16:12, Klearchos-Angelos Gkountras wrote:
Can some explain why I have to Disable loading IMAP parts on
demand Disable flowed text (RFC 2646) View message body as plain
text Use 8 bit encording for message sending Do not compose HTML
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This smells like a bug.
I'll look into it.
- -Patrick
On 16.08.13 10:20, Thomas Hotz wrote:
Hi Øystein, Hi list,
I have a similar behaviour here, on one correspondent. Does it
happen with adresses to which there is more than one key in your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17.08.13 14:09, David wrote:
For several days the Enigmail development page, the Nightly
builds, has had no links for downloads. Is this intended? Have I
missed something?
We switched from http to https a few days ago. The problem might be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17.08.13 18:21, Max Maass wrote:
So, your proposal would be to define a new header like
X-Enigmail-Encrypt for this, and add the logic to enable
encryption somewhere in the compose*-Files?
Yes, exactly. You can probably just re-use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18.08.13 12:41, Max Maass wrote:
On 08/18/2013 12:13 PM, Patrick Brunschwig wrote:
I'd say go ahead using X-Enigmail-Draft-Status and leave it up
to the user to decide for inline-PGP vs. PGP/MIME. And yes,
you'll need to set
.
Thomas
Am 16.08.2013 16:29, schrieb Patrick Brunschwig:
I can't reproduce this. Do you see any error message in the
Error Conosle (Tools Error Console)?
-Patrick
On 16.08.13 12:06, Patrick Brunschwig wrote:
This smells like a bug.
I'll look into it.
-Patrick
On 16.08.13 10:20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13.09.13 14:53, Kosuke Kaizuka wrote:
Hi Patrick,
On Thu, 12 Sep 2013 18:20:10 +0200, Patrick Brunschwig wrote:
Over the last few months I developed two new features that I
would like to have tested a bit more widely than just by myself
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14.09.13 14:15, Max Maass wrote:
I can confirm this behaviour on Linux x64 with latest (non-beta)
Enigmail and Thunderbird 17.0.8 (latest from ubuntu repositories).
Never noticed it before, but this is a big information leak.
Also, saving
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14.09.13 15:22, Bob Williams wrote:
I'm confused as to how to increase the time my passphrase is
cached. In openPGP/Preferences/Basic I have entered a value of 360
minutes, but when I click OK, I see the following message:
Your system uses
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14.09.13 17:32, Tom Ritter wrote:
While Thunderbird is open, but not being used, just downloading
messages in folders in the background (constantly) - Enigmail will
pop up the passphrase dialog. I didn't try and open an encrypted
mail,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15.09.13 16:44, Lars Noodén wrote:
On 09/15/2013 05:39 PM, Patrick Brunschwig wrote:
On 14.09.13 14:15, Max Maass wrote:
On 09/14/2013 01:56 PM, Lars Noodén wrote:
Hi,
I notice that if a message draft is started encrypted
they be
using right now?
I notice that I am asked more than once for the password to send a
message. Should it be asking for the password to encrypt and again
to sign the message?
Thanks, Ernie Gargas
On 9/29/2013 10:28 AM, Patrick Brunschwig wrote:
Since Thunderbird 24 is released, Enigmail does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm happy to announce the availability of Enigmail v1.6, a new major
version for Thunderbird 17.x, Thunderbird 24 and newer, and
SeaMonkey 2.16.x and newer. There were several new features added and
several bugs, issues and regressions found in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13.10.13 09:48, Robert J. Hansen wrote:
On 10/12/2013 4:57 PM, dpmurvih...@wpi.edu wrote:
I'm having an issue that is preventing me from sending email.
The first question is, is this an Enigmail issue?
I'd suggest uninstalling Enigmail.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.11.13 20:43, Daniel Kahn Gillmor wrote:
hi there enigmail folks!
It looks to me like the released enigmail-1.6.tar.gz is drawn from
commit id a16b43c68c9a829034f44082c392e5f9fb42e864, but that commit
is not explicitly tagged (or maybe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.11.13 21:11, Daniel Kahn Gillmor wrote:
This patch allows the build to proceed cleanly when using
-Wunused-but-set-variable and without FORCE_PR_LOG ---
src/nsEnigMsgCompose.cpp | 2 +- 1 file changed, 1 insertion(+), 1
deletion(-)
On 12.11.13 19:49, Daniel Kahn Gillmor wrote:
i'm trying to use the standard enigmail debugging capability to figure
out why a message is failing verification in enigmail.
The message is clearsigned PGP/MIME, and it verifes correctly in another
MUA (notmuch, using libgmime). Other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22.11.13 17:36, Per Gunnarsson wrote:
Hello!
I am using enigmail on Debian Wheezy for AMD 64.
When trying to attach my public key from the OpenPGP menu, the
option is greyed out and I can't click the box Attach my public
key. Of course
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14.11.13 09:06, Daniel Kahn Gillmor wrote:
This patch records the library name and constants expected for
debian GNU/kFreeBSD. Without this line, enigmail 1.6 on that
platform fails with:
[ERROR] enigmail.js: Enigmail.setAgentPath:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13.12.13 22:29, Daniel Kahn Gillmor wrote:
in http://bugs.debian.org/732067, a user reports that the checkbox
Automatically decrypt/verfiy messages in the OpenPGP menu isn't
working any more.
Apparently, the menu option is only available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15.12.13 17:59, Peter Lebbing wrote:
Hello list,
I mentioned[1] on the GnuPG-Users mailing list that I sometimes
encounter a bug in Enigmail where the resulting mail is strangely
formatted when signing with my smartcard fails. Daniel Kahn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18.12.13 00:24, Philip Jackson wrote:
On 17/12/2013 14:38, Anne Wilson wrote:
On 15/12/2013 17:43, Philip Jackson wrote:
1. import public key : this seems to work and the imported key
is immediately displayed in Kleopatra but not in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15.12.13 18:43, Philip Jackson wrote:
[...]
Second Case : after the 'import public key' option has been used
and the key is available in the key manager and appears to be valid
but I have not yet set a trust level nor signed the key.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23.12.13 23:33, Philip Jackson wrote:
Hi,
During recent testing with enigmail 1.7a1pre, I found that
sometimes under the 'Details' button there was the usable option to
'View OpenPGP photoID'. That surprised me because I thought it had
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12.11.13 18:41, Patrick Brunschwig wrote:
On 12.11.13 18:33, Daniel Kahn Gillmor wrote:
On 11/12/2013 12:27 PM, Patrick Brunschwig wrote:
This patch won't work for Thunderbird 19 and newer, as the
referenced ${enigDllFile} (line 153) is only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31.12.13 14:45, Nicolai Josuttis wrote:
[...]
I was very confused because again and again I found no way to
define per-recipient rules (although several places referred to
them, such as when sending an email the menu entry Ignore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03.01.14 18:20, Nicolai Josuttis wrote:
Again, what do we consider as a beginner, here (see above)? Anybody
not just trying things out but registering his/her email address
needs the ability and all required informations to sign the key.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.01.14 04:52, Doug Barton wrote:
On 01/10/2014 01:56 AM, Patrick Brunschwig wrote: | On 09.01.14
21:38, Daniel Kahn Gillmor wrote: | This addresses
http://sourceforge.net/p/enigmail/bugs/239/ --- |
ui/content/enigmailCommon.js | 5 - 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09.01.14 21:38, Daniel Kahn Gillmor wrote:
This addresses http://sourceforge.net/p/enigmail/bugs/239/ ---
ui/content/enigmailCommon.js | 5 - 1 file changed, 4
insertions(+), 1 deletion(-)
patch is committed.
- -Patrick
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This is a message targeted to everyone who builds Enigmail on their
own, in particular all Enigmail package maintainers for Linux and *BSD.
I have rewritten the build system of Enigmail from scratch. The new
build system is now completely decoupled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31.01.14 15:25, Nicolai Josuttis wrote:
Hi,
currently, not many of the people I exchange emails with use PGP.
For this reason, I have some receiver rules (usually enabling PGP)
and by default encryption disabled.
Now, if I send emails
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01.02.14 12:09, Mathias Koerber wrote:
Recently I detected that enigmail seems to be selecting the wrong
keys to encrypt a mail to.
I changed the config to manual key selection only, and the
matching recipient keys are selected at the top
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02.02.14 14:57, Philip Jackson wrote:
Hi,
Thanks for the replies from Patrick, Sebastian and Nicolai. (I
don't really understand the comment about standard for showing /
hiding columns in Thunderbird but that doesn't really matter.) I
do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05.02.14 07:57, Doug Barton wrote:
On 02/04/2014 10:42 PM, Charly Avital wrote:
Doug Barton wrote on 2/5/14, 6:00 AM:
I have a correspondent whose key1 has been on my key ring for
years. They recently sent me key2 which they would prefer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19.02.14 08:27, Daniel Kraft wrote:
Hi all!
As I understand it, the key ingredient into a secure encrypted
messaging system is a trusted exchange of public keys. GPG and
Enigmail solve this at the moment using a WoT with key signatures
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23.02.14 04:43, Daniel Kahn Gillmor wrote:
hi enigmail folks--
i know a few people have reported seeing a message verification
pane that was unrelated to the message shown beneath it.
We just got another one of these reports at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23.02.14 00:32, Daniel Kahn Gillmor wrote:
--- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1
deletion(-)
diff --git a/configure.ac b/configure.ac index f1b97c9..bbb3d13
100644 --- a/configure.ac +++ b/configure.ac @@ -2,7 +2,7 @@
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23.02.14 10:47, Daniel Kraft wrote:
Hi!
On 2014-02-22 23:42, John Clizbe wrote:
Robert J. Hansen wrote:
Daniel Kraft wrote:
Ok, I see So you don't think that Enigmail would want
to add some extra functionality over GnuPG's OpenPGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15.03.14 16:41, Egbert van der Wal wrote:
Hi,
Sorry if this has been asked before, I searched the archives and
found no references to the same thing.
I'm looking into setting up PGP signing and encryption. Especially
the signing is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20.03.14 13:52, Antoine Polatouche wrote:
Viewing signed and crypted messages : the messages are seen as
ascii (not verified, not decrypted), no enigmail header
displayed. At this time, - gpg is working fine in a terminal (
version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20.04.14 15:30, Nicolai Josuttis wrote:
Hi all,
as announced some weeks ago, I just pushed a patch for a first
implementation to provide the ability to automatically encrypt
messages if all valid keys are known without the need to have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24.04.14 20:52, Mike Acker wrote:
On 04/23/2014 10:33 PM, Daniel Kahn Gillmor wrote:
FWIW, i fully agree that the right place to fix this misbehavior
is in GnuPG itself, not in enigmail. I care about non-enigmail
users of GnuPG, and i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27.04.14 14:02, Philip Jackson wrote:
I prepared a first message to be encrypted to a new recipient whose
key I had retrieved from a key server. First attempt to send it
resulted in an abort :
Send operation aborted.
USERID_HINT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05.05.14 02:13, Daniel Kahn Gillmor wrote:
On 05/04/2014 11:41 AM, Phil Stracchino wrote:
It appears to em that terms like 'thorough', 'careful' are
scarcely even applicable to what you're trying to accomplish
here. Mode 1 is basically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19.05.14 12:59, Remi Collet wrote:
Le 12/01/2014 17:35, Patrick Brunschwig a écrit :
This is a message targeted to everyone who builds Enigmail on
their own, in particular all Enigmail package maintainers for
Linux and *BSD.
Do you have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06.06.14 08:47, Onno Ekker wrote:
Hi,
Yesterday another OpenSSL was published:
https://www.openssl.org/news/secadv_20140605.txt
Along with it the security advisory came a fix for servers.
Enigmail is using GPG, which probably uses
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21.06.14 17:25, Clayton Dewey wrote:
Hi All,
I'm excited to start using Enigmail. I tried setting up with
Thunderbird on my Mac, it's running OSX 10.7.5 right now (I know,
out of date :P).
However, I ran into the following issue when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30.06.14 18:39, Kosuke Kaizuka wrote:
-- enigmail.seeAccountSettings.label says (see Account
Settings - OpenPGP Security)
2. help/messenger.html
- line 31 and 33 do not follow re-labeling OpenPGP to Enigmail
- line 46 Enigmail -gt;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.07.14 23:53, Daniel Kahn Gillmor wrote:
hi folks--
a friend recently sent me a PGP/MIME encrypted/signed message from
k-mail 1.13.7.
enigmail decrypted it but claimed bad signature.
Looking at it in more detail, i see that the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.07.14 17:43, Daniel Kahn Gillmor wrote:
On 07/11/2014 11:32 AM, Patrick Brunschwig wrote:
Enigmail can decrypt/verify both methods. However, unless you use
Enigmail 1.7 (or nightlies) KMail emails cannot be verified
correctly.
Hm, i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm happy to announce the availability of Enigmail v1.7 for
Thunderbird 24 - 31, and SeaMonkey 2.20 and newer.
This version brings many new features (special thanks to Nico
Josuttis!) plus a lot bug fixes. Furthermore, this version ensures
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09.07.14 00:10, Daniel Kahn Gillmor wrote:
i am seeing the following misbehavior with the 1.7 beta i packaged
from yesterday (i have convenient encryption set as the
default):
When i reply to a message from someone for whom i have a key,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14.07.14 20:55, Martin Vegter wrote:
Hello,
I am using Enigmail 1.6 and Thunderbird (Icedove) 24.6.0.
In the main menu on the top, I have following option deactivated:
OpenPGP - Automatically Decrypt/Verify messages
However, when I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18.07.14 14:18, Alexander Buchner wrote:
Am 18.07.2014 13:45 schrieb Ludwig Hügelschäfer:
So you have the possibility to compare sent and received message.
You could do that by hand or by a file diff tool after exporting
the message out of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03.08.14 23:06, David wrote:
Win 7 x86_64 Enigmail 1.7
I do not have 'attach your key' set anywhere that I look but
Enigmail insists on attaching my key to all signed/encrypted emails
that I send.
Is this now a default? Or an i missing a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08.08.14 17:46, Dr. Martin Senftleben wrote:
Hi,
I'm new to this list and apologise in advance in case my request
has been discussed already. I've been using GPG for quite a while,
and since I use Thunderbird I also use EnigMail and am very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09.08.14 12:09, Olav Seyfarth wrote:
Hi Martin, Hi Patrick,
Patrick wrote:
We use the same place that Thunderbird ueses to display
information about the message, such as Thunderbird thinks this
message is junk/scam/...
Martin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09.08.14 13:10, Martin wrote:
Hi,
Enigmail 1.7 added a feature to work around buggy Exchange
servers. However, it is being a bit too helpful and prevents the
correct parsing of posts to (some) mailman mailing lists.
1. here is an excerpt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09.08.14 15:14, Patrick Brunschwig wrote:
[...]
Note that it was packaged up in multipart/mixed and that This
is an OpenPGP/MIME encrypted message (RFC 4880 and 3156)
appears twice.
3. Previous versions of Enigmail had no problem parsing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09.08.14 16:56, Martin wrote:
Hi Patrick,
thanks for the quick response. I can confirm that this fixes the
bug for signed e-mails. For *encrypted* e-mails the bug is still
there.
The patch was supposed to fix encrypted mails, not signed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12.08.14 10:36, George Stachovskis wrote:
Patrick . . .
Please note the following spelling error in the Enigmail
Preferences dialogue of the recent release . . .
Should be A*dd*resses!
Thanks, that's already fixed on the master branch
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14.08.14 13:41, Jogi Hofmüller wrote:
Dear all,
After a recent upgrade to enigmail 1.7 (Debian/testing) I got
annoyed by the gnome hijacked gpg-agent message and disabled the
gpg part of gnome keyring. Now enigmail asks for my passphrase
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15.08.14 10:55, Onno Ekker wrote:
On Fri, Aug 15, 2014 at 9:36 AM, digg...@openmailbox.org
mailto:digg...@openmailbox.org wrote:
I am trying to install Enigmail 1.7 on Windows and Linux computer
but when I try to download from Thunderbird
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
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 Hammerl wrote:
Ok, thanks for pointing that out. I installed the nightly (build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12.09.14 13:17, Philip Jackson wrote:
T'bird 31.0, enigmail 1.7.2, ubuntustudio 1404 :
I don't have the 'automatically decrypt / verify messages' option
set - my choice.
When I see the mention [Enigmail] appear in the Thunderbird header
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21.09.14 23:00, Doug Barton wrote:
FYI, I moved my list subscription to my new e-mail address today,
and noticed that lists.enigmail.net presents an SSL cert for
hotpoint. It's particularly bad to encourage users to click through
such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03.10.14 08:41, Onno Ekker wrote:
On Fri, Oct 3, 2014 at 8:31 AM, Onno Ekker o.e.ek...@gmail.com
mailto:o.e.ek...@gmail.com wrote:
Hi, I think I have the same problem. When I send a message to
myself and choose to sign and encrypt, on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07.10.14 17:14, Tobias Hahn wrote:
Hello everybody,
I was wondering if there is a way to directly check in Enigmail if
there are keys available for the recipients entered when writing a
new email. Using Enigmail - Manage Keys - Keyserver -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01.11.14 22:14, Willi Mann wrote:
Hi,
I got a bug report saying that enigmail does not work on Debian
armel/armhf ports [1]. In the Add-ons window, enigmail is listed as
disabled, but it does not say why (and there is no way to enable
it).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02.11.14 12:39, Willi Mann wrote:
Hi Patrick,
Patrick Brunschwig wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
On 01.11.14 22:14, Willi Mann wrote:
Hi,
I got a bug report saying that enigmail does not work on
Debian armel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02.11.14 16:48, Willi Mann wrote:
Hi,
Patrick Brunschwig wrote:
Components.classes[@mozilla.org/xre/app-info;1].getService(
Components.interfaces.nsIXULRuntime).XPCOMABI
The result is
arm-eabi-gcc3
I've checked the icedove
On 03.11.14 07:24, Willi Mann wrote:
Hi,
Patrick Brunschwig wrote:
In which file should this be fixed? configure.ac? Makefile?
That's in config/getOsTarget.pl.
I've applied the following patch:
http://sources.debian.net/src/enigmail/2:1.7.2-2/debian/patches/0004-fix_target-os.patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09.11.14 19:31, David wrote:
What was ever decided about the request that Enigmail *always*
occupy the top of a Thunderbird email header instead of pushing the
message down only when active with a signed/encrypted message?
Why do you ask?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15.11.14 21:22, Włodzimierz J. Ziółkowski wrote:
Hi all,
I created key pairs for all of my e-mail accounts and with one I've
got a problem in my Thunderbird. The inbox is displayed in /gray
italics/ (see attached file) and any message that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05.12.14 23:27, terrygal...@mailbolt.com wrote:
Hi,
I have two mail accounts in Thunderbird.
Enigmail is installed and working.
I can set up DEFAULTs in Enigmail that ALL accounts will use for
each sender.
I'd say you can set up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08.12.14 18:15, Philip Jackson wrote:
Using linux, Thunderbird 31.3.0, enigmail 1.8a1pre (of 2014-12-08)
I'm getting increasing numbers of emails where an enigmail alert
warns that there is an Unverified signature, Untrusted good
signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08.12.14 22:26, Philip Jackson wrote:
On 08/12/14 18:28, Patrick Brunschwig wrote:
On 08.12.14 18:15, Philip Jackson wrote:
Using linux, Thunderbird 31.3.0, enigmail 1.8a1pre (of
2014-12-08)
I'm getting increasing numbers of emails where
-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:
-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 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
1 - 100 of 697 matches
Mail list logo
