Fast, flexible & efficient delivery software

Transcription

1 by Fast, flexible & efficient delivery software Built on top of industry-standard AMQP message broker. Send millions of s per hour. Why MailerQ? No Cloud Fast Flexible Many solutions require you to send your customer data to third parties. Keep your data secure on your own servers with MailerQ. It is just as easy to integrate. MailerQ is fast. Its sole purpose is to send s. Storing, queuing and prioritizing messages is done in a separate AMQP message broker. MailerQ gives you full control over d messages. Monitor delivery and intervene when necessary. Prioritizing and routing messages has never been easier. Download & install on your server Questions? Call us

2 What is MailerQ? MailerQ is a high performance Mail Transfer Agent (MTA) and is designed to deliver large volumes of messages at very high speeds. It uses RabbitMQ, the industry standard AMQP message software, to its messages. MailerQ offers maximum flexibility without compromising on stability or performance. What is RabbitMQ? RabbitMQ is open source AMQP message software. It allows you to easily create reliable first-in-first-out message s. MailerQ is built on top of RabbitMQ and uses RabbitMQ to store and prioritize messages. MailerQ focuses solely on the sending process. Download the latest version of RabbitMQ at RabbitMQ can be installed on both Linux and Windows servers. How MailerQ works MailerQ has one goal: fast and reliable delivery, but how does it work? You install the software on your own servers. MailerQ connects to your RabbitMQ server and retrieves messages from the RabbitMQ. Every message retrieved from the is sent through SMTP. MailerQ adjusts its send speed to the capacity of the receiving mail server. Installing MailerQ Installing the MTA on your server is easy: download MailerQ for Debian, Ubuntu or Red Hat based systems and install it either by double-clicking on the file, or with one of the following commands. Red Hat $ sudo rpm -i /path/to/mailerq-version.rpm Debian $ sudo dpkg -i /path/to/mailerq-version.deb Sending s with MailerQ Your application Outbox Consume JSON message Send by SMTP Internet Add to outbox JSON encoded Figure 1: Post your messages directly to RabbitMQ } "id": "1" "envelope": "[email protected]", "recipient": "[email protected]", "custom-property-name": " debug data that will be visible only in RabbitMQ message", "generated": " :00:00", "key": "message-store-key-where-body-can-be-found" "maxdelivertime": " :00:00", "maxattempts": 6, "ips": [" ", " "], JSON All messages in the RabbitMQ message are coded in JSON. The JSON input for every message consists of at least the envelope address, recipient, and the body in MIME. Other properties can be added for additional delivery settings. 2

3 3 ways to get messages into RabbitMQ 1. Post directly to RabbitMQ Publish a JSON encoded message directly into RabbitMQ's outbox. MailerQ reads the message from the and sends the through SMTP. (See figure 1) 2. Use MailerQ's built-in SMTP server Configure your servers and/or software to use MailerQ as SMTP server. MailerQ opens an SMTP port and messages sent to the port are automatically added to the. MailerQ reads from this and delivers the Run MailerQ as command line utility Start MailerQ as a command line utility (like Postfix or Sendmail). MailerQ reads messages from standard input, converts them into JSON and publishes them to RabbitMQ. Chaining and clustering MailerQ instances can be connected in two different ways: chaining and clustering. When MailerQ instances are placed in sequence (chaining), messages are sent from one instance to another through SMTP. Messages can be filtered and modified by adding your own scripts for example, to verify if an gets through spam filters, or to check if an contains viruses. (See figure 2) MailerQ instances can also be clustered. Clustered MailerQ instances communicate through a shared message. This way each MailerQ instance knows exactly what other instances are active. If a message cannot be sent by one MailerQ instance (for example, because the desired IP address is not available on the server), MailerQ will automatically pass the message on to an instance that can send it. 1 by SMTP 2 Internet Inbox Your script Outbox Inbox Your script Outbox Figure 2: MailerQ instances placed in sequence (chaining) MailerQ configuration Many things can be configured in MailerQ: Domains Deliveries MySQL PostgreSQL IP addresses DKIM keys And more... SQLite This configuration is stored in a relational database. Your own applications may access this database and read or update its data. MailerQ reloads its entire configuration every few minutes and picks up changes automatically. Using a database is optional. MailerQ can also run without connecting to a relational database. 3

4 Improve your deliverability with MailerQ MailerQ delivers , anywhere and anytime. To Gmail, to Hotmail, and to remote servers anywhere in the world. You can configure MailerQ's delivery settings on a global, IP, domain, and even individual message level. All you have to do is update the settings in the database, use the MailerQ management console, add the delivery properties to the JSON, or meta fields to the MIME header. Automatic retries Domain limits DKIM support 15 DKIM MailerQ returns messages that cannot be delivered to RabbitMQ. Here they are stored in temporary s and are retried automatically. The interval between retries increases with every retry. This process continues until the is delivered. Configure retries yourself and set a retry limit, maximum delivery time, or the retry interval. Some mail servers limit the number of connections or deliveries from a single IP address. You can specify from which IP addresses an can be sent. If the first IP address is unavailable, MailerQ will automatically send your from the first available IP address. You can also configure MailerQ to send the from specific IP addresses. MailerQ supports DKIM. Store your private keys in the database or add them using the MailerQ management console. 4

