Build 2.2.3.0 (August 20, 2018)

This update is mostly related to inbox performance optimizations and adding transparency for soft and hard bounces. 

Check-in's for the '2.2.3 Branch:

  • 2018-08-17 - Users can no longer be deleted if they're the current user, or if they've generated registration codes.
  • 2018-08-17 - The new Bounce Details screen is now based on environment-specific, server-specific config settings. This is so that multiple servers/clusters can process bounces simultaneously - this change is related to scaling.
  • 2018-08-17 - Updated NuGet packages and TypeScript to the latest version.
  • 2018-08-17 - On the Edit Contact -> Activity -> Bounce screen, users can now click to see the details of a bounce message. Under Bounce Activity we show the date, mailing name, and type of bounce with a link to details. On Details we show the entire header and the message returned. We recognize two basic types of bounces, and we handle them differently. Hard bounces happen when an email can't be delivered. This can be caused by an invalid email address or an unexpected error during sending. Soft bounces are recognized by the email server, but are returned to the sender because the mailbox is full, there is a DNS failure, the message size is too large, the service is temporarily unavailable, the sender is a known spammer, SPAM is detected, the mail is blocked due to an attachment, the relay is denied, there was an auto reply, the bounce was transient, the mail was blocked at the subscribers request, the mail is configured with a challenge/response, or the email message was blocked for some other reason. Examining bounce headers can lead to fixing delivery problems that would be impossible to fix without header detail. Currently we only keep header information for 120 days [this length may be reduced later to conserve hard disk space].
  • 2018-08-14 - Additions to the Latest News & Features section.
  • 2018-08-14 - Fixed a bug in the naming of non-conflicting auto-provisioned sites.