Re: [Enigmail] Compatibility issue with Whiteout Mail

2014-08-27 Thread Felix Hammerl
Ok, thanks for pointing that out. I installed the nightly (build date:
2014-08-28, version: 1.8a1pre, git rev:
7c9b70e1c587c8daae9409e2347a36a5fe326201), restarted Thunderbird, but
that was to no avail. Same log output, same error message.

However I just discovered that Enigmail just fails for anything else
but 7bit Content-Transfer-Encoding. This makes me wonder: What is
Enigmail doing with the MIME nodes? Does it even decode them according
to the declared encoding? I have tried the following encodings for the
MIME node containing the PGP payload:
- base64: fail
- quoted-printable: fail
- 7bit: works

So this makes me wonder: Does enigmail try to scrape the PGP payload
directly from the string representation of the flattened MIME tree
instead of interpreting and decoding the MIME tree first and then
doing its work on the properly decoded MIME tree?!

Cheers
Felix

On Thu, Aug 28, 2014 at 1:25 AM, Olav Seyfarth  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> Hi Felix,
>
> this is a known bug in 1.7, your issue should be fixed if you use the current
> nightly. There will be a 1.7.1 shortly.
>
> Olav
> - --
> The Enigmail Project - OpenPGP Email Security For Mozilla Applications
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> Comment: Dies ist eine elektronische Signatur - http://www.enigmail.net/
>
> iQGcBAEBAwAGBQJT/mjlAAoJEKGX32tq4e9WRKQL/RHHeZrONwsZ/NDQsF5nNj89
> o7ouuWyDpfg5cEqsW6ciU/PF7Te1VocBBB9F7XoaFrZbkdsdER5j9cM59jNOInSi
> xy7se9bJTipAOgeO9gRKd7YgsI6J5ipL37O4I9udowMAF446VMI6E0ht+BMRT7pT
> bi4PKOVw1CBKHOxcW9DsU7QP7dNMGlFe82C7houkVdQZJ1UVZs0y0yjXirwtmBFC
> pV+ZBUjFg6o6vqmUj59tnPVAPo8FAVqg8cp2etgtcDQy01MFz4lO22LlOilH8W6I
> Ng7FS1+X8+IW7ad9jEZuBRwzf9TXBpP5wg1tuRBtZNa3UpyA6dtEjW9REL53uLKa
> iu1Dq/umRRnHHPRrZO1xxUQpRPEif0aDlmJiGaCzp9OPwAJdV6BbGbXwyY2IKOCv
> h+OKuNds0vlkJ8BvgclNY96u7II8RXSoOomXk4Q7QLfKrj0DvRHt/BwdkYod5jjI
> isTGTDPuDW5jx23xCevagWAsXCmIJYhAonybh0WMHA==
> =8MlA
> -END PGP SIGNATURE-
>
> ___
> 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

___
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


Re: [Enigmail] Problem in Manjaro

2014-08-27 Thread Dr. Martin Senftleben
Hi,

Am 28.08.2014 um 03:00 schrieb Klearchos-Angelos Gkountras:
> If u use the same home and format the only the root it will work
> fine :) but if you tried to move to flash drive the ~/.gnupg wont
> work . maybe it's problem of gnupg on linux .. maybe you had to
> export it with different way .. I go to sleep

Hm, I'm not sure what you are trying to say. I'm not using a flash
drive, I didn't export anything...

> 
> On 08/28/2014 02:23 AM, Olav Seyfarth wrote:
>> Hi Martin,
> 
>>> Enigmail gives message that the key might be expired, and
>>> doesn't allow me to sign the message. I'm sure the key is not
>>> expired. The message is: The key was not found or is invalid.
>>> The (sub-)key could have been expired.
> 
>> for the key in question, what validity does "gpg --list-key 
>> " yield? UIDs should be "[ uneing.]" (german).
> 
>>> I guess that it has to do with the switch of Distros
> 
>> I doubt that.
> 
>> If that all doesn't help, please 1) upgrade to Enigmail nightly
>> if installed through package manager, I recon you should close
>> TB, uninstall Enigmail package, install XPI from enigmail.net
>> through TB AddOn Manager and restart TB, then redo your test
> 
>> If that all doesn't help, please 2) create debug directory,
>> enable debugging (needs expert settings), restart TB, redo your
>> test, close TB, ZIP debug dir and send cleaned files along with 
>> screenshots, exported public keys, prefs.js and pgprules.xml to 
>> me.
> 
>> Olav
> 
>> ___ 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
>
>> 
> 
> 
> ___ 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
>
> 
-- 
Herzliche Grüße!

