How to send email using MailerQ

MailerQ is a Mail Transfer Agent (MTA) that uses RabbitMQ, an AMQP message broker for queuing messages. One of the queues MailerQ creates within RabbitMQ is the outbox queue. This queue holds all messages that are waiting to be sent. MailerQ picks up the messages from this queue (which are JSON encoded) and sends the out over an SMTP connection.

After sending the email MailerQ publishes a JSON encoded copy to the result queue and, depending on whether the delivery was successful, into the success or failure queue. Here your own application or script can pick them up for further processing.

Sending email

There are three ways to send email with MailerQ, you can either:

Post email directly to the outbox queue

MailerQ fetches all messages from the RabbitMQ outbox queue. This makes using an application or script to directly publish messages to the outbox queue the fastest way to inject your emails into MailerQ. These messages should be JSON encoded, which makes it very easy because it is a widely known data format that can be easily created and processed by almost every program language out there.

The message queues can be easily accessed (add messages, remove messages) using the AMQP protocol, for which many plugins and libraries are available. To help you out, we have created a few examples for commonly used languages.

MailerQ put it in RabbitMQ

Besides being faster, publishing messages directly into the outbox queue also makes it possible to use special features that are not natively available when you use SMTP. When using SMTP you can add most of these features by adding special x-mq-* headers, which we will explain in the SMTP part of this article.

This means that when you cannot easily change or add e-mail headers publishing messages directly into the outbox queue is nessecary when you want to make use of these features.

Sending messages

As we mentioned above, to send out emails with the MailerQ MTA, you can simply add a message to the outbox message queue. This JSON encoded message should contain a minimum of three fields that hold the envelope email address, recipient's email address and full MIME message.

Minimal requirements for a JSON encoded email

That's it. In short, the minimal JSON encoded message to put in the queue therefore looks like this:

    "envelope": "",
    "recipient": "",
    "mime": "From:\r\n
             Subject:Example subject\r\n\r\n
             This is the example message text"

Note that for ease of reading we added some spaces to the message mime in the above example.

If you have a MailerQ license that includes the responsive email feature, you have several other options. You can read about them in the responsive email documentation

Using the built-in SMTP server

If you do not want to inject mails directly into the RabbitMQ message queue, you can send emails to the SMTP port that is opened by MailerQ. All messages sent to this port are received by MailerQ and are automatically published to the inbox queue as set in your config file. Most users set this to the same value as the outbox queue, so that all received emails are automatically published to the outbox queue, from which they are then directly picked up again and scheduled for immediate forwarding.

MailerQ shared inbox outbox queue

MailerQ stores all incoming messages in the inbox queue first. You can add intermediate scripts that process these messages before they are forwarded to the outbox queue. Would you like to add a script that does additional processing or filtering before a message is forwarded? Configure MailerQ to publish received messages in an inbox queue and let your scripts read these messages, from this inbox queue, to process or filter them. After that, post the message to the outbox queue where MailerQ picks them up to deliver them. You might be interested in AMQPipe, a high performance application that reads messages as fast as it can from a RabbitMQ message queue, runs your scripts to process these messages, and publishes the results back to RabbitMQ.

MailerQ seperate inbox outbox queues

SMTP and multiple IP addresses

If you run MailerQ on a server with multiple IP addresses, the SMTP server is available on all those addresses too. You can thus choose to which IP address to send your mail. MailerQ recognizes the IP address to which the mail was originally submitted, stores that information in the JSON message, and when the mail is finally forwarded to the internet, it will be sent out from exactly the same IP address. You should be aware that this can cause problems if you deliver your email to an IP address from which no external connections can be made (like

If you want MailerQ to send out the mail from a different IP address than that you originally sent it to, you can include an extra mime header field that instructs MailerQ to use a different IP instead.

MailerQ as command line utility

The MailerQ program can be started in two different modes: as a daemon process that runs all the time and sends out the messages, or as a command line utility that reads a message from standard input and publishes it to the inbox queue. As a command line utility, MailerQ does not attempt to send out the mail

MailerQ mime output

When you normally start up MailerQ, it operates as a daemon process. To start it as a command line utility for reading a message from standard input, you need to pass extra arguments to the program; either the email addresses of the recipients, or the option '--extract-recipients' to tell MailerQ that it should read in a mime message from standard input and filter out the destination addresses from it.

$ mailerq
$ mailerq --extract-recipients

The message read in by MailerQ is converted into a JSON encoded email message and published to the inbox queue. An other MailerQ daemon process can then pick it up from there and take care of the delivery.

End of message

MailerQ reads in all data from standard input until it encounters a line with a single dot on it. It treats this line as the end-of-message marker and will publish all data up to this dot (but not including the dot) to the inbox message queue.

This could become problematic if your email also contains lines that start with a dot. Such lines should of course not be treated as end-of-message markers. There are two ways to prevent this; you can either stuff those lines with an extra dot in front. MailerQ will automatically recognize this and remove the extra dot, or you can add the command line option '--ignore-dot' to instruct MailerQ that dots do not have a special meaning, and that the message is ended with end-of-file instead.

$ mailerq --ignore-dot
$ mailerq --ignore-dot --extract-recipients

Envelope address

The envelope address that MailerQ uses for sending out an email is automatically filtered from the message MIME (it can be set in the custom x-mq-envelope header, or in the return-path header). However, you can also set the envelope address manually with the '--envelope' command line option.

$ mailerq --envelope --extract-recipients

Message format

Messages that are read from standard input should be in MIME format. The headers should be seperated from the message data by a newline, and lines should end with either a newline character, or a linefeed+newline character.

Subject: Example message
x-mq-maxdelivertime: 2013-05-01 00:00:00

Example email data.
Email data ends when a single dot followed by new line character is send.

Sending emails from file

Because MailerQ reads in messages from standard input, you can use regular unix shell pipes and I/O redirection operators for sending mail.

$ cat email.txt | mailerq --extract-recipients --ignore-dot
$ mailerq --extract-recipients --ignore-dot < email.txt 

Using MailerQ in PHP mail() function

The PHP mail() function internally uses a command line utility (for example: "sendmail") to send out the mail. By modifying the configuration of PHP you can change this into "mailerq", so that all mails sent from PHP are automatically delivered by MailerQ.

To use MailerQ for sending emails in PHP using mail() function, set property "sendmail_path" in php.ini to:

sendmail_path = mailerq --envelope --extract-recipients --ignore-dot