In this release, we are fixing issues with how BLOX Email Reach notifications work when sent by the BLOX Notifier application.
- We are increasing the rate limit needed to query our email vendor's reporting API. This will help prevent reporting errors in the future. (MAILLIST-357)
- We will now scrape the asset page of an asset when sending a automatically-triggered or manually-triggered Email Reach notification. In order to get an email-friendly version of the page, we add ?mode=email to the end of the asset URL, and that is the version of the page that gets scraped (similar to how alerts worked in Email Reach itself). Manual messages created in BLOX Notifier that are not tied to an asset will still use the "simple HTML" format, since there is no page to scrape. (MAILLIST-356)