Not sure where this post belongs but since it is regarding the Forum notifications I will start it here. No this is not about the known individual post notification issue either.
When easycgi switched platforms, one of the things they changed is to no longer allow anonomous smtp from within DNN. I did not know this until a few hours and about 3 forum posts went by. Within the scheduler I could see that there were a couple tasks that took 140 seconds to "successfully" complete after those tasks showed failed for the entire time leading up to the 120 - 140 seconds. Initially you would think the task kept retrying then finally had success. The reality is that the task failed due to incorrect smtp settings. The event log shows the following:
InnerException: Unable to connect to the remote server
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 66.245.177.160:25 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) --- End of inner exception stack trace --- at System.Net.ServicePoint.GetConnection(PooledStream PooledStream, Object owner, Boolean async, IPAddress& address, Socket& abortSocket, Socket& abortSocket6, Int32 timeout) at System.Net.PooledStream.Activate(Object owningObject, Boolean async, Int32 timeout, GeneralAsyncDelegate asyncCallback) at System.Net.PooledStream.Activate(Object owningObject, GeneralAsyncDelegate asyncCallback) at System.Net.ConnectionPool.GetConnection(Object owningObject, GeneralAsyncDelegate asyncCallback, Int32 creationTimeout) at System.Net.Mail.SmtpConnection.GetConnection(String host, Int32 port) at System.Net.Mail.SmtpTransport.GetConnection(String host, Int32 port) at System.Net.Mail.SmtpClient.GetConnection() at System.Net.Mail.SmtpClient.Send(MailMessage message)
Source:
Server Name: IIS06101
Once I realize what happened, I fixed the smtp settings but the notification emails were lost forever. Shouldnt those emails that failed to send have queued and then finally sent once I fixed the setting? How could the task say that it successfully completed when in fact it failed to successfully complete?