6
Anyone running Build 8993 (Aug 15, 2024)
Question asked by Brian Bjerring-Jensen - 8/16/2024 at 2:12 AM
Unanswered
Just curious... its a pretty long fix list. Anyone tried it yet?


  • Added: A setting for an outbound gateway configuration to enable/disable SMTPUTF8.
  • Added: Descriptions (and alternate descriptions) for Appointment Types in Scheduling.
  • Added: Implemented XMPP RFC XEP-0393 to allow for stylized chat messages.
  • Added: Secure connection support for configuring LDAP and AD servers as authentication providers.
  • Added: The ability to "Load More" Chat history on demand.
  • Added: The ability to bind LDAP ports with SSL/TLS and StartTLS.
  • Added: The ability to create usernames with uppercase letters.
  • Added: The ability to force SSL certificate renewal.
  • Changed: Chat bubbles in alias chats now only display username/user name to avoid redundancy.
  • Changed: Cleaned up the Grid View for Calendars to indicate when a recurring appointment has expired.
  • Changed: Improved the display of the View Availability modal for better readability.
  • Changed: Updated custom 404 pages.
  • Fixed: A unique customer issue affecting new message notifications.
  • Fixed: A unique customer issue where an upgrade caused issues with Chat, including connection issues to clients.
  • Fixed: Adding a similar domain with an added TLD extension occasionally fails.
  • Fixed: An issue adding Work Info to a contact.
  • Fixed: An issue where a Console error displays when logging out of webmail while in the contacts section.
  • Fixed: An issue where administrators that work on a Windows install may not work on a Linux install.
  • Fixed: An issue where an upgrade could cause odd XMPP behavior.
  • Fixed: An issue where LDAP connectivity fails with immediate timeout several times before succeeding.
  • Fixed: An issue with the Scheduling link when Online Meetings are disabled.
  • Fixed: An LDAP authentication provider that requires the username to be in DN format can fail to authenticate.
  • Fixed: An XMPP Bearer Token authentication issue.
  • Fixed: Automated Forwarding for UTF8 addresses fails to properly encode those addresses.
  • Fixed: Bounce messages to external accounts can get held up in the spool.
  • Fixed: Cannot add an LDAP authentication provider unless domain and organizational indicators in the LDAP binding string are in all caps.
  • Fixed: Domain aliases don't inherit domain-level login customization.
  • Fixed: Drive stats for disk space is not showing the correct amount.
  • Fixed: Emails that fail DMARC and are rejected are leaving orphaned HDR files in the spool folders.
  • Fixed: Google Drive is not working for File Storage.
  • Fixed: Issue where sending a message to a domain alias, then a message to a primary domain account, can cause two versions of MailboxManager to be created.
  • Fixed: Issues attaching users when moving them from Windows to Linux.
  • Fixed: Log searching can break if a client's local time is different than server time.
  • Fixed: Mailing Lists configured to use Subscriber Address for the To: address sometimes displays just the first subscriber.
  • Fixed: Messages sent from webmail to Gmail, with XML attachments, are showing the xml in the body.
  • Fixed: Messages with foreign characters received by and sent through IMAP clients can disrupt the foreign characters.
  • Fixed: Migrating from Kerio Connect fails with "Unable to connect with the credentials supplied" regardless of credentials provided.
  • Fixed: Notes occasionally use the full body for the Note's subject.
  • Fixed: Occasionally, the cursor doesn't behave properly in webmail when using Firefox.
  • Fixed: Refresh issues when saving a draft in webmail when the draft message is displayed in the preview window.
  • Fixed: Replying to a message using Apple Mail (EWS) displays "received date/time" when viewed in eM Client, but doesn't show "replied on" text in webmail.
  • Fixed: Scheduling Time Zone defaults to UTC (Sao Tome).
  • Fixed: Sending to a valid email address and an email address that's too long doesn't actually send to the too long address, but it doesn't display an error as it should.
  • Fixed: Signature Images seem to shrink in the editor when you save a draft.
  • Fixed: Signatures created using HTML can deform when typing in the compose window in webmail.
  • Fixed: Some folder labels missing translations.
  • Fixed: Some issues affecting the ability to use third-party chat clients with Chat.
  • Fixed: The Send Email dialog is not sized properly.
  • Fixed: Turkish characters appear to be corrupted for BCC in Outlook (MAPI).
  • Fixed: Upgrading across a few Builds can duplicate AD providers.
  • Fixed: Webmail version of sent messages that include Turkish characters in the To/CC/BCC fields show puny code in the message headers.
  • Fixed: When acting as an LDAP server, authentication fails if the username is not formatted like an email.
  • Fixed: XMPP Status occasionally doesn't update automatically across clients when a user logs out.
  • Security: One or more security issues were fixed. It is recommended that all users update to this release.
  • Translations: Updated and fixed multiple translation files.

