4
recommended smartermail version
Question asked by Fadi Hussein - 9/24/2024 at 4:18 AM
Unanswered
Hi,

May i ask which is the recommended version or most stable version of smartermail for production environment? we are currently on version 8055 and looking to upgrade our smartermail but want to check which version is recommended by the users?

Thanks for the advise,
Best regards,

10 Replies

Reply to Thread
7
8930
2
+1 for 8930
2
kevind Replied
We've been using 8930 also and it's stable.

But we need to upgrade to 8971 or later to fix this issue:
  • Added: New setting to complement "Enforce strict certificate validation" that eases certificate naming restrictions.
So planning a jump to 9008 and will see how it goes.
3
Heimir Eidskrem Replied
We are using 8930.  Very worried about upgrading after seeing so many issues.

4
Fadi Hussein Replied
Thank you all for the feedback, looks like 8930 is the most reasonable upgrade target, after going though all the release notes and reading in the community,  with every new release more issues appear, I think smartertools need to put on hold adding new features and mainly focusing on making the current release stable , with every new feature added; 2 or 3 new problem discovered. 

Thanks again for all,
Much appreciated. 
0
Richard Laliberte Replied
We are currently running 8993 and haven't have many issues, however it depends on features you are using. our server is fairly small compared to most, and we don't use MAPI and such at this time, so we aren't affected by a lot of the currently outstanding / ongoing issues. we were happy with 8930 before that as everyone else is pointing out.
1
James North Replied
9008 is stable and reliable for us on Ubuntu without any major issues. We don't use MAPI, but we do use EWS with Outlook.

Upgrading to 9014 destroys emails coming through a customer's WHMCS ticket system, so we're staying on this version for now.
1
Jorel Haggard Replied
Employee Post
Hello James,

I'm fairly confident that the bug you're seeing in 9014 is due to malformed headers and was fixed in 9028. 9028 did have a small clam related issue that we fixed in 9032, so if you wanted to try out an upgrade I'd aim for 9032. 

Best regards,
Jorel Haggard System/Network Administrator SmarterTools Inc. www.smartertools.com
4
Jay Dubb Replied
+1 for 8930.  We moved up and hit a serious MAPI bug.  Reverted to 8930 and life returned to normal.  

We're very anxious to update, because there are some MAPI fixes we've been anxiously awaiting, but the fallout from our "few hours" recently on a newer build (before reverting to 8930) have left us justifiably paranoid about rocking the boat again, until we see a lot of "good" experiences on the latest build posted in this forum.

To @James North's point -- the only problems with Smartermail that we've had have been 99% related to MAPI.  We have been using Smartermail continuously since 2006 (version 3) and other than MAPI, it has been a very solid platform.  MAPI has proved to be an extreme challenge for us, not just for bugs, but moreso in having to deal with all the customer complaints and unhappiness.  In our case, the scope is around 1,900 MAPI enabled accounts across 3 domains, and many are extremely active "corporate" users who depend on all the features of Outlook like it's oxygen.  If a bug is in there, they WILL find it, and complain loudly.  In our tiny part of the planet, if Smartertools could get their implementation of MAPI completely bug-free, it would be the perfect mail platform.  (with the understanding that it's a daunting task with Microsoft constantly changing things, including Outlook and how it connects with MAPI)
 
0
James North Replied
I'm fairly confident that the bug you're seeing in 9014 is due to malformed headers and was fixed in 9028. 9028 did have a small clam related issue that we fixed in 9032, so if you wanted to try out an upgrade I'd aim for 9032.
Great, thanks for the tip!

Reply to Thread