Download the PHP package fei/mailer-client without Composer

Mailer client

This is the client you should use to send email to Mail Api.

The client can use two kind of transports to send emails:

• Asynchronous transport implemented by BeanstalkProxyTransport
• Synchronous transport implemented by BasicTransport

BeanstalkProxyTransport delegate the API consumption to workers by sending email properties to a Beanstalkd queue.

BasicTransport use the classic HTTP layer to send emails.

If asynchronous transport is set, it will act as default transport. Synchronous transport will be a fallback in case when asynchronous transport fails.

Installation

Add this requirement to your composer.json: "fei/mailer-client": : "^1.0.0"

Or execute composer.phar require fei/mailer-client in your terminal.

Quick start

Let's start with a simple client :

Keep in mind that you should always initialize a mailer client by a dependency injection component, since it requires at least one dependency, which is the transport. Moreover, the OPTION_BASEURL parameter should also depends on environment.

Real world example

Below a more robust example which use the BeanstalkProxyTransport as default transport.

To work properly, BeanstalkProxyTransport needs a instance of a Beanstalkd server able to listen to its requests. Workers will consume Beanstalkd messages tube (or queue) and will send email data to Mail API server.

The message workflow:

Use the logger

Mailer client is Logger client aware. You could set a logger instance like this example below in order to activate logging functionality.

As is each mail sent will be recorded with logger service.

Email and attachments

Here a example if you need to send email with attachments :

Embedding attachment

Sometime, you need to include image (or other media) inline in your message. You could use a resource URL in order to linking the media but this approach is usually blocked by mail clients. A another approach is to embed your media directly into your message.

And that's it.

Catch them all

In non production environment, you often don't need to send email to the real recipient. For testing purpose, you could initialize the client with the option OPTION_CATCHALL_ADDRESS and all email will be forwarded to email address passed to this option.

Add callback functions before Mail instance validation

For different needs, you could registered a callback to apply on Mail to be send before its state validation.

You can see this as a another way to extends the "mailer-client" functionalities.

With this example, all Mail send with this client will have theirs recipients changed by [email protected].

We provide a couple of another method to manage callbacks:

• Mailer::addFirstCallbackBeforeValidation: append a callback on the first place of the stack to be executed in contrast to addCallbackBeforeValidation which place the callback in the end of the chain execution.
• Mailer::clearCallbackBeforeValidation: remove all callback registered in the stack

Pricer integration: meet the PricerMailer class

We provide a child class of Mailer for the Pricer need: PricerMailer.

PricerMailer extends functionalities Mailer plus a callback which apply email filtering on the Mail instance to be send. Naturally, you can remove this filter or add yours own.

Client option

Only one option is available which can be passed to the __construct() or setOptions() methods: