I noticed some sluggishness (the attachment was 7MB), but never any timeouts as I see in your logs Carolina.

Can we try this again on your end, to see if the problem remains?

If my steps are similar to the way you use the Help Desk then you can follow them exactly. Otherwise follow the same steps as above - except you can skip 4 and in step 5 you don't necessarily have to include a large attachment.

When you clear and re-enter your mail settings do you receive the first "Test email from your Spiceworks Desktop" from the helpdesk that tells you the settings were configured correctly? Have you tried the suggestion of enable or disable TLS?

It seems like you're having connectivity issues between your SW server and the mail server. Can you describe your mail server environment in more detail: software, version, network layout? Do you experience these issues when the mail server is very busy and not responding?

Your mail server is the issue, not your small network. We have Spiceworks running on networks many times that size. Your mail server is not reliable enough to guarantee delivery of helpdesk email. It either goes down completely ("An established connection was aborted by the software in your host machine" error) or becomes so busy that it can not handle the load of delivering new messages, which is the timeout. If this is something you need, then you might want to look at setting up your own mail server or talk to the hosting company about how you can get your mail account to be more reliable.

5.1 adds multithreading to the application server. Now you shouldn't have the application go busy while it is checking email. But again this goes back to the mail server. If your application was going busy often, it means that the mail server is very slow in processing the requests. I'd suggest you set the mail check interval lower (it is 5 minutes by default).

Another potential issue could be your ISP. If you are seeing this problem across different mail hosts then it might be your internet connection that is bogging down. It's hard to tell from a handful of comments. Do you have general internet connectivity issues especially when you see these errors occur? Try connecting to the mail server from a mail client like Outlook when the Spiceworks errors occur. Can you connect to the mail server? Can you send/receive emails? If this boils down to Spiceworks being the only machine with issues, then we need to troubleshoot that connection. Some users report anti-virus/malware software interfering with Spiceworks. If this seems to be unique to your Spiceworks machine then let's get our support people to take a closer look and see if they can help you.

Just checking in again - hopefully you're able to get things stable again in 5.0.

I setup a test environment with your mail server and did some Help Desk testing (sending/receiving emails to the Help Desk, assigning, opening, closing, unassigning, commenting, etc. on tickets). I did not experience any of the problems you have seen so far. I did my testing with TLS enabled.

Let me know when you're back on 5.0. Once we've worked through that we can try to bring up a second test environment on your network and run 5.1 there.