Download the PHP package instaclick/base-mail-bundle without Composer

On this page you can find all versions of the php package instaclick/base-mail-bundle. 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?

Informations about the package base-mail-bundle

InstaClick Base Mail Bundle

Build Status

Introduction

This bundle provides a lower level support for mail manipulation on Symfony2. It is supported to deal with composing, sending and dealing with bounced messages in an abstract API.

Installation

Installing this bundle can be done through these simple steps:

  1. Add this bundle to your project as a composer dependency:

  2. Add this bundle in your application kernel:

Configuring the bundle

By default, any composed message contains a sender name and address. This simplifies the implementation time and cleaner code. You are allowed to change these values anytime, but if negative, you can globally configure this support.

To define the default sender name and address, do the following:

This bundle also comes with a bounced email handler. For any reasons, when dealing with delivery of messages to users' mailbox, you also need to handle possible failures that users may have done. The best example is mispelled email addresses. To configure the bounced email handler, configure the mail_bounce section in bundle's configuration:

Using available Services

The purpose of this bundle is to simplify mail creation, sending and handling possible failures. These three sections derived into three services that can be used by any application that consumes this bundle.

Composer Service

Responsible to compose messages. Configured default sender automatically injects sender name and address to any message that gets created out of this service. The methods setDefaultSenderName and setDefaultSenderAddress provide an ability to modify the values at runtime if necessary. Apart from the before mentioned methods, this service only contains one method: createMessage; it initializes a new message to be prepared for sending.

A message instance contains a lot of options that can be defined by consuming its API. By default, any message is configured to be a text/html message and the method setContentType provides an ability to modify this behavior.

The interface for Message API is the following one:

Sender Service

After your message is composed, it is time to send it. Sender service provides this support by exposing a public method called send. This method returns a boolean value in case of successful delivery or failure. It does not take into consideration bounced mail, since this is an asynchronous action that must be implemented by a consumer of BounceMail Service.


All versions of base-mail-bundle with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.2
symfony/twig-bundle Version ~2.1
symfony/framework-bundle Version ~2.1
symfony/swiftmailer-bundle Version ~2.1
symfony/finder Version ~2.1
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 instaclick/base-mail-bundle contains the following files

Loading the files please wait ....