Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Client receive loop Exception #16

Open
endmax opened this issue Sep 17, 2024 · 17 comments
Open

Client receive loop Exception #16

endmax opened this issue Sep 17, 2024 · 17 comments
Assignees
@zabszk
Labels
bug Something isn't working

Comments

@endmax
Copy link

endmax commented Sep 17, 2024 •
edited
Loading

I use the SMTP server to process mails from a specific gmail account.
It frequently happens that there are subsequent System.IO.IOException inside the receive loop.

2024-09-08 22:09:01.772 +02:00 [ERR] [Client receive loop] Exception: System.IO.IOException, at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.IO.StreamReader.ReadBufferAsync(CancellationToken cancellationToken)
at System.IO.StreamReader.ReadLineAsyncInternal(CancellationToken cancellationToken)
at CSharp_SMTP_Server.Networking.ClientProcessor.Receive(), Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..

2024-09-08 22:11:21.449 +02:00 [ERR] [Client receive loop] Exception: System.IO.IOException, at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.IO.StreamReader.ReadBufferAsync(CancellationToken cancellationToken)
at System.IO.StreamReader.ReadLineAsyncInternal(CancellationToken cancellationToken)
at CSharp_SMTP_Server.Networking.ClientProcessor.Receive(), Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..

2024-09-08 22:12:51.415 +02:00 [ERR] [Client receive loop] Exception: System.IO.IOException, at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.IO.StreamReader.ReadBufferAsync(CancellationToken cancellationToken)
at System.IO.StreamReader.ReadLineAsyncInternal(CancellationToken cancellationToken)
at CSharp_SMTP_Server.Networking.ClientProcessor.Receive(), An existing connection was forcibly closed by the remote host..

After 3 exceptions the loop is exited but the exception is not throwed and the listener is not stopped by anyone.


catch (Exception e)
{
	Server.LoggerInterface?.LogError("[Client receive loop] Exception: " + e.GetType().FullName + ", " + e.StackTrace + ", " + e.Message);
	_fails++;
	if (_fails <= 3) continue;
	break;
}

I have some questions:

  • do you have an idea why I get this errors so frequently ?
  • Is the error intentionally handled to not re throw the exception ?
  • Could I make some modifications to throw the exception in order for an application to be restarted in such a case ?
@zabszk
Copy link
Owner

zabszk commented Sep 17, 2024

Hi,
Thank your for reporting the issue. I'm starting analyzing it.

@zabszk
Copy link
Owner

zabszk commented Sep 17, 2024

The exception itself means that the client forcefully stopped connection (either sent RST packet or connection was dropped). It should not affect the server itself. If that's the case, I will make changes to simply disconnect such client.

Can you answer to these two questions:

  1. Can you tell me more about your use-case? Is this a "regular" SMTP server and external clients (eg. users or other SMTP servers) connect to this server, send messages and disconnect or do you have some custom client that maintains long connection that gets for some reason dropped with this exception?
  2. How the SMTP server behaves after this exception? New clients should be able to connect to it. Is this the case or does the server stop accepting new clients?

@zabszk zabszk self-assigned this Sep 17, 2024
@zabszk zabszk added the bug Something isn't working label Sep 17, 2024
@zabszk
Copy link
Owner

zabszk commented Sep 17, 2024