Martin Senftleben

P.s.: Ein Anhang lässt sich nicht öffnen? Hier gibt's Infos dazu:
http://www.drmartinus.de/pgpindex.html


___
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


Re: [Enigmail] Problem in Manjaro

2014-08-27 Thread Dr. Martin Senftleben
Hi and thanks for replying,

Am 28.08.2014 um 01:23 schrieb Olav Seyfarth:
> Hi Martin,
> 
>> Enigmail gives message that the key might be expired, and doesn't
>> allow me to sign the message. I'm sure the key is not expired.
>> The message is: The key was not found or is invalid. The
>> (sub-)key could have been expired.
> 
> for the key in question, what validity does "gpg --list-key
> " yield? UIDs should be "[ uneing.]" (german).

Yes, it says "[ uneing.]"

>> I guess that it has to do with the switch of Distros
> 
> I doubt that.
> 
> If that all doesn't help, please 1) upgrade to Enigmail nightly if
> installed through package manager, I recon you should close TB,
> uninstall Enigmail package, install XPI from enigmail.net through
> TB AddOn Manager and restart TB, then redo your test

Nightly build doesn't do any better

> If that all doesn't help, please 2) create debug directory, enable
> debugging (needs expert settings), restart TB, redo your test,
> close TB, ZIP debug dir and send cleaned files along with 
> screenshots, exported public keys, prefs.js and pgprules.xml to
> me.

You got to help me here a bit. I set a folder for a log-file, but it's
not been created (have severy restarts past me). I'm not wsure where
to get to the expert settings. I tried sending emails to me each time
I restarted TB.
Where do I find all the other things you mention (cleaned files along
with screenshots, exported public keys, prefs.js and pgprules.xml),
and what kind of screenshots do you want? What do you mean by
"cleaned" files?

A new problem occured, however: Since I wanted to write down step by
step what's happening, I saved this mail (actually a previous mail) as
draft in order to restart TB. After opening and editing it, all of a
sudden TB or enigmail decided that it can't decrypt the mail, and now
the draft is empty. However, it wasn't encrypted, as I never got to
the point to encrypt it.

Thanks,

Martin

> 
> Olav
> 
> ___ 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
>
> 
> 

-- 
Herzliche Grüße!

Martin Senftleben

P.s.: Ein Anhang lässt sich nicht öffnen? Hier gibt's Infos dazu:
http://www.drmartinus.de/pgpindex.html


___
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


[Enigmail] [UX] [UI] Attach Public Key entry in composition window

2014-08-27 Thread Michael Carbone
Hi all,

Whenever I first introduce users to Enigmail, we run into a UI issue.

It comes up when showing a user how to attach their public key to an
email they are composing. The functionality for "Attach Public Key..."
is neither in the "Attach" or "Enigmail" entires of the composition
toolbar. It is instead only in the "Enigmail" menu bar.

If the point of the entries in the composition toolbar are to filter
composition-relevant options from the larger menu bar functionality, I
think this counts as such a option. Currently I have to always clarify
that it is the menu bar Enigmail entry and not the composition bar
Enigmail entry that has the option available.

My recommendation would be to add an entry for Attach Public Key in
Enigmail entry of the composition toolbar. Having it in the Attach entry
of the composition toolbar may also work. But I believe it needs to be
somewhere in the composition toolbar and not just in the menu bar.

Thanks,
Michael

-- 
Michael Carbone
Tech & Policy Manager
Access | https://www.accessnow.org

GPG: 0x81B7A13E
Fingerprint: 25EC 1D0F 2D44 C4F4 5BEF EF83 C471 AD94 81B7 A13E




signature.asc
Description: OpenPGP digital signature
___
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


Re: [Enigmail] Problem in Manjaro

2014-08-27 Thread Klearchos-Angelos Gkountras
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

