Server O.S.: Windows Server 2008 Standard x64 Edition SP2
Web Server: IIS 7
ASP.NET 2.0.50727.0
Database: MSSQL Server 2008
Mojoportal: 2.3.4.4 and 2.3.4.5

After Upgrading to 2.3.4.4, Comments to Blog Posts cause error.
Upgrading to 2.3.4.5 did not solve.
 

mojoPortal System Log:

2010-06-21 14:28:04,272 ERROR mojoPortal.Web.Global - 192.168.3.115-it-IT - /prova-blog-and-comments-dopo-upgrade-2344.aspx
System.Security.Authentication.AuthenticationException: Il certificato remoto non è stato ritenuto valido dalla procedura di convalida. (The remote certificate is invalid according to the validation procedure)
in System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
in System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
in System.Threading.ExecutionContext.runTryCode(Object userData)
in System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
in System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
in System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
in System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
in System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
in System.Net.Mail.SmtpConnection.Flush()
in System.Net.Mail.ReadLinesCommand.Send(SmtpConnection conn)
in System.Net.Mail.SmtpConnection.GetConnection(String host, Int32 port)
in System.Net.Mail.SmtpClient.Send(MailMessage message)
in mojoPortal.Net.Email.Send(SmtpSettings smtpSettings, String from, String replyTo, String to, String cc, String bcc, String subject, String messageBody, Boolean html, String priority, String[] attachmentPaths, String[] attachmentNames)
in mojoPortal.Net.Email.SendEmailNormal(SmtpSettings smtpSettings, String from, String replyTo, String to, String cc, String bcc, String subject, String messageBody, Boolean html, String priority)
in mojoPortal.Net.Email.SendEmailNormal(SmtpSettings smtpSettings, String from, String to, String cc, String bcc, String subject, String messageBody, Boolean html, String priority)
in mojoPortal.Net.Email.SendEmail(SmtpSettings smtpSettings, String from, String to, String cc, String bcc, String subject, String messageBody, Boolean html, String priority)
in mojoPortal.Net.Notification.SendBlogCommentNotificationEmail(SmtpSettings smtpSettings, String messageTemplate, String fromEmail, String siteName, String authorEmail, String messageLink)
in mojoPortal.Web.BlogUI.BlogViewControl.btnPostComment_Click(Object sender, EventArgs e)
in System.Web.UI.WebControls.Button.OnClick(EventArgs e)
in System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
in System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
in System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
 

Hi Joe,

I have checked this issue with my business partner which is our system engineer responsible for the mail server administration. Apparently all certificates will expire in 2011 therefore the authentication problem could be due to something else.

The web server used to send email with an authenticated SSL connection to the mail server (same domain and network) on port 25.

We created a specific new connector for SSL on port 587 and now the web server can send mail again.

We will check this more deeply in the coming days but we do not exclude that a security update affected somehow the possibility to send wih SSL on port 25.

Thank you anyway for your feed back. I just wanted to be sure to have correctly upgraded the sites.
 

Regards.
Diego