使用C# ASP.NET通过SMTP发送邮件时出现‘操作超时’错误

Hey there, let's figure out why your custom SMTP server is throwing an "operation timed out" error while Gmail's SMTP works perfectly. Here are the most likely fixes to test out:

1. Double-Check SMTP Host & Port Details #

First off, make sure you're using the correct host address and port for your custom SMTP server. Different providers use different ports:

• Common non-SSL/TLS ports: 25, 587 (587 is often preferred for STARTTLS)
• SSL-only port: 465

A quick way to test connectivity is using PowerShell on your server:

Test-NetConnection your-smtp-host.com -Port 587

If this fails, your server can't reach the SMTP host at all—skip to the firewall section below.

2. Firewall & IP Whitelist Restrictions #

This is one of the most common culprits:

• Your application server's firewall (or company network firewall) might be blocking outbound traffic to your SMTP port. Check if outbound rules allow access to the SMTP host and port.
• Many custom SMTP servers use IP whitelisting—only specific IPs can send mail through them. Make sure your application server's public IP is added to the whitelist in your domain email settings.

3. Fix SSL/TLS Mismatches #

Your code sets EnableSsl = true, but not all custom SMTP servers work the same way:

• Some servers require STARTTLS (which upgrades a plain connection to TLS) instead of immediate SSL. Try setting EnableSsl = false first, then check if your server supports STARTTLS (most modern ones do).
• If you're using a self-signed SSL certificate on your SMTP server, your application might reject it. For testing, you can temporarily bypass certificate validation (not recommended for production), but in production, use a certificate from a trusted CA.

4. Increase Timeout Value #

You commented out the timeout setting—default timeouts might be too short for a slower custom SMTP server. Try setting a longer timeout (like 30 seconds) to give the server enough time to respond:

client.Timeout = 30000; // 30,000 milliseconds = 30 seconds

5. Verify Credentials Are Correct #

Double-check your NetworkCredential details:

• Many domain email services require the full email address as the username (e.g., john@yourdomain.com instead of just john).
• Make sure the password is the correct SMTP-specific password (some services use app-specific passwords instead of your regular account password).

Adjusted Sample Code #

Here's your code with some key tweaks to test:

protected void send_Click(object sender, EventArgs e) {
    string to = "xyz@gmail.com"; //To address
    string from = "your-actual-email@yourdomain.com"; // Use your full domain email here
    MailMessage message = new MailMessage(from, to);
    string mailbody = "Welcome to custom SMTP testing...";
    message.Subject = "Sending Email via Custom SMTP";
    message.Body = mailbody;
    message.IsBodyHtml = true;

    // Replace with your SMTP host and correct port
    SmtpClient client = new SmtpClient("your-smtp-server-host", 587); 
    System.Net.NetworkCredential basicCredential1 = new System.Net.NetworkCredential("your-full-email@yourdomain.com", "your-smtp-password");
    
    client.EnableSsl = true;
    client.Timeout = 30000; // Longer timeout for slower servers
    client.UseDefaultCredentials = false;
    client.Credentials = basicCredential1;

    try {
        client.Send(message);
        // Optional: Add success feedback
        // StatusLabel.Text = "Email sent successfully!";
    } catch (Exception ex) {
        // It's better to log the full exception details for debugging
        // Logging example: Logger.Error($"Email send failed: {ex.Message}", ex);
        throw new Exception($"Failed to send email: {ex.Message}", ex);
    }
}

If none of these work, check your custom SMTP server's logs—they'll have detailed error messages that can pinpoint exactly what's going wrong (like authentication failures, rejected IPs, or protocol mismatches).

内容的提问来源于stack exchange，提问作者monika mangal