Daniel Kahn Gillmor

Arguably, the problem here is that thunderbird is interpreting/accepting inline PGP at all, because that introduces the problem that Enigmail is trying to sensibly defend against. If enigmail were to deliberately ignore inline PGP signatures, then it wouldn't have this problem (and it would encourage people to either switch to PGP/MIME or simply to stop signing altogether, either of which would be better than continuing to do inline PGP signatures)

Attached is the source of the RFC5322 message as I received it. I note that it passes DKIM verification over the body of the message using the following selectors: d=caltech.onmicrosoft.com; s=selector1-caltech-onmicrosoft-com; bh=pvh+22xNt5x1DZo3Ytpyz9FhvIGmM0xZO/+9OIACjwc=; So that suggests that the mangling happened before the DKIM signer got ahold of it.

Data loss: Enigmail "repair" of MS Exchange mangling destroys content

Attached is the source of the RFC5322 message as I received it. I note that it passes DKIM verification over the body of the message and the following selectors: d=caltech.onmicrosoft.com; s=selector1-caltech-onmicrosoft-com; bh=pvh+22xNt5x1DZo3Ytpyz9FhvIGmM0xZO/+9OIACjwc=; So that suggests that the mangling happened before the DKIM signer got ahold of it.

message mangled by MS Exchange, but applying Enigmail "repair" destroys content

thanks for the merge! I assume you mean the github repository here. There are copies of pymilter scattered across the Internet, and none of the ones i could find point to any resource that appears to be the canonical one. Do you prefer to work on the project over at github? Would it make sense to shutter this sourceforge project and point it there? Also, can you point me to documentation of the relevant changed semantics of "import" between py2 and py3? i'd like to understand that better, and while...

thanks for the merge! I assume you mean the github repository here. There are copies of pymilter scattered across the Internet, and none of the ones i could find point to any resource that appears to be the canonical one. Do you prefer to work on the project over at github? Would it make sense to shutter this sourceforge project and point it there? Also, can you point me to documentation of the relevant changed semantics of "import" between py2 and py3? i'd like to understand that better, and while...

thanks for the merge! where is the github repository? there are copies of pymilter scattered across the internet, and none of the ones i could find point to any resource that appears to be the canonical one. also, can you point me to documentation of the relevant changed semantics of "import" between py2 and py3? i'd like to understand that better, and while i gave a quick pass at the upstream import documentation i couldn't find an reference to what had specifically changed since py2.