5 MailerQ management console Deliverability in the management console MailerQ comes with a web-based management console, For example: set MailerQ to temporarily pause sending to where you adjust deliverability settings on the go. Monitor domains that give the response 'connection rate limit real-time performance of your IP addresses, reroute s to exceeded' and slowly build up connections after the pause. other IP addresses or set up flood patterns to react to server responses. Adjust these settings, and more in your browser. Live monitoring and logging One of the cool features of the MailerQ management console Per domain performance is its live SMTP monitor. A HTML WebSocket connects to the Zoom in on a single IP address to get a detailed picture of core MailerQ process. SMTP traffic received and set by MailerQ is sent to this WebSocket. Keep an eye on everything that their global and per domain performance or check the overall performance of your IP addresses on a single domain. This is is happening from your browser window. updated in real-time, making it easy to instantly adjust settings to improve deliverability where needed. MailerQ stores all details of send attempts in its log files. If an attempt fails the logs show exactly what happened. For throttling example '[email protected]' does not exist, or MailerQ limits the amount of attempts, connections and the 'mailbox unavailable'. amount of messages over a single SMTP connection to specific domains. All settings can be adjusted on the fly in the management console. "The management console allows you to adjust deliverability settings on the go" Use your own scripts to easily handle results and notify you when an error persists. There is no need to set up throttling for example, hotmail.com, live.com as well as outlook.com. MailerQ recognizes domains that use the same mail servers and groups them automatically. Flood patterns Set up MailerQ to respond to specific errors from receiving mail servers. These flood patterns will automatically react to these responses and overrule the default throttling settings. 5

6 Processing results All results are published back to RabbitMQ s. Your application can retrieve messages from these s and process the results. The result s MailerQ publishes JSON encoded messages to the RabbitMQ result s. The JSON output holds the same properties as the original message, making them easily recognizable for processing by your scripts and programs. MailerQ has four different result s: Results Failed Success Retry These s can be turned on or off and customized. Outbox Consume JSON message Send Add result to JSON Internet Retry If greylisted Retry Success Failed All results Retry s This stores transient results for all deliveries that have not yet failed or succeeded. These messages will be retried. Success and failed s These s are used for the messages that are delivered successfully or failed completely and receive a subset of the message published in the results. Results This is used by MailerQ to publish all results, both successful deliveries and failures. Benefits of the retry MailerQ moves messages that will be retried back into RabbitMQ. This way messages do not have to be moved through MailerQ constantly. These s are temporary, messages are retried at increasing intervals. Store messages in a NoSQL database To prevent MailerQ from loading messages from the at every send attempt, it can use a NoSQL database. By adding a unique key to the JSON that refers to the message body stored in the database, MailerQ can retrieve the message body associated with the key. The message body is only loaded from the database once an SMTP connection is made. Temporarily store message bodies NoSQL database Load message body once SMTP connection has been set up 6

7 JSON results The input and output JSON look similar. The only difference is the 'result' property that is added to the output JSON. Different types of results When MailerQ attempts to send an there are three possible outcomes: The message was delivered The message could not be delivered (fatal error) The message could not be delivered (reschedule) MailerQ adds a result property to the JSON at every outcome. The first two outcomes are published to the result, where your scripts can pick it up and process the message. The last outcome returns the message to a retry. Understanding the results Every attempted delivery adds a result property to the JSON. s with multiple retries keep their earlier results. If the delivery of an fails, the JSON will specify the reason for the failure under 'type' in the result property (e.g. refused, overflow, expired, nodata). You can read exactly what happened to the before it was sent in the RabbitMQ results. Expired messages Rescheduled s that fail because the maximum delivery time has expired are directly moved to the results. These message are not retried, but still show a result property that normally triggers a retry. } } "id": "1" "envelope": "[email protected]", "recipient": "[email protected]", "custom-property-name": " debug data that will be visible only in RabbitMQ message", "generated": " :00:00", "key": "message-store-key-where-body-can-be-found" "maxdelivertime": " :00:00", "maxattempts": 6, "ips": [" ", " "], "id": "1" "envelope": "[email protected]", "recipient": "[email protected]", "custom-property-name": "debug data that will be visible only in RabbitMQ message", "generated": " :00:00", "maxdelivertime": " :00:00", "ips": [" ", " "], "results": [ "attempt": 1, "time": " :00:20", "type": "error", "from": " ", "to": "receiving IP", "state": "mail from", "code": "421", "status": "4.7.0", "description": "[GL01] Message from(" ")temporarily deferred" }, ] } JSON input JSON output "attempt": 2, "time": " :00:36", "type": "success", "from": " ", "to": "receiving IP", "state": "accept", "code": "250", "status": "2.0.0", "description": "Message accepted for delivery" System requirements MailerQ is Linux based software, it runs on Debian based environments (Debian, Ubuntu, etcetera) and Red Hat based environments (Red Hat, Fedora, CentOS, etcetera). Before you install MailerQ you first need to have access to a working RabbitMQ (version ) message broker. Optional The MailerQ MTA supports a number of database engines: MySQL, SQLite and PostgreSQL. The configuration for domains (e.g. max delivery rate and max connect rate) is stored in a database. 7

8 MailerQ is made, maintained and supported by Copernica Marketing Software, a leading provider of high quality marketing software located in Amsterdam, The Netherlands. About Copernica Marketing Software With Copernica Marketing Software you can deliver relevant and timely communications using , sms, landing pages and PDF. MailerQ Copernica Marketing Software