46 Replies

Reply to Thread
3
I'm testing it in production on a small (58 users) customer on premise "guinea pig" server (with the customer's consent, of course...).

I await feedback from users...

But it will take some time, because here in Italy almost all companies make almost everyone go on holiday during the central weeks of August
Gabriele Maoret - Head of SysAdmins 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)
1
Waiting for your feedback  Gabriele. It would be going on a production server, so we dont need more problems :)
8
Matt Petty Replied
Employee Post
Same, can't wait for the feedback. Haven't heard anything yet myself. We really gave it our all. We had a meeting beginning of last week, we knew what had to happen. We took more careful but meaningful steps and worked with customers along the way. I think we did like 3 custom builds in that time with lots of back and forth with a handful of customers. Everyone here is firing on all cylinders, support, engineering, our IT team has been doing upgrades, and even others that helped make us a nice breakfast earlier this week. So I'm definitely interested to hear what feedback people have on the new version. 

Docker on Desktop and Linux are great for test servers. Linux makes servers easy to deploy and Docker on Desktop setup with mounts makes it easy to test SM since you can just point the mount at backups or a copy of a domain.
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com
2
Hi Matt! I know you guys are working very hard!

By the way, I'm on Windows and not planning to go on Linux (or Docker) for now, maybe next year...
Gabriele Maoret - Head of SysAdmins 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)
1
Stefan Mössner Replied
In mobile webmail on my smartphone now the mail folders are all listed without any structure when moving mails. Subfolders are listed on the same level as the folders. So it's hard to find the right subfolders.
0
Sébastien Riccio Replied
I noticed that mail bounces are not sent via our gateway anymore, but directly to the target server. Is that on purpose ?
I think this changed since previous build but I see no entry for this in the changelog.
Sébastien Riccio System & Network Admin https://swisscenter.com
0
Matt Petty Replied
Employee Post
That may be new to SM in general, but not with this specific weekly build. Likely that changed with the "linux era" releases, not really sure what to call these releases post 8930. Its something we can talk about, but I'm feeling like there is an RFC/transmission reason for why we're doing it like that now. 
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com
1
Sébastien Riccio Replied
Hello Matt,

Okay, it would be interesting to know about why this changed. I'll need to check that our server real IP is added to the SPF entry so that the bounces aren't rejected by remotes.
It's not our case, but I'm thinking about scenarios where people use an outgoing gateway because their server/vps hoster closes port 25 for outgoing.
In that case the bounces will probably stack in queue (connection timeout with remotes MX) if they are not sent through the gateway.

That being said, on overall it seems that the issues we had with many mails stuck in spool with "Error: 0" is almost gone now.

I still have some checks to do with this build and forwarded mails (SRS enabled), and also how the remotes handle the ARC entries added by SmarterMail (that we can't disable unefortunately).

Kind regards
Sébastien Riccio System & Network Admin https://swisscenter.com
1
Brian Kropf Replied
Is no news good news? I'm not hearing much about the latest build. Is it safe to upgrade a production server?
1
Brian A. Replied
There is an issue in 8992 & 8993 wherby internal users cannot reply to an email when using Outlook/MAPI and Global Address List is turned off.

1
Patrick Mattson Replied
I needed to create a new DKIM record. My issue is I cannot delete the current DKIM record, there are no controls. Saw one of the releases mentioned a fix for that. Figured it would be in this version. Installed no luck.

Created a ticket.
1
Hi everyone!!!

I'm currently using the 8993 in a small on-premise "guines-pig" server (1 domain - 57 users) and, so far, I haven't received any complaints from users yet... fingers crossed!

@Brian A.  - my users all have GAL enabled, so perhaps for this reason I have no report of the problem you reported...
Gabriele Maoret - Head of SysAdmins 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)
2
Andrew Barker Replied
Employee Post
Patrick,

Since build 8755, SmarterMail has included a DKIM rollover mechanism. Using this, SmarterMail will generate a new DKIM key pair and put it in a standby status. It will periodically check if the appropriate DNS record has been created while continuing to use the previous keys. Once SmarterMail detects the new DNS record, the new keys are made active and the old keys are forgotten.