If u use the same home and format the only the root it will work fine
:) but if you tried to move to flash drive the ~/.gnupg wont work .
maybe it's problem of gnupg on linux .. maybe you had to export it
with different way .. I go to sleep

On 08/28/2014 02:23 AM, Olav Seyfarth wrote:
> Hi Martin,
> 
>> Enigmail gives message that the key might be expired, and doesn't
>> allow me to sign the message. I'm sure the key is not expired.
>> The message is: The key was not found or is invalid. The
>> (sub-)key could have been expired.
> 
> for the key in question, what validity does "gpg --list-key
> " yield? UIDs should be "[ uneing.]" (german).
> 
>> I guess that it has to do with the switch of Distros
> 
> I doubt that.
> 
> If that all doesn't help, please 1) upgrade to Enigmail nightly if
> installed through package manager, I recon you should close TB,
> uninstall Enigmail package, install XPI from enigmail.net through
> TB AddOn Manager and restart TB, then redo your test
> 
> If that all doesn't help, please 2) create debug directory, enable
> debugging (needs expert settings), restart TB, redo your test,
> close TB, ZIP debug dir and send cleaned files along with 
> screenshots, exported public keys, prefs.js and pgprules.xml to
> me.
> 
> Olav
> 
> ___ 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
>
> 
- -- 
Klearchos-Angelos Gkountras
- 
weblog   → http://jemadux.noblogs.org
xmpp → k...@grrlz.net
Diaspora → jema...@diasp.eu
irc  → jemadux @ freenode/oftc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBAgAGBQJT/n89AAoJEDKKe8UCEhldvJ0P/0Yrz/UqPGByy5j2I8QQvjGi
Ak45+2DvRYpZUSEMO5+qtiynG6XJpccs7QGabCH5eiVyIRzGW1gFdW+cv9zlraQU
1CVhZX2j9IYnLknv4M1FG8/nS8sSVFrSgh8XngbqEbpt5dP0WIz7yggzRYww4z4m
VOT33AUFHJAJFp2YbvLvULltFsxfdV0O67fuNVPYG2CDTv0G1J9+ZRtR0qAmjawb
YkskUlOitSLiCPEqTx0QxQudbg4AJN86ZV+JYvQNKUPzEcokHlIKRvnqy3Cy5fTv
rkVokQJqgys9Kf7HlJsfFGZNNTt+fOYLlrIpqgBKmS6Rj2Bz+AJf2qCCCzoa/Mnr
/Mfc49DoNHHwe52zm5g/JwA7SvWXIG9zu051cOUGNX2587Yv4pmJlw+1vvW/zrxa
o9C0AjfO5Yt1k22R5/pqzXfJQCiYaEZ3UJlOff59bxQaCF+IGvxQRxqASsjq9aJX
nCkvM5m54Wd6XiFcJ1etrRz/y8NN3h+gL8/5vi/7dfQzconuTZVsPQBApkgV6yva
GlTQPg/oK+nwhAi7Xp/BcNf18MdHalOQgNEihwwL5l2Xe987Uwhvwuioh5irgvMx
JkxWlJXVzvSZdnTaAHObAjugRCvjQbSCuDcccAX0yqAwkochKyTC+2fzcILKCdCL
ERX2UCCnU7Ys9aAj8sgJ
=Gszh
-END PGP SIGNATURE-

___
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


Re: [Enigmail] Compatibility issue with Whiteout Mail

2014-08-27 Thread Olav Seyfarth
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

Hi Felix,

this is a known bug in 1.7, your issue should be fixed if you use the current
nightly. There will be a 1.7.1 shortly.

Olav
- -- 
The Enigmail Project - OpenPGP Email Security For Mozilla Applications
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Dies ist eine elektronische Signatur - http://www.enigmail.net/

