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 helps?

In any case, here's the relevant extract for an encrypted message:

Cheers,
Martin

==============
...
Received-SPF: none
X-SPF-Guess: pass

This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156)
--===============3016024926762490198==
Content-Type: multipart/encrypted; protocol="application/pgp-encrypted";
        boundary="1SI1MHtXLR4sjRsIjeDNLqRangjWleort"

This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156)
--1SI1MHtXLR4sjRsIjeDNLqRangjWleort
Content-Type: application/pgp-encrypted
Content-Description: PGP/MIME version identification

Version: 1

--1SI1MHtXLR4sjRsIjeDNLqRangjWleort
Content-Type: application/octet-stream; name="encrypted.asc"
Content-Description: OpenPGP encrypted message
Content-Disposition: inline; filename="encrypted.asc"

-----BEGIN PGP MESSAGE-----
Version: GnuPG v1

hQEMAwrXinnsTn9qAQf/SY5DsFoeq9jQUQ8/X3wXFHQl70sOzP6nCVO5v1EUXml+
sJExDcu1xyXEkqv66Jk4zskW32ODg6cFMbfQAirRyo/mu6wXkEFhlg5ovqcWiqKq
+ePYQTxouzFBWBM0CSRlfjQ/78wJ21o0M3OeU11jTHmZDIkwQWH0YVe2Ft0YoDmE
eCcco3zh8RRcwy9UhDMWJixzT1Rra597JlVYZ2kspmHQMI6ztl489BXcbvojtMQW
nVa/oFCBlMopXqwfYIsSBnJeLRgnzNn1emqaiamJ3FxDdG1oHAYucBAULpwsmUDI
kAUx4lpe1+0SJ47yOzWtmjJDnhmh3feEvw0hM67+/dLpAc2IKQGiPyHIu7yHd4ox
DjM42JlFkqaYSHBc37LHH5BHaLWANIQBc2B42vUNDmhmcMv+z+s1J5ovUd76Ciqu
JBck9CuZ2hlNs2HWszu+mC5YG0FIY+FX3RY/2oiYKBpKpPm3e78NN9K1JNHjXUro
yJMdbBTyCs+FkQPKaJwNvnHC5EScvREAOCp1CrSulhyKttD7XgEFsi5UIz9+T6OF
YrE6VnKENibytH0IrH54hTXwJg57RzrxVT37B8CI3c7PS6yPcS84G0Ep6ap1hcy8
CDF7xiLbQZiVqY5E9GfhsFm9+RH7Tc5ZUNgSUiurYOt/+DDKuS+g4Su2xE5CkM86
c6eQXELAmDqRHpzJiuR0kmCVLAZQGDBKJ+vVeUpMYMtNF/ZGIkSBJ1FSC/D7OBfl
tvhPaUKmBjvivwaHajbU62MI5TfOUXc3A54hA7Bkq/b9b3ycKBAkEEPlmXHrVOa1
OgPdX4E4S/DoH5O92Gofn562LU0DBUVGLZygyRmKFsv8RnCeMijcxuJBTsPaNv0b
07WA+xTZoYyMgnRmfZxHgSGMW5nEEIVtLjWfZof8oiux7NR4IZ6ttSSCNNoELW52
HKv6FMCNC3gRZqh6v5+w0ArfEr92zgeL5E8JuyfRMuyqvwfHYEflAM2H/n7TZJcn
Anb/hK+0vBHP3FcINJZXn6ITHF3JiaGQKg3HTJ2fTM2HqcRBFg==
=LHbM
-----END PGP MESSAGE-----

--1SI1MHtXLR4sjRsIjeDNLqRangjWleort--


--===============3016024926762490198==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


==============

On 09/08/14 15:32, Patrick Brunschwig wrote:
> 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 these 
>>> messages. However, now I get:
> 
>>>> Decrypted message (restored broken PGP email format probably 
>>>> caused by an old Exchange server, so that the result might not
>>>> be perfect to read)
> 
>>> Is there any way to disable this heuristic?
> 
>> Currently not, but this is definitely a bug.
> 
> I think I have fixed this bug. As I don't have such messages, could
> you please try the latest nightly build (which I just created) to test
> this?
> 
> https://www.enigmail.net/download/nightly.php
> 
> -Patrick
> 
> _______________________________________________
> 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
> 

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