If you no longer want to use a DKIM key, you need to either disable DKIM signing, or initiate a DKIM rollover.
Andrew Barker Software Developer SmarterTools Inc. www.smartertools.com
4
Jay Dubb Replied
@Gabriele - please keep us updated.  We need to take a post-8965 release to resolve some MAPI issues we have on 8930, but aren't making that jump until we are reasonably sure of not walking into another MAPI meat grinder.
 
1
Merle Wait Replied
Wait.. What???  Our main mail server is not set to return ANY email except via inbound /outbound gateways...
All returns are handled through gateways......  
In the thread about I read "the main mail server now handles rejects" ??
Matt Petty Replied  8/17/2024 at 10:55 AM  = as an example.
If that is true.... I am in @#@#@#@@# going forward
Is there not anyway around that?


0
Matt Petty Replied
Employee Post
@Merle Wait 
What version are you currently on? I believe this behavior changed before 8930.
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com
0
Merle Wait Replied
Enterprise 100.0.8629 - Aug 17th 2023
Our gateways Inbound/Outbound .. would either be that version or older

0
Brian Kropf Replied
I upgraded one of our servers to Build 8993 this morning. I have multiple email accounts in my personal Outlook from several different domains on the server I updated as well as accounts from domains from a different SmarterMail server that is still on Build 8930.
After updating to Build 8993, I have several accounts from one domain that cause Outlook to crash whenever I select an email. I can open Outlook, select the account, and view the list of emails without causing it to crash. But selecting an individual email causes Outlook to immediately freeze up and then crash. 
I did a Rebuild and Reindex on the affected accounts in an effort to fix the issue and that didn't fix the problem.
If I log into web mail and make changes such as marking Read/Unread or deleting emails, Outlook almost immediately refreshes to reflect my actions in web mail.

Any ideas on what the problem is or how to recover?

Edit: I connected to my work computer, opened Outlook and I am not seeing the same behavior on it. It only has a total of three email accounts and my personal Outlook has twelve accounts. But it also has accounts from both SmarterMail servers.

Update 2: I submitted a ticket (375-2E5CDBD2-0007) because I'm seeing this behavior on a second computer. 
4
Brian A. Replied
@Brian K

I'm seeing this as well. Outlook is crashing a lot.  Sometimes it crashes on starting and sometimes on opening an email, over and over until Outlook tries to start in "safe mode."

I've had to install eM Client on quite a few computers because Outlook is unusable now. Clients are losing patience... And so am I.
1
SmP Replied
We're holding onto 8909 until these issues get fixed as most of our business users are Outlook-heavy environments.
2
We havent upgraded since 8930 thank god.

MAPI users all over the place and we cant afford to lose more clients.
3
Tim Uzzanti Replied
Employee Post
Microsoft has updated the old Outlook, which has changed some of its behaviors. For example, even if you are using MAPI, they are now utilizing new EWS calls for some searches that we had not implemented because no clients had used them before. There have been a couple of other changes we've had to make regarding GAL and sharing related to MAPI. Additionally, there are some issues with how Outlook handles international domain and email addresses, which is a new feature we added in SmarterMail. It's been a bit of a whack-a-mole situation with Outlook over the last month!

We are receiving conflicting information from Microsoft regarding updates to Exchange on-premise as they keep pushing cumulative updates and a possible new version. It appears Microsoft may be updating Outlook to address some shortfalls with Exchange at the moment.  

If you open a ticket with us, we can assist you in providing a Fiddler trace of the network traffic, which will help us identify the cause of the issue with a specific mailbox.
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
0
Brian A. Replied
@Tim

Thanks for the info. That could explain why some people are having problems and others not if everyone is on a different update version of Outlook.

I would prefer that they move Outlook totally to EWS because EWS on eM Client and AquaMail is working really well for me (now that we got that "sending on behalf of" stuff taken care of).
2
Scarab Replied
We just switched over to Build 8993 and are experiencing a myriad of issues:

  1. Smarthost Spam Score is not being passed from Incoming Gateways
  2. DMARC Score from Incoming Gateway is ignored if it is enabled on the Gateway but disabled on the Primary Server. (This might actually be W.A.I. but didn't do this previously.)
  3. Incoming Gateways are accumulating a large amount of mail in Waiting To Deliver Spool that are unable to be delivered (just fails with a "Exception: No addresses found" even though there is a valid RFC TO: address in the Headers.) . All messages stuck there have "messageFixesRan: True" in the Header.  (Error Stack: at MimeKit.InternetAddressList.TryParse(AddressParserFlags flags, ParserOptions options, Byte[] text, Int32& index, Int32 endIndex, Boolean isGroup, Int32 groupDepth, List`1& addresses) at MimeKit.InternetAddressList.Parse(ParserOptions options, String text) at SmarterMail.MailService.RelayServer.Clients.SMTP.SmtpMessage.PrepareForSmtp(Boolean allowSmtpUtf8, Boolean allow8BitMime, IReadOnlyList`1 recipients) at MailService.RelayServer.Clients.SMTP.SmtpClientSession.StartProcessing(SmtpMessage message, String sessionId)
  4. Previously created mail folders containing special characters (i.e. Inbox\Sanford & Sons LLC. or Inbox\Groups, Assoc., Orgs) are throwing "Error trying to fix paths for user directory" errors and email can't be delivered to any accounts with mail folders generating this error. It will also duplicate that mail folder creating an error if you attempt to recursively Rebuild Folders (I got 8 additional folders named the same after doing a Rebuild Folders and another 8 if I tried to rename it from the webmail. Ultimately I had to rename the folder manually on the Server instead and then delete the duplicate virtual folders that direct to the physical folder from the account)
  5. Getting a lot of "Specified argument was out of the range of valid values." and "[MAIL SERVICE] The given key '22866' was not present in the dictionary." but haven't had the chance this morning to figure what these are about.
  6. One SmarterMail Gateway on Windows Server 2022 is not starting on startup (even though the service is set to Automatic). It is failing with Error 502.3(Event ID 7009 "A timeout was reached (30000 ms) while waiting for the MailService service to connect" followed by Event ID 7000 "The service did not respond to the start or control request in a timely fashion"). I've rebooted, uninstalled SmarterMail, rebooted, installed SmarterMail, rebooted, but it persists. When manually started it starts but it does not accept any connections other than Webmail.
  7. Previously quarantined spam or virus messages are unable to be displayed in the Spool Management (minor QOL issue that will resolve itself in 30 days).

I'm sure there is plenty more to come, but I'm getting the impression that QA routinely doesn't test on Gateways before release.
0
Merle Wait Replied
Thanks @Scarab  - our whole email processing is built on inbound and outbound gateways...
@Matt Petty - any idea about the outbound gateway issue?  

Enterprise 100.0.8629 - Aug 17th 2023
Our gateways Inbound/Outbound .. would either be that version or older

0
Tim Uzzanti Replied
Employee Post
Scarb,

I don't see any tickets submitted?  If you could submit with some additional details and logs, it will help us get things resolved quickly.    

We are ware of a couple of the items (1 and 2) which are related.  We have another customer who reported.
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
1
Brian Kropf Replied
I was given a custom build (9000) by SmarterMail and my Outlook hasn't frozen or crashed since (a couple of hours) and it seems more responsive when moving from one email to another or one account to another. Something could still act up so far it's looking good.

Thanks for all the efforts you put into making SmarterMail a great product!
3
Unfortunately, after a few days of using version 8993 on a small on-premise server with 58 users and only 1 domain, we, like Brian Kropf, started receiving reports of MS Outlook crashes (especially from a couple of key users who we can't tell to wait)...

We reverted to 8930 and that temporarily fixed the problem.

We are waiting for a new version to be released (hoping that the fix contained in the 9000 custom release that Brian Kropf received will be included)
Gabriele Maoret - Head of SysAdmins 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)
3
Patrick Jeski Replied
@Matt Petty - " Likely that changed with the "linux era" releases, not really sure what to call these releases post 8930."

Some radical software companies use major and minor version numbers. It's a thought.
0
Scarab Replied
@Tim

I didn't have a chance yesterday to open a Support Ticket as Mondays tend to get a little crazy (three and a half days of work crammed into one day to do it all in). Since items #1 and #2 are Known Issues, I submitted a Support Ticket for Item #3 as that is the most critical issue for us. We were able to resolve Item #7 on our own by manually deleting the previous SmarterMail installation entirely, doing a clean install and manually re-doing all the configuration settings (a PITA but not the first time we had conflicts caused by left-over SmarterMail files from previous versions upon upgrade).
0
Jereming Chen Replied
Employee Post
Hello Scarab,
Most of SmarterMail's files are left over because the installer is meant to use them as a base when upgrading to avoid the need for admins from re-doing all their configuration settings. 
We do appreciate you submitting the ticket and hopefully we can find a resolution for that soon.
Jereming Chen System/Network Administrator SmarterTools Inc. www.smartertools.com
4
Derek Curtis kindly provided me with the 9000 custom build. I installed it this morning (Italy time) and have had no crash reports so far, so hopefully the MS Outlook crash issue is resolved...

I'll keep you posted.

Forza SmarterTools, we're on the right track!
Gabriele Maoret - Head of SysAdmins 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)
0
Is anyone facing slow response while creating a new account?

0

I'm using custom release 9000 and stable release 8930.

I don't see this problem in either release.
Gabriele Maoret - Head of SysAdmins 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)
0
I had no problem with 8930. The problem started with 8993. The support team says there is some problem with my backup solution or my installation had some corrupted files or network throttling in my server. They also say that there are no reports about the issue. We had this type problem in older builds. 
0
Kyle Kerst Replied
Employee Post
It sounds like your backup system or antivirus might be locking files preventing the new user being added in a timely manner. This can happen during upgrades specially because the files are being rapidly read/updated causing antivirus programs to take notice. If you haven't already excluded our file types/directories that would be a great first step. These exclusions should be implemented in all antivirus solutions you operate on the server: 


For the backup solution resolution can be a bit trickier. What do you use for backups, and does it utilize Volume Shadowcopy Services (VSS) in Windows?
Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com
0
Uninstalled antivirus. Our backup solution runs at 1000pm alternate days. Procyon not able to record any process accessing the files. 
0
We have 46 domains in the same server. We haven’t observed this issue with other domains. 

Is it possible to share the build 9000 ?
2
Zach Sylvester Replied
Employee Post

Hello,

 

Here is a link to download and install our 9007 version:

https://www.smartertools.com/smartermail/downloads. This version includes the discussed fixes.

 

Kind Regards,

Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com
3
Stefan Mössner Replied
With build 9007 in mobile webmail on my smartphone now the mail folders are all listed with the known structure again when moving mails. Subfolders are now listed on a sublevel again. This fix isn't listed in the release notes or I didn't find it.

Thank you, SmarterTools.
1
James North Replied
Running 9007 for Ubuntu.

This release seems to have fixed Oncehub➜Smartermail/EWS integration :)

There are no more frequent EAS/SSL errors in the system journal. Completely clean logs.

Aside from that, incoming and outbound email seems to be working just dandy on Outlook and Thunderbird.

For some reason, Smartermail was using 7 out of 8GB of RAM an hour after updating, so I restarted the service. After observing it for another hour, memory usage has returned to and remained at reasonable levels.

Seems like a great release!
4
Matt Petty Replied
Employee Post
We have a lot of upgrade processes that kick off after a big upgrade or a move from Windows<->Linux, these will sometimes cause all the users to load and get cached. After a major upgrade or system change though and its running a bit hot, a restart is a probably good idea just to bring it back to a normal running condition.

We're a lot more proactive now with our file caching which keeps certain files permanently cached in memory allowing the disk to not be used in many cases except when we need to write data. You can tune this cache in the troubleshooting area, if you got the memory and wanna keep read's off the disks you can turn this up.

Mail data also got some loading and cache optimizations. Before when someone would access a folder or a delivery to the inbox would occur, we would load ALL of their user's email headers in ALL folders AND sometimes shared folders. Now we will only load the folders that are accessed and even further now, the emails that are accessed. Then anything that is loaded we keep while they are connected with devices anytime they aren't accessed for about 10-15 minutes, we'll start dropping that email data from memory. 

We also dropped our base memory usage of an empty server by atleast 300-400mb during the dotnet and linux changes we've made. Also with big improvements to "allocated memory over time" during a full EWS/MAPI sync.
SmarterMail can technically now run on a 1gb raspberry pi or ARM board, though ARM is just a technical experiment atm.

Hope you all enjoyed my random deep dive into some of the optimizations that will heavily effect memory that we've done over the past year or so. 

PS: Its good to hear the new build is working out.
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com
0
Jay Altemoos Replied
Just to chime in here, we upgraded to version 8993 on 8/30/24 and on 9/5/24 Smartermail became completely unresponsive. Cannot log into the web interface, no email traffic at all and restarting the service did absolutely nothing to resolve any of that. I am in the process now of upgrading to 9008 and being the start of all my client's workday, this is going to make a lovely day I can see it already.
0
Patrick Jeski Replied
Hope it goes well for you Jay.
0
Zach Sylvester Replied
Employee Post
Hey Jay, 

If this ever happens again, can you try accessing SmarterMail using port 17017? You could do this via localhost:17017 on the server. If this works, that means the issue is with IIS, not SmarterMail. 

Thanks, 
Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com
0
Jay Altemoos Replied
Good day Zach,
Thank you for that bit of info, I will keep that in mind for next time if it's needed. The 8993 update worked flawless for 5 days and then this morning is when the support calls started. I updated to 9008 and if anything goes awry here I will open a support ticket. I appreciate the response very much. Thank you.

Reply to Thread