通过SMTP服务器发送邮件：Windows Server 2012 R2配置技术咨询

Hey there! Let's break down the optimizations for your SMTP setup and PowerShell script, plus key troubleshooting points based on your current setup with Windows Server 2012 R2's SMTP Virtual Server and Office 365 SMTP.

1. SMTP Virtual Server Configuration Optimizations #

• Switch to Office 365's Recommended Port: You’re currently using port 25, but Office 365 prioritizes port 587 (STARTTLS) for better security and reliability. Port 25 is often blocked by ISPs or firewalls, so switching to 587 will cut down on delivery failures.
• Lock Down Authentication: Since you’re relaying through Office 365, disable anonymous access on your SMTP Virtual Server. Go to its properties → Access tab → Authentication, check "Basic authentication", and ensure it’s set to pass credentials to the smarthost. This prevents unauthorized use of your relay.
• Set Connection Timeouts: Under the Delivery tab → Outbound Connections, set a reasonable timeout (e.g., 300 seconds) to avoid hanging connections to Office 365’s servers.
• Tune Smarthost Settings: In the Delivery tab → Advanced, set the smarthost to smtp.office365.com. If you only send to Office 365 domains, uncheck "Attempt direct delivery before sending to smarthost" to streamline the process.

2. PowerShell Script Optimizations #

• Ditch Plaintext Passwords: Storing passwords in plaintext is a major security risk. Use secure credential storage instead:

  # Option 1: Store password as a secure string (save to file for repeated use)
  $securePass = ConvertTo-SecureString "your-password" -AsPlainText -Force
  $credential = New-Object System.Management.Automation.PSCredential ($email, $securePass)
  
  # Option 2: Prompt for credentials (safer for interactive runs)
  $credential = Get-Credential -UserName $email -Message "Enter Office 365 SMTP Password"
  

• Use Send-MailMessage (Simpler & More Reliable): Instead of working directly with Net.Mail classes, PowerShell’s built-in Send-MailMessage cmdlet is easier to maintain. Here’s a rewritten version of your script:

  $email = "xxxxxxxxxx@xxxxxx.com"
  $securePass = ConvertTo-SecureString "your-secure-password" -AsPlainText -Force
  $credential = New-Object System.Management.Automation.PSCredential ($email, $securePass)
  
  $mailParams = @{
      From = $email
      To = "recipient@domain.com"
      Subject = "Your Email Subject"
      Body = "Email body content here"
      SmtpServer = "smtp.office365.com"
      Port = 587
      UseSsl = $true
      Credential = $credential
      Attachments = "C:\abcd\123.txt"  # Fixed path typo (Windows uses backslashes, not forward slashes)
  }
  
  Send-MailMessage @mailParams
  

• Add Error Handling: Wrap your script in a try/catch block to capture and log issues:

  try {
      Send-MailMessage @mailParams
      Write-Host "Email sent successfully at $(Get-Date)"
  }
  catch {
      Write-Error "Failed to send email: $_"
      # Log errors to a file for later debugging
      "[$(Get-Date)] Error: $_" | Out-File "C:\SMTP_Error_Log.log" -Append
  }
  

• Clean Up Attachments (If Sticking to Net.Mail): If you keep using the original Net.Mail approach, always dispose of attachments to free system resources:

  $attachment.Dispose()
  

1. Delivery Failures #

• Test Port Connectivity: Verify your server can reach Office 365’s SMTP server using:

  Test-NetConnection smtp.office365.com -Port 587
  

• Validate Office 365 Credentials: Confirm the email account and password are correct. If multi-factor authentication (MFA) is enabled for the account, you’ll need to use an app password instead of your regular password.
• Check SMTP Logs: Enable logging for your SMTP Virtual Server (Properties → General tab → Enable logging) and review logs at C:\Windows\System32\LogFiles\SMTPSVC1 for error codes like 550 (relay denied) or 535 (authentication failed).

2. Authentication Issues #

• Confirm SMTP Virtual Server Auth Settings: Ensure Basic authentication is enabled and configured to pass credentials to the smarthost.
• Check Office 365 Tenant Settings: In the Microsoft 365 admin center, go to Users → Active Users → Select your user → Mail → Manage email apps, and make sure "Authenticated SMTP" is enabled.

3. Attachment Problems #

• Verify File Permissions: The account running the script needs read access to the attachment file. Check the file’s security settings to confirm permissions.
• Fix Path Syntax: Windows uses backslashes (\) for file paths, so correct any forward slashes (/) in your attachment path to avoid "file not found" errors.

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