{"id":432,"date":"2026-09-22T11:10:26","date_gmt":"2026-09-22T16:40:26","guid":{"rendered":"https:\/\/photonconsole.com\/blog\/?p=432"},"modified":"2026-09-22T11:10:27","modified_gmt":"2026-09-22T16:40:27","slug":"spring-boot-email-javamailsender-configuration-for-production","status":"publish","type":"post","link":"https:\/\/photonconsole.com\/blog\/spring-boot-email-javamailsender-configuration-for-production\/","title":{"rendered":"Spring Boot Email: JavaMailSender Configuration for Production"},"content":{"rendered":"\n

Spring Boot makes email look almost free. Add one starter dependency, set a few properties, inject JavaMailSender<\/code>, and a test message goes out on the first try.<\/p>\n\n\n\n

Production is where the gaps show. A request thread hangs for minutes because a mail server stopped responding. The application refuses to start because a bean could not be created. An @Async<\/code> method runs synchronously for reasons nobody can see. Or everything succeeds and the message lands in spam anyway.<\/p>\n\n\n\n

This guide covers the production setup: the properties that matter, the timeout default that causes most outages, HTML templates with Thymeleaf, asynchronous sending that actually works asynchronously, and the relay configuration underneath it all.<\/p>\n\n\n\n

Quick Answer: How Do You Send Email in Spring Boot?<\/h2>\n\n\n\n

Add the mail starter, configure SMTP in application.properties<\/code>, and inject JavaMailSender<\/code>:<\/p>\n\n\n\n

<dependency>\n    <groupId>org.springframework.boot<\/groupId>\n    <artifactId>spring-boot-starter-mail<\/artifactId>\n<\/dependency><\/code><\/pre>\n\n\n\n
spring.mail.host=smtp.photonrelay.com\nspring.mail.port=587\nspring.mail.username=${SMTP_USER}\nspring.mail.password=${SMTP_PASS}\nspring.mail.properties.mail.smtp.auth=true\nspring.mail.properties.mail.smtp.starttls.enable=true\nspring.mail.properties.mail.smtp.starttls.required=true\nspring.mail.properties.mail.smtp.connectiontimeout=5000\nspring.mail.properties.mail.smtp.timeout=5000\nspring.mail.properties.mail.smtp.writetimeout=5000<\/code><\/pre>\n\n\n\n
@Service\npublic class EmailService {\n\n    private final JavaMailSender mailSender;\n\n    public EmailService(JavaMailSender mailSender) {\n        this.mailSender = mailSender;\n    }\n\n    public void sendCode(String to, String code) {\n        SimpleMailMessage message = new SimpleMailMessage();\n        message.setFrom(\"noreply@yourdomain.com\");\n        message.setTo(to);\n        message.setSubject(\"Your verification code\");\n        message.setText(\"Your code is \" + code + \".\");\n        mailSender.send(message);\n    }\n}<\/code><\/pre>\n\n\n\n
The three timeout lines are not optional, and the next sections explain why. Delivery itself depends on the server you authenticate against and whether your domain is authorised to send \u2014 an authenticated relay such as PhotonConsole<\/a> covers that side.<\/p>\n\n\n\n
How Spring Boot Mail Works<\/h2>\n\n\n\n
Spring Boot<\/a> auto-configures a JavaMailSenderImpl<\/code> bean when it finds spring.mail.host<\/code> in your configuration. That bean wraps Jakarta Mail<\/a>, which opens the SMTP connection and speaks the protocol.<\/p>\n\n\n\n
Two consequences follow. The bean only exists if the host property is present. And every connection setting Jakarta Mail understands \u2014 timeouts, TLS, authentication \u2014 is passed through the spring.mail.properties.*<\/code> namespace, not through dedicated Spring properties.<\/p>\n\n\n\n
Note<\/p>\n\n\n\n
Spring Boot 3 moved from javax.mail<\/code> to jakarta.mail<\/code>. Code copied from older tutorials that imports javax.mail.internet.MimeMessage<\/code> will not compile on Spring Boot 3. Change the imports to the jakarta.mail<\/code> package \u2014 the class names are otherwise identical.<\/p>\n\n\n\n
Why Spring Boot Email Fails in Production<\/h2>\n\n\n\n
\"Diagram
Four configuration gaps that cause most Spring Boot email incidents.<\/figcaption><\/figure>\n\n\n\n
Most failures come from configuration rather than defects in Spring. These five account for the majority.<\/p>\n\n\n\n
1. No Timeouts Are Set<\/h3>\n\n\n\n
Jakarta Mail’s default connection, read and write timeouts are effectively infinite. If the mail server accepts the connection and then stops responding, the calling thread waits indefinitely. In a web application that thread is a request thread, and enough of them stalled at once takes the whole service down.<\/p>\n\n\n\n
This is the single most important property block in any Spring Boot mail configuration, and most tutorials leave it out.<\/p>\n\n\n\n
2. JavaMailSender Bean Not Found<\/h3>\n\n\n\n
The application fails to start with an error saying no qualifying bean of type JavaMailSender<\/code> is available. The cause is almost always a missing or misspelled spring.mail.host<\/code>, often because it is defined in a profile that is not active in that environment.<\/p>\n\n\n\n
3. STARTTLS Not Enabled<\/h3>\n\n\n\n
Setting the port to 587 does not enable encryption by itself. Without mail.smtp.starttls.enable=true<\/code> the client never upgrades the connection, and most relays reject authentication over a plaintext channel.<\/p>\n\n\n\n
4. @Async Runs Synchronously<\/h3>\n\n\n\n
Annotating a method with @Async<\/code> does nothing unless async support is enabled, and nothing when the method is called from inside the same class. The send appears to work, but it is still blocking the request thread.<\/p>\n\n\n\n
5. No Authentication Records on the Sending Domain<\/h3>\n\n\n\n
Without SPF and DKIM, receiving servers cannot verify your application is allowed to send as your domain, in line with Google’s sender guidelines<\/a>. Our guide to SPF, DKIM and DMARC<\/a> covers the records, and the free email deliverability checker<\/a> shows what your domain currently publishes.<\/p>\n\n\n\n
Common Mistake<\/p>\n\n\n\n
Deploying without the three mail.smtp.*timeout<\/code> properties. Because Jakarta Mail waits indefinitely by default, one unresponsive mail server can hold request threads open until the container’s thread pool is exhausted. The symptom looks like the whole application freezing, not like an email problem, which is why it is so often misdiagnosed.<\/p>\n\n\n\n
Quick Fix<\/p>\n\n\n\n
Application Fails to Start or Mail Never Connects<\/p>\n\n\n\n