Upgrading Mail servers to SmarterMail 4.2 Release

Picture of Tim Davis

Tim Davis

Senior Cloud and Security Engineer

Share Post:

We will be upgrading our mail servers to the latest release SmarterMail 4.2 this Thursday, May 24th at 11p.m. EST. There will be around 5-10 minutes downtime.

 The following new enhancements features are available in Smarter Mail 4.2

ADDED: An option is now available in user settings to turn off menu scrolling.

ADDED: SSL is now supported for POP retrieval.

EFFICIENCY: IMAP connections will now run asynchronously, improving overall system efficiency and lower thread usage.

EFFICIENCY: Improved performance when deleting multiple messages from a large mailbox.

  • EFFICIENCY: Local delivery has been optimized for locked mailboxes.
  • EFFICIENCY: POP connections will now run asynchronously, improving overall system efficiency and lower thread usage.
  • FIXED: Corrected some issues with mailing list digests. Digested HTML should no longer become corrupt, and digests should now be sent out on time after making a change to the trigger.
  • FIXED: Fixed a bug that would prevent contact importing with .VCF files.
  • FIXED: Fixed a bug that would sometimes cause SmarterMail to lose the default domain skin.
  • FIXED: Fixed a bug which could cause the SmarterMail service to stop if the “Temp” directory did not exist when trying to send email reports.
  • FIXED: Fixed an issue with uploading messages with Thunderbird IMAP. Thunderbird will no longer disconnect from the server after uploading several messages.
  • FIXED: Folder lists will no longer link to an incorrect folder when a subfolder is created before the parent folder.
  • FIXED: HTML signatures should no longer contain extraneous new lines.
  • FIXED: Message Archiving will now sort the domains in the drop down list.
  • FIXED: Occasional mailbox corruption when using APOP. (Affects Mac Mail and other clients)
  • FIXED: Pop retrieval will now work correctly with Comcast servers when leaving mail on server.
  • FIXED: Resolved an issue where the HTML composer would delete the highlighted text when right clicking.
  • FIXED: Several occurrences of untranslatable text have been made translatable.
  • FIXED: SmarterMail should no longer report an error (Failed to get message list. Folder not found.) when sending a message immediately after logging back in after a session timeout.
  • FIXED: SmarterMail will no longer append “.eml” to attachments that already end in “.eml”.
  • FIXED: SmarterMail will no longer disconnect clients who issue the NOOP command.
  • FIXED: SmarterMail will now look for CNAME records when no MX records are found.
  • FIXED: SmarterMail will now prevent users from accidentally sending a mail twice by clicking “send” in rapid succession.
  • FIXED: The “Max bad commands” limit in IMAP now correctly counts all bad commands.
  • FIXED: The “Max bad commands” limit in POP now correctly counts all bad commands.
  • FIXED: The Blacklist/Whitelist page will now select the correct tab when adding/deleting rules.
  • FIXED: The content-type header will now properly quote filenames when dealing with attachments.
  • FIXED: The search bar on the messages page will now correctly show up after viewing a message and then using the back button.
  • FIXED: The session timeout for POP completely closes the connection rather than simply issuing a timeout error message. Additionally, the timeout error message has been adjusted to better comply with the RFC.
  • FIXED: When importing addresses to a mailing list, SmarterMail will now correctly report the number of addresses imported.
  • FIXED: When sending an email to a large number of contacts, the contact list will no longer be sent via the querystring. This should improve compatibility with Internet Explorer.
  • FIXED: When sending daily/weekly/monthly email reports, SmarterMail will automatically adjust the time offset if necessary. For instance, an email report showing “CPU Usage this month” sent out on May 1st, will show April’s usage, rather than Mays.
  • There are many other features for admins that are not lister here.

    Thank you.


    Stay Connected

    More Updates

    Log4j2 Vulnerability

    Revion is not using Log4j2 tool for apache-tomcat, we are using default lightweight API – Java logging API — java.util.logging. Additionally, we are not exposing

    Bind/DNS services upgraded

    To address security vulnerability discovered in Bind 9.8.1. we have upgraded all bind dns servers to 9.8.1.-P1