GreenArrow Email Software Documentation

Change Log

GreenArrow 4.209.0

August 21, 2020
  • Update GreenArrow’s Docker container support to work with both CentOS 7 and Debian 10. Previously, only CentOS 7 was supported. See our drhinternet/greenarrow-docker Github repository for more information on how this beta feature works.

  • Updated the remote list retry schedule. Formerly, connections to remote list databases would get a total of 3 attempts in quick succession prior to marking the campaign as failed. The new retry schedule will make a total of 11 attempts with 30 seconds between each attempt.

  • Fix an issue that could cause Studio campaigns to fail with links longer than 2,712 bytes.

GreenArrow 4.208.0

August 17, 2020
  • Added a new configuration option to the Event Processor that allows events to be delivered to HTTP endpoints as JSON, instead of form data. The option use_json_for_http_post can be set globally or on individual event destinations.

GreenArrow 4.207.0

August 4, 2020

GreenArrow 4.205.0

July 29, 2020
  • New segmentation criteria - “Date Deactivated” - this allows you to find subscribers that were deactivated on a specific date (or date range). See the Segmentation Builder documentation for more information.

GreenArrow 4.204.1

July 28, 2020
  • Fix an issue introduced in GreenArrow 4.203.0. An interaction between throttle limits and connection reuse could cause some throttle groups to lock up, causing delivery attempts to that throttle group to stop.

  • Support for installing GreenArrow in Docker is now in beta. See our drhinternet/greenarrow-docker Github repository for more information on how this works.

GreenArrow 4.204.0

July 28, 2020
  • You can now save custom rows for reuse in our responsive content editor. Custom rows are associated with a single mailing list, but can easily be used for campaigns on other lists. Read more in our content editor documentation.
    • You must access Studio via HTTPS in order to use custom rows.

GreenArrow 4.203.0

July 23, 2020
  • The criteria for outgoing SMTP connection reuse has changed.

    The previous behavior only reused connections when the domain of the recipient email address matched an available connection’s domain.

    The new behavior reuses connections when all of the following are true:

    • The recipient’s domain is part of the same throttle rule in GreenArrow as an available connection’s original recipient domain.
    • The destination IP of the available connection matches at least one IP of the MX record returned by the recipient’s domain.
    • The TLS status of the connection meets the requirement of the starttls_use and starttls_require directives.

    This allows for more connection reuse.

GreenArrow 4.202.2

July 16, 2020
  • When creating new IP addresses, if there is exactly one throttling template, it will be selected as the default when the form loads.

GreenArrow 4.202.1

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.

GreenArrow 4.202.0

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.

GreenArrow 4.201.0

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.

GreenArrow 4.200.1

June 15, 2020

GreenArrow 4.200.0

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

Copyright © 2012–2020 GreenArrow Email