Re: 8-bit MIME vs quoted-printable for signed messages

2017-09-25 Thread chokito 
Therefore the same at Thunderbird.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 8-bit MIME vs quoted-printable for signed messages

2017-09-25 Thread Andrey ``Bass'' Shcheglov 
-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 https://www.cryptosys.net/pki/manpki/pki_usinginm
ime.html: "You are strongly recommended to use quoted-printable encoding
 for the content part of the message to prevent the signed data being ch
anged during transmission."
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlnI9BgACgkQFX2weoTrDGfvcgCdGd+LsCTlmNkLscN/pS9XgojL
Y14AoOiEA8CohdHXxiVItYFD1nNa+5+d
=N5ui
-END PGP SIGNATURE-
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 8-bit MIME vs quoted-printable for signed messages

2017-09-25 Thread chokito 
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."
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 8-bit MIME vs quoted-printable for signed messages

2017-09-25 Thread Andrey ``Bass'' Shcheglov 
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 encrypted message body.

Regards,
Andrey.

On 22.09.2017 16:09, chokito wrote:
> 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
> Content-Disposition: attachment; filename="smime.p7m"
> Content-Description: S/MIME Encrypted Message
> 
> SeaMonkey 2.49.1 ( 20170619162041)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 8-bit MIME vs quoted-printable for signed messages

2017-09-22 Thread chokito 
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
Content-Disposition: attachment; filename="smime.p7m"
Content-Description: S/MIME Encrypted Message

SeaMonkey 2.49.1 ( 20170619162041)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

8-bit MIME vs quoted-printable for signed messages

2017-09-21 Thread Andrey ``Bass'' Shcheglov 
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: text/plain; charset=KOI8-R
> Content-Transfer-Encoding: 8bit

or plain-text messages with attachments:

> MIME-Version: 1.0
> Content-Type: multipart/mixed;
>  boundary="35CC02DE2AE5C262E603123C"
> 
> This is a multi-part message in MIME format.
> --35CC02DE2AE5C262E603123C
> Content-Type: text/plain; charset=KOI8-R
> Content-Transfer-Encoding: 8bit


If, however, I want to send an S/MIME:

> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; 
> micalg=sha-256; boundary="ms090906030006040802020901"

or a PGP/MIME signed message:

> Content-Type: multipart/signed; micalg=pgp-sha1;
>  protocol="application/pgp-signature";
>  boundary="JtS08MAj4iIEUA9NbuVGRLWU7ge3cLOTW"

my message body gets always encoded as quoted-printable:

> Content-Transfer-Encoding: quoted-printable


What is the reason for this behaviour, and how can change it (i. e.
force SeaMonkey to use 8 bit MIME)?


Regards,
Andrey.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey