Thanks for the confirmations. I do see the connection error you are referencing:
No connection could be made because the target machine actively refused it 10.1.0.203:8032
This one is benigh. It's a temporary error logged during the startup process. The scheduling service is trying to talk to the GUI runner service, but the GUI runner service was JUST started and wasn't quite ready to receive. If this error appeared more than once I'd be worried. But it's just a background ping which often happens during startup. Thus I'm discounting it as being any part of the email problem.
Further proof that it's not a problem is that the test list did execute. If the GUI runner was not working, or communication to it was really broken, then no tests would have executed at all.
The latest log still shows no attempt was made to send an email. I'd like you to verify one last thing. Make sure the project is configured to connect to the scheduling server as "Run Remotely" as shown in the attached screen shot.
If this doesn't solve the email problem then it's time I look at this problem on your computer via an online meeting.