iQGcBAEBAwAGBQJT/mjlAAoJEKGX32tq4e9WRKQL/RHHeZrONwsZ/NDQsF5nNj89
o7ouuWyDpfg5cEqsW6ciU/PF7Te1VocBBB9F7XoaFrZbkdsdER5j9cM59jNOInSi
xy7se9bJTipAOgeO9gRKd7YgsI6J5ipL37O4I9udowMAF446VMI6E0ht+BMRT7pT
bi4PKOVw1CBKHOxcW9DsU7QP7dNMGlFe82C7houkVdQZJ1UVZs0y0yjXirwtmBFC
pV+ZBUjFg6o6vqmUj59tnPVAPo8FAVqg8cp2etgtcDQy01MFz4lO22LlOilH8W6I
Ng7FS1+X8+IW7ad9jEZuBRwzf9TXBpP5wg1tuRBtZNa3UpyA6dtEjW9REL53uLKa
iu1Dq/umRRnHHPRrZO1xxUQpRPEif0aDlmJiGaCzp9OPwAJdV6BbGbXwyY2IKOCv
h+OKuNds0vlkJ8BvgclNY96u7II8RXSoOomXk4Q7QLfKrj0DvRHt/BwdkYod5jjI
isTGTDPuDW5jx23xCevagWAsXCmIJYhAonybh0WMHA==
=8MlA
-END PGP SIGNATURE-

___
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


Re: [Enigmail] Problem in Manjaro

2014-08-27 Thread Olav Seyfarth
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

Hi Martin,

> Enigmail gives message that the key might be expired, and doesn't allow me
> to sign the message. I'm sure the key is not expired. The message is: The
> key was not found or is invalid. The (sub-)key could have been expired.

for the key in question, what validity does "gpg --list-key " yield?
UIDs should be "[ uneing.]" (german).

> I guess that it has to do with the switch of Distros

I doubt that.

If that all doesn't help, please
1) upgrade to Enigmail nightly
   if installed through package manager, I recon you should close TB, uninstall
   Enigmail package, install XPI from enigmail.net through TB AddOn Manager and
   restart TB, then redo your test

If that all doesn't help, please
2) create debug directory, enable debugging (needs expert settings), restart TB,
   redo your test, close TB, ZIP debug dir and send cleaned files along with
   screenshots, exported public keys, prefs.js and pgprules.xml to me.

Olav
- -- 
The Enigmail Project - OpenPGP Email Security For Mozilla Applications
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Dies ist eine elektronische Signatur - http://www.enigmail.net/

iQGcBAEBAwAGBQJT/mh3AAoJEKGX32tq4e9W33oL/2BulblS5TOHgA1AtmqD4BT1
Q1vZ6vtzds4worLcSvAQY8PIcr3c6SNkCC4jFpMG/8uMgudkcX+0hCDyoy2DhqI1
PguoXXo3CdN9HdPSNV9+o6Na4WjlwPV0s0hTZ8g/2ehyjDU+D/hseLGxhf4yk1H/
h28h8lkoUjxZmrJjPX+HyGE3DEbO+BBSuKVXI8UkN1YBmEDRYFemvsizO5d5HJEs
rR6lODxEMn7O/G8T3WU8j+zRXoANgQQzgLSw5CSSu2nkSKm4TStIjAUFOAiiinyl
4hf1XUuBfW19Sx3FoT/KmJBnvAAB25wvLYMxR1jA/y3UTdzS4r7GVZ7f1k6WoXY3
zdv4AE+CVEaIjjGicXqy0RAb19mfNPPBEQiG2MbYYl+Fk9blfGGg8QOTo0UFKBfu
FgnUY6OmAirVXPlPVj9KgpRl3031DkgisLu8kEsh7rZHvmGgBpMM+jMSZE/zIeVg
TAOsZPpQVuA03UVTEfnYnDpToUPtLIm7LRUhpRzmRg==
=I+9t
-END PGP SIGNATURE-

___
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


Re: [Enigmail] reply encrypted to encrypted messages broken?

2014-08-27 Thread Olav Seyfarth
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

Hi Flo,

> feature is broken? Since I updated to TB 31 and the new Enigmail, it only
> works unreliably - sometimes messages signed/and or encrypted are replied
> to as plain text, sometimes it works upon the second reply. quick update:
> only seems to happen when selective quoting (mark text with mouse, then
> only that text is quoted) is used. When quoting full message, all seems to
> work.

thanks for letting us know. If you can reproduce this with current nightly in
a clean minimal profile, then pleas open a bug.

Olav
- -- 
The Enigmail Project - OpenPGP Email Security For Mozilla Applications
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Dies ist eine elektronische Signatur - http://www.enigmail.net/