I reproduced the issue. It happens when connection to client is dropped (or reset) when server is in progress of reading data (that happens as well if client didn't send \n or \r at the end and then disconnected).

Server seems to properly handle new clients. Can you confirm that's the case?

zabszk added a commit that referenced this issue Sep 17, 2024
@zabszk
Handled unhandled exceptions reported in #16
0dadf2d
@zabszk
Copy link
Owner

zabszk commented Sep 17, 2024

For now I simply handled that exception. There is a way to rewrite part of the code to avoid this exception in the first place (it will require implementing part of the StreamReader manually) and I will consider doing so.

The questions from my second reply are still relevant.

@endmax
Copy link
Author

endmax commented Sep 18, 2024

The exception itself means that the client forcefully stopped connection (either sent RST packet or connection was dropped). It should not affect the server itself. If that's the case, I will make changes to simply disconnect such client.

Can you answer to these two questions:

  1. Can you tell me more about your use-case? Is this a "regular" SMTP server and external clients (eg. users or other SMTP servers) connect to this server, send messages and disconnect or do you have some custom client that maintains long connection that gets for some reason dropped with this exception?
  2. How the SMTP server behaves after this exception? New clients should be able to connect to it. Is this the case or does the server stop accepting new clients?

Well, it is a "regular" SMTP server that accept only a specific google mail sender. The SMTP server stops quite frequently after it gets the errors I've reported in my first post. The gmail account is configured to forward emails from a specific sender to my SMTP server.
Here is a screenshot of the log where you can see these errors and when the server stopped.
image

@zabszk
Copy link
Owner

zabszk commented Sep 18, 2024

Thanks. Has the program crashed right after this exception?

I don't think that this exception caused it, because it's handled. Do you log stdout and stderr as well? If so, are there any exceptions or errors there? I believe that the crash is caused by some other exception (either in my library, in your app or some other library you use).

@endmax
Copy link
Author

endmax commented Sep 18, 2024

The program does not crash but the smtp server does not respond anymore to any request.
The smtp server is started inside a BackGroudService

public class Worker : BackgroundService
{
	
	protected override async Task ExecuteAsync(CancellationToken stoppingToken)
	{
		_logger.LogInformation("Executing service...");

		....

		StartSMTPServer();

		_logger.LogInformation("Service is ready!");

		await stoppingToken;
		_smtpServer?.Dispose();
		watcher.EnableRaisingEvents = false;
		_logger.LogInformation("Service is shutting down");
	}
	
	
	private void StartSMTPServer()
	{
		_logger.LogInformation("Configuring SMTP Server...");
		var store = new X509Store("WebHosting", StoreLocation.LocalMachine);
		store.Open(OpenFlags.ReadOnly | OpenFlags.OpenExistingOnly);

		var collection = store.Certificates;
		var certificates = collection.Find(X509FindType.FindBySubjectName, _smtpServerConfiguration.TLSCertificateName, false);

		X509Certificate2 certificate = certificates?.FirstOrDefault();

		if (certificate != null)
		{
			_logger.LogInformation("Using certificate {c}", _smtpServerConfiguration.TLSCertificateName);
		}

		_logger.LogInformation("Ports {@p}", _smtpServerConfiguration.Ports);
		_logger.LogInformation("TLSPorts {@p}", _smtpServerConfiguration.TLSPorts);

		var parameters = new ListeningParameters(IPAddress.IPv6Any, _smtpServerConfiguration.Ports,_smtpServerConfiguration.TLSPorts, true);
		var options = new ServerOptions()
		{
			ServerName = "my SMTP Server",
			RequireEncryptionForAuth = true,
			MessageCharactersLimit = 1024 * 1024 * 100
		};

		_smtpServer = new SMTPServer(new[] { parameters }, options, _mailDelivery, _smtpLogger);
		_smtpServer.SetAuthLogin(_mailAuth);
		_smtpServer.SetFilter(_mailFilter);
		_smtpServer.Start();

		_logger.LogInformation("SMTP Server ready");
	}
}

@zabszk
Copy link
Owner

zabszk commented Sep 18, 2024

  1. Is _logger.LogInformation("Service is shutting down"); executed during that "crash" or not?
  2. Are all SMTP ports stop being reachable?
  3. Can you check netstat (netstat -a -p tcp) on the server after the crash (before restarting the server)? Can you see any of the SMTP ports there? If you not familiar with netstat, you can run the command before it breaks to see how it should look like (port 25 should be on one of the first lines with state LISTENING).

@endmax
Copy link
Author

endmax commented Sep 19, 2024

  1. No, the service is not shut down, the LogInformation is not executed.
  2. A telnet to the server does not respond
  3. I'll do as soon as the exception occurs
    The strange thing is that the exception is trapped in the receiving loop and the SMTP server stops to respond when the loop is exited in the catch statement. In my understanding of your code, the listener is not notified about this event and stays hanging.

@zabszk
Copy link
Owner

zabszk commented Sep 19, 2024 •
edited
Loading

Thanks.

I'll do as soon as the exception occurs

Ok, I'm waiting for a crash.

In my understanding of your code, the listener is not notified about this event and stays hanging.

Listener isn't responsible for receiving data from clients. Listener is only responsible for accepting new clients. AcceptTcpClient() creates a new socket for this specific client and the listener socket keeps waiting for new clients and doesn't do anything related to that client that got accepted.

So either _dispose bool in Listener is set to true or listener is stuck for some reason on accepting new client (that will mean that there is some OS/C# issue, so I think it's an issue with dispose).

@zabszk
Copy link
Owner

zabszk commented Sep 19, 2024

I created branch dispose-log that logs disposal. Can you try using that branch for testing? Build attached.

release.zip

@endmax
Copy link
Author

endmax commented Sep 23, 2024

I'will try this version and I'll let you know as soon as I get the error.

@endmax
Copy link
Author

endmax commented Sep 26, 2024

Hi, today the situation is the following:
the smtp server does not receive any email, the log is not reporting anything, it seems not running

  • telnet myserver 25 -> it connects but but it does not show the 220 response
  • telnet myserver 587 -> 220 my SMTP Server ESMTP
    the netstat output is the following:
Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:21             ............:0         LISTENING
  TCP    0.0.0.0:25             ............:0         LISTENING
  TCP    0.0.0.0:80             ............:0         LISTENING
  TCP    0.0.0.0:135            ............:0         LISTENING
  TCP    0.0.0.0:443            ............:0         LISTENING
  TCP    0.0.0.0:445            ............:0         LISTENING
  TCP    0.0.0.0:465            ............:0         LISTENING
  TCP    0.0.0.0:587            ............:0         LISTENING
  TCP    0.0.0.0:1433           ............:0         LISTENING
  TCP    0.0.0.0:2548           ............:0         LISTENING
  TCP    0.0.0.0:3389           ............:0         LISTENING
  TCP    0.0.0.0:5985           ............:0         LISTENING
  TCP    0.0.0.0:8021           ............:0         LISTENING
  TCP    0.0.0.0:8031           ............:0         LISTENING
  TCP    0.0.0.0:8080           ............:0         LISTENING
  TCP    0.0.0.0:47001          ............:0         LISTENING
  TCP    0.0.0.0:49152          ............:0         LISTENING
  TCP    0.0.0.0:49153          ............:0         LISTENING
  TCP    0.0.0.0:49154          ............:0         LISTENING
  TCP    0.0.0.0:49155          ............:0         LISTENING
  TCP    0.0.0.0:49157          ............:0         LISTENING
  TCP    0.0.0.0:49159          ............:0         LISTENING
  TCP    XX.XX.XXX.XX:25        azpdws44.stretchoid.com:51254  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        ec2-18-237-182-105.us-west-2.compute.amazonaws.com:32924  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        starttls-virginia.securing-email.com:35034  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        60.190.248.12:19994    ESTABLISHED
  TCP    XX.XX.XXX.XX:25        scan-65-4.shadowserver.org:53271  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        soda.census.shodan.io:48008  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        soda.census.shodan.io:52070  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        soda.census.shodan.io:53144  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        79.110.62.17:2160      CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        87.121.69.198:49335    ESTABLISHED
  TCP    XX.XX.XXX.XX:25        94-156-177-79.virtualine.org:59157  ESTABLISHED
  TCP    XX.XX.XXX.XX:25        internettl.org:42115   ESTABLISHED
  TCP    XX.XX.XXX.XX:25        internettl.org:49994   ESTABLISHED
  TCP    XX.XX.XXX.XX:25        35.39.168.109.cust.ip.kpnqwest.it:54430  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        147.185.132.83:60708   CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-wm1-f41.google.com:55632  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-wm1-f42.google.com:54566  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-wm1-f54.google.com:54699  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-lf1-f52.google.com:52616  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-ed1-f46.google.com:53339  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-ed1-f52.google.com:61784  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-lj1-f169.google.com:53677  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-lj1-f173.google.com:60634  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-lj1-f177.google.com:55737  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-ej1-f41.google.com:54582  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-ej1-f45.google.com:60700  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-ej1-f48.google.com:61547  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-ej1-f50.google.com:60540  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-wr1-f41.google.com:53525  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        mail-wr1-f46.google.com:53453  CLOSE_WAIT
  TCP    XX.XX.XXX.XX:25        scan-08i.shadowserver.org:40397  CLOSE_WAIT

The application log shows the following errors:

[16:35:34 ERR]  MailError: [Client receive loop] Exception: System.Security.Authentication.AuthenticationException, Authentication failed, see inner exception.
[00:28:55 ERR]  MailError: [Client receive loop] Exception: System.IO.IOException,  Received an unexpected EOF or 0 bytes from the transport stream.

Now I'm going to use the dispose-log branch to compile my application and I'll let you know what happens.

@endmax
Copy link
Author

endmax commented Sep 27, 2024

Just another log before to pass to dispose-log branch.

2024-09-27 02:42:27.154 +02:00 [ERR] [Client write] Exception: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host..
2024-09-27 02:42:40.067 +02:00 [ERR] [Client receive loop] Exception: System.IO.IOException,    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
   at System.IO.StreamReader.ReadBufferAsync(CancellationToken cancellationToken)
   at System.IO.StreamReader.ReadLineAsyncInternal(CancellationToken cancellationToken)
   at CSharp_SMTP_Server.Networking.ClientProcessor.Receive(), Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..

2024-09-27 05:00:08.655 +02:00 [ERR] [Client receive loop] Exception: System.IO.IOException,    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
   at System.IO.StreamReader.ReadBufferAsync(CancellationToken cancellationToken)
   at System.IO.StreamReader.ReadLineAsyncInternal(CancellationToken cancellationToken)
   at CSharp_SMTP_Server.Networking.ClientProcessor.Receive(), Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..

here I've restarted the IIS server but the _logger.LogInformation("Service is shutting down"); is not executed but this could be a problem in my code.

2024-09-27 09:49:02.015 +02:00 [INF] Stopping service...

2024-09-27 09:49:16.527 +02:00 [INF] Starting service...
2024-09-27 09:49:17.020 +02:00 [INF] Executing service...
2024-09-27 09:49:17.020 +02:00 [INF] Checking for unprocessed files...
2024-09-27 09:49:17.074 +02:00 [INF] Configuring SMTP Server...
2024-09-27 09:49:17.105 +02:00 [INF] Ports [25,587]
2024-09-27 09:49:17.107 +02:00 [INF] TLSPorts [465]
2024-09-27 09:49:17.537 +02:00 [INF] SMTP Server ready
2024-09-27 09:49:17.537 +02:00 [INF] Service is ready!
2024-09-27 09:49:17.679 +02:00 [INF] AspNetCoreThreadingTimerStoragesCleaner.StartCore

In this particular case the first exception is inside the Client Write and the _fails counter is incremented by one. The other two exceptions are in the Client receive loop and after 2 exceptions the loop is exited and the SMTP server no more accepts emails even if it is active on all ports (tested with telnet).
The following is the netstat output:

  TCP    0.0.0.0:80             XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:135            XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:443            XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:445            XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:465            XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:587            XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:5040           XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:7070           XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:7680           XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:49664          XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:49665          XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:49666          XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:49667          XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:49668          XXXXXXXXXXXXXXX:0      LISTENING
  TCP    0.0.0.0:49670          XXXXXXXXXXXXXXX:0      LISTENING
  TCP    XXXXXXXXXXXX:25        79.110.62.17:64586     CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        80.94.92.156:8972      CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        80.94.92.156:31512     CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        80.94.92.157:14064     CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        80.94.92.157:35590     CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        80.94.92.158:8650      CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        80.94.92.158:51571     CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        80.94.92.159:8258      CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        80.94.92.159:29875     CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        35.39.168.109.cust.ip.kpnqwest.it:49854  CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        119-40-84-186.bdcom.com:49295  CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        119-40-84-186.bdcom.com:51660  CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        119-40-84-186.bdcom.com:52459  CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        119-40-84-186.bdcom.com:52716  CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        119-40-84-186.bdcom.com:58387  CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        183.134.104.170:62653  ESTABLISHED
  TCP    XXXXXXXXXXXX:25        185.196.9.190:63569    CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        185.196.9.190:65414    CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        mail-lj1-f170.google.com:53353  CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        mail-lj1-f173.google.com:42181  CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        mail-lj1-f177.google.com:53438  ESTABLISHED
  TCP    XXXXXXXXXXXX:25        mail-lj1-f179.google.com:43277  CLOSE_WAIT
  TCP    XXXXXXXXXXXX:25        mail-ej1-f47.google.com:42068  ESTABLISHED

@endmax
Copy link
Author

endmax commented Oct 3, 2024

Good news

with the dispose-log branch the client is still alive even after more then three consecutive exceptions.
here is the log

[20:08:09 ERR] [Client receive loop] Exception: System.Security.Authentication.AuthenticationException,
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
   at CSharp_SMTP_Server.Networking.ClientProcessor.ProcessResponse(String response) in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 245
   at CSharp_SMTP_Server.Networking.ClientProcessor.Receive() in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 128, Authentication failed, see inner exception.
[20:08:11 ERR] [Client receive loop] Exception: System.Security.Authentication.AuthenticationException,
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
   at CSharp_SMTP_Server.Networking.ClientProcessor.ProcessResponse(String response) in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 245
   at CSharp_SMTP_Server.Networking.ClientProcessor.Receive() in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 128, Authentication failed, see inner exception.
[20:08:14 ERR] [Client receive loop] Exception: System.Security.Authentication.AuthenticationException,
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
   at CSharp_SMTP_Server.Networking.ClientProcessor.ProcessResponse(String response) in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 245
   at CSharp_SMTP_Server.Networking.ClientProcessor.Receive() in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 128, Authentication failed, see inner exception.
[20:08:16 ERR] [Client receive loop] Exception: System.Security.Authentication.AuthenticationException,
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
   at CSharp_SMTP_Server.Networking.ClientProcessor.ProcessResponse(String response) in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 245
   at CSharp_SMTP_Server.Networking.ClientProcessor.Receive() in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 128, Authentication failed, see inner exception.
[20:08:19 ERR] [Client receive loop] Exception: System.Security.Authentication.AuthenticationException,
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
   at CSharp_SMTP_Server.Networking.ClientProcessor.ProcessResponse(String response) in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 245
   at CSharp_SMTP_Server.Networking.ClientProcessor.Receive() in C:\Users\Massimo\source\repos\CSharp-SMTP-Server\CSharp-SMTP-Server\Networking\ClientProcessor.cs:line 128, Authentication failed, see inner exception.

@zabszk
Copy link
Owner

zabszk commented Oct 23, 2024

Hi,

Sorry for the delay. So adding debug somehow fixed the issue? I love this kind of bugs...

@endmax
Copy link
Author

endmax commented Oct 23, 2024 •
edited
Loading

Yes me too !!!
but apparently the solution is in the commit 0dadf2d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zabszk zabszk

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@endmax @zabszk