Download the PHP package zfr/zfr-mail without Composer
On this page you can find all versions of the php package zfr/zfr-mail. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package zfr-mail
Short Description Lightweight abstraction around common mail API
License MIT
Homepage https://github.com/zf-fr/zfr-mail
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package zfr-mail
ZfrMail
ZfrMail is a lightweight abstraction around common mail API. It provides only a way to send a message (or templated mail if the provider
Dependencies
- PHP 7.0+
- Guzzle 6.0+
Installation
Installation of ZfrMail is only officially supported using Composer:
Usage
Creating a mail
The first thing is to create a mail. Mails are immutable and follow a similar logic to PSR-7 objects. There are two different kinds of mails in ZfrMail:
- Rendered mails: those are mails that you are rendering yourself, so you set manually the text and HTML body. ZfrMail does not come with any integration with template engine such as Twig or Plates. It's up to you to render them.
- Templated mails: some providers like Postmark or Mandrill provide a template system where the templates are stored in the provider. This allows non-technical people to edit the mail, and make maintenance easier. Make sure that the provider you are using supports templated emails before using it.
For instance, here is how you can create a simple rendered email:
And a templated email:
Mail can also accepts options. Those options are specific to the mail provider you're using. For instance, if you are using Postmark, the accepted options are (we're following Postmark convention on naming to make it easy):
TagInlineCssTrackOpensHeaders
Configuring a mailer
For now, ZfrMail provides integration with Postmark and Amazon SES.
Postmark
In order to configure Postmark, add the following code to your config:
The server token can be found in your Postmark account.
Amazon SES
In order to configure Amazon SES, add the following code to your config:
You have to had those dependencies in order to use Amazon SES :
Using the mailer
You can now inject the ZfrMail\Mailer\PostmarkMailer or ZfrMail\Mailer\AwsSesMailer class into your services. Those class comes with a single
send method. The mailer will automatically either send a templated or rendered mail for you:
Mailer also returns the message ID of the underlying platform (if supported). This can be useful if you need to implement features such as open tracking, where you would need to save into your database the message ID of the mailer:
ZfrMail is meant to be a lightweight solution with minimal overhead. As a consequence, it does not any validation to check whether your email addresses are valid, or if you are properly formatting the options according to your chosen provider.
To-do
- Add more providers
- Better error support (for now it will throw Guzzle exceptions, but we may create some pre-defined exceptions in the future and extract those from the Guzzle error)
