All
I forget now how, but the problem from August 2018 went away, but has now returned, and there has been no change in the behaviour and reported messages.
Avast, if I have understood the information provided correctly, still refuses to let Outlook send messages because it, Avast, cannot scan the connection. Why will it not provide a better message? Why will it not provide a tool to overcome the problem and allow the user to increase the concurrent connections limit, even if only a temporary basis? Perhaps as well it should show a list of all fifty, or however many, indicating which applications are using the connections? If this were provided, then surely we would be able to close down the programmes we are not using and free up some connections.
However, if it really were Outlook that were hogging all fifty connections, then I would anticipate that closing Outlook would free those connections. Outlook restarting would surely, perhaps I hope too much of MS software, immediately grab them all again, and this problem would go away, but it does not. Avast continues to claim that the number of concurrent connections has been exceeded, and continues to refuse to allow Outlook (and I understand form other comments other client email applications would be similarly affected) to send email.
I mentioned in the earlier post that even a reboot of the machine did not clear the problem, so the problem is not of the operating system’s nor the running applications’ making. And yet, somehow the problem goes away for a time.
Will Avast fix this? It is clearly an avast problem as it is Avast that is standing in the way.
