Application Event Viewer Error:
No connection could be made because the target machine actively refused it 127.0.0.1:25
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
This article applies to Cloud Plus customers.
1) Changed web.config files for asischeduler, and (NET) folder as follows:
a. Replaced loopback ip address from 127.0.0.1 to hostname used on this specific Cloud Plus environment. Note, each Cloud Plus customer should have its own smart host name which is typically, your company acronym name used in the ssl certs <xyz>.imiscloud.com. Or the instance name. If iMIS instance name is "USA" as an example, then use usa.imiscloud.com.
<smtp deliveryMethod="Network" from="firstname.lastname@example.org">
<network host="usa.imiscloud.com" port="25" defaultCredentials="true" />
b. Performed IIS Reset.
2) Opened up IIS Version 6.0 > all programs > Administrative tools > Internet Information Services 6.0 Manager:
a. Expanded Server name > Right click on [SMTP Virtual Server #1] > Properties >
b. Navigated to Access Tab > Clicked on Authentication > Put check mark on "Integrated Windows Authentication.
c. Navigated to Access Tab > Clicked on Connection > Only the list below > Added both:
Granted - 127.0.0.1
Granted - 192.168.29.151 - (This will be your assigned private ip address)
d. Navigated to Access Tab > Clicked on Connection >Relay
Granted - 127.0.0.1
Granted - 192.168.29.151 (This will be your assigned private ip address)
3) Send a test from Marketing campaigns, and it was delivered successfully.
a. Tested password reset for a test user, and it was delivered successfully.
b. Used the link, and I was able to successfully changed it and logged in with the new password.
c. Sent a test email from Rise > Marketing > and confirm the email messages is sent successfully.
After performing (iisreset) go back to IIS 6.0 and restarted the smtp as the iss reset seems to stop it...