-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I think I never sent an update to this. Indeed Thunderbird does not
always do the transfer-decoding. I fixed this quite a while ago for
signed as well as for encrypted PGP/MIME messages.

- -Patrick

On 28.08.14 09:54, Felix Hammerl wrote:
> Awesome, thanks a lot! While we're at it, I just made the discovery
> that the very same thing is true for the signature, too. PGP/MIME
> signatures are ignored when the application/pgp-signature MIME node
> has Content-Transfer-Encoding as base64 or quoted-printable, but it
> seems to work for 7bit. I assume that's the same root cause...
> 
> Cheers Felix
> 
> On Thu, Aug 28, 2014 at 9:09 AM, Patrick Brunschwig 
> <[email protected]> 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 Hammerl wrote:
>>>> 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
>>>> <[email protected]> wrote: 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
>>>>> 
>>>>> _______________________________________________
>>>>> enigmail-users mailing list [email protected] To
>>>>> unsubscribe or make changes to your subscription click
>>>>> here: 
>>>>> https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmai
l.net
>>>>
>>>>>
>>>>
>>>>> 
_______________________________________________ enigmail-users
>>>> mailing list [email protected] To unsubscribe or
>>>> make changes to your subscription click here: 
>>>> https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail
.net
>>>>
>>
>>
>>>> 
_______________________________________________
>> enigmail-users mailing list [email protected] To
>> unsubscribe or make changes to your subscription click here: 
>> https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.n
et
>
>> 
> _______________________________________________ enigmail-users
> mailing list [email protected] To unsubscribe or make
> changes to your subscription click here: 
> https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.ne
t
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJUsWPFAAoJEMk25cDiHiw+PTgIAM3mGK5L+NW4nnEm+Fvs+yze
8kZ576/0dPytIE1f//3lQP23S1okP5iFDNwQxRCu985l4HsBv8aG6484gt8ZIGeA
vrnAcvSPOqHLXrPRKkej4R/HkWagvRODRh3bYueFDHF221DK9qrKLSXpl2EIyd47
A2pfCk2urr1sX0OL0THTCLASzoI6mM94Mho8yFjNzDbdVwPrXpFXEpe/ZWJfV65V
LvwdAsN9855G/cKoRbg/kYgHiGKlLNEHKfCL584neuGJhM5fORPz+RFQvNyH4rrZ
K5PJrQd/e5Ms53BOaSz4RM92XXYQZsxwjfzdD9I8jeMWlxcRtHgoa0oWL1JD4/4=
=DbDa
-----END PGP SIGNATURE-----

_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to