For about a week, the connection to the mail account has returned the following message:
Error: System.IO.IOException: Authentication failed. The remote party has closed the transport flow.
in System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
in System.Net.Security.SslStream.AuthenticateAsClient(String targetHost)
in POP3Client.POP3client.connect()
The service downloads the mail every 10 minutes and there are 4 accounts.
Sometimes the mistake is for everyone, sometimes just for a few accounts.
Thank you,
Ivan
Last edit: Ivan 2021-10-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am getting the same error message on the bug tracker site.
I was also getting the same error in one of my own apps that sends out emails and I could fix that by adding the line: System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12; in the function that sends the email.
Does anyone know how we can get that info to the developer so he can try add it into the system?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has anyone been able to work around this error and find a solution?
I think it could be related to Office365. If I set up the system to use a gmail account, then I don't get the errors. I would prefer to use our domain for the emails and not use gmail
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Your solution, adding that line, makes sense. You have BugTracker.NET source code - you can just add it yourself (but I'm not sure where). I'm currently not set up to really test things. If you figure out where to add it, can you let me know?
I've been using an old cable modem with an admin website on it. The last time I tried to visit that website the browsers said they couldn't connect, because they've dropped support for older unsafer TLS protocols, I guess, if understand correctly.
So.... the world moves forward and BugTracker.NET slowly decays. class Asp.NET itself is no longer being invested in by MS. Now it's dotnet core. During some of the covid lockdown I did play around with rewriting BugTracker.NET for dotnet core: https://github.com/ctrager/budoco
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone, we were able to find a work around without changing the code.
You can read the below article. Option 2 worked for us. I hope this helps some other people.
For about a week, the connection to the mail account has returned the following message:
Error: System.IO.IOException: Authentication failed. The remote party has closed the transport flow.
in System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
in System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
in System.Net.Security.SslStream.AuthenticateAsClient(String targetHost)
in POP3Client.POP3client.connect()
The service downloads the mail every 10 minutes and there are 4 accounts.
Sometimes the mistake is for everyone, sometimes just for a few accounts.
Thank you,
Ivan
Last edit: Ivan 2021-10-27
I am getting the same error message on the bug tracker site.
I was also getting the same error in one of my own apps that sends out emails and I could fix that by adding the line: System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12; in the function that sends the email.
Does anyone know how we can get that info to the developer so he can try add it into the system?
Has anyone been able to work around this error and find a solution?
I think it could be related to Office365. If I set up the system to use a gmail account, then I don't get the errors. I would prefer to use our domain for the emails and not use gmail
I think this is a clue to the problem: https://blog.gigamon.com/2021/07/14/what-is-tls-1-2-and-why-should-you-still-care/
Your solution, adding that line, makes sense. You have BugTracker.NET source code - you can just add it yourself (but I'm not sure where). I'm currently not set up to really test things. If you figure out where to add it, can you let me know?
I've been using an old cable modem with an admin website on it. The last time I tried to visit that website the browsers said they couldn't connect, because they've dropped support for older unsafer TLS protocols, I guess, if understand correctly.
So.... the world moves forward and BugTracker.NET slowly decays. class Asp.NET itself is no longer being invested in by MS. Now it's dotnet core. During some of the covid lockdown I did play around with rewriting BugTracker.NET for dotnet core: https://github.com/ctrager/budoco
Hi everyone, we were able to find a work around without changing the code.
You can read the below article. Option 2 worked for us. I hope this helps some other people.
https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365