ÃÛ¶¹ÊÓƵ

Email service

Send emails from AEM as a Cloud Service by configuring AEM’s DefaultMailService to use advanced networking egress ports.

Because (most) mail services do not run over HTTP/HTTPS, connections to mail services from AEM as a Cloud Service must be proxied out.

Since secrets must not be stored in code, the email service’s username and password are best provided using secret OSGi configuration variables, set using AIO CLI, or the Cloud Manager API.

Typically, flexible port egress is used to satisfy integrating with an email service unless it is necessary to allowlist the ÃÛ¶¹ÊÓƵ IP, in which case dedicated egress ip address can be used.

Additionaly, review AEM documentation on sending e-mail.

Advanced networking support

The following code example is supported by the following advanced networking options.

Ensure the the appropriate advanced networking configuration has been set up prior to following this tutorial.

OSGi configuration

This OSGi configuration example configures AEM’s Mail OSGi Service to use an external mail service, by way of the following Cloud Manager portForwards rule of the operation.

...
"portForwards": [{
    "name": "smtp.mymail.com",
    "portDest": 465,
    "portOrig": 30465
}]
...

Configure AEM’s DefaulMailService as required by your email provider (e.g. smtp.ssl, etc.).

{
    "smtp.host": "$[env:AEM_PROXY_HOST;default=proxy.tunnel]",
    "smtp.port": "30465",
    "smtp.user": "$[env:EMAIL_USERNAME;default=myApiKey]",
    "smtp.password": "$[secret:EMAIL_PASSWORD]",
    "from.address": "noreply@wknd.site",
    "smtp.ssl": true,
    "smtp.starttls": false,
    "smtp.requiretls": false,
    "debug.email": false,
    "oauth.flow": false
}

The EMAIL_USERNAME and EMAIL_PASSWORD OSGi variable and secret can be set per environment, using either: