Product Update - v6.4.2, December 2023

This is a minor product release and contains the following updates:

  • Support for List-Unsubscribe Header Configuration in Outbound Emails (sent via AWS SES route)
  • Enhancements for logging into Webex Connect via Webex SSO
    Please refer to the details below to learn about all the changes and enhancements.

📘

Release Date

The date of release will be communicated separately over an email.

Details

Added – Support for List-Unsubscribe Header Configuration in Outbound Emails (sent via AWS SES route)

We’ve introduced the option to add ‘List-Unsubscribe-Post’ and ‘List-Unsubscribe’ headers when sending emails using Webex Connect in combination with AWS SES.

List-Unsubscribe is an optional header that allows email recipients to opt-out from future email communications without the need to get redirected to the subscription management portal/pages. The recipient email client (such as Gmail) can use this information to create an Unsubscribe hyperlink right next to the ‘From’ address on the email received by the recipient (as shown in below screenshot). If the email recipient clicks this link, the unsubscribe event will be triggered and Webex Connect will send an unsubscribe notification to the outbound webhook configured by you.

To apply the ‘List Unsubscribe’ headers, you would need to enable the Unsubscribe settings toggle on the Email app asset configuration page within Webex Connect and then select the ‘Enable Unsubscribe Header’ checkbox. Once done, both the List Unsubscribe headers (List-Unsubscribe-Post for enabling one-click unsubscribe and List-Unsubscribe for passing the unsubscribe URL and mail-to address) will be added to emails sent using this email app asset.
If you want to skip these headers from certain outbound emails (e.g., emails that are not subscription-based), you can do so by configuring the list of email Sender Ids that you use for sending such emails in the ‘Skip Unsubscribe Headers for these Email Ids’ field.

One can pass both an unsubscribe URL as well as an email id that recipients can send an email to for unsubscribing from future emails. While Webex Connect automatically generates the unsubscribe URL to be passed, the mail-to email address needs to be configured under the ‘Unsubscribe Mail to Address’ field. Please note that you would need to enable inbound email processing to be able to use this feature, and it would be limited to regions where AWS SES supports inbound emails.

Please note that List-Unsubscribe header addition feature is currently in Beta. Refer Webex Connect documentation on email delivery best practices for more info on this.

Changed – Enhancements for logging into Webex Connect via Webex SSO

We launched the option to login to Webex Connect using Webex SSO in v6.3.0 in addition to the Webex Connect specific login credentials. As an enhancement to that, we have now added the option to restrict username and password-based login to Webex Connect once Webex SSO based login has been enabled. Please reach out to the support team if you would like to enable this feature for your tenant.

Important Additional Notes

  • As announced previously, we will soon be phasing out support for using standard voices for configuring new Text to Speech experiences as Azure has announced that it will be retired by 31st August 2024. Hence, we recommend you migrate your existing services from standard voice to neural voice, as well as not use standard voice option when configuring new voice services using Webex Connect APIs and/or flows.
  • Gmail and Yahoo Mail have announced a new set of requirements for email senders effective from February 2024. We highly recommend that you refer to these requirements and also follow email best practices covered in this article on our documentation portal.

Changelog

UpdateDescription
AddedSupport for List-Unsubscribe Header Configuration in Outbound Emails (sent via AWS SES route)
ChangedEnhancements for logging into Webex Connect via Webex SSO
FixedContent type in meta data for inbound attachments on MMS channel.
FixedMalware scanning is getting disabled when a Channel App Asset configuration is updated. This applies only to Webex CC integrated Webex Connect tenants.
FixedDuplicate delivery receipts for some in-app messages. [INC0184453
FixedStart node doesn't have the abc.timestamp output variable for Conversation Closed, Form Response, and Typing Indicator message/event types.
FixedScheduled export logs not working when ‘All existing and any new’ option is selected. [WxC-CS0020931]