Hi jktieman,

 

Would you please try upgrading to the latest version of the software and let me know if this issue persists? You can download 16.3.6600 from our Downloads page and follow our steps for a Minor Upgrade of SmarterMail. 

We are still getting this issue with a client, and have always had the latest version of everything.
Has anyone else found the issue.   In the past it has been an Outlook issue, but now we seem to be getting it with the Web interface,   again, only one reporting the issue and we can not duplicate it on any of our machines.

Seeing this issue as well in apple devices. Can't reproduce here, but multiple users reporting the issue. Will check error logs tomorrow and report back.

 

Anyone seeing any Errors in the logs?

 

Also, I noticed on my customers environment they have GAL enabled, and used simple CSV import for user creation, so have a lot of users with profile name "N/A", I wonder if the NA breaks SM trying to build the email to field in compose window?

we are also getting this problem with the web interface;
it all started when the user logged in with email-1, then logged off, then logged in with email-2, then logged off etc.
at one moment it started giving this error all the time he logs out, with email-1 and with email-2;

there is also a problem during work: he is working with email-2 and there are incoming mails he can see for email-1, although he is not working with email-1;

to bypass this problem he actually has to

- log out

- await the error message

- close the browser

- log in with the other mail-address

 

Hi Giovanni,

It looks like you're on a version a couple months old. Please upgrade your mail server to the latest minor release. If this error persists, I would recommend submitting a ticket with the Support Department for their review. I'm unfortunately not able to replicate this behavior. 

Anyone find a resolution to this? It's a new issue with the latest version we install on Tue (1-22-2019).

we had this problem August 2018;

the problem was solved with a succcesive version than the one we installed before;
we are now working on Version: 16.3.6733, and it didn't happen again;
we also cleared caches and did a lot of other stuff, but it was probably the update which solved the problem;

as you are reporting here, it seems the issue was reintroduced in this new version (we won't update the actual version as it is working well)

We tried the clearing of Cache with no success. And it's a tough one as I can not recreate the issue though I have a client on the phone that clearly has this issue.

FYI we have this version installed: Build 6956 (Jan 17, 2019)

We've encountered this with several browsers (Safari/Chrome) on different Iphone and Ipads.  I don't think it's a cache issue because on the Iphone 6 we tested on, it had never been to our Smartermail login before.

We're running tests on Iphones/Ipads because a client is having a related issue.  In Safari, there is no send button visible when she creates a new mail or replies. She sent a screen shot and it appears she needs to scroll up to the send button, but is unable to scroll up.

We're trying to duplicate her error, but when we try (even from here account) to make a new mail or reply to an existing mail, we just get a blank page and the "Error Loading Autocomplete List" message.

We recently upgraded and we're on Build 6963 (Jan 24, 2019).

FYI, Tony from support currently has access to my server for other stuff he's working on for me.

I did some further testing. 

On an IPAD  iOS 12.1.3 and (I guess that means Safari 12) and Chrome (71.0.3578.89)

On  MacBook Air (10.13.4) Safari (11.1) it worked as expected.

iOS devices run Safari for iOS by default but you can download a Google Chrome browser on iOS devices also if you want to try other tests.

Hi Steve,

I ran these same tests in both Chrome and Safari - same results on both.

Has anyone come up with a fix to this problem? It suddenly popped up for me after completing the upgrade to SmarterMail Enterprise Version - 100.0.7118

I'm currently on SmarterMail Professional Build 7090.  This issue seemed to have resolved itself in on of the many upgrades I've had applied over the last couple months.