Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

forwarded pec mail attachments not visible

  • 7 odpowiedzi
  • 1 osoba ma ten problem
  • 1 wyświetlenie
  • Ostatnia odpowiedź od azarrillo

more options

Dear sirs, in my company, when i receive a forward of a mime message (got from from pec.aruba.it) i cannot open it through TB. The application crashes asking me to send a report to you.

This is the last crashid i've sent to you: [code]crashid: bp-4bb95211-2fc3-4177-8a45-d16240180602/code

Looking around i've found the problem are attachments cause when i disable "view attachments inline" the message opens (TB does not crash) BUT NOT ALL attachments are visible. "simple" attachments like *.xml and *.eml file show correctly but attachments to the forwarded mail does not appear (p7m files). The source of the message starts with:


--=_2jwkfuvhvg4m Content-Type: multipart/signed; boundary="----4D3B73D549713A1A55639575342C4F69"; protocol="application/x-pkcs7-signature"; micalg="sha1"; name="" Content-Transfer-Encoding: 7bit


and it contains the signed attachment like this


Content-Type: application/octet-stream; name="=?utf-8?Q?lett.=5Fnota=5Fcid=5Fft.=5F96=5Fdell=5F11.09.2017=5F.docx.pdf.p7m?=" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="=?utf-8?Q?lett.=5Fnota=5Fcid=5Fft.=5F96=5Fdell=5F11.09.2017=5F.docx.pdf.p7m?="

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwGggASD A6DCJVBERi0xLjQNCiXIycrLDQo2IDAgb2JqDQo8PC9UeXBlIC9QYWdlL1BhcmVudCAzIDAg Ui9Db250ZW50cyA3IDAgUi9NZWRpYUJveCBbMCAwIDU5NS4zNDk5NzU1OSA4NDEuNzAwMDEy ....


and the attachment itself

--_=__=_XaM3_.1527493421.2A.125804.42.16611.52.42.007.582225178 Content-Type: application/octet-stream; name="=?utf-8?Q?Copia=5FDocPrincipale=5Flett.=5Fnota=5Fcid=5Fft.=5F96=5Fdell=5F11.09.2017=5F.docx.pdf?=" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="=?utf-8?Q?Copia=5FDocPrincipale=5Flett.=5Fnota=5Fcid=5Fft.=5F96=5Fdell=5F11.09.2017=5F.docx.pdf?="

JVBERi0xLjQNJcjIyMjIyMgNMSAwIG9iago8PC9DcmVhdGlvbkRhdGUoRDoyMDE4MDUyNTEw MzAwMCkvQXV0aG9yKFwzNzZcMzc3XDAwMENcMDAwaVwwMDBuXDAwMHpcMDAwaVwwMDBhKS9D cmVhdG9yKEFzcG9zZSBMdGQuKS9UaXRsZShcMzc2XDM3N1wwMDBBXDAwMHpcMDAwaVwwMDBl XDAwMG5cMDAwZFwwMDBhXDAwMCBcMDAwVVwwMDBuXDAwMGlcMDAwdFwwMDBcMzQwXDAwMCBc MDAwU1wwMDBhXDAwMG5cMDAwaVwwMDB0XDAwMGFcMDAwclwwMDBpXDAwMGFcMDAwIFwwMDBM XDAwMG9cMDAwY1wwMDBhXDAwMGxcMDAwZVwwMDAgXDAwME5cMDAwLlwwMDAgXDAwMDNcMDAw IFwwMDAgXDAwMCJcMDAwQ1wwMDBlXDAwMG5cMDAwdFwwMDByXDAwMG9cMDAwIFwwMDBNXDAw MG9cMDAwbFwwMDBpXDAwMHNcMDAwZVwwMDAiKS9Nb2REYXRlKEQ6MjAxODA1MjgwNzQzMjQp ....


The same attachments appears twice in the source...(i think in my humble opinion cause it is forwarded twice, is it right?).

Anyway I can see the same message from my company webmail (horde) without any problem. Hope you can help me solve this problem.

Thank you very much in advance. All the best

