Download the PHP package everlutionsk/email-bundle-2 without Composer

On this page you can find all versions of the php package everlutionsk/email-bundle-2. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of everlutionsk/email-bundle-2

Informations about the package email-bundle-2

Email Bundle

This Symfony bundle provides mechanism for sending and receiving email messages through various mail systems.

Installation

Enable the bundle

Configure the bundle

Following configuration snippet describes how to configure the bundle. Configuration requires a names of services, which implements corresponding interfaces. Only exception is doman_name, where you should set something like appdomain.com

mail_system - Name of service, which will be used for sending email messages. This service usually comunicate with SMTP server or with some transactional email platform like Mandrill.

enforced_delivery_address - [Optional] Email address, which will be used to override recipient address in every outbound message.

async_stream - Bundle allows to send email messages asynchronously. Email messages is stored in memory unil some value is added into this Stream. Good example is a Stream of Symfony's kernel.terminate events.

attachment_swappers - After sending or receiving a message, bundle try to save the message's attachments by using this attachment swappers. This swappers can save attachments in various ways.

request_processors - Bundle provide common mechanism to handle inbound messages and outbound message events. This events may occur for example when external mail system try to send scheduled messages. However, different mail systems sending data in different format. Request processors transform this data into format, which is known for this bundle.

Routing

Bundle provides controllers for handling inbound messages and outbound message events.

Basic Usage

Create new outbound message

Get mailer

Synchronous mailer - Mail system is called immediately.

Asynchronous mailer - Mail system is called after adding value into corresponding Stream.

Send / Schedule message

Advanced usage

Message transformers

Every message could be modified before it is forwarded into mail system.

Transforming outbound messages
Register service, which implements OutboundMessageTransformer and add following tag:

Transforming inbound messages
Register service, which implements InboundMessageTransformer and add following tag:

Message templates

Some mail systems supports message templates, which are defined in this systems. The following code shows how to use this templates.

Handle Inbound messages

Inbound messages can be handled by listeners, which listening to events. Events are instances of Inbound message and about its storable version, which has been saved into database.


Caution: If application doesn't need to create associations with inbound message in database, then storable version of message should be ignored.

Mock a mail system

Use service as mail system (see Configure the bundle section).

Supported mail systems

Mandrill

All versions of email-bundle-2 with dependencies

PHP Build Version
Package Version
Requires php Version >=5.4.0
doctrine/orm Version ^2.3
symfony/http-kernel Version ^2.6 || ~3.0 || ~4.0 || >=5.0
symfony/config Version ^2.6 || ~3.0 || ~4.0 || >=5.0
symfony/dependency-injection Version ^2.6 || ~3.0 || ~4.0 || >=5.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package everlutionsk/email-bundle-2 contains the following files

Loading the files please wait ....