iQGcBAEBAwAGBQJT/mUVAAoJEKGX32tq4e9WlHcMAKL7T/RfbjIIl84TeSsxj5U7
NkLcXUASTiA1ljL+i3RXqyPfH54OmpcndT6CVsNsKwyCnh9oPwOCM6aXpFhhgDVX
58teTPUt/bAThWa3n5Pvj7UWcRfce7fPnDJ6SOAijuqVsgi6CdQvvrpD89/2VvQs
DRa9fMpHH9QvPG63GDpXjaSI3l9zpJ5T45ZwBkvqpvpYcNXOM0w6xya9kApNq/TL
6DATLmrUShtqf2Yhk+cSaqCCz9sDUSPZ+amzYW+ZtpI4LLlnM/ECOGPw0p8/yWC8
Y2gq4otq2hMfs/oKAWrV00wfn0Oo0gO9PHtfX6qNExPWlXFW9s5tXObWZueqUmU4
3VgderLi0PVZPlBGTmA4gR87Iok2hwtDw3W6vTL07XQutZ1FfZt9ukD08quzQlYh
18WT7jsdFNljb2Y4TNYk3jTGal95erRBqhqYePz3yJDe6PTsRGLZlxPIcRs+byUx
BzAXxmuqojDO70mKawpSx8TSMZsGI9dEsc5HR8yTNg==
=+Gjb
-END PGP SIGNATURE-

___
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


Re: [Enigmail] reply encrypted to encrypted messages broken?

2014-08-27 Thread Florian Effenberger
Hi,

2014-08-27 12:05 GMT+02:00 Florian Effenberger :

> feature is broken? Since I updated to TB 31 and the new Enigmail, it
> only works unreliably - sometimes messages signed/and or encrypted are
> replied to as plain text, sometimes it works upon the second reply.
>
> Anyone else seeing similar issues?

quick update: only seems to happen when selective quoting (mark text
with mouse, then only that text is quoted) is used. When quoting full
message, all seems to work.

Florian

___
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


Re: [Enigmail] reply encrypted to encrypted messages broken?

2014-08-27 Thread Ludwig Hügelschäfer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 27.08.14 12:05, Florian Effenberger wrote:
> Hello,
> 
> can anyone confirm that the reply encrypted to encrypted messages 
> feature is broken? Since I updated to TB 31 and the new Enigmail,
> it only works unreliably - sometimes messages signed/and or
> encrypted are replied to as plain text, sometimes it works upon the
> second reply.
> 
> Anyone else seeing similar issues?

