There is a lot of clicking in the UX and I miss some things from Mailenable.

IN Mailenable you could track all emails to one specific user and then click on an email to trace its logs in SMTP and see what has happened to it. It made it very easy to see if it was marked as spam or something else. The first one is just the overall layout of the admin console.

When you track a message from a specific user or to a specific user then its super simple and instead of searching through logs the console does it for you and you can backtrace through SMTP logs. I miss that a lot when a client calls and tells me that he is expecting an email but havent received it yet.

Sorry Brian, but the second part of yours seems to be more of a "feature request" than an impression on the difference between "old smartermail" and "new smartermail".

This is not the purpose of this post, maybe it's better if you move your request to your post here:

https://portal.smartertools.com/community/a95403/what-would-you-like-to-see-in-upcoming-sm-releases.aspx 

P.S.: I was also a Mailenable user before switching to SmarterMail (which in my opinion is much superior...), and I too miss the MailTracking functionality a lot...

Sorry Gabriele. I saw that afterwards :)

No problem! ;)

On my end I can say that unread messages are not so clearly visible when comparing  them to already read. 

I'm wondering how icons on the left of message are generated. Does only domain.com/favicion.ico/png/etc is checked or maybe HTML  header is being also parsed for favicon image or maybe other way of getting domain image file.

I would also like to have possibility whitelist and show images in webmail not only from sender email address but also from sender domain name (this is how it is being done in Thunderbird: show images, show images from sender, show images from sender domain name).

Hi. I upgraded from 8451 to 8545 a week ago. It's been seven days without any serious issue, but I started to have one problem that I never had before.

This server has 4500 users. It's a governmental instituition, so because of some internal rules I cannot use a relay to send e-mails out (I cannot filter outgoing e-mails with a antispam server). So I use throttling to prevent cases where infected accoutns could send hundreds or thousands of e-mails.

This server has been running since 2018 and I've been using throttling since then. On this recent update several accounts started to get throttled for outgoing messages, but I did not change any rule and the number of outgoing messages has not changed.

Is anyone else having a similar problem? When I check the logs or the archive to check how many messages were sent, it shows that it never actually met the "Outbound Messages per Hour" limit. Could this be a bug or has the throttling rules been changed?

Hello to all!!! 

I've edited my comment at the top of this post by adding a fourth point to the list of things that are, in my opinion, worse in the new version of SmarterMail 8552: basically I'm seeing a big increase in RAM consumption compared to the old 8451 version.

I want to point out that no changes have been made regarding users or the system, therefore the increased use of resources (both CPU and RAM) is due only to the new version of SmarterMail.

Hi Rafael! 

At the moment I have never noticed that I have this kind of problem that you are reporting...

But now that you've pointed it out, I'll be careful too and if I notice anything strange about it I'll let you know.

I agree with Webio, it is very difficult to tell the difference between read and unread email in the current version. This week I was upgraded from something like ver 15.7.6855 (Oct 8, 2018) to build 8545 (May 25, 2023). The difference in color between read and unread email is literally really dark grey vs somewhat dark grey. It is very frustrating to do the most basic feature in an email client: find and read my unread email.

I know this is moving into the territory of a feature request, but couldn't we have some selectable options, like a brighter color for unread mail, and a washed-out light grey for read mail? 

Unfortunately, my hosting company only updates SmarterMail about once every 5 years, so even if you fix this issue in a new release, I won't see it for many years. I guess it is time to move to a different hosting company and a different email platform.

We've received over 2 dozen tickets about the read/unread being difficult to distinguish, mainly with the dark theme. Hopefully ST can do something for this.

Hi,

We have upgrade to the new SM eight days ago and since the upgrade we see a high increase of Disk usage, I don't know what SM is doing but the webmail interface is very, very slow comparing to the old version.

Can anyone explain what SM is doing reading the .grp files and when it is going to slow down ?

We have almost 11TB of ocupied space with SM files.

Thanks.

@Manuel

"

Everyone will see a jump a bit after their first update to these versions as we have a background process that will revisit every GRP file for each user. We do this because there is some additional information the CFG now stores, such as "HasCalendarItem" for example. This process happens in the background after a user is loaded for the first time, it happens in the background without interrupting the user but it does put load on the server. This only occurs once per user after the update to one of our recent versions, so after a couple days you should no longer see this.

This background process uses a maximum of 5 threads (on a 8 thread machine that's half your CPU). This process will also cause us to use more RAM than normal because we cache items that are recently loaded, and if were loading everything a user has we're technically caching quite a bit.

This process I'd expect large servers to finish in a day or 2 with some users being trickle updated throughout the week as they log in for the first time. User's with mobile devices will hit the server first and be visited first. I know there are other CPU/Mem concerns and we are looking a profiles as we get them. Hopefully this helps explain what the initial jump could be after upgrading in some scenarios. If you have been running for week+ on the current update it very likely that this ISNT what your seeing, but if you recently updated likely IS what you are seeing.

EDIT: You can adjust mailbox_subversion_upgrader_thread_count in your server's settings.json if you wish to speed up or slow down this process, though it still requires your users to be touched (they login, they receive an email, etc) before they upgrade.

(my response from https://portal.smartertools.com/community/a95316/how-many-have-upgraded.aspx)

Is distinguishing between the read and un-read, still an issue?

Small server, but wasn't happy to find archiving turned off.  Took several days before I found that it had been turned off for the entire server.

@Matt Perry, if we reduce the number of threads, aside from slowing down the process, how specifically will it impact end users?  Will they be lacking features or anything else until the one-time conversion process is performed on their mailbox?

Our SM server is dedicated to Smartermail only and has no other function.  It has 26 Xeon CPU cores and 96 GB of RAM.  Under normal daily operation it sustains 50% CPU(*) and 65-70 GB RAM, so we're deeply concerned how this post-upgrade process will impact us operationally.

(*) Down to 50% from 65-70% sustained, after turning off all RBLs and virus scans, since there's a filtering server in front of it.

 

@Jay Dubb - We definitely don't want you running into issues there and I reached out to your team directly via a support ticket to see about helping you guys profile an upgrade to our latest release to identify and resolve any issues you might encounter when you do get the upgrade started. Unfortunately it sounds like hardware won't allow for this currently. 

So, I'd like to work with you guys to see if we can find anything (resolvable) we can do to reduce your current memory usage and hopefully free up some space for upgrade testing? If you're open to letting me look things over please let me know and I'd be happy to see if we can help smooth things out and make room for more testing! Thanks Jay!