Обсуждение на форуме тут: http://www.forum.nobat.ru/index.php?topic=5906.0
What´s new in 184.108.40.206 since 220.127.116.11:
[ ! ] The new editor for Quick Templates;
[ - ] Fixed some AVs which might very rarely happen during the finalization of POP3/SMTP sessions;
[ - ] In OTFE mode, when you move a folder to another account or to the root (common folders) level, the contents of this folder was lost.
What´s new in 18.104.22.168 since 22.214.171.124:
[ - ] gb2312 character set in HTML messages was not displayed correctly;
[ - ] Messages, signed by expired certificated, were displayed as valid in S/MIME internal implementation;
[ - ] If a "Trusted Root CA" address book was inaccessible while adding a certificate to it, The Bat! might give an "Access Violation" error. Now, if The Bat! cannot add a certificate to the address book, it displays detailed reason to the user.
What´s new in 126.96.36.199 since 188.8.131.52:
[ + ] You can specify AES 128 bit and 256 bit for encryption when using S/MIME internal implementation;
[ * ] If a mail server was ill-configured to have different self-signed TLS certificates to send and receive mail, and these certificates had the same "Subject" but different key data, and the user have added the first certificate to the Trusted Root CA address book, the second certificate gave "Signature match failed" error, because The Bat! first uses certificates from address book and then from TLS sessions, and since these certificates had different "Subject" (which is prohibited by X.509), The Bat! did use key data from first certificate as though it was the second certificate. The "Signature match failed" error gave no clue to the user of how to resolve this problem. Now The Bat! have workaround for such ill-configured servers. In case of "Signature match failed" error during a TLS session, The Bat! tries to verify the certificate again, but in this time certificates transmitted in the TLS session have priority over the certificate from the address book. This avoids the error above mentioned.