Tuesday, October 2, 2012

The Bat! 5.2.2 Portable by Evan

The Bat! mail client has a lot of vital benefits and useful features that make your email experience simple and convenient. All these features perfectly fit any Windows OS. Moreover, The Bat! is the first and only email client Certified for Windows Vista by Microsoft Corporation. “Certified for Vista” logo guarantees the highest level of compatibility between Vista and The Bat! mechanisms.
Protection of privacy The Bat!’s characteristic feature is the most widespread support of authentication protocols and of encryption while working with mail servers.
Anti-virus defense The other side of safety is protection against malicious codes. The Bat! benefits of its own HTML viewing mechanism – Robin HTML Viewer, as well as of its own image viewing module.

What's new:
#New features:
- Highlighting of the iecm

#Improvements:
- Cosmetic fixes at The Bat! Preferences
- The recipient's photo is displayed (if available) for messages in the "Outbox" and "Sent" folders


# Fixes:
- The Internal HTML viewer could not correctly display messages in the Japanese character set
- Some IMAP servers (g.g. Zimbra) cannot handle the ID command sent simultaneously with Login
- The Edition Type (Home/Professional) wasn't displayed in the about box
- Fixes for the Mail Dispatcher list/header view size and the list fonts
- When a sub-set of folders was restored from the backup file while they has been missing in that account, those folders were created under the account's Inbox folder
- Not all Google contacts were imported into The Bat!'s address book
- The changes to Character Sets (XLAT) were not saved ("Options -> Preferences -> Other options")
- The changes to the character set "Translation FROM Windows" could not be saved (Options -> Preferences -> Other options -> Character Sets (XLAT))
- When an HTML message was loaded for editing, the viewer options were used
- Inline images for the HTML formatted messages were not displayed if system's HTML viewer had been used
- The "Error reading xtSigners.Options: Invalid property value" issue when verifying S/MIME messages has been fixed