Back to Community Threads
I'm testing new 9091. Please share your experiences, I will share mine...
Question asked by Gabriele Maoret - SERSIS - 11/22/2024 at 12:35 AM
Unanswered
I'm testing new 9091. Please share your experiences, I will share mine...


EDIT: FYI, I'm updating from 8930 on dedicated Windows 2019 servers, everyones using various MS Outlook MAPI (2016-2019-2021-365...), all in Italian language.

Also there are some users who use EAS (with various software on various smartphones) and some use IMAP with Thunderbird or MS Outlook
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
Sébastien Riccio Replied
11/22/2024 at 12:52 AM
Updated this night. So far no new breaking issues. Let's see how it's going the next days.
Sébastien Riccio
System & Network Admin
I report a problem (which, from what I see, seems to be only a display issue...).

In the management interface, in the "ACCOUNTS" tab of a domain, many users report 0 (zero) GB as occupied space, even though they actually have some GB of data.

Example:




However, if, for example, I enter ROSANNAC's webmail I see this:
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
Sébastien Riccio Replied
11/22/2024 at 2:16 AM
It might be related to this change in build 9084:

  • Efficiency: Information from some JSON files was moved to a new SBIN file to increase efficiency and add functionality.
When I asked to support what data was moved from JSON to SBIN, because I was about to downgrade from a custom build  >8094 to 8056, they talked about mailbox sizes:

So the two items we store in the activity.sbin file are the mailbox sizes (which used to be in the accounts.json) and the last login times (which used to be in the user's settings.json). If they downgrade, this data will be outdated. When they then upgrade back to this version (or a future version) both of those values will still be outdated. The last login time may not be a big deal as most of that is just information that is shown to system/domain admins in the "User Connections" tab. The size part is more important but the Accounts tab has an option where you can "recalculate disk usage" and that value will get fixed.


Last login times will be rectified as users login. If you want it as up to date as possible (when re-upgrading later) without people logging back in first, delete the activity.sbin file from the domain and its ArchiveData folder before re-upgrading. That will make SmarterMail redo the conversion with whatever data is available after running in the downgrade state.

Maybe you should try to trigger a size recalculation of these mailboxes ?

Kind regards.
Sébastien Riccio
System & Network Admin
Triggering a new mailbox size calculation will be a real pain in the ass if you have thousands of users across hundreds of domains...

I can't do that...
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
Sébastien Riccio Replied
11/22/2024 at 4:10 AM
You can try on one affected mailbox to see if it helps. 

Then a small script that loops over domains and their mailboxes and issue a recalc via the API can be a solution. 

I have such a (python) script for another mass action on mailboxes that I can adapt for this and share, if needed. 
Sébastien Riccio
System & Network Admin
It works, but (again) it's a pain in the ass...
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
Employee Replied
11/22/2024 at 8:55 AM
Employee Post
Hello,

Unfortunately this is currently expected behavior for those who downgraded to 9056 or earlier, and then re-upgrade past 9084 due to the sbin file changes. This is one reason we recommend against rolling back.

Sébastien, your offer to share your API script is very kind and I'm sure would be much appreciated by those who did roll back and are seeing discrepancies. 

Thank you,
And how to circumvent that when upgrading?
Ok, I can understand.


But if I upgrade from a previous version that works perfectly, I expect the new one to work similarly...
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
We all do Gabriele :)
J
J. LaDow Replied
11/22/2024 at 12:06 PM
[... quote ...] . This is one reason we recommend against rolling back. [ ... end ... ]

Recommending against rolling back would not be near an issue if releases did not contain so many bugs.  It's understandable that rolling backwards creates it's own "unknown problems". Reverting to backups on live mail servers causes lost email one way or another.

Being live guinea pigs with customers and enterprise software requires the ability to roll back changes or upgrades. 

Having the expense of spinning up additional servers just to test software that should already be tested should not fall on us.
MailEnable survivor / convert --

Admin panel.... it changes when you change something in the account and hit save.

And if you hit the mark all box and recaculate it brings everything back as it was.
Another visualization issue: in SPOOL I cannot see the "Virus Quarantine" items list.
The other tabs seem to be OK.
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
I am getting Error 1053  when trying to restart services in services.msc.
After 3-4 days of testing with 9091 (upgraded from 8930), we are again receiving (from several users) reports of synchronization problems between SmarterMail and MS Outlook MAPI (various versions of MS Outlook from 2016 to 365, all in Italian).

Unfortunately these problems are blocking for our customers, so we were forced to go back to 8930, which immediately solved the synchronization problems of these users and restored the functionality to the state before the upgrade.

Unfortunately again, being forced to downgrade does not allow us to investigate the problem thoroughly...
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
Oliver Replied
11/25/2024 at 4:21 AM
Hello Gabriele,

Unfortunately, since version 8965 I have been experiencing problems with S/MIME signed mails. 

As I didn't want to blow up your post here, here is the link to the post that describes this problem in more detail.

Regards
Oliver
Kyle Kerst Replied
11/25/2024 at 7:23 AM
Employee Post
@Gabriele: I think Jorel might have thought that you had downgraded previously. When that occurs the data that would have already been moved to the new file is lost to the old version, and so I think that's why he was probing that direction. It sounds like you just did a straight upgrade from 8930 though, correct? If so can I have you get a ticket submitted on this so we can take a look? I wonder if some of those user's disk usage data may not have moved over properly and if we can get a backup of the pre-upgrade user we can likely get that replicated and escalated. Thanks Gabriele!
Kyle Kerst
Lead Internal Network/System Administrator
SmarterTools Inc.
It goes away if you mark all users and recalculate storage.

Then its fine again.
I am getting this in sent items


No headers and unable to search for sender.

Tried this on numerous builds and now downgrading again to good ol' 8930....

The email had "" in it... timezone is GMT+1 and using UTF8 as characterset.
Back to Community Threads

Reply to Thread

Enter the verification text
Related Knowledge Base Articles
Set up SmarterMail as an IIS Site in IIS 8SmarterMail > Server Configuration and Management
Upgrading SmarterMail (Domain Conversion)SmarterMail > Installation and Configuration
Moving SmarterMail Data to Shared StorageSmarterMail > Server Configuration and Management
Set up SmarterMail as an IIS Site in IIS 10SmarterMail > Server Configuration and Management
How Does MAPI & EWS and EAS Licensing Work?SmarterMail > Installation and Configuration