GreenArrow Email Software Documentation

Getting Started with Email Injection

When injecting email into GreenArrow Engine, there are two portions of the configuration that need to be set up.

Injecting to GreenArrow

SMTP Credentials

Typically most customers inject to GreenArrow via SMTP. For SMTP injection you will need at least a hostname and port number. The hostname will be your server’s primary domain - this is the URL you see on your GreenArrow Engine web interface. For example, if you see this URL when you open GreenArrow’s web interface, then your SMTP host will be If you are Cloud customer, see the notes for cloud customers below.

We recommend using port 587 for injection. It separates your injected traffic from regular traffic that comes into port 25 such as bounces and spam complaints.

In order to authorize an injecting server you must either assign a Username / Password (this is also called SMTP AUTH), or authorize the IP address where the email will be coming from.

In summary:

  • SMTP hostname: your server hostname as explained above
  • SMTP port: 587
  • SMTP encryption: None (or STARTTLS, if you set up GreenArrow to support encryption)
  • SMTP username: (skip if using IP authorization) email address created as explained above
  • SMTP password: (skip if using IP authorization) password

Other SMTP ports can be used for injection but only 25 and 587 are enabled on a newly installed server. To see all available options, check out the SMTP services documentation

Mail Classes and Message attributes

Once you’re authorized to inject, you’ll need to tell GreenArrow how to handle the email that it receives from your application.

GreenArrow Engine uses Mail Classes to define various attributes for the email you’re injecting.

A Mail Class defines things like what VirtualMTA and URL Domain you want to use, or whether you want click + open tracking enabled.

Once you have your Mail Class set up, you’ll need to use a header to define what Mail Class a particular email should be a part of (or another method, if you’re unable to add custom X- headers to your emails)

Getting data back from GreenArrow

After GreenArrow sends an email there will be some additional data that GreenArrow collects, which typically needs to get back to the source of the email.

For example, GreenArrow Engine and Studio have integration built in to automatically update the subscribers’ status when there is a bounce or spam complaint. Since there isn’t this integration with 3rd party applications that generate the email, you must do some additional steps to make this happen so that your application has the most current subscriber data (so you’re not continually sending to bad addresses).

Your GreenArrow server can log event data when various things happen in GreenArrow that your injecting application needs to “know” about. These are the different Types of Events that you can push back to your application.

And these are the different methods that you have to get this data back to your server. And here is how to configure the delivery methods.

GreenArrow Engine will not start logging events until you configure it to do so. Instructions on how to enable event collection can be found in this document.

Notes for Cloud Customer

Your SMTP hostname has the form Port 587 on your Cloud server has been configured to use SimpleMH. It also accepts encrypted connections with STARTTLS for added security.

For authentication, we recommend setting up a username and password as explained above. If you need to authorize IP addresses for relay, contact our technical support team and they will guide you through the process.

Email injected into port 587 will be assigned the mail class default unless you override those settings with custom headers.

To setup Event Delivery methods and event collection, choose one or more delivery methods and events to collect, and contact our technical support team with that information.

Copyright © 2012–2024 GreenArrow Email