Change Log

July 9, 2020

Fix a bug that could allow GreenArrow Engine web interface users with a -statsonly suffix to view non-stats pages in GreenArrow’s web interface.

July 8, 2020

Add support for triggering Studio Anniversary Autoresponders with global custom fields.
Update GreenArrow’s packages to mark them as providing email related capabilities. This corrects a bug introduced in GreenArrow 4.200.0, where these markers were removed.
- For Red Hat-based Linux distributions, the markers restored are: /usr/sbin/sendmail, MTA, and smtpdaemon
- For Debian-based Linux distributions, the marker restored is: mail-transport-agent
Sending the alarm signal to the disk-queue (svc -a /service/hvmail-disk-qmail-send) now causes all queued messages in the disk-queue to be retried. This speeds up dumping messages from the disk-queue.
Dynamic Delivery charts will no longer show an error regarding falling behind on new installations of GreenArrow.

June 24, 2020

Added an option https_verify_peer to the Event Processor configuration. This option allows you to disable HTTPS certificate verification during event delivery.
Added an option https_client_certificate to the Event Processor configuration. This option allows you to set an HTTPS client certificate to be included event delivery to HTTPS destinations. This is useful if the destination server requires client certificate authorization.
The list of trusted Certificate Authorities used by the Event Processor has been updated.
Added an option commit_batch_size to the Event Processor configuration. This option can provide increased event delivery performance.
New configuration directive lets_encrypt_registration_server. This lets you override the Let’s Encrypt registration server, useful for testing without impacting your Let’s Encrypt Rate Limits.
Increased frequency of event delivery, leading to a significant increase in the Event Processor’s throughput.
A new value (mtaid_exists) is available to custom code that’s run during delivery attempts.

June 15, 2020

Added documentation how to process clicks and opens behind a proxy server
In reaction to Google Chrome 84 blocking insecure downloads from secure (HTTPS) contexts, GreenArrow now uses HTTPS for communication when using the responsive content editor.

As such, we continue to recommend that you use GreenArrow’s Let’s Encrypt integration.

To avoid warnings or errors in the responsive content editor, ensure that you have a valid certificate for either the domain in /var/hvmail/control/me or use the new bee_images_domain configuration directive.
Improved the appearance of very large message counts in Dynamic Delivery Statistics.

June 1, 2020

Unified GreenArrow Engine and GreenArrow Studio into a single “greenarrow” package
Unified GreenArrow’s miscellaneous non-Engine and non-Studio packages into a single “greenarrow-support” package
Reduced the disk space requirements of GreenArrow packages

Before GreenArrow version v4.200.0, Engine and Studio maintained separate changelogs. Refer to the Historic Engine Changelog or the Historic Studio Changelog for those versions