I recently experienced the same thing on build 7090. Like your install the web interface seemed to be fine and all the mailboxes were intact.

I did not perform a rollback but did manage to figure out what was configured incorrectly.

Check the bindings, I discovered that during the upgrade/reinstall that bindings were enabled from a previous install, and once I removed the inappropriate bindings SMTP etc started working immediately.

Hi Daniel,

I'm sorry to hear you had trouble with your IMAP and SMTP connections on Build 7117. I've done some testing and haven't been able to replicate this issue on my test installation, and we haven't heard of any similar reports today. I verified that my IMAP connection in Outlook can send and receive email and that an Email Retrieval via IMAP works as expected. Do you happen to have a VM or testing environment that can be used to replicate the upgrade issue in a non-production environment? If you do, there are a few things I'd like you to check:

If all else fails, go ahead and start a ticket with us in the Customer Service Department and provide the IMAP credentials of a test account. If we can't get it to work either, and if your SmarterMail license has active Maintenance and Support, we can get you in touch with the Support Department for their review. 

I hope this helps! 

Hello Andrea,

Since I do not have any test environment available and also because being a bit short of time these days, I have not yet performed any testing and deeper analysis of the issue. I just checked the bindings settings as advised by another community user, but those were correct so issue had some other cause.

But today, after your latest post, I have downloaded and installed SmarterMail Build 7118 and after upgrade to this build, I can now confirm the issue is resolved and all seems to work now correctly.

Thank you very much for help and support, such fast replying to my thread was appreciated and beyond my expectation. :-) So thanks again.

Kind regards,

Daniel Mikel.

Thank you so much for the update, Daniel! I'm happy to hear that Build 7118 resolved the issue you experienced on your last upgrade.