quartzy / courier Goto Github PK

The implementation should wrap the Amazon SDK V3 library. Basis documentation of the SESClient can be found at the Amazon documentation site.

SaaS email system will generally return an ID of some sort representing the delivery in their system whenever we sent the request to them. This ID can be important when troubleshooting and auditing the lifecycle of the delivery.

For non-SaaS deliveries (NullCourier is the only courier in this boat currently), the concept of a receipt ID makes much less sense. This means that a courier build around mail or another local server transmission mechanism won't have an ID to return.

When originally built, the idea around Courier was to specifically support SaaS providers, so changing the interface signature to deliver(Email $email): string would make sense. Before making a decision on changing the interface we should determine:

• Should the library stay flexible enough to support local delivery of emails?
• Is there a way to maintain a simple, concise interface but still support both a void and a string return type?

It would be best to figure out a good way to actually send requests to the services that are implemented by this project to ensure there are not edge cases that are missing.

SendGrid currently has a bug in their processing that causes templates to render incorrectly if more than one email attachment is included. The workaround suggested by the SendGrid support team is to send an inline template instead of using a saved template. This pattern is similar to how the SparkPostCourier currently works.

The courier should wrap the existing Mailgun PHP library.

The implementation should wrap the existing Mailjet V3 Client.

SendGrid has released 7.2.1 of their client library. The dependency of this project should be updated to ^7.0.