Questions on usage about elasticemail-mailer HOT 5 OPEN

Hi @landNull

I have developed it for a Craft CMS plugin, which is based on the Symfony Mailer.
Therefore Symfony does support adding custom transports, but I just discovered I did not well on that for now. Since I have looked at other mailer integrations. But they are part of the core of the framework.
I have to make changes to make this work.

Tested things out for now; you have to register the factory yourself for now, by tagging it like this in your services.taml configuration file.

bertoost\Mailer\ElasticEmail\Transport\ElasticEmailTransportFactory:
  tags:
    - { name: mailer.transport_factory }

I the nearby future I will check how to auto-tag this transport factory from the package itself. Thanks for pointing this out.

Regards, Bert

from elasticemail-mailer.

Thank you for following up so quickly. :D

from elasticemail-mailer.

I have updated the package to work with Symfony natively. Can you try updating to version 1.1.0?
You can remove the above suggestion too. It's now handled by the package
Like to hear from you again.

from elasticemail-mailer.

Hi there,

Thank you for the quick update! I upgraded via composer, but Mautic still isn't picking it up.

from elasticemail-mailer.

I don't know about Mautic. But as far I can see, you should use "elasticemail+stmp" instead of "api" in the scheme name. The API is meant for connecting with API credentials (a key) instead of username/password of the SMTP service.

from elasticemail-mailer.