Email is easy but using email effectively is hard. It's easy for an OpenInsight developer to use the rti_cdomail function to send an email message without concern for what happens to the message after the function returns. The process becomes a lot more difficult when the developer must deal with:
-
Un-subscription link tracking and response
-
Verifying message delivery from within code
-
Handling bounced messages
-
Each client site having a different mail server configuration
-
Bad email reputation delaying message delivery
With enough time and resources each of these challenges can be addressed by the developer and staff resources but the goal of this article is to leverage existing email services for use in OpenInsight to address these problems and reduce the use of staff resources to manage email.