You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We received a report send to flowcrypt compatibility account about a Public key-encrypted message attachment named after "noname" and another "noname" file where it contains Version: 1. The application used the Canary Mail.
We should be able to recognize each file based on their content types but upon checking, we somehow defaults the attachment type to application/octet-stream but didn't know the reason why so completely yet.
application/octet-stream is a default mime type for unknown files, so for cases when we don't have any file type set - application/octet-stream is used
…il (#5727)
* Improve encrypted message detection for multipart email
* Add a test
* Add mime type checks for "application/pgp-encrypted"
---------
Co-authored-by: martgil <martroblesit@gmail.com>
…il (#5727)
* Improve encrypted message detection for multipart email
* Add a test
* Add mime type checks for "application/pgp-encrypted"
---------
Co-authored-by: martgil <martroblesit@gmail.com>
Description
We received a report send to
flowcrypt compatibility
account about a Public key-encrypted message attachment named after "noname" and another "noname" file where it containsVersion: 1
. The application used the Canary Mail.The issue produces a seemingly blank page:
The
noname
file attachment content:Reference: https://mail.google.com/mail/u/flowcrypt.compatibility@gmail.com/#inbox/FMfcgzGxTFXMFnDNbgknpqvXKtSmMgSK
The text was updated successfully, but these errors were encountered: