Problem with 9540 (solved)

Problem reported by Oliver - 2/13/2026 at 5:22 PM

Resolved

Leider ist Version 9540 für uns nicht verwendbar.

Das folgende Problem:

Ein IMAP- oder MAPI-Konto, das auf zwei Computern verwendet wird, wird nicht aktualisiert.

Ein Beispiel:

Auf PC1 wird eine gelesene E-Mail als ungelesen markiert. Im Webmail wird sie korrekt als ungelesen angezeigt. Auf PC2 bleibt sie jedoch als gelesen markiert und ändert ihren Status nicht.

Ein weiteres Beispiel:

Auf einem Mobiltelefon mit ActiveSync wird eine gelesene E-Mail als ungelesen markiert. Im Webmail wird dies korrekt korrigiert. Auf PC1 und PC2 ist diese E-Mail jedoch weiterhin als gelesen markiert.

---------------------

Aktualisieren:

Das Problem wurde durch Löschen und anschließendes Neuerstellen des Outlook-Profils auf den betroffenen Computern behoben.

6 Replies

Reply to Thread

Dave Replied

2/13/2026 at 8:13 PM

Working here for me between 2 IMAP and the web.

Have not checked AS yet

George Replied

2/14/2026 at 12:29 AM

Build 9540 is working fine for us so far. We use MAPI/EWS and IMAP (50/50). I haven't checked EAS yet. Our server runs on Linux.

Update:
I tested EAS on MS Outlook for Android. So far, it looks good. No problems. We'll see when more users connect. Apple MAC OS and IOS have not been tested yet.

digital.iway Replied

2/15/2026 at 12:27 AM

Build 9540 has no issues for us (installed 2/15/2026). Windows 2019 (VM) Running IMAP/EAS/DECLUDE. Tested outlook read/unread/delete/send with no issues and we saw good sync/performance between EAS iphone, webmail and outlook (all brief testing just after install).

Oliver Replied

2/15/2026 at 5:24 AM

Marked As Resolution

Thanks to everyone for their feedback.

The problem was solved by deleting and recreating the Outlook profile on the affected computers.

Mark Johnson Replied

2/15/2026 at 5:37 PM

regarding the command-line action changes,

can some one explain a bit more about this please?

how can we confirm if we use any command-line actions that will be impacted by the upgrade?

One major change in this release is how command-line actions are handled. Previously, commands were added directly within the SmarterMail interface. We have changed this behavior and now system administrators will reference a Script File Name for command-line actions. These scripts will be stored in an Assets folder within the Service directory of SmarterMail. That means that when an administrator upgrades SmarterMail to this release, SmarterMail will convert any existing command-line commands into files and place those in the Assets folder. The files will be named based off their location and purpose. For example, Command-Line Antivirus would be named "antivirus", a system event with a command-line action will be named the same as the display name of the event itself, etc.

This change affects a few different areas in SmarterMail, including:

- System Event Actions
- Volume Mounts
- Spool
- Command-Line Antivirus
- Automatic SSL Certificates
- ACME Certificates in SmarterMail HA

Derek Curtis Replied

2/16/2026 at 6:39 AM

Employee Post

@Mark -- as the email and Community post noted, the areas listed are the only areas command-line is available for customized handling of particular items. The easiest to check is your Volume Mounts: These don't require commands, but they can be used. Same with Command-Line Antivirus: if it's enabled, you can check it by going to the Antivirus page and seeing if anything is enabled on the Command-Line Antivirus card. System Events may be a bit more difficult to check, especially if you have several system Events set up as you'll need to check the Actions for each. That said, on newer versions those are all in a grid, so it's simpler to check now than it was before.

Spool, SSL items -- unless you know for sure you're using commands in those areas, chances are you're not.

Derek Curtis CCO SmarterTools Inc. www.smartertools.com

Back to Community Threads

Please leave this box unchecked

Reply to Thread

Enter the verification text