Looks like a few people have installed 9623...

Jay asked a good question in another thread:

Do you have to install any previous versions first before updating to 9623?

Nope :)

I can recommend this build. No issues so far.

Thank you very much, Smartermail Team, for implementing the feature request for configurable booking windows. :-)

Using EAS?  Beware Updating...

I try to stay a few updates behind to hedge against bugs.  Unfortunately it hasn't worked out for me this time.

Updated from 9526 to 9575 on Saturday although SM has told me this bug is present in the most recent builds too.

Several of users with iPhones using EAS to sync errored out and stopped syncing emails.  The user looks in the mailbox on their phone and there are no emails in it at all---it is empty.

Per SM the problem is one email or multiple emails in the user's mailbox using an XML breaking character:
https://en.wikipedia.org/wiki/Bell_character

SM's first suggestion was to stop using the character.  This is unrealistic as it's impossible to control what characters someone uses in an email they send to you.

The next idea was to filter out emails using this character into a different subfolder.  In testing this didn't work. It just took all emails in the Inbox and moved them to the filter folder.

Finally they suggested use IMAP instead of EAS.  That means changing everyone's phone from EAS to IMAP as work around.  Seems crazy to me.  Particularly as EAS is a SM feature that I pay for.

I've asked SM multiple times for an ETA on a fix and they can't give me one.  I can live with 'We're working on it and we think we'll have a fix in a few days.'  I can't live with an ETA black hole as that could be forever.

I'm sure they'll get around to fixing it eventually but I'm considering downgrading from 9575 back to 9526 tonight.

Looking @ the threads I know others have downgraded in the past due to other issues.  

Hopefully this post helps someone else avoid my current pain.

Thanks in advance for any help.

Upgrade to the latest. Your builds are old and insecure.

The goal is to get on the latest build.  

Any software update incurs risk.  This invaluable series of threads with each software release is proof of that fact.  The mark is how fast bugs that effect base functionality are fixed---not that they are introduced in the first place--which is why I would love some ETA to fix the problem.

I've been dinged a few times by SM updates over the years---particularly on the API side.  If other posts in this forum are accurate other people have too.  That's just the nature of software.

In the absence of other information or need at this point I need to sit tight @ 9575 until there's a fix to the EAS problem.  Upgrading to the latest build without a resolution to my current issue could expose me to other bugs and one problem is better than two.

Unfortunately, my downgrading per Derek Cutis's note in https://portal.smartertools.com/community/a97900/smartermail-build-9610-april-24-2026.aspx didn't work.  Maybe it was the build I was trying to downgrade to.

Hello Mike,

I am sorry to hear about the issues you have encountered. I have reviewed the task, and it has been assigned to a developer. Based on my experience, if all goes well during QC, the resolution should be included in the next release within the next couple of weeks.

Kind regards,

Thanks Zach!

We upgraded to Build 9623 during our Monthly Scheduled Maintenance yesterday morning and so far the only problem we've been experiencing is with the Spam Score not being passed to Smartermail from the Incoming Gateways (see https://portal.smartertools.com/community/a97936/spam-score-not-passed-from-gateway-build-9623.aspx). Using Incoming Gateways I understand are a fringe/edge case and this issue isn't going to affect most SmarterMail installations, but this is a pretty big issue for those that do as no Spam Filtering is occurring at all as of this Build.

Any other updates for Build 9623, especially with Linux?

Thanks.

SM sent me a custom build for the EAS problem I was experiencing.  It appears to have resolved the problem.  Thanks to SM to helping me out.