Dear sirs, in my company, when i receive a forward of a mime message (got from from pec.aruba.it) i cannot open it through TB. The application crashes asking me to send a report to you. This is the last crashid i've sent to you: [code]crashid: bp-4bb95211-2fc3-4177-8a45-d16240180602[/code] Looking around i've found the problem are attachments cause when i disable "view attachments inline" the message opens (TB does not crash) BUT NOT ALL attachments are visible. "simple" attachments like *.xml and *.eml file show correctly but attachments to the forwarded mail does not appear (p7m files). The source of the message starts with: --=_2jwkfuvhvg4m Content-Type: multipart/signed; boundary="----4D3B73D549713A1A55639575342C4F69"; protocol="application/x-pkcs7-signature"; micalg="sha1"; name="" Content-Transfer-Encoding: 7bit and it contains the signed attachment like this Content-Type: application/octet-stream; name="=?utf-8?Q?lett.=5Fnota=5Fcid=5Fft.=5F96=5Fdell=5F11.09.2017=5F.docx.pdf.p7m?=" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="=?utf-8?Q?lett.=5Fnota=5Fcid=5Fft.=5F96=5Fdell=5F11.09.2017=5F.docx.pdf.p7m?=" MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwGggASD A6DCJVBERi0xLjQNCiXIycrLDQo2IDAgb2JqDQo8PC9UeXBlIC9QYWdlL1BhcmVudCAzIDAg Ui9Db250ZW50cyA3IDAgUi9NZWRpYUJveCBbMCAwIDU5NS4zNDk5NzU1OSA4NDEuNzAwMDEy .... and the attachment itself --_=__=_XaM3_.1527493421.2A.125804.42.16611.52.42.007.582225178 Content-Type: application/octet-stream; name="=?utf-8?Q?Copia=5FDocPrincipale=5Flett.=5Fnota=5Fcid=5Fft.=5F96=5Fdell=5F11.09.2017=5F.docx.pdf?=" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="=?utf-8?Q?Copia=5FDocPrincipale=5Flett.=5Fnota=5Fcid=5Fft.=5F96=5Fdell=5F11.09.2017=5F.docx.pdf?=" JVBERi0xLjQNJcjIyMjIyMgNMSAwIG9iago8PC9DcmVhdGlvbkRhdGUoRDoyMDE4MDUyNTEw MzAwMCkvQXV0aG9yKFwzNzZcMzc3XDAwMENcMDAwaVwwMDBuXDAwMHpcMDAwaVwwMDBhKS9D cmVhdG9yKEFzcG9zZSBMdGQuKS9UaXRsZShcMzc2XDM3N1wwMDBBXDAwMHpcMDAwaVwwMDBl XDAwMG5cMDAwZFwwMDBhXDAwMCBcMDAwVVwwMDBuXDAwMGlcMDAwdFwwMDBcMzQwXDAwMCBc MDAwU1wwMDBhXDAwMG5cMDAwaVwwMDB0XDAwMGFcMDAwclwwMDBpXDAwMGFcMDAwIFwwMDBM XDAwMG9cMDAwY1wwMDBhXDAwMGxcMDAwZVwwMDAgXDAwME5cMDAwLlwwMDAgXDAwMDNcMDAw IFwwMDAgXDAwMCJcMDAwQ1wwMDBlXDAwMG5cMDAwdFwwMDByXDAwMG9cMDAwIFwwMDBNXDAw MG9cMDAwbFwwMDBpXDAwMHNcMDAwZVwwMDAiKS9Nb2REYXRlKEQ6MjAxODA1MjgwNzQzMjQp .... The same attachments appears twice in the source...(i think in my humble opinion cause it is forwarded twice, is it right?). Anyway I can see the same message from my company webmail (horde) without any problem. Hope you can help me solve this problem. Thank you very much in advance. All the best

Zmodyfikowany przez azarrillo w dniu

Wszystkie odpowiedzi (7)

more options

Just some observations. a PDF attachment should be encoded as application/PDF not application/octet-stream, so the send is sending incorrectly encoded emails. That might have something to do with it. Thunderbird uses mime encodings to determine what to do with attachments. So PDF files will simply be treated as random DAT or data files.

P7M files are not attachments as such they are digital signatures. All Thunderbird does with them is verify the signature and place an icon in the header to signify the mail is digitally signed.

However there does appear to be a bug for this. https://bugzilla.mozilla.org/show_bug.cgi?id=548212

more options

First of all thanks Matt for the reply. I've opened my question cause i've seen that old versions of thunderbird (i.e. TB 52.0) open that particular mail without any issue.

But i've seen also that with the latest thunderbird, with another pc, the same mail opens; maybe it is because i've made all the updates from the different versions till the latest...i'm just supposing though...

Anyway i'll take a look and will follow the bug at bugzilla. EDIT: bug opened 8 years ago...not so active :p

Thanks again and have a good evening!

Zmodyfikowany przez azarrillo w dniu

more options

Is it you used to have this add-on... it came up in another thread today. Apparently handy with the Italian s/mime implementation.

https://addons.mozilla.org/it/thunderbird/addon/thunderpec/

more options

Sorry for delay. Thanks for the suggestion. I've installed the plugin and it seems ok so far. I need some more time to see if all function correctly but it is a good start. I'll let you know. Thanks again and have a good time!

more options

azarrillo

Several fixes have been made to version 60. Can you reproduce the crash with your testcase when using the version 60 beta from https://www.thunderbird.net/en-US/channel/ ??

more options

Wayne Mery said

azarrillo Several fixes have been made to version 60. Can you reproduce the crash with your testcase when using the version 60 beta from https://www.thunderbird.net/en-US/channel/ ??

Have you stopped using Thunderbird? Still crashing?

more options

Morning Wayne, still using Thunderbird, don't worry. With PEC extension suggested all is good now (at least so far :) )

Anyway as soon as possibile i will check with beta version to see if the problem has been fixed in the new version.

Have a nice day