AEM Communities Email Configuration

Once the default mail service is configured, the two existing instances of the AEM Communities Email Reply Configuration OSGi config, included in the release, become functional.

Only the instance for subscriptions needs to be further configured when allowing reply by email.

  1. [email](#configuration-for-notifications) instance

    for notifications, which does not support reply email, and should not be altered

  2. [subscriptions-email](#configuration-for-subscriptions) instance

    requires configuration to fully enable creating post from reply email

To reach the Communities email configuration instances:

chlimage_1-99

Configuration for Notifications

The instance of AEM Communities Email Reply Configuration OSGi config with the Name email is for the notifications feature. This feature does not include email reply.

This configuration should not be altered.

  • Locate the AEM Communities Email Reply Configuration

  • Select the edit icon

  • Verify the Name is email

  • Verify Create post from reply email is unchecked

chlimage_1-100

Configuration for Subscriptions

For Communities subscriptions, it is possible to enable or disable the ability for a member to post content by replying to an email.

  • Locate the AEM Communities Email Reply Configuration
  • Select the edit icon
  • Verify the Name is subscriptions-email

chlimage_1-101

  • Name : (required) subscriptions-email. Do Not Edit.

  • Create post from reply email: If checked, recipient of subscription email may post content by sending a reply. Default is checked.

  • Add tracked id to header: Default is Reply-To.

  • Maximum length of Subject: If tracker id is added to subject line, this is the maximum length of subject, excluding tracked id, after which it will be trimmed. Note that this should be as small as possible to avoid tracked id information from being lost. Default is 200.

  • Email “From” address: (required) Address that notification email would be delivered from. Likely the same SMTP user specified for the default mail service. Default is no-reply@example.com.

  • Reply-to-Delimiter: If tracker id is added to Reply-to header, this delimiter will be used. Default is + (plus sign).

  • Tracker Id prefix in subject: If tracker id is added to subject line, this prefix will be used. Default is post#.

  • Tracker id prefix in message body: If tracker id is added to message body, this prefix will be used. Default is Please do not remove this:.

  • Email as HTML: If checked, Content-Type of email will be set as "text/html;charset=utf-8". Default is checked.

  • Default user name: This name will be used for no name users. Default is no-reply@example.com.

  • Templates root path: The email is built using template stored at this root path. Default is /etc/community/templates/subscriptions-email.