本地正常的Java邮件服务部署AWS EC2 Ubuntu后失败，遇Velocity初始化异常

Hey there, let's work through your issue step by step. First, that Exception: Velocity could not be Initialized is the immediate red flag, and while AWS EC2 has some network constraints to consider, we'll start with the Velocity setup since that's what the error directly points to, then cover EC2-specific email sending configurations.

1. Fixing Velocity Initialization Failures #

This error means your app can't set up the Velocity template engine, which is almost always tied to your deployment setup on the Ubuntu instance, not just AWS itself. Here are the most common fixes to check:

• Verify Dependency Completeness: Double-check that all Velocity-related JARs (like velocity-engine-core, velocity-runtime) are included in your deployment package. If you use Maven/Gradle, make sure these dependencies are marked as compile or runtime (not provided), so they get bundled with your app when you deploy.
• Check Template File Paths & Permissions: If your email uses Velocity templates:
  • Confirm the template files are present in your deployed app (either inside the JAR/WAR or in the correct filesystem path on the EC2 instance).
  • Ensure the Ubuntu user running your app has read permissions for these template files. You can test this with a quick cat /path/to/your/template.vm command as the app user to rule out permission issues.
• Validate Velocity Config: If you're using a velocity.properties file, make sure it's in your app's classpath and that any path configurations (like resource.loader.path) match the deployed environment. Local paths (e.g., src/main/resources/templates) won't work the same way on EC2 as they do on your machine.

2. AWS EC2 Configurations for Email Sending #

Once you resolve the Velocity initialization issue, you might still hit email sending failures if EC2's network rules are blocking traffic. Here's what to configure:

• Avoid Port 25: AWS restricts outbound traffic on port 25 for EC2 instances to prevent spam. Office 365's SMTP service uses ports 587 (TLS) or 465 (SSL) — update your app's SMTP configuration to use one of these ports instead of 25. This is the quickest fix for most cases.
• Security Group Rules: Modify your EC2 instance's security group to allow outbound traffic on ports 587 and 465. Add an outbound rule for TCP traffic to 0.0.0.0/0 (or restrict it to Office 365's SMTP server smtp.office365.com for tighter security).
• Port 25 Exception (If Absolutely Necessary): If you must use port 25, you'll need to submit a support request to AWS to lift the restriction for your EC2 instance. This process can take a day or two, so switching to 587/465 is the faster, preferred option.

Quick Test Tip #

After adjusting Velocity and EC2 settings, test the Velocity initialization separately first (write a small test class that just initializes Velocity and renders a simple template) to confirm that part works before testing full email sending. This helps isolate issues faster.

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