Change Log
GreenArrow v4.234.0
-
SimpleMH now supports multiple click and open tracker URL formats. See the X-GreenArrow-Tracker-Format documentation for more information.
-
Fixed an error in reporting of the disk queue size by
greenarrow disk_usage
when the disk queue is heavily used. -
Studio: Added support for autoresponders in both the “Subscriber Clicked Campaign” (now labeled as “Subscriber Clicked Campaign/Autoresponder”) and “Subscriber Clicked Link” clauses.
GreenArrow v4.233.1
- Fixed an issue where a queue was not flushed and a small percentage of messages could be lost in specific configurations.
GreenArrow v4.233.0
- Internal changes for GreenArrow Cloud.
GreenArrow v4.232.0
-
Added a new delivery_paused configuration directive. This is also available on the UI and API. This configuration will cause deliveries from a specific IP address to be paused in a fashion similar to the effect of pausing deliveries of individual sends in Engine’s UI.
-
Reduced GreenArrow’s CPU utilization when the disk queue has been idle for a long period of time.
GreenArrow v4.231.0
-
Added a new configuration directive replace_content_domain for changing domain names in content at the time of delivery based upon the IP Address or Relay Server used for delivery. See our documentation about this feature for more information.
-
Studio will now send remaining seeds “as fast as possible” once all campaign recipients have been sent. This fixes an edge case where you could pause a campaign after it had sent to all recipients (excluding seeds), leading to the campaign crashing.
GreenArrow v4.230.5
- Fixed an issue in Studio’s TinyMCE editor where the “Campaign Images Browser” would spin forever after uploading a new image.
GreenArrow v4.230.4
- Fixed an issue regarding migrations when upgrading from very old versions of GreenArrow. Previously individual migrations might call
greenarrow_config reload
; instead, this is now performed automatically afterhvmail_migrate migrate
is run.
GreenArrow v4.230.3
- Fixed an issue where the
GREENARROW_LOG_SMTP_COMMANDS
debug logging option on SMTP services would cause all authenticated incoming SMTP sessions to fail.
GreenArrow v4.230.2
- Fixed a UI error when viewing IP addresses and no settings were present in
greenarrow.conf
.
GreenArrow v4.230.1
-
Added an option file
/var/hvmail/control/opt.simplemh.debug
to enable more detailed logging in the SimpleMH service. -
Fixed a bug in the suppression list user interface where you could errantly get a “Mailing List cannot be set” error.
GreenArrow v4.230.0
-
SimpleMH will now always report the user agent of clicks and opens in the engine_click and engine_open Events. This was formerly controlled by the value of the
/var/hvmail/control/opt.simplemh_tracking_include_user_agent
file. -
Marketing Studio will now report the user agent of clicks and opens in the studio_click and studio_open Events.
-
Added a new
synchronous
attribute on bounce_all Events. -
Studio: Add a new type of suppression list that is not applied by default. See our Suppression List documentation for more information.
-
Studio: Add a segmentation criteria “Not In Suppression List” that can be used to segment on the new type of suppression list.
-
Increased the number of open files that Passenger may open. This resolved an issue where the web interface could display “Internal server error” instead of the requested content when under a high load.
-
Added support for RFC 8058 (List-Unsubscribe-Post) three ways.
-
SimpleMH: Added support for a
X-GreenArrow-List-Unsubscribe-HTTP-URL-Post
header.- If you are specifying a HTTP/HTTPS URL to be used in the
List-Unsubscribe
header by using theX-GreenArrow-List-Unsubscribe-HTTP-URL
header, then you can now also specify the value of theList-Unsubscribe-Post
header by adding aX-GreenArrow-List-Unsubscribe-HTTP-URL-Post
header. - The value of
X-GreenArrow-List-Unsubscribe-HTTP-URL-Post
will set theList-Unsubscribe-Post
header in the final message. - If
X-GreenArrow-List-Unsubscribe-HTTP-URL
is not specified, this header will not be used.
- If you are specifying a HTTP/HTTPS URL to be used in the
-
SimpleMH: If
X-GreenArrow-List-Unsubscribe-HTTP-URL
is not specified, an HTTPS unsubscribe link will be added toList-Unsubscribe
automatically.- Previously, the
List-Unsubscribe
header added by SimpleMH included only amailto
address. - Now, the
List-Unsubscribe
header added by SimpleMH will also include an HTTPS unsubscribe link and aList-Unsubscribe-Post
header will be added as well. - That unsubscribe link requires confirmation unless a POST is issued to it.
- Previously, the
-
Marketing Studio: All email sent from Marketing Studio will now include the
List-Unsubscribe-Post
header.- This header enables one-click unsubscribe workflows in some email readers.
- Previously, Marketing Studio’s unsubscribe page never required confirmation when
using the HTTPS unsubscribe link found in the
List-Unsubscribe
header. With this release, a confirmation click will be required if the user has JavaScript is disabled.
-
GreenArrow v4.229.1
- Fix an issue introduced in v4.228.2 where in Engine’s “SMTP Server Stats” tab, the popup of Failure messages failed to dismiss.
GreenArrow v4.229.0
-
Add support for the Ubuntu 20.04 Linux distribution.
-
Add the
hvmail_snapshot_stats
command which, records system statistics snapshots for GreenArrow support. -
Make the hvmail_unmanged_backup command ignore sockets recently added to GreenArrow. Before this release, the new sockets caused the script to print two harmless
socket ignored
notices.
GreenArrow v4.228.3
-
Make the permissions of the
/var/hvmail/studio/gems
directory more restrictive. -
Update PHP from 7.3.28 to 7.3.29.
GreenArrow v4.228.2
-
Fixed a visual issue in the Engine “sends” page where a long send name could cause the table to appear broken.
-
Performance optimization to the “Distribute Unsubs / Bounces / Spam Complaints” feature.
-
Upgrade jQuery to 3.6.0
GreenArrow v4.228.1
-
Update third-party software that ships with GreenArrow:
GreenArrow v4.228.0
-
GreenArrow now supports version 1 of HAProxy’s PROXY Protocol for SMTP delivery. This is configured with the proxy_server directive. See the Proxy Protocol documentation for more information.
-
The “SMTP Server Stats” each-message report can now be filtered by the SMTP result code.
-
Fix an issue where messages injected while the GreenArrow MTA is being restarted could show up twice in statistics.
-
Fixes in preparation for an upcoming conversion of subscriber IDs to be 64-bit integers.
GreenArrow v4.227.3
- Add a missing package to dependencies: shared-mime-info
GreenArrow v4.227.2
-
Eliminate the fade-on-hover effect on the dynamic delivery charts.
-
Fixed an issue that could cause autoresponders to send duplicate messages.
GreenArrow v4.227.1
- Fixed an issue introduced in v4.227.0 which caused some SMTP log messages to be logged incorrectly.
GreenArrow v4.227.0
-
Delivery Attempt Events now include
mx_hostname
andmx_ip
. -
Updated the processed logfile format to include
mx_hostname
andmx_ip
. -
Add option file
/var/hvmail/control/opt.send_api_debug_log
to write details about HTTP Submission API requests to the Apache error log.
GreenArrow v4.226.1
- Reduce memory requirements of downloading Marketing Studio campaign/autoresponder statistics.
GreenArrow v4.226.0
-
Add support for 2048-bit DH keys to GreenArrow’s SMTP services.
-
Add new bounce processor rules.
-
Fix a bug where NUL bytes (0x00) in a subscriber import would cause the import to fail.
GreenArrow v4.225.0
-
Fix a bug that prevents the default HTTPS VirtualHost from loading the intermediate certificate specified by tls_certificate_files.
-
The control file
/var/hvmail/control/opt.simplemh_tracking
was previously an undocumented feature that enabled both/var/hvmail/control/record_events.simplemh.open
and/var/hvmail/control/record_events.simplemh.click
. This file has been removed. If the file was enabled, the two individual control files will be turned on. -
/var/hvmail/bin/logdir_select_time
now supports LZOP compressed log files. -
Fix an issue with GreenArrow Docker integration where initialization of new volumes would fail on recent releases.
GreenArrow v4.224.0
-
Expand the ability to import and export throttle rules on the command line to support Throttle Templates. Previously, only throttle rules assigned to specific IP addresses could be imported and exported.
-
Remove the “Fullscreen” menu option when TinyMCE is launched from the campaign editor. That editor is already fullscreen and using it caused a graphical glitch.
GreenArrow v4.223.0
-
GreenArrow has a new disk-queue. This disk-queue uses a new data format. Your existing queue will be automatically converted to the new format. If you run into trouble and choose to downgrade, follow the downgrade instructions here.
-
Messages will no longer receive a final delivery attempt after expiring. Instead, the expiration time is compared to the next retry time after each delivery attempt. If the next retry time is beyond the expiration time, the message is treated as expired and bounces.
-
Added retry_time directive for overriding the retry time of messages on a per-VirtualMTA and/or per-domain basis. Using this directive, you can specify your own retry schedule.
-
Added queue_lifetime directive for overriding how long messages will be retried on a per-VirtualMTA and/or per-domain basis.
-
Fix a bug that caused
hvmail_report
’s processed logfile format to omit the SendSliceID field unless the--human
option was used. This could break compatibility for integrations depending on the order ofhvmail_report
’s output of the last 3 fields (SendSliceID, throttleid, and clicktrackingid).
GreenArrow v4.222.0
- Update the SMTP sink service to use GreenArrow Sink. This change speeds up the sink service. The sink no longer delays delivery by 1 second.
- Studio: Fixed an issue causing Special Sending Rule previews to falsely claim a URL domain or bounce email was deleted.
GreenArrow v4.221.0
- Internal changes for GreenArrow Cloud.
GreenArrow v4.220.2
- Studio: Campaign attachments will now have the correct Content-Type set for Microsoft Office documents.
GreenArrow v4.220.1
-
SimpleMH: Fixed an issue where HTML entities that don’t end in semicolons would be decoded when click tracking. For example, HTML with a link to
http://example.com/?a®=123
would be decoded ashttp://example.com?a®=123
. HTML entities now must end in a semicolon to be decoded. -
Engine: Fixed an issue in the event processor where a remote database connection that has encountered an error would continue to be tried.
GreenArrow v4.220.0
-
Add a new soft bounce rule to the bounce processor.
-
Update third-party software that ships with GreenArrow:
GreenArrow v4.219.0
-
Add a tool for viewing the remote connections that are currently open from the MTA. See this documentation for more information.
-
Engine: Update the HTTP Submission API to allow setting a custom Date header with the
headers
hash. -
Studio: Users can now change their default campaign HTML editor. This option does not affect existing campaign contents. See our user documentation for more information.
-
Engine: Make the hvmail_init status command report on the disk-queue’s
ok
file status. It previously only reported that file’s status for the ram-queue and bounce-queue. -
Studio: Updated SQL used by some segmentation criteria that could lead to slow starts to campaigns.
GreenArrow v4.218.0
-
Fix a configuration issue that could allow anonymous FTP logins if the
/var/ftp/
directory exists. -
Engine: smtpd services will now log a message that looks like this when it cannot parse AUTH input:
smtpd: smtp-auth authentication failure from (HOST) for username (unknown) with reason (malformed auth input)
-
Fixed an issue where some DKIM keys may not be used for signing.
GreenArrow v4.217.0
-
On December 14-15, 2020, Google sent out “The email account that you tried to reach does not exist” bounces for valid email addresses. This caused any such email addresses sent to during this time to be considered a bad address and deactivated.
We’ve added a greenarrow bounce_recovery tool to enable recovery from these erroneous bounces.
This page dedicated to the December 2020 Gmail Outage details how to recover from this specific outage.
-
Studio: Fixed an issue that prevented API keys that had created subscriber imports from being deleted.
-
Studio: Fixed an error that could appear in TinyMCE related to subscriber quotas.
-
Engine: Incorporated a new DKIM library that will eliminate sporadic generation of invalid signatures.
-
Engine: Changed the default DKIM signing algorithm from SHA1 to SHA256. The applies to both new and existing installs.
GreenArrow v4.216.0
- Added new columns to the Campaign Statistics Index export file:
- Campaign ID
- Subject (newline separated when more than one is present)
- Accepted
- Total Renders / Opens
- Total Render / Open rate
- Total Clicks
- Total Clicks rate
- Segment (if a named segment was used)
-
Added the number of “Accepted” messages to Studio’s statistics index.
- Fixed an issue wherein GreenArrow’s “Received:” header could simply be written as “Received: from unknown”.
GreenArrow 4.215.0
-
Fixed CVE-2011-0411: Plaintext command injection in multiple implementations of STARTTLS
-
Add support in User Defined JavaScript for Extending BEE Custom Rows with content dialog.
GreenArrow 4.214.0
-
GreenArrow can now run in SELinux permissive mode. Before this release, SELinux had to be disabled. SELinux enforcing mode remains unsupported.
-
Upgrade GreenArrow’s version of Highcharts to the latest release - 8.2.2.
GreenArrow 4.213.0
-
Upgrade TinyMCE to the current release (5.5.1).
-
Updates to the following third-party software that ships with GreenArrow:
GreenArrow 4.212.0
-
Studio: Anniversary autoresponders in Studio were using their delay settings inverted of what was intended. So if you have an anniversary autoresponder set to send “2 days before at 6pm”, it would actually send “2 days after at 6pm” (the reverse is also true - so “4 days after at 12pm” would be treated as “4 days before at 12pm”). This behavior has been fixed.
See GreenArrow Updates for information on updating existing autoresponders to maintain the old behavior.
-
Studio: Fixed an issue that could cause subscriber import deactivations to take an exceptionally long time.
-
Engine UI: Reword “SMTP Deferral Percentage” to be “SMTP Deferral+Failure Percentage”. The functionality has not changed - we’ve updated the label to better reflect the existing behavior.
-
Engine UI: Dynamic delivery charts date ranges should now be more accurate and reliable. Previously there was a mix of web browser and server time zones being used; now the charts use only the server time zone.
-
Engine/Studio: Fix a bug that caused the default HTTPS TLS certificate to take precedence over httpd.ssl.listen entries that did not specify a server name.
-
Upgrade TinyMCE to the current release (5.5.1).
GreenArrow 4.211.0
- Updated the Mailing List, Templates, and Campaigns tables so that each column can be used to sort the table.
GreenArrow 4.210.0
- Remove a limitation that prevents domain wildcard entries like
*.example.com
from being used when define_virtual_mtas_in_config_file is enabled.
GreenArrow 4.209.0
-
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
- 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
- Add attachment support to the HTTP Submission API.
- Add support for CentOS 8 and Red Hat Enterprise Linux 8 Linux distributions.
GreenArrow 4.205.0
- 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
-
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
- 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
-
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
- 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
- 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
- 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
, andsmtpdaemon
- For Debian-based Linux distributions, the marker restored is:
mail-transport-agent
- For Red Hat-based Linux distributions, the markers restored are:
- 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
-
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
-
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.
GreenArrow 4.200.0
- 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