​

RafaleMTA API

(EN)

​

INTRODUCTION

​

RafaleMTA is a synchrone SMTP relay, that is to say that unlike traditional systems which put the received messages in a queue before sending them (store & forward), RafaleMTA relays the message immediately after its reception (post phase DATA), during the SMTP session, and returns the original acknowledgment message from the remote server.

​

The advantage of this system is that it allows you to instantly know the result of the transmission from the remote mail server, and thus know if the email has been delivered, or if not, if the address is a hard bounce or even identify possible blocking of IPs or sender domains.

​

The system must therefore be sized upstream to allow the establishment of as many simultaneous incoming as outgoing SMTP sessions, whether they are public IP address ranges, or dynamic Cloud instance IPs (eg: EC2).

​

The management of deliverability being ensured by the system, in particular the sending volumes per time unit, by outbound IP and by destination domain, as well as the temporary suspension of sending in the event of blocking, it can occur that instantaneous resources are not sufficient to carry traffic immediately. For this purpose, timeouts can be specified in the message routing parameters (email header or JSON variable).

​

In the same way, when a blacklisting is detected, the system performs transparently - to the extent of the available resources - other transmission attempts from other transmitting IPs. The number of fallbacks and their notification in the form of temporary messages are configurable.

​

Sending messages can be done either by SMTP relay or via a RESTful / JSON API.

​

RafaleMTA also includes a mailing list management system (newsletters and acquisition campaigns) which takes care of all the technical steps necessary to carry out an end-to-end campaign: mailing list expansion recipients, personalization and DKIM signature of messages, routing with deliverability management, tracking of openings and clicks, recording of unsubscriptions, publication of real-time statistics and production of logs and detailed reports.

​

Sending campaigns is done through a RESTful / JSON API.

​

The description of the JSON objects used in the headers of emails relayed in SMTP as well as in the RESTful requests of the message and campaign APIs, is detailed in section 6.

​