5
SM 8622 released. Share your thoughts...
Question asked by Brian Bjerring-Jensen - 8/10/2023 at 11:12 PM
Answered

Build 8622 (Aug 10, 2023)

                        
  • Added: A system-wide option for 'Block Authentication by Country'.                                    
  • Added: Aged password grid on  Password Requirements pages for both System and Domain settings.                                    
  • Added: Debug logging implemented for Indexing service to detect what is causing CPU / Memory to spike and SmarterMail to go unresponsive.                                    
  • Added: Password requirement support added for domain administrators.                                    
  • Changed: "Keep original recipients when forwarded" renamed to "Keep original sender and recipients when forwarded" as it more closely describes  how that functionality works.             
  • Changed: Automated Forwarding's "Keep original recipient" setting enabled by default.           
  • Changed: DMARC skipped messages now show why DMARC was skipped in the email header and in logs.                                    
  • Changed: Reduced the number of retries on standard DNS (A, MX, etc.) lookups.                  
  • Changed: When a user marks/unmarks a Trusted Sender, entries will be added/removed based on the DMARC results of that email.                                    
  • Changed: When an email's Trusted Sender status cannot be verified due to the DMARC results, the email header now shows the email as being from a Trusted Sender and shows the reason the spam weight was still applied.                                    
  • Fixed: A customer issue where the inbox in Outlook (MAPI) will not sync.                                    
  • Fixed: A damaged account can prevent other accounts from accessing the Inbox and causes red console errors in those accounts.                                    
  • Fixed: After joining an online meeting, attendees can't change their audio input device.
  • Fixed: An issue validating an SPF record: "v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all".
  • Fixed: An issue where language choice was modifying root folders for File Storage.
  • Fixed: Attendees can't upload files in online meeting chat.
  • Fixed: Category encoding in eM Client (IMAP).                                    
  • Fixed: Changing the flag state for a message does not sync to IMAP clients.
  • Fixed: Client-side Outlook rules (MAPI) must be run manually -- they do not run automatically.
  • Fixed: Deleting/renaming a category in webmail updates affected messages but doesn't notify IMAP clients.
  • Fixed: Delivery logs have "Index was outside the bounds of the array" exception.
  • Fixed: Domains in a 'Failed to Load' state require a detach/attach versus reload once their JSON files have been repaired.
  • Fixed: Embedded signature images cause unexpected behavior with the attachment count and broken embedded images in webmail.                                    
  • Fixed: Embedded signature images cause unexpected behavior with the attachment count and broken embedded images in webmail.
  • Fixed: EWS time zones in all-day appointments can be improperly defined in iCal data.
  • Fixed: For some emails, the attachment icon doesn't appear in MAPI, EAS, and EWS clients.
  • Fixed: IMAP category encoding is broken in eM Client.                           
  • Fixed: In Chrome, a user's first login to webmail cannot proceed until browser notifications are allowed or blocked.                           
  • Fixed: In Thunderbird (IMAP), some folders are greyed out and cannot be interacted with.           
  • Fixed: Issues with folder name encoding in IMAP.                           
  • Fixed: Outlook (MAPI) shows attachment icons on the majority of emails whereas webmail does not.                           
  • Fixed: Rescheduled "Collective" type meetings in Calendly fail to update secondary user's calendars via updated invite email.                           
  • Fixed: SMTP logs show DMARC failed, but Delivery log and email header show [_DMARC: 0,none].                           
  • Fixed: Snoozing Notifications in webmail doesn't work as expected.                           
  • Fixed: Some users fail to display piechart graphics at the top of Reports>Disk Usage though this is displayed properly elsewhere.                           
  • Fixed: Some users fail to display piechart graphics at the top of Reports>Disk Usage though this is displayed properly elsewhere.                           
  • Fixed: System clock warning erroneously appears.                           
  • Fixed: The DMARC check that is used for Trusted Sender verification is not being handled correctly when the spam score is passed from a gateway.                           
  • Fixed: The DMARC check that is used for Trusted Sender verification is not being handled correctly when the spam score is passed from a gateway.                           
  • Fixed: There are two different "Potentially dangerous scripts" messages that can appear on one email.
  • Fixed: Unpin/pin user doesn't work consistently in online meetings.
  • Fixed: Upgrade from 8587 to 8594 creates second copy of folder and renders mail data missing.
  • Fixed: User Propagate modal shows bad encoding for an ampersand.
  • Fixed: Users with missing settings.json files are flagged as "Failed to Load".
  • Fixed: WebDAV occasionally sends meeting messages incorrectly.
  • Fixed: When a user attempts to share a folder with their own username, either a bad validation error shows or the share is completed.
  • Fixed: When a user attempts to share a folder with their own username, we either show a bad validation error or allow the share to be completed.
  • Fixed: When an email is popped out, the Sender Verification Shield gets cut off if the display name or email address is short.                                   
  • Fixed: When navigating to a specific URL, SmarterMail is not redirecting to the login page.

16 Replies

