Hi,
I can confirm that with the newest nightly (communicated off list) the
bug is indeed fixed. Thanks!
Cheers,
Martin
On 09/08/14 16:12, Patrick Brunschwig wrote:
> On 09.08.14 16:56, Martin wrote:
>> Hi Patrick,
>
>> thanks for the quick response. I can confirm that this fixes the
>> bug for
-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 signe
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.
Looking at your git commit this would make sense to me as it is
filtering for "multipart/encrypted". I can send you an .eml message off
list, if it
-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 probl
-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 e
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi Martin,
this should be looked into. Not to be forgotten, please open a bug for it.
Olav
- --
The Enigmail Project - OpenPGP Email Security For Mozilla Applications
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Dies
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 from a mail I *sent* to a mailman list:
=
Content-Type: mult
