Me too!
Ended up the same for me as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733195
-GtFiT6T1yQf799arGhJa8UNHShi3xkC0xPSIM3eyQ9LOlBUgRma87bbRjWmLEg=3D=3D -=3DFdhF +GtFiT6T1yQf799arGhJa8UNHShi3xkC0xPSIM3eyQ9LOlBUgRma87bbRjWmLEg== +=FdhF
So had to replace =3D with = It did look very odd, as the PGP block was not fully justfied.
It looks like gmail is just very broken... Despite quoted-printable encoding.
Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable
I wonder if the original email set that, or if gmail helpfully "improved" the email to be quoted-printable. I think i want to try if format="flowed" would be any better. Or, I have seen gmail perform better with base64 Content-Transfer-Encoding.
Me too!
Ended up the same for me as https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 733195
-GtFiT6T1yQf799 arGhJa8UNHShi3x kC0xPSIM3eyQ9LO lBUgRma87bbRjWm LEg=3D= 3D arGhJa8UNHShi3x kC0xPSIM3eyQ9LO lBUgRma87bbRjWm LEg==
-=3DFdhF
+GtFiT6T1yQf799
+=FdhF
So had to replace =3D with =
It did look very odd, as the PGP block was not fully justfied.
It looks like gmail is just very broken... Despite quoted-printable encoding.
Content-Type: text/plain; charset="utf-8" Transfer- Encoding: quoted-printable
MIME-Version: 1.0
Content-
I wonder if the original email set that, or if gmail helpfully "improved" the email to be quoted-printable. I think i want to try if format="flowed" would be any better. Or, I have seen gmail perform better with base64 Content- Transfer- Encoding.