.NET Core 1.1网站使用MailKit发送邮件时出现异常问题

Hey there, let's dig into this tricky authentication issue you're hitting with your .NET Core 1.1 site's email functionality. That AuthenticationInvalidCredentials error is usually a clue that something's off with how credentials are being passed—especially when dealing with enterprise proxies, which often add extra layers that can disrupt the SMTP auth flow. Here are the steps I'd recommend to debug and fix this:

• Separate proxy credentials from SMTP credentials
  Enterprise proxies often require their own authentication, which is totally separate from your SMTP server's credentials. MailKit doesn't automatically handle proxy auth, so you need to explicitly configure it. Use the Proxy property on your SmtpClient to set up the proxy and its credentials:

  var proxy = new HttpProxy(new Uri("http://your-proxy-address:port"));
  proxy.Credentials = new System.Net.NetworkCredential("proxy-username", "proxy-password");
  
  using (var client = new SmtpClient())
  {
      client.Proxy = proxy;
      // Rest of your SMTP setup...
  }
  

  Make sure you're not mixing up proxy credentials with your SMTP server's credentials—this is a super common mistake.

• Verify SMTP credential format and validity
  Double-check that your SMTP credentials are formatted correctly for your enterprise server. Many corporate SMTP/Exchange servers expect domain-prefixed usernames (like DOMAIN\userid instead of just the email address or user ID). Test these credentials directly with a tool like Telnet or PowerShell's Send-MailMessage to confirm they work outside of your app—this will rule out invalid credentials as the root cause.

• Check TLS version and encryption settings
  .NET Core 1.1 defaults to older TLS versions, which might be blocked by your enterprise proxy or SMTP server. Force TLS 1.2 (the most widely supported secure version for enterprise environments) in your MailKit setup:

  using (var client = new SmtpClient())
  {
      client.SslOptions.EnabledSslProtocols = System.Net.Security.SslProtocols.Tls12;
      // Connect with the right secure option (StartTLS for port 587, SslOnConnect for 465)
      await client.ConnectAsync("smtp.yourcompany.com", 587, SecureSocketOptions.StartTls);
      // ...
  }
  

  Also confirm that your proxy allows outbound TLS traffic to your SMTP server's port.

• Enable MailKit debug logging
  This is hands-down the most useful step to see exactly what's happening during the auth process. Enable debug logs to capture the full SMTP conversation and proxy interactions:

  using (var client = new SmtpClient())
  {
      client.LogLevel = LogLevel.Debug;
      // Log to console (or redirect to a file for production debugging)
      client.Logger = new ProtocolLogger(Console.OpenStandardOutput());
      
      // Your connection, auth, and send logic here...
  }
  

  Look for lines related to proxy connections, AUTH commands, and server responses—this will show if the proxy is blocking the auth request, or if the server is rejecting the credentials for a specific reason.

• Confirm enterprise proxy rules
  Reach out to your IT team to verify:

  • Outbound SMTP traffic to your target server/port is allowed through the proxy
  • The proxy isn't modifying or stripping authentication headers from SMTP requests
  • There are no IP whitelisting rules that your app server isn't compliant with

• Consider .NET Core version limitations
  .NET Core 1.1 is end-of-life and has known limitations around proxy handling and TLS support. If possible, upgrading to a supported version (like .NET Core 2.1 or later) might resolve underlying bugs that are contributing to this issue. If upgrading isn't an option, ensure you're using the latest patch for .NET Core 1.1.

By working through these steps, you should be able to pinpoint whether the issue is with proxy configuration, credential formatting, TLS settings, or enterprise network rules.

内容的提问来源于stack exchange，提问作者Abhay Dhar