Unfortunately, it appears that Swiftmailer 6 changed how messages are instantiated, with no deprecation period. Now it is

$message = (new \Swift_Message('Subject of Email'))

instead of

 $message = \Swift_Message::newInstance()
      ->setSubject('Subject of Email')

This only shows up twice in the bundle, but not sure how this should be dealt with. Maybe with versioning? A 4.0 tag? (The 3.0 tag was from Jan, 2017).

README file contains the following, invalid instructions:

// in AppKernel::registerBundles()
$bundles = array(
    // ...
    new Azine\EmailBundle\EmailBundle(),

should be:

// in AppKernel::registerBundles()
$bundles = array(
    // ...
    new Azine\EmailBundle\AzineEmailBundle(),

This:

    # the service-id of your implementation of the web view service to be used
    web_view_service:     azine_email.example.web.view.service

should be:

    # the service-id of your implementation of the web view service to be used
    web_view_service:     azine_email.example.web_view_service

Do you have plans to support Symfony 4?

Hi,
Can you add LICENSE information.

I see you have : "license": "MIT", in the composer.json but would it be possible for you to add an explicit license in the actual codebase?

I can do a PR if you are happy for an MIT to be added.

Hey,

What ideas would you have to make it possible to extend/override SendEMail and Notification entity classes?

For example, I'd like to be able to add additional fields when creating in my services.

Hi,

Is there a reason for this method to be limited to a text format?
What about HTML templates?

https://github.com/azine/email-bundle/blob/master/Controller/AzineEmailTemplateController.php#L328

Looks like the dependency on FOSUserBundle can be made optional or abstracted such that the FOS Specific mail sending code may be used by custom implementations too. While FOSUserBundle may be the de-facto solution for Symfony auth system, it is not always the case.

Since recipient_class and a few other fields are required, a flex recipe would automatically create config/packages/azine_email.yaml, then cache:clear would work as part of the installation process.

Also, the default class could probably be App\Entity\User, since that's probably pretty common for people using FosUserBundle in Symfony4.

i do really want to send newsletter!
but how ?
i had try :

first of all the following line does not work :
immediateMailer: "@swiftmailer.mailer.immediateMailer"

so it was replaced with :
immediateMailer: "@mailer"
OR

immediateMailer: "@swiftmailer.mailer.immediateMailer"

then :
class User extends BaseUser implements \Azine\EmailBundle\Entity\RecipientInterface

the user class was implemented by RecipientInterface

then i had run :
emails:sendNewsletter

the result was :
Thu, 12 Feb 2015 08:37:34 +0100 : starting to send newsletter emails.
Thu, 12 Feb 2015 08:37:34 +0100 : 0 newsletter emails have been sent.
Thu, 12 Feb 2015 08:37:34 +0100 : The following email-addresses failed:

what should i do ?

When I wanted to update my Symfony project to Symfony 3.3.6,, Composer let me do it (while requerring AzineEmailBundle at dev-master). The problem is that AzineEmailBundle has a services.yml syntax which is no longer accepted in Symfony. The argument names in services declarations need to be like $name_of_the_php_argument: argument_value and cannot (anymore) be like name_of_the_argument: argument_value. For instance,

    azine_email.example.template_provider:
        class: Azine\EmailBundle\Services\AzineTemplateProvider
        arguments:
          router:       "@router"
          translator:   "@translator.default"
          parameters:
            image_dir:  "%azine_email_image_dir%"
            allowed_images_folders: "%azine_email_allowed_images_folders%"
            tracking_params_campaign_name:    "%azine_email_tracking_params_campaign_name%"
            tracking_params_campaign_term:    "%azine_email_tracking_params_campaign_term%"
            tracking_params_campaign_content: "%azine_email_tracking_params_campaign_content%"
            tracking_params_campaign_medium:  "%azine_email_tracking_params_campaign_medium%"
            tracking_params_campaign_source:  "%azine_email_tracking_params_campaign_source%"

should be replaced by

    azine_email.example.template_provider:
        class: Azine\EmailBundle\Services\AzineTemplateProvider
        arguments:
          $router:       "@router"
          $translator:   "@translator.default"
          $parameters:
            image_dir:  "%azine_email_image_dir%"
            allowed_images_folders: "%azine_email_allowed_images_folders%"
            tracking_params_campaign_name:    "%azine_email_tracking_params_campaign_name%"
            tracking_params_campaign_term:    "%azine_email_tracking_params_campaign_term%"
            tracking_params_campaign_content: "%azine_email_tracking_params_campaign_content%"
            tracking_params_campaign_medium:  "%azine_email_tracking_params_campaign_medium%"
            tracking_params_campaign_source:  "%azine_email_tracking_params_campaign_source%"

I tried to override this file but I couldn't, which led to an error stipulating that the first argument of service azine_email.example.template_provide should be named with the $ symbol, or by referring its index in the arguments list with an integer. The order of the arguments no longer have a predominant role like it did in previous versions of Symfony.

I know AzineEmailBundle is a Symfony2 bundle, but as Composer allows to use it with Symfony 3.3.6, and as the bundle is completely compatible on the other levels, I wondered: is something going to be done about this? I see two possible fixes:

• rename arguments with the $ symbol in services.yml
• omit argument names in services.yml, only relying on their order in the constructor signature

I'm trying to use the bundle to manage email notifications. Ca you please provide an example on how to send an email notification using a twig template.

Thank you.