This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

[Thunderbird] Obsolete PGP encryption method

more options

Hello,

i am encrypting emails with PGP on mail server, and i have not the possibility to sign them because i can only have the public keys available on server.

So when i download the emails with Thunderbird , they are PGP encrypted but not signed.

When i open these emails with Thunderbird, i get an error saying the message has been encrypted by an obsolete method, and may have been modified during transmission, so it will not be displayed.

I guess the problem is missing signature? Is there a way to tell Thunderbird to ignore the missing signature and decrypt the message anyway? Or may the problem be the application/pgp mime type i am using, which is obsolete? I may try with Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; but i guess it makes no difference if the problem is in the missing signature

Example email that gives me the error:

....

....

Content-Type: multipart/alternative; boundary="_000_VI1P194MB063950F8AFCFEF8AE12E5510A13C0VI1P194MB0639EURP_" .... ....

--_000_VI1P194MB063950F8AFCFEF8AE12E5510A13C0VI1P194MB0639EURP_ Content-Type: application/pgp


BEGIN PGP MESSAGE-----

Version: BCPG C# v1.6.1.0

hQIMA3drgilSCIWPAQ/9Hu9QPY3oTma4xDs7HR6/rcAASC+avaxbUlw/LUx2mHaj TcyxpTQz7xFoegvz/lv7P7uKxgcEVsG+splamkT20IwG0wUifsCCSJLjtnSh9QH5 uxj0nkas5BgIWT47YycL8gRxQfAkMmXWuYS9tO3QZi6gIn9/lgj/npclZhSnZZzJ BVJWwBPPUBc7EKkgJW0bAbtZbyrs5n0CEvqbWx6w6Yjp/xf0naB0oT1oROQB053s iIFkXdhhdDI56zNIETeh/RuLVMJ0tqmEAYnzX7oX5+30d4ZA8Du0rU2ygwfHtvhd AgbmT6Zglp+kFmLt5Uq/MyovnJfk6e5dHqNZ03O7YsoMaBoeJ3/3R6pCH4Yr+S2R SJtRIuVoDRcMZYjE56dqVCrCPCxHFNP0EzIZS6oOd6PSIeA67nZVCiBOdEEdGes/ 8RY5/OsI8iGezaEDgxljEDFSkw96ujf4GZxZ5OXhxPKF0oyY2bQnQz+WzjocXvHR R6iMk3G1nAK20EwURKnFkWI0IJiUb0JJbrnVbhuOx15QHs+DLuUj/WjWj37HWqa3 ckeQOYcV7E2snCNucgmbmfmxmHAmZM1HK5ZRcHWThK++F0gAv5GXUD4HiiaarxTc A8YR7RwdIf1wnIb3+yoA0sxDXIV+mcyT38U10nj5PDjvdCwUar5spOXvpiU2TPfJ Jwlu+mjBBsRHPcAP/Oq/kqTXtvowcJxGvz16MlfO/PWofOEIhUz1Dg== =d10C


END PGP MESSAGE-----

--_000_VI1P194MB063950F8AFCFEF8AE12E5510A13C0VI1P194MB0639EURP_--

Hello, i am encrypting emails with PGP on mail server, and i have not the possibility to sign them because i can only have the public keys available on server. So when i download the emails with Thunderbird , they are PGP encrypted but not signed. When i open these emails with Thunderbird, i get an error saying the message has been encrypted by an obsolete method, and may have been modified during transmission, so it will not be displayed. I guess the problem is missing signature? Is there a way to tell Thunderbird to ignore the missing signature and decrypt the message anyway? Or may the problem be the ''application/pgp'' mime type i am using, which is obsolete? I may try with ''Content-Type: multipart/encrypted; protocol="application/pgp-encrypted";'' but i guess it makes no difference if the problem is in the missing signature Example email that gives me the error: .... .... Content-Type: multipart/alternative; boundary="_000_VI1P194MB063950F8AFCFEF8AE12E5510A13C0VI1P194MB0639EURP_" .... .... --_000_VI1P194MB063950F8AFCFEF8AE12E5510A13C0VI1P194MB0639EURP_ Content-Type: application/pgp -----BEGIN PGP MESSAGE----- Version: BCPG C# v1.6.1.0 hQIMA3drgilSCIWPAQ/9Hu9QPY3oTma4xDs7HR6/rcAASC+avaxbUlw/LUx2mHaj TcyxpTQz7xFoegvz/lv7P7uKxgcEVsG+splamkT20IwG0wUifsCCSJLjtnSh9QH5 uxj0nkas5BgIWT47YycL8gRxQfAkMmXWuYS9tO3QZi6gIn9/lgj/npclZhSnZZzJ BVJWwBPPUBc7EKkgJW0bAbtZbyrs5n0CEvqbWx6w6Yjp/xf0naB0oT1oROQB053s iIFkXdhhdDI56zNIETeh/RuLVMJ0tqmEAYnzX7oX5+30d4ZA8Du0rU2ygwfHtvhd AgbmT6Zglp+kFmLt5Uq/MyovnJfk6e5dHqNZ03O7YsoMaBoeJ3/3R6pCH4Yr+S2R SJtRIuVoDRcMZYjE56dqVCrCPCxHFNP0EzIZS6oOd6PSIeA67nZVCiBOdEEdGes/ 8RY5/OsI8iGezaEDgxljEDFSkw96ujf4GZxZ5OXhxPKF0oyY2bQnQz+WzjocXvHR R6iMk3G1nAK20EwURKnFkWI0IJiUb0JJbrnVbhuOx15QHs+DLuUj/WjWj37HWqa3 ckeQOYcV7E2snCNucgmbmfmxmHAmZM1HK5ZRcHWThK++F0gAv5GXUD4HiiaarxTc A8YR7RwdIf1wnIb3+yoA0sxDXIV+mcyT38U10nj5PDjvdCwUar5spOXvpiU2TPfJ Jwlu+mjBBsRHPcAP/Oq/kqTXtvowcJxGvz16MlfO/PWofOEIhUz1Dg== =d10C -----END PGP MESSAGE----- --_000_VI1P194MB063950F8AFCFEF8AE12E5510A13C0VI1P194MB0639EURP_--

Modified by it_support1

Chosen solution

Solved. I was putting wrong headers in the email

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

Solved. I was putting wrong headers in the email