I recently got an armored encrypted mail that I couldn't decrypt. I asked the
sender to send me the mail in a way that it is protected from modification on
the way, and here is the diff:

% diff -u problematic-mail.good problematic-mail.borken

• problematic-mail.good 2016-02-10 18:15:50.712836224 +0100

+++ problematic-mail.borken 2016-02-10 18:15:56.236875821 +0100
@@ -40,5 +40,5 @@
J7lYvtLaB5/M57r8r3mcn03cK/yVBA+tUZzV3zVEc7YeV7XTQNvO+tpElvgsjdDa
juZ8GPOPY1VSa883xbaPYtdDs82gDtkKhO2OvY0c66JwGPdScfw2ajkC+6lBDblO
crp5FDSZ8rG3r/mhSymUrEqB1yVv
-=jl1Y
+=3Djl1Y
-----END PGP MESSAGE-----

I just found the gpg flag --ignore-crc-error, which let's me decrypt the message
in its mangled form. In any case, I believe that this should not happen, and
blaming the MTAs involved or the sender for using PGP/INLINE does not help,
because people are going to blame "this encryption thing".