We like to wait a week too.  Thank you for starting this thread.

Ron

I have an issue and support told me to download the latest. I always get nervous, still do not understand how something that was working can potentially no longer work.

Will let you know what happens.

Quick update: When I went to click on download the MSI, I got the EXE, not a good start. Looking for the Legacy build.

Over the weekend we have upgraded 2 larger installations of Smartermail from build 7859 to 7866. So far everything looks to be ok.

We violated our week rule for 7866 as we waited a week for the 7859 build that fixed an issue we were experiencing. 7866 was a smaller releases with what appeared to be nothing major changing, so we deployed it. No issues to report thus far.

Hello everyone, we updated from build 7817 to 7866 72 hours ago, did several tests and everything seems stable for now. We have about 1000 accounts on this server. It was the weekend and we have a lot of vacationing customers, so I'll keep my fingers crossed for a few weeks before concluding that everything is perfect.

Hi,

We upgraded last night and this morning we had a CPU spike to 99,99% and the services were not responding, we had to restart the SM service, after that everything seems fine for now...

Thank you all for the feedback. Never a fan of updates during the week so a job for this weekend, unless SM advise the security patch is critical.

Installed  16/07/2021... No new issues so far...

I would recommend this update for the security update alone.

No issues so far here as well

I had to restart SM Service after install. During first startup MailService started, I was able to log in as admin but it looks like no user was able to authenticate and also I was getting some out of bounds errors in admin interface. After service restart it looks like it is working correctly.

No major issues here.

The only reported problem is some messages that had been previously viewable in webmail are now not showing properly and display the potentially dangerous scripts warning. I wonder if this is related to the security fix. Regardless, I've opened a ticket to troubleshoot further, but it's frustrating that there isn't a way for users (or at the very least admins) to override these script warnings. Especially since other webmail platforms, like Gmail, don't have an issue with displaying the content. Users aren't very satisfied with being told to use a mail client to work around the issue.

7866 installed fine for us. Had some issues with some EAS clients after the upgrade. Other than that all is well.

@Matthew : What kind of issues your affected EAS users had?

Have a good one!

Before MAPI many of our customers were using EAS with Outlook to get as close to Exchange functionality as possible. Somewhere along the line we were told that EAS was only for mobile devices. Anyway… about 5 out of maybe 20 EAS clients got hosed after the upgrade. Their Outlook inbox showed empty yet shows “all folders up to date” so they were very scared that they lost everything until I assured them that all data was on the server. I tried a few different solutions to try and fix it but in the end all those accounts had to remove the account in Outlook, add it back, and let the account resync. For a few users it was no big deal but a few had 10-20gb of data and they weren’t happy about it at all.

As best as I am aware it was only the Outlook people that had problems. My PC is on the same LAN as the mail server so it did resync my data without intervention (I watched the inbox go from 9,000 emails down to zero and then started repopulating) and I didn’t have to remove the account, etc.

Eventually I’ll have to migrate all those users PCs from EAS to MAPI. One client is leaving us for O365 so I don’t have to worry about them.

It was a headache but if there were security patches in the update I consider it all good. I’m only now deploying the first MAPI accounts as I waited a number of SM revisions before wanting to roll it out live.

Matt

Thanks Matt for all these details.

Deployed 7866 but now cannot delete broken EAS 'profiles' via webmail. Every attempt to delete across different users returns:

"The given key was not present in the dictionary"

Anyone encounter this and have a fix?

For anyone reading in the future... The workaround was:

1. Attempt a resync from the device - sync still fails

2. Now you can delete the sync profile -  sync still will not work

3. Delete the account from the device

4. Re-add the account to the device

Note - it was only possible to delete the profile after the device had tried to sync again. Without this step deleting the profile failed consistently across different users/domains with the "The given key was not present in the dictionary".

I'm seeing higher than normal CPU usage on Sunday, which is unusual. 55% Smartermail Service, and actually now noticing that since July 1st, there is a large increase in CPU usage overall. 

Before July 1st before with build 7803, 5% weekends to 35% weekdays

After July 1st with builds 7852 & 7866, 40% weekends to 75% weekdays

This seems like a substantial increase, is anyone else seeing CPU usage spike like this.

Ours is running normally, no issues to report.

Normal CPU usage here too with 7866

No issues with CPU (or RAM) here

Same here, no issue with CPU or Mem usage.

Same here, no issues with CPU and Memory

Hi everyone,

I updated to 7866 yesterday, and everything went quite smooth apart from an EAS issue with one user as reported above, that I fixed deletenig and recreating the account in Outlook.

This morning however I got several notices from different clients that many emails they were waiting for didn't come. Looking into SMTP logs there were a lot of errors like "rsp: 451 Requested action aborted: error in processing" - "Exception: Failed to deserialize SmarterMail.Common.Files.SystemFiles.SystemGreylistFile value".

I had to disable Greylisting to resume normal delivery. If I reenable it errors come out again.

Has anyone experienced this issue before?

Thank you.

@Ale, please create a support ticket so that we can examine the greylist.sbin file.  In the meantime, you may work around this be renaming/deleting the existing greylist.sbin file in the C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Settings folder (or wherever you have SmarterMail installed).  After deleting/renaming that file you will need to restart the mail service.