IMAP Logging full of: [IP Unknown][1472819] Exception: (PooledTcpItem.cs) Authentication failed because the remote party has closed the transport stream.

Problem reported by Freek S. - 8/9/2018 at 12:58 PM

Submitted

My IMAP logging is full of these Exceptions:

[2018.08.08] 00:02:16 [IP Unknown][1472819] Exception: (PooledTcpItem.cs) Authentication failed because the remote party has closed the transport stream.
[2018.08.08] 00:02:16 [IP Unknown][1472819] StackTrace:    at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
[2018.08.08]    at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
[2018.08.08]    at MailService.TcpServerLib.Common.PooledTcpItem.EndConvertToSSL(IAsyncResult #ULi)
[2018.08.08] 00:07:15 [IP Unknown][47083043] Exception: (PooledTcpItem.cs) Authentication failed because the remote party has closed the transport stream.
[2018.08.08] 00:07:15 [IP Unknown][47083043] StackTrace:    at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
[2018.08.08]    at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
[2018.08.08]    at MailService.TcpServerLib.Common.PooledTcpItem.EndConvertToSSL(IAsyncResult #ULi)
[2018.08.08] 00:12:15 [IP Unknown][1373405] Exception: (PooledTcpItem.cs) Authentication failed because the remote party has closed the transport stream.
[2018.08.08] 00:12:15 [IP Unknown][1373405] StackTrace:    at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
[2018.08.08]    at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
[2018.08.08]    at MailService.TcpServerLib.Common.PooledTcpItem.EndConvertToSSL(IAsyncResult #ULi)
[2018.08.08] 00:17:16 [IP Unknown][64670025] Exception: (PooledTcpItem.cs) Authentication failed because the remote party has closed the transport stream.
[2018.08.08] 00:17:16 [IP Unknown][64670025] StackTrace:    at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
[2018.08.08]    at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
[2018.08.08]    at MailService.TcpServerLib.Common.PooledTcpItem.EndConvertToSSL(IAsyncResult #ULi)
[2018.08.08] 00:22:16 [IP Unknown][35399656] Exception: (PooledTcpItem.cs) Authentication failed because the remote party has closed the transport stream.
[2018.08.08] 00:22:16 [IP Unknown][35399656] StackTrace:    at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
[2018.08.08]    at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
[2018.08.08]    at MailService.TcpServerLib.Common.PooledTcpItem.EndConvertToSSL(IAsyncResult #ULi)
[2018.08.08] 00:27:16 [IP Unknown][13491089] Exception: (PooledTcpItem.cs) Authentication failed because the remote party has closed the transport stream.
[2018.08.08] 00:27:16 [IP Unknown][13491089] StackTrace:    at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
[2018.08.08]    at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
[2018.08.08]    at MailService.TcpServerLib.Common.PooledTcpItem.EndConvertToSSL(IAsyncResult #ULi)
[2018.08.08] 00:32:16 [IP Unknown][11454106] Exception: (PooledTcpItem.cs) Authentication failed because the remote party has closed the transport stream.
[2018.08.08] 00:32:16 [IP Unknown][11454106] StackTrace:    at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
[2018.08.08]    at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
[2018.08.08]    at MailService.TcpServerLib.Common.PooledTcpItem.EndConvertToSSL(IAsyncResult #ULi)
[2018.08.08] 00:37:16 [IP Unknown][39839562] Exception: (PooledTcpItem.cs) Authentication failed because the remote party has closed the transport stream.
[2018.08.08] 00:37:16 [IP Unknown][39839562] StackTrace:    at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
[2018.08.08]    at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
[2018.08.08]    at MailService.TcpServerLib.Common.PooledTcpItem.EndConvertToSSL(IAsyncResult #ULi)

As you can see, this Exception occurs every 5 minutes and is triggered from an Unknown IP. This has been going on for at least 30 days, the maximum I can go back in time in terms of logging. I am using SmarterMail 16.3.6782. What can I do to resolve these Exceptions or can I safely ignore them? Thank you!

4 Replies

Reply to Thread

Matt Petty Replied

8/10/2018 at 7:28 AM

Employee Post

Anytime you see "because the remote party has closed the transport stream." That means the client thats attempting to talk to your server closed the connection from their side. We don't usually know this occurs until we attempt to "read" or "write" back to that connection but since they abruptly closed the connection we get an exception.

So it's a problem caused by them closing their connection. While the error itself is a bit verbose and annoying you can usually ignore these but I'd check that client that's constantly trying to connect to you and failing as they may be trying to do something fishy. They may try to authenticate then bounce out after a few attempts.

We do have a slight issue that I believe we fixed with the IP UNKNOWN showing up however you should be able to look higher up in the log for session id `39839562` and there should be the initial connection with the IP included. Its just that specific error message that doesn't see the IP. What version are you on?

Matt Petty Software Developer SmarterTools Inc. (877) 357-6278 www.smartertools.com

Paul Blank Replied

8/10/2018 at 8:45 AM

Please: Make the SM SMTP send/receive "engine" a module that is tested 100% and upgraded as needed, and works with all current and future versions. The rest of SM can then connect to this module.

Same goes for things like Exchange/Outlook compatibility, if I may be so bold.

And while you're at it, if you want a different GUI, it should be allowed to run concurrently with the older one. I'm referring, of course, to v16 vs. v15.

Without that, you've got an "us vs. them" situation, both on the same side of the argument. Nobody can win that argument.

Freek S. Replied

8/10/2018 at 10:52 AM

Thanks for your detailed reply, Matt
I am running SmarterMail 16.3.6782.

echoDreamz Replied

8/12/2018 at 9:56 AM

How exactly would that work? What if the SMTP module has an update that the "rest of SM" needs to be aware of or vice-versa? This gets ugly really quick. If the SMTP module, POP module etc. all run on a shared library / common interface and that changes or has to be changed then you have to do a full update of the platform anyways.

Then you get to the cat and mouse type game of what SMTP version are you on, what POP, what web mail, what core etc. etc. It becomes a development and support nightmare.

Back to Community Threads

Please leave this box unchecked

4 Replies

Reply to Thread

Tags

Related Knowledge Base Articles