Search  Rules  Login
TheBat English » The Bat! - Configuring the E-mail Client
Pages: 1
RSS
Problem with S/MIME encrypt and sign - after update to 4.0.x
 
#1
0  
Hi,

I use internal implementation S/MIME, in TB v3.99 heder of messages after encryption and sign was:

X-Mailer: The Bat! (v3.99.24) Professional
MIME-Version: 1.0
Content-Type: application/pkcs7-mime; name="smime.p7m"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7m"
Content-Description: S/MIME Encrypted Message

now, after update to TB v4.0.14 heder is:

X-Mailer: The Bat! (v4.0.14) Professional
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="-----

In TB v3.99 sign was integrated with encrypted message, now (TB v4.0.14) is multipart (sign and encrypted data).

How can I change method of signing ? (like in TB v3.99)

Please help.
 
 
 
#2
0  
Same problem with v4.0.14.9

Sending a S/MIME-signed message writes the header:

MIME-Version: 1.0
Content-Type: multipart/signed;
protocol="application/pkcs7-signature"; micalg=md5;
boundary="----------82AD9DA2ADE02"


Results:
Error-message by checking the signature in v3.99.3
OK-message bei checking in v4.0.14.9
 
 
 
Pages: 1