Skip to content

[Mailer] Dispatch event for Postmark's "inactive recipient" API error #19233

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fabpot opened this issue Dec 8, 2023 · 3 comments
Closed

[Mailer] Dispatch event for Postmark's "inactive recipient" API error #19233

fabpot opened this issue Dec 8, 2023 · 3 comments
Labels
Milestone

Comments

@fabpot
Copy link
Member

fabpot commented Dec 8, 2023

Q A
Feature PR symfony/symfony#52916
PR author(s) @vicdelfant
Merged in 7.1

We created this issue to not forget to document this new feature. We would really appreciate if you can help us with this task. If you are not sure how to do it, please ask us and we will help you.

To fix this issue, please create a PR against the 7.1 branch in the symfony-docs repository.

Thank you! 😃

@fabpot fabpot added this to the 7.1 milestone Dec 8, 2023
@fabpot fabpot closed this as completed Dec 8, 2023
@vicdelfant
Copy link

@fabpot given that there is no clear structure for documenting transport-specific features like this yet, are there any objections to adding it under the Mailer Events? Also in case the PostmarkDeliveryEvent (or DeliveryEvent, rather) would be transport-agnostic in the future.

@xabbuh
Copy link
Member

xabbuh commented Dec 8, 2023

Would it make sense to add this to the readme of the Postmark bridge in the code repository?

@vicdelfant
Copy link

That would be similar to the ones for Sendgrid and Sendinblue, so I guess it could work? IMHO it prevents the official docs from get cluttered with information that’s too specific.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants