Tracking Bounced Emails
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
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:
- In Tools , select the Feed Importer.
- Click Add to create a new configuration.
- 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 connectingpassword : The password to use for connectingIn 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:pop3s://pop.gmail.com:995/INBOX?username=user&password=secretUsing pop3 over SSL to connect to GMail on port 995 with user/secret, leaving messages on server by defaultpop3s://pop.gmail.com:995/INBOX?username=user&password=secret&pop3.leave.on.server=falsepop3s://pop.gmail.com:995/INBOX?username=user&password=secret&pop3.leave.on.server=falseIMAP configuration properties:Allows you to set flags to search for.imap.flag.SEEN :Set false for new/unseen message, true for already-read messagesSee https://java.sun.com/products/javamail/javadocs/javax/mail/Flags.Flag.html for the full list of flags.IMAP examples:imaps://imap.gmail.com:993/inbox?username=user&password=secretUsing IMAP over SSL to connect to GMail on port 993 with user/secret. Getting new messages only by default.imaps://imap.gmail.com:993/inbox?username=user&password=secret&imap.flag.SEEN=trueUsing IMAP over SSL to connect to GMail 993 with user/secret, only getting already seen message.imaps://imap.gmail.com:993/inbox?username=user&password=secret&imap.flag.SEEN=true&imap.flag.SEEN=falseUsing IMAP over SSL to connect to GMail 993 with user/secret, getting already read OR new messages.
- Save the configuration.