Guess that means no upgrade for us... Sorry for the stability issues Stefan! We do not upgrade immediately anymore. I watch the forums for a week or so, see what is going on and what issues are being reported, anything major like that, #wait.

Same here, we do not upgrade right away anymore, unless it's a custom build that addresses one particular issue and has no other changes.
In the meantime ST publishes an article on how SmarterMail helps system administrator gain 90% of administration time over Exchange.
My colleagues laughed at me when they've seen this, knowing how much time I have to spend on troubleshooting and even coding our own diagnostics and recovery tools for SM... as no tools are shipped with the product.

(cf: https://portal.smartertools.com/community/a94154/ship-_cfg-_grp-parsing-viewer-repair-tools-with-smartermail.aspx)

EDIT: Sorry I did not mean to hijack the original topic but I had to say it

Hi all,

I've running SmarterMail for personal use and the release notes gave a hint to a solution of an older issue with signatures. So I wanted to try the newest build.

Because of the personal usage of SmarterMail it isn't much critical to early adopt to new releases - as long as SmarterMail is running and I can work with my mails ;-). And if there are no early adopters the bugs won't be found. We all know that many of the software products won't be tested hard before they're released. So the users are the testers :-(.

For using SmarterMail in professional environments it's the right way to wait for a while before updating. A lot of bugs are critical if there are a lot of users who can't work anymore.

Kind Regards.

Do you have a ticket open about this Stefan?

No, I didn't open a support ticket because I'm using the free edition.

It's interesting that the high CPU load didn't come back since last sunday. For the moment all mails are downloaded from the external mail hoster by SmarterMail.

I'm using 7845 from last friday and I'm not aware of any malfunction realted to CPU, RAM or service not working.

To me it's working as expected.

Hello Stefan,

Thank you for your post. The most likely cause of the high CPU usage after the upgrade was due to the upgrade having to convert old files to new ones. If you go to Troubleshooting->Logs->Conversion. There is a new log to see the conversion process. The conversion would also explain the high CPU usage after the upgrade but then it subsiding. 

Best Regards, 

Hello Zach,

I can't find any conversion logs. There are none under Troubleshooting->Logs->Conversion, none in the log file folder.

For Troubleshooting->Logs->Conversion you have to be logged in as system administrator, not as domain administrator, right?

Kind Regards.

Stefan,

Yes, you'll need to be logged in as the system administrator. In Troubleshooting > View Logs tab change the Type to Conversion.

Emily,

thank you. So I did the right steps but there are no conversion logs.

Kind Regards.