Quarkus - Sending emails

    To complete this guide, you need:

    • less than 15 minutes

    • The SMTP hostname, port and credentials, and an email address

    • an IDE

    • JDK 1.8+ installed with configured appropriately

    • Apache Maven 3.6.2+

    • GraalVM installed if you want to run in native mode.

    Architecture

    In this guide, we are going to see how you can send emails from a Quarkus application. It covers simple emails, attachments, inlined attachments, the reactive and imperative APIs…​

    Creating the Maven Project

    Create a new project with the following command:

    If you already have an existing project, add the mailer extension:

    1. ./mvnw quarkus:add-extensions -Dextensions="mailer"

    This will add the following to your pom.xml:

    1. <dependency>
    2. <groupId>io.quarkus</groupId>
    3. <artifactId>quarkus-mailer</artifactId>
    4. </dependency>

    Configuring the mailer

    The Quarkus mailer is using SMTP. In the src/main/resources/application.properties file, you need to configure the host, port, username, password as well as the other configuration aspect. Note that the password can also be configured using system properties and environment variables.

    Here is an example using sendgrid:

    1. quarkus.mailer.from=test@quarkus.io
    2. quarkus.mailer.host=smtp.sendgrid.net
    3. quarkus.mailer.port=465
    4. quarkus.mailer.ssl=true
    5. quarkus.mailer.username=....
    6. quarkus.mailer.password=....
    7. quarkus.mailer.mock=false
    For more information about the Mailer extension configuration please refer to the .

    In a JAX-RS resource, or in a bean, you can inject the mailer as follows:

    1. @Inject
    2. Mailer mailer;
    3. @Inject
    4. ReactiveMailer reactiveMailer;
    • io.quarkus.mailer.Mailer provides the imperative (blocking and synchronous) API;

    • io.quarkus.mailer.reactive.ReactiveMailer provides the reactive (non-blocking and asynchronous) API

    The two APIs are equivalent feature-wise. Actually the Mailer implementation is built on top of the ReactiveMailer implementation.
    Mutiny

    The reactive mailer uses Mutiny reactive types, if you’re not familiar with them, read the Getting Started with Reactive guide first.

    To send a simple email, proceed as follows:

    For example, you can use the Mailer in a JAX-RS endpoint as follows:

    1. @GET
    2. @Path("/simple")
    3. public Response sendASimpleEmail() {
    4. mailer.send(Mail.withText("to@acme.org", "A simple email from quarkus", "This is my body"));
    5. }
    6. @GET
    7. @Path("/async")
    8. public CompletionStage<Response> sendASimpleEmailAsync() {
    9. return reactiveMailer.send(
    10. Mail.withText("to@acme.org", "A reactive email from quarkus", "This is my body"))
    11. .subscribeAsCompletionStage()
    12. .thenApply(x -> Response.accepted().build());
    13. }

    With the quarkus-resteasy-mutiny extension, you can return an instance of Uni directly.

    With such a JAX-RS resource, you can check that everything is working with:

    1. curl http://localhost:8080/simple
    2. curl http://localhost:8080/async

    You can create new io.quarkus.mailer.Mail instances from the constructor or from the Mail.withText and Mail.withHtml helper methods. The instance lets you add recipients (to, cc, or bcc), set the subject, headers, sender (from) address…​

    You can also send several Mail objects in one call:

    1. mailer.send(mail1, mail2, mail3);

    Sending attachments

    To send attachment, just use the addAttachment methods on the io.quarkus.mailer.Mail instance:

    1. @GET
    2. @Path("/attachment")
    3. public Response sendEmailWithAttachment() {
    4. mailer.send(Mail.withText("to@acme.org", "An email from quarkus with attachment",
    5. "This is my body")
    6. .addAttachment("my-file.txt",
    7. "content of my file".getBytes(), "text/plain"));
    8. return Response.accepted().build();
    9. }

    Attachments can be created from raw bytes (as shown in the snippet) or files.

    Sending HTML emails with inlined attachments

    When sending HTML email, you can add inlined attachments. For example, you can send an image with your email, and this image will be displayed in the mail content. If you put the image file into resources folder, you should specify the full path to the file. “e.g.” “META-INF/resources/quarkus-logo.png” otherwise quarkus will lookup in the root folder of the project

    1. @GET
    2. @Path("/html")
    3. public Response sendingHTML() {
    4. String body = "<strong>Hello!</strong>" + "\n" +
    5. "<p>Here is an image for you: <img src=\"cid:my-image@quarkus.io\"/></p>" +
    6. "<p>Regards</p>";
    7. mailer.send(Mail.withHtml("to@acme.org", "An email in HTML", body)
    8. .addInlineAttachment("quarkus-logo.png",
    9. new File("quarkus-logo.png"),
    10. "image/png", "<my-image@quarkus.io>"));
    11. return Response.accepted().build();
    12. }

    Note the content-id format and reference. By spec, when you create the inline attachment, the content-id must be structured as follows: <id@domain>. If you don’t wrap your content-id between <>, it is automatically wrapped for you. When you want to reference your attachment, for instance in the src attribute, use cid:id@domain (without the < and >).

    Message Body Based on Qute Templates

    It’s also possible to inject a mail template, where the message body is created automatically using Qute templates.

    Injected mail templates are validated during build. If there is no matching template in src/main/resources/templates the build fails.

    You can also do this without type-safe templates:

    1. @Inject
    2. MailTemplate hello; (1)
    3. @GET
    4. @Path("/mail")
    5. public CompletionStage<Response> send() {
    6. return hello.to("to@acme.org") (2)
    7. .subject("Hello from Qute template")
    8. // the template looks like: Hello {name}!
    9. .data("name", "John") (3)
    10. .send() (4)
    11. .subscribeAsCompletionStage()
    12. .thenApply(x -> Response.accepted().build());
    13. }
    1If there is no @ResourcePath qualifier provided, the field name is used to locate the template. In this particular case, we will use the hello.html and hello.txt templates to create the message body.
    2Create a mail template instance and set the recipient.
    3Set the data used in the template.
    4MailTemplate.send() triggers the rendering and, once finished, sends the e-mail via a Mailer instance.

    You can then write tests to verify that your emails were sent, for example, by a REST endpoint:

    1. @QuarkusTest
    2. private static final String TO = "foo@quarkus.io";
    3. @Inject
    4. MockMailbox mailbox;
    5. @BeforeEach
    6. void init() {
    7. mailbox.clear();
    8. }
    9. @Test
    10. void testTextMail() throws MessagingException, IOException {
    11. // call a REST endpoint that sends email
    12. given()
    13. .when()
    14. .get("/send-email")
    15. .then()
    16. .statusCode(202)
    17. .body(is("OK"));
    18. // verify that it was sent
    19. List<Mail> sent = mailbox.getMessagesSentTo(TO);
    20. assertThat(sent).hasSize(1);
    21. Mail actual = sent.get(0);
    22. assertThat(actual.getText()).contains("Wake up!");
    23. assertThat(actual.getSubject()).isEqualTo("Alarm!");
    24. assertThat(mailbox.getTotalMessagesSent()).isEqualTo(6);
    25. }
    26. }

    Gmail specific configuration

    If you want to use the Gmail SMTP server, first create a dedicated password in Google Account > Security > App passwords or go to https://myaccount.google.com/apppasswords.

    When done, you can configure your Quarkus application by adding the following properties to your application.properties:

    With TLS:

    1. quarkus.mailer.auth-methods=DIGEST-MD5 CRAM-SHA256 CRAM-SHA1 CRAM-MD5 PLAIN LOGIN
    2. quarkus.mailer.from=YOUREMAIL@gmail.com
    3. quarkus.mailer.host=smtp.gmail.com
    4. quarkus.mailer.port=587
    5. quarkus.mailer.start-tls=REQUIRED
    6. quarkus.mailer.username=YOUREMAIL@gmail.com
    7. quarkus.mailer.password=YOURGENERATEDAPPLICATIONPASSWORD

    Or with SSL:

    1. quarkus.mailer.auth-methods=DIGEST-MD5 CRAM-SHA256 CRAM-SHA1 CRAM-MD5 PLAIN LOGIN
    2. quarkus.mailer.from=YOUREMAIL@gmail.com
    3. quarkus.mailer.host=smtp.gmail.com
    4. quarkus.mailer.port=465
    5. quarkus.mailer.ssl=true
    6. quarkus.mailer.username=YOUREMAIL@gmail.com
    7. quarkus.mailer.password=YOURGENERATEDAPPLICATIONPASSWORD

    The quarkus.mailer.auth-methods configuration option is needed for the Quarkus mailer to support password authentication with Gmail. By default both the mailer and Gmail default to XOAUTH2 which requires registering an application, getting tokens, etc.

    Using SSL with native executables

    Note that if you enable SSL for the mailer and you want to build a native executable, you will need to enable the SSL support. Please refer to the Using SSL With Native Executables guide for more information.

    Using the underlying Vert.x Mail Client

    The Quarkus Mailer is implemented on top of the Vert.x Mail Client, providing an asynchronous and non-blocking way to send emails. If you need fine control on how the mail is sent, for instance if you need to retrieve the message ids, you can inject the underlying client, and use it directly:

    1. @Inject MailClient client;

    Three API flavors are exposed:

    • the Mutiny client (io.vertx.mutiny.ext.mail.MailClient)

    • the Axle client (io.vertx.axle.ext.mail.MailClient), using CompletionStage and Reactive Streams Publisher - deprecated, it is recommended to switch to the Mutiny client

    • the RX Java 2 client (io.vertx.reactivex.ext.mail.MailClient) - deprecated, it is recommended to switch to the Mutiny client

    Check the for further details about these different APIs and how to select the most suitable for you.

    The retrieved is configured using the configuration key presented above. You can also create your own instance, and pass your own configuration.

    This guide has shown how you can send emails from a Quarkus application. The mailer extension works in JVM and native mode.

    Mailer Configuration Reference