Yes, there is a bug in 1.7 in respect to setting the final
encryption/signing state. Could you please use a nightly build
(https://www.enigmail.net/download/nightly.php), see if it fixes
things for you and report back here.

Thanks!

Ludwig

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCgAGBQJT/hldAAoJEA52XAUJWdLjWu0H/A5MdP7M05Scuro+Oqdjukh5
TfP31f4bpfKq3Qm9UOlaDKh8i1C8z8CK76hS2SpkPfgkPLh8oYTk+oiVIgrX8vpJ
rnQ741rxUqYvXsizN8ZOQHp+pp3u33aPwV24oyvPzDL06IUFHwPALkywocbJlIOY
2CsYhuTLfZvBfa7Dgyx2v9eIanTAxXa8vcn053EzDGi+wlvKXc/SlHYj0+r69yII
Zkw6nUYB47nmVfoetm1Nh69Q7lz+tjlLCaKUR/88X5OZZjVYq0Tp1M2KxXjaXul6
6/tjLiyaqCDFKmg/YIrE4iws5kdAhaRymNyx6nDGGLBQ5alVZosqBJGx0oLYw5g=
=Akbo
-END PGP SIGNATURE-

___
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


[Enigmail] reply encrypted to encrypted messages broken?

2014-08-27 Thread Florian Effenberger
Hello,

can anyone confirm that the reply encrypted to encrypted messages
feature is broken? Since I updated to TB 31 and the new Enigmail, it
only works unreliably - sometimes messages signed/and or encrypted are
replied to as plain text, sometimes it works upon the second reply.

Anyone else seeing similar issues?

Thanks,
Florian

___
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


[Enigmail] Compatibility issue with Whiteout Mail

2014-08-27 Thread Felix Hammerl
Hi,

I am a developer at Whiteout Networks, we're building an HTML5 MUA
with integrated OpenPGP support.
I'm having some compatibilty issues with Enigmail where it refuses to
give a meaningful error message, when I send a PGP/MIME message from
the Whiteout Mail client. The message can be decrypted in Whiteout
Mail, Apple Mail + GPG, and Mailvelope. Signatures are correct,
parsing and everything works nicely there. Only Thunderbird + Enigmail
does not seem to be able to parse/decrypt it properly.

Here's the blank error message:
Enigmail Security Info
Decryption incomplete

Here's my setup:
Mac OS 10.9.4
Thunderbird 31
Enigmail 1.7
gpg (GnuPG/MacGPG2) 2.0.22

Excerpt from the log file and the email source are in the attachment.

I am totally lost on this one and am very grateful for anything to
point me in the right direction.

Cheers
Felix
Return-Path: 
Received: from localhost (mnch-5d8689ef.pool.mediaWays.net. [93.134.137.239])
by mx.google.com with ESMTPSA id rd2sm1416425lbc.32.2014.08.27.10.01.41
for 
(version=TLSv1.1 cipher=AES128-SHA bits=128/128);
Wed, 27 Aug 2014 10:01:41 -0700 (PDT)
Content-Type: multipart/encrypted; protocol="application/pgp-encrypted";
 boundary="sinikael-?=_1-14091588997850.56355688162148"
Content-Description: OpenPGP encrypted message
Subject: asd
From: Felix Gmail Test 
To: throwaway.fe...@gmail.com
Date: Wed, 27 Aug 2014 17:01:39 +
Message-Id: <1409158899788-b2067985-5218f9f4-f4bb0...@gmail.com>
MIME-Version: 1.0

This is an OpenPGP/MIME encrypted message.

--sinikael-?=_1-14091588997850.56355688162148
Content-Type: application/pgp-encrypted
Content-Description: PGP/MIME Versions Identification
Content-Transfer-Encoding: base64

VmVyc2lvbjogMQ==
--sinikael-?=_1-14091588997850.56355688162148
Content-Type: application/octet-stream
Content-Description: OpenPGP encrypted message
Content-Disposition: inline; filename=encrypted.asc
Content-Transfer-Encoding: base64

LS0tLS1CRUdJTiBQR1AgTUVTU0FHRS0tLS0tDQpWZXJzaW9uOiBPcGVuUEdQLmpzIHYwLjcuMg0K
Q29tbWVudDogV2hpdGVvdXQgTWFpbCAtIGh0dHBzOi8vd2hpdGVvdXQuaW8NCg0Kd2NCTUE5VEF4
U253Z00xTUFRZ0FnQVhoQ2hQdFhmK2JaMjQ5UWYzQTVRVXorc3BsNkgwdmxIYTNoT0lnClg2Z29t
UjM2RjIydldBVDViUTRKTkFKTzVuOEwxd3hIR1dma1p4K3VxSWlOZ3JxbWpkNldLZ21FUXYrZwpC
SjN2V3F5VmEwRmZDZW1DME9ieFNPdGRqdXIxakM4ZTlVVEZVRGpDQTZwRlFxRk5sN21WV3ZOUFBt
eVYKY0sxZ01oaVhYb0g0U3ZObEUyZVdjcHJQNi9ld2xmN1hDdDBDVjcybHh4cU9jY1N0Rm12TGJZ
S0dZUkZmCkFGdnZsdm5UYXJBWjRoTmF4OEI0aHk3czl2ejRYRU8zRHAwVmtpTkVzL2t3V3JiUENV
cWttZTB1UnFsbgpzb0JQZ3BvYUhBZUlrQkthS1ZKQ2cvZ3RIb2dmbENqYmorQjJCMDMrdUxzV3Vr
QmEzelVkNGM3c09qZG8KSnNIQVRBUFV3TVVwOElETlRBRUlBSWpLejhGN01vSzNUcGQ0TmNpUW1I
MW9HVmhEeW0xeSttR2x0cHo4Cjg4ZGhPeUQvRzZzdUlNdnNZZWlwblAzclRNOUZhVlgwVFVTTy9s
eTl4ODd5dHA4Ky8yaFV4VDZYeTRiUwpQaDdZeVZQSUh6RnlLM0QrTFFYQlV2bTBERXpwbzk3RGpV
V3JCVkdIYWdzZHpzQUpjNlArOVVmRTFGdHcKaTFwbXFjWTV0Z25MeXhkeVkvSXZCTE9JVHgxZU8z
M2dxNVVlL3Y5d2Y4eEwzZU82alFieWpTN1VqcGh0Cmp5dWZvRzh0cng1ekRkcGdHdzRJUHhJdGZ4
TUNha1VXa1BsOU1LVFFlRlp5a0t4eVE4dE93bEszc1ZHagpWMWFwWTdFS1RXdXQwN0U2Z0wvVkZE
SFAzWHBOWExnVHhLVTEzbFRyb1NCSWZsUUJPTXRmZHJpNUpMYTYKVkpEU3hlRUJjOWNJVWtZdWM5
aWl2b1JCTVgxN0hMbHlBS2N2ckdUaEtvOHBVcWd3Q0RLeDIwN2J3a0ZiCnlvWFN0dlZkbG9EaExq
ZDRUcWpaUWJDMDMzOVE1MDFDVHZkaUhsREFCUWNyR3hYaDVkS0dSeGlmZ3JrRAoyNVhrb05KZytH
MGpQWWNvTXdYWVFsN09qOHd2bS9CaFdvdzFPaHIzRWFhZmxkb2V2eHhrSHVab2E3RWcKMkZTVFp3
TnZZNUYrTjQ1dU1NcnpmSU41ZCtGc2tiSGd5L0x4ODZZRmZOY0VZcDlKY2lSVHBKQ0dDTlUyCnhT
NGJVdkQrN1RUK0RmemtnaVNWMmRzOHBTSktsUkRZMEJVU2ZJSTQwWkZ5Vkh5WXhKUWhRM3gxM3RS
Twoxako0MEwwVjgwMUdoZXVWcDlqVnRlZUdHeEdxamQ3eHQxNzRFNUcySmtTVWNLZVNXTG9td0ta
WHhiK1IKaVpiRFdFZ1FKY3orek5iMnpBM1F6WnkrRGRoUG5DUkVIZ1FFUUd0U1htdHJxR0s5cWlz
L1cwZzRTUzZrCkQ2a2RONjRESDFEMXpRc09HZmd0NnBXRjJuOUMwSWJ1b25vdm1aemZmdEQ1aGww
TVlJcGgweXBtbFhWdQprWWkwN2xZa3pJNVkvdXlMNFR1WE43MEZUTEtvYWltR0tiUElYc1VPaFRk
OXlrb3VDWTJhMDNnSlF2c0wKSEdRWXIydFpCNlN0NGV3V1Y4d0VVQlM5bi9sbWV3emllUEJtQ3VO
MGphSmZyQ3BNQTBCSU56Y1h5KzlKCnVlaXkvbnVSMWVRMVRiMUt4aVNIRUt2eklSUTRPZk9DZ1pE
djFNVDBTekJNT0pONmdCa0hsZmdTQkVjWQo2S2lXeU5kWVBmZkUrRGJnMFI2UkRRUFNvR2RaY1Nw
WXhKdENxWmZrd202MzFObHBKRVIyYzdJNVFML0wKSjIwOExHWjZJWDl3ZVhDWmNzTkdNWmZiZ1Vt
NE5YaEpjcjFJcytGcWlnKzV4ZnV1aENSVjNmS1cxWUZFCnJPNVVyaVlHL0dDMjZ5emF4LzNNTHIx
VEpzeHdwd296MDlQd1g4UmxxQmpZZmFCV0JwRGxCUFRDMVpKcQprVDBQcjBhbGNxUGRrTzNpZ1JK
YVI5L3BjTTMvTjIyWXdsQ05UT0RielNiMGJmWE9FZDJ4SUlOd0lQZkMKbmNlTmxlZ29aSktwcG1I
WHVoU0lHNjRLRUw3OTQ4NTlxRkFBcU9xcWI4WFBGMElnN1NnanJrdWxMM2RNCjBKTDBIcmVYRFFj
c1RaMVRpbDZhNTZOekxuVENuUmVFN3kzSXJ6K3dXS3AyWjVtZFYrVWxtdW1Ra3RGQwpVMWxCVG1p
QjBOMmxGTElMSVZtT2VrVlJtZWlOT3NQaWhJaHlKa1JFVFVMeHVQYndEUDBTamQ0cHN3Q24KUitk
elptTklaUFNsTlk0RDluMFEyYXBVdG5zZVowbTdmaGoyb1UwYnV6WUoyVmZKQWVWbnh3K2dZL0l5
CkVkbEIrRWg1YktaYi9sa1JKQ0pQV1BuZ2xKVTdQQ3ExZ1RsdWZNaC9SN2dxUW1CUnVVa1ZoRmNq
Q3hxNApWMXcrbXY5MjJJTGI5Y3NmRW9ETlBPRG0zQ2JaY0VTcVJvQkZ2aytlQUFGL3FtcEZjS25L
NXd4YTh4bXcKQ2NTR1lPS2E5Q3BQYlpqbHhqU0xsckdqZ0dYMWIzT2tiTUllbktyTTFybm1tRXVU
VG44bmJjVjVoZGJyClhHZkZKRU5lTDR2RFgvcVFqbkkrbVR2TzlsYlZwWGhVOFVxZ1BUb1dnTFZT
eFRuVVpBMDJSWVdOOGY4Twp

[Enigmail] Problem in Manjaro

2014-08-27 Thread Dr. Martin Senftleben
Hi,

I have recently switched to Manjaro, because Kubuntu gave me lots of
problems out of a sudden. I remember that Enigmail worked fine the first
day after installation, but after a reboot, enigmail gives me the
message that the key might be expired, and doesn't allwo me to sign the
message. I'm sure the key is not expired. The full message is:

"Der Schlüssel xxx wurde nicht gefunden oder ist ungültig. Der
(Unter-)Schlüssel könnte abgelaufen sein."

In English:

The key xxx was not found or is invalid. The (sub-)key could have been
expired."

Insted of xxx, my key-ID was placed.

I guess that it has to do with the switch of Distros, but can't tell
what could be the reason. Any help will be appreciated.

Regards,

Martin Senftleben



___
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


Re: [Enigmail] strange logic re keys information

2014-08-27 Thread Philip Jackson
On 24/08/14 17:03, Philip Jackson wrote:
> On 24/08/14 16:34, Ludwig Hügelschäfer wrote:
>> On 17.08.14 15:06, Ludwig Hügelschäfer wrote:
>>> JFTR: I have opened ticket 310 
>>> (https://sourceforge.net/p/enigmail/bugs/310/) for this issue.
> ..
>>
>> I cannot reproduce this any more. Even high stress on gpg in the
>> background (like on my first sight importing keys did trigger
>> check-trustdb) did not cause Enigmail to fail again.
>>
>> Philip, would you mind trying to install a nightly version of Enigmail
>> (https://www.enigmail.net/download/nightly.php) and see if it happens
>> to you again?
>>
>> I have left the bug open, but did set importance to "minor".
>>
> 
> I've just installed latest nightly build -
> 
>> build date: 2014-08-24, version: 1.8a1pre, git rev: 
>> e4b0addf0919594fbd4706425c6f54bfe0bbfe4d
> 
> We'll see how it goes - and if I get another example I'll let you know.

Ludwig,

I've not seen any further events of this type since I changed to the nightly
build (above) but the difficulty is that most of the people writing on the lists
are the same and I already have their keys.

However, today, I had an instance where there was no enigmail header but the
email contained the typical text of gpg signature at the end.  Before my eyes, I
saw appear the "untrusted good signature header" and when I clicked on
Details/View key properties, there were all the normal infos.

I checked in the debug log and saw that gpg had been to the keyservers to
collect a missing key for this email.  I still don't use enigmail's
preferences/keyserver option to collect missing keys but I do use gpg.conf.

Clearly in this case, the key was collected by gpg and the updated keyring was
re-read by enigmail before displaying the enigmail header.

So it is beginning to look like the problem does not exist now.

Philip



0x23543A63.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
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