Therefore the same at Thunderbird.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thank you.
Just found that both Sylpheed and Claws-Mail do exactly the same for
signed messages, even if transfer encoding is set to "8 bit".
Regards,
Andrey.
On 25.09.2017 14:06, chokito wrote:
> I have found this on
I have found this on https://www.cryptosys.net/pki/manpki/pki_usinginmime.html:
"You are strongly recommended to use quoted-printable encoding for the content
part of the message to prevent the signed data being changed during
transmission."
___
In my original message, I was asking about S/MIME signed messages.
S/MIME encrypted messages is a separate matter: your message body is
never transmitted in plain text, nor is quoted-printable encoding used.
The "smime.p7m" MIME part is actually a base64-encoded binary file which
represents the
Settings: default values
mail.strictly_mime;false
mail.strictly_mime.parm_folding;1
mail.strictly_mime_headers;true
Received header:
---
MIME-Version: 1.0
Content-Type: application/pkcs7-mime; name="smime.p7m";
smime-type=enveloped-data
Content-Transfer-Encoding: base64
Hello,
SeaMonkey Mail has a flag to turn MIME Quoted-Printable on
(mail.strictly_mime=true), or use the 8-bit MIME for non-ASCII
characters instead (mail.strictly_mime=false, the default).
8-bit MIME support works fine as long as I use plain-text messages:
> MIME-Version: 1.0
> Content-Type:
6 matches
Mail list logo