Reply to Thread
4
The first comment I have to make is that they should re-read and better review the Changelog before publishing it...

  • There are many double lines (really double, written 2 identical times...)
  • There are some "FIX" spelled 2 or more times in different ways, but they seem to mean exactly the same thing.
Eg:





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
First BIG issue with 8622: I cannot change general password policy because of an error every time I click SAVE button.

This happens under SETTINGS -> Password Requrement -> Options:


This also prevents you from creating different settings for each domain, because they are blocked by the general settings:



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
kevind Replied
Wow, 39 fixes! But as Gabriele pointed out, several duplicates. Need to proofread the release notes.
1
Tan Replied
I like the blocked by country and logging for index spike but i will wait out for a while before rolling to production 
1
Derek Curtis Replied
Employee Post
Sorry about the duplicates. They were taken care of on Friday. 

We'll also be releasing a fix for the password requirements issue this morning. 
Derek Curtis COO SmarterTools Inc. www.smartertools.com
1
Tim Uzzanti Replied
Employee Post
We removed Thursday's release and will release again this week.  There could be a bug related to special characters in folders that can cause missing emails.  Only one customer has brought this to our attention but not knowing what or how it happened, we are being extremely proactive.  The customer who reported the issue has a LARGE number of users but only affected a few users.  More info to come. 
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
0
Thomas Lange Replied
@Tim: Our employees are sometimes using German-Umlaut/special characters in folder names to organize their emails.

until now no one of our employees reported "emials missing/being lost" - what should we do to stay save?
Do you suggest downgrading/going back to build 8601 - or should we stay on Build 8622?
Or do you kind of fix or debuginfo/data we can add for analyzing such an error being reported by your customer?

2
Tim Uzzanti Replied
Employee Post
I would recommend rolling back for now just to be safe until we have more info.  
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
1
Tim Uzzanti Replied
Employee Post
We will release once we determine if this special character issue is an issue or not.  We have the other fix ready to go and if you need it, contact support and we can give you a custom build. 
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
0
Rudolf Lindinger Replied
I have exactly the same issue with Foldernames containing special characters (German Umlaut). One custoimer has ß in the foldernames. He is connecting via IMAP and the folders are empty. In webmail there is no problem - all folders and mails are visible. I renamed the folders in webmail (ß -> ss) and then the syncing via IMAP worked.
The problem is, that i cannot reproduce this issue. i tried to make new folders with ß,ä,ü or other special chars in a test mailbox. But there all folders are working. So i would like to say, that we are having the same issue as Thomas Lange.
i am running 8601 - so i think a downgrade from 8622 to 8601 will not correct the issue (@Tim and @Thomas).
0
Is it old remains from a previous release that causes this?

We have the same issue med / and ÆØÅ in the folders
0
Thomas Lange Replied
@Rudolf: nobody of our employees reported an issue with German Umlaut/special characters in foldernames yet But if there is an issue inside build 8622 I supose we would be affected :-(
I read Tim´s post/answer here and I asked if we could be affected and probably should better go back to 8601.

If I understand you right are running 8601 - and you did not install 8622? And one of your customers has issues with the German Umlauts in the foldernames. only using IMAP or even using other protocols?
Did the customer already tried different protocols and/or other email-clients?

In case you or anyone else discovers steps for reproducing I can try to reproduce at our system.
Or name the progrrams/versions and I can see what I can reproduce at our SmarterMail system.
4
Tim Uzzanti Replied
Employee Post Marked As Answer
We figured out the email folder issue which was the primary reason we had pulled the 8622 build. The issue is VERY uncommon but I'm still glad we pulled the build. 

We included some code in 8622 to fix an IMAP issue with special characters.  That code did its job but it didn't take into account users who had another folder called INBOX.  We're not sure how users were able to create these but our fix didn't take that into account because it shouldn't have been allowed.  We had a couple customers upgrade to 8622 that had a few users with this scenario.  

This issue was clearly concerning enough that we wanted to be on the safer side and pull the build.  The settings issue we had was another reason and the combination just made pulling it, the right choice.

One of these issues was very obscure but the settings issue should never have slipped through QC.  The amount of tests and efforts we make before release are why we have so many good releases, this settings issue needs us to re-evaluate interface steps before release because that super bothers me!

Wanted to give an update, a new build will be ready on Thursday.  
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
0
Rudolf Lindinger Replied
@Thomas: Sorry, i misunterstood this. We use 8601 and have never updated to 8622. Our customer uses imap only. He uses Apple Iphone Mail on two phones and emClient on PC. The problem was on all clients. I tried to reproduce this on one of my own mailboxes but could not reproduce this. Maybe this only comes on "old" mailboxes.
0
Ben Replied
Oh could this be why I had customers with ampersands (&) in their folders losing mail?

The original folder is still there, but then a second one where the ampersand is changed to &- is then created (and used) so to the client looks empty. 

I'm only on 8601 though. 
0
Tim Uzzanti Replied
Employee Post
Not sure what you are seeing is related but we have resolved some issues in that area in the upcoming release on Thursday. If you still see something odd and can reproduce after upgrading, please open a ticket so we can look into it for you.  
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com

Reply to Thread