Build 8594 (Jul 13, 2023)
Question asked by kevind - 7/14/2023 at 8:39 AM
As usual, please share any successes, issues, or other findings with this new build...

Build 8594 (Jul 13, 2023)

  • Changed: 'Enable Sender Verification' change to 'Enable Sender Verification Shield'.
  • Changed: Updated the new "Failed to load" user handling to match the changes to a domain's "Failed to load" handling.
  • Fixed: An instance where a customer's deliveries from Outlook (MAPI) resulted in blank recipients on the outbound messages.
  • Fixed: Calendar/Task attachments don't sync either way in WebDAV.
  • Fixed: Content filters can fail to read the file extensions when an attachment is sent using 7 bit encoding.
  • Fixed: Firefox can fail to send or save a draft when it loads too slow.
  • Fixed: High memory usage in MAPI calendars.
  • Fixed: On a shared note, and embedded image overruns the body field for the recipient of the share.
  • Fixed: Retry intervals of 24 hours or longer are saved to the JSON file incorrectly, causing unexpected behavior with the spool's Retry Intervals.
  • Fixed: S/MIME encrypted messages fail to prompt for credential use and don't display contents.
  • Fixed: Shared/Personal Calendar attachments sometimes disappear in Outlook (MAPI).
  • Fixed: Some appointments can't be deleted from webmail.
  • Fixed: Some folders are not visible in certain IMAP clients.
  • Fixed: Specific EMLs display formatting issues in FairEmail due to DKIM content in BODY during FETCH command.
  • Fixed: SRS is not used when 'keep original recipients' forward setting is enabled, and the original sender is a local user on the domain.
  • Fixed: Syncing a shared calendar doesn't load anything via Caldav.
  • Fixed: The date/time of some calendar components can be miscalculated based on the user's time zone and desktop date/time settings, and these components also show Tehran times with DST still being applied.
  • Fixed: WebDAV still forcing HTTPS when HTTPS redirect is not enabled for the domain.
  • Fixed: When an invitation is sent from Outlook (MAPI) as a winmail.dat file (from some Exchange servers), SmarterMail isn't correctly displaying the appointment's date and time.
  • Fixed: When trying to create an appointment in an EWS client using the MimeContent field, the created appointment is empty.
  • Efficiency: Improved IMAP keyword handling.
  • Efficiency: User connection counts optimized.
  • Security: Fixed one or more security issues were fixed. It is recommended that all users update to this release.

9 Replies

Reply to Thread
Updated. No (new) issues so far...
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)
echoDreamz Replied
Nothing reported thus far (aside from the time issue at startup), but no problems being reported by end-users and the few issues we did have before this build have been reported as fixed.
Webio Replied
It looks like trusted senders are still being moved to junk folder (because of spam scoring) even if they are trusted (reported here also: https://portal.smartertools.com/community/a95401/sm-8580-upgrade-any-issues-so-far.aspx)
Douglas Brantley Replied
The following is from a client...

After the installation of SM Build 8594 (July 13, 2023), I have begun experiencing crashes on my Android phone when connecting to the IMAP server I've been using on my Gmail aggregator app without any prior problems.

I've downgraded the Gmail version--not the problem.

I've deleted the account in Gmail and reapplied the configuration settings--not the problem.

I've rebooted the phone--not the problem.

I installed a security update this morning--no help.

I then turned to the Outlook app to establish a connection. No luck. But the resulting message said to send the following to the mail administrator:
Correlation Id: 80a0ffb5-ac3e-4b25-875a-4c968093c277
Timestamp: 2023-07-17T15:58:29.000Z
DPTI: 9eb44a2c2475d44e


The mobile apps on my iPad have not been affected by this SM update.

This problem seems to be device specific. I know my phone is making a connection despite crashing on each connection because I can see the following time stamp right after the Gmail app crashes by looking at the SMTP Connectivity activity in the SM Web browser:

Authenticated IPs (This IP is associated with my Spectrum account) - United States
7/17/23 9:51 AM (IMAP)
7/17/23 9:29 AM (Webmail)
7/16/23 9:14 PM (SMTP)
7/16/23 9:02 PM (POP) successful connection yesterday)

Based on this information, I can tell a connection is being made.

However, under the Synchronized Devices heading, none have connected to SM. (I'll experiment with delaying the sync setting, but I don't think that should affect the initial account sync.

J. LaDow Replied
[[ moved in from another thread that was not matching the version of SM we are running, but has similar issues as reported here: https://portal.smartertools.com/community/a95495/build-8601-jul-20-2023.aspx#140817 ]]

We've seen this issue where the UI stops responding or doesn't update as expected as well -- usually when dealing with large numbers of items in a user's mailbox - but there are other situations, such as running a content filter - the toast notification stays hung in the lower left corner even though the task finished in 3-5 seconds.  This also happens when emptying folders sometimes - a hard-refresh is required.  In the case of the content filter run, a hard refresh is required (even though the task finished) in order to manually run it again on another folder in the same session.

Please note - this is not limited to Firefox, but it is our "daily driver" -- we've been able to replicate in Chrome and Vivaldi as well.  Developer console doesn't reveal any errors but there are multiple times when the response from the server to client (we believe SignalR) is an empty object after one of these operations.

Will be willing to provide any logs or documentation as needed if specified.  We were waiting on this next release to update and see if the issues persisted before raising an issue.

MailEnable survivor / convert --
Matt Petty Replied
Employee Post
[[Moved this over too since it's relevant]]

This might be a symptom of SignalR not running correctly. We have a "Self Test" that runs to verify it's working correctly. If you open up your developer console and look for "SignalR Self Check" you can see how it's doing. 
If you notice it failing, try restarting IIS or doing an IIS reset.

You should see "SignalR is working! Check PASSED." Somewhere in your console. If this isn't working it will cause mail actions to hang or if you change something in another browser and your tabs don't update. Or if you're on the spool overview page which refreshes stats every couple seconds. The entire Online Meetings area relies on it. It's a pretty important component for a good web experience.
Matt Petty
Software Developer
SmarterTools Inc.
(877) 357-6278
J. LaDow Replied
Thank you for that -- we are going to revisit the issue and do some better "controlled" testing to confirm.  We also note that there were updates to SM in versions newer than ours that were noted to address some SignalR issues - and had waited to raise this fully until we were up to date.  Currently waiting the re-release of the next update and we will test this properly and return results.

Thank you for your continued attention to these issues.  The participation of developers and team members here is extremely reassuring as a customer and operator.
MailEnable survivor / convert --
Jim Morgenthaler Replied
Is anyone else running into an issue with mail forwarding on this build?  My webhost, HostGator, is using SmarterMail and is currently on Build 8594.  Until very recently (within the past month or two) mail forwarding is no longer working.  HostGator tech support says that they are aware of the problem and it is something that SmarterTools/SmarterMail is working on but that they (HostGator) can't do anything to resolve the problem until SmarterMail comes out with a fix.  Mail forwarding seems like such a basic email feature that it's hard to believe that it hasn't been fixed after all this time.  So is anyone else experiencing problems with mail forwarding not working?  And if so, any idea why it hasn't been fixed yet?

Reply to Thread