Overview
You have lost the Email2Fax functionality after performing an upgrade of the FaxMaker server Operating System, and now users cannot send faxes from their email client.
The messages may fail with the following error (where 10.1.1.19 will vary according to your local Exchange server):
"Server at [10.1.1.19] (10.1.1.19) returned '400 4.4.7 Message delayed'
2/26/2022 7:42:52 AM - Server at [10.1.1.19] (10.1.1.19) returned '451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect -> SocketConnectionRefused: Socket error code 10061'"
Faxing from the web client, though, works as expected.
Solution
The operating system upgrade process may have affected IIS settings that have an impact on the Email2Fax functionality.
Take the following steps to fix the situation:
- Ensure the start type for the SMTP service is set to Automatic (in the Windows Services app).
- Follow the steps from the Verifying Settings for the IIS SMTP Instance on the FaxMaker Server article.
- Follow the steps from the Faxes remain stuck in the drop folder in IIS article (to allow emails to be processed by FaxMaker)
For additional troubleshooting steps, check the Cannot Send Outbound Faxes Via Email Client article.