Tracking Bounced Emails tracking-bounced-emails

AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.
Adobe does not plan to further enhance tracking of opened/bounced emails send by AEM SMTP service.
The recommendation is to leverage Adobe Campaign and its AEM integration.

When you send a newsletter to many users, there are usually some invalid emails adresses in the list. Sending newsletters to those addresses bounce back. AEM is capable of managing those bounces and can stop sending newsletters to those adresses after the configured bounce counter is exceeded. By default, the bounce rate is set to 3 but is configurable.

To set AEM up to track bounced emails, you need to set up AEM to poll an existing mailbox where bounced emails are received (usually this is the “from” email address that you specify where you send the newsletter). AEM polls this inbox and imports all emails below the path specified in the polling configuration. A workflow is then triggered to search for the bounced email adresses within the users and updates the bounceCounter property value of the user accordingly. After the configured max bounces is exceeded, the user is removed from the newsletter list.

Configuring the Feed Importer configuring-the-feed-importer

The feed importer lets you repeatedly import content from external sources into your repository. With this configuration of the feed importer, AEM checks the sender’s mailbox for bounced emails.

To configure the feed importer for tracking bounced emails:

  1. In Tools, select the Feed Importer.

  2. Click Add to create a new configuration.


  3. Add a new configuration by selecting the type and by adding information to the polling URL to configure the host and port. In addition, you need to add some mail and protocol-specific parameters to the URL query. Set the configuration to poll at least once a day.

    All configurations need information about the following in the polling URL:

    username: The username to use for connecting

    password: The password to use for connecting

    In addition, depending on the protocol, you can configure certain settings.

    POP3 configuration properties:

    pop3.leave.on.server: Defines whether to leave messages on server or not. Set to true to leave messages on server, false otherwise. Defaults to true.

    POP3 examples:

    table 0-row-2 1-row-2
    pop3s:// Using pop3 over SSL to connect to GMail on port 995 with user/secret, leaving messages on server by default
    pop3s:// pop3s://

    IMAP configuration properties:

    Allows you to set flags to search for.

    imap.flag.SEEN:Set false for new/unseen message, true for already-read messages

    See for the full list of flags.

    IMAP examples:

    table 0-row-2 1-row-2 2-row-2
    imaps:// Using IMAP over SSL to connect to GMail on port 993 with user/secret. Getting new messages only by default.
    imaps:// Using IMAP over SSL to connect to GMail 993 with user/secret, only getting already seen message.
    imaps:// Using IMAP over SSL to connect to GMail 993 with user/secret, getting already read OR new messages.
  4. Save the configuration.

Configuring the newsletter service component configuring-the-newsletter-service-component

After configuring the feed importer, you need to configure the From address and the bounce counter.

To configure the newsletter service:

  1. In the OSGi console at <host>:<port>/system/console/configMgr and navigate to MCM Newsletter.

  2. Configure the service and save the changes when finished.


    The following configurations can be set to adjust the behavior:

    table 0-row-2 1-row-2
    Bounce Counter Maximum (max.bounce.count) Defines the number of bounces until a user will be omitted when sending a newsletter. Setting this value to 0 disables the bounce check completely.
    Activity No Cache (sent.activity.nocache) Defines the cache setting to use for the newsletter sent activity

    Once saved, the newsletter MCM service does the following:

    • Writes an activity to the users hidden stream upon successful sending of a newsletter.
    • Writes an activity if a bounce is detected and the users bounce counter changes.