JavaMail集成问题：Gmail邮件发送跨网络失效求助

Hey there, let's break down why your JavaMail setup works on your original network but fails elsewhere—this is super common with network restrictions and Gmail's security checks. Here are the most likely culprits and fixes:

1. Network Firewall/Proxy Blocking SMTP Ports #

Most corporate, public Wi-Fi, or restricted networks block outgoing SMTP ports (Gmail uses 587 for STARTTLS and 465 for SSL). First, verify if the ports are accessible on the problematic network:

• On Linux/macOS: Run nc -zv smtp.gmail.com 587 in terminal. If you get a "connection refused" error, the port is blocked.
• On Windows: Use PowerShell command Test-NetConnection smtp.gmail.com -Port 587. Check the "TcpTestSucceeded" result.

Fix for Proxy Environments #

If the network requires a proxy to access external services, add these system properties before initializing your JavaMail Session:

// Set HTTP/HTTPS proxy (adjust values to your network's proxy)
System.setProperty("http.proxyHost", "your-proxy-server");
System.setProperty("http.proxyPort", "8080");
System.setProperty("https.proxyHost", "your-proxy-server");
System.setProperty("https.proxyPort", "8080");

// If proxy requires authentication
System.setProperty("http.proxyUser", "proxy-username");
System.setProperty("http.proxyPassword", "proxy-password");
System.setProperty("https.proxyUser", "proxy-username");
System.setProperty("https.proxyPassword", "proxy-password");

2. Gmail Security Restrictions Triggered by New Network #

Gmail flags logins from unfamiliar locations/networks as suspicious, even if your code is correct. Here's what to check:

• Check your Gmail Security Log: Go to your Google Account > Security > Recent activity. Look for blocked login attempts from the new network and approve them if they're legitimate.
• Use App Password (if 2FA is enabled): If you have Two-Factor Authentication turned on, your regular password won't work for JavaMail. Generate an App Password in your Google Account > Security > App passwords (only visible if 2FA is on) and use that in your code instead of your regular password.

3. Misconfigured JavaMail Session #

Double-check your Session properties to ensure they're compatible with Gmail's requirements. Here's a working baseline configuration:

Properties mailProps = new Properties();
mailProps.put("mail.smtp.host", "smtp.gmail.com");
mailProps.put("mail.smtp.port", "587"); // Preferred port for STARTTLS
mailProps.put("mail.smtp.auth", "true");
mailProps.put("mail.smtp.starttls.enable", "true"); // Mandatory for Gmail's 587 port
mailProps.put("mail.smtp.ssl.trust", "smtp.gmail.com"); // Trust Gmail's SSL certificate

// Initialize session with authenticator
Session session = Session.getInstance(mailProps, new Authenticator() {
    @Override
    protected PasswordAuthentication getPasswordAuthentication() {
        return new PasswordAuthentication("your-email@gmail.com", "your-app-password-or-regular-password");
    }
});

4. DNS Resolution Issues #

Some networks have DNS servers that can't resolve smtp.gmail.com. Test this by pinging the domain on the problematic network—if it fails to resolve, try using Gmail's direct SMTP IP address (e.g., 64.233.184.108) in your mail.smtp.host property temporarily to confirm.

Quick Troubleshooting Checklist #

• Can you access Gmail's web interface on the problematic network? If not, the network has full restrictions on Google services.
• Are you using the correct password/App Password for your Gmail account?
• Did you hardcode any network-specific settings (like proxy) in your original code that don't apply to the new network?

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