Skip to content
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

Feature Request: Support for Additional Provider #277

Open
trueqap opened this issue Feb 13, 2025 · 1 comment
Open

Feature Request: Support for Additional Provider #277

trueqap opened this issue Feb 13, 2025 · 1 comment

Comments

@trueqap
Copy link

trueqap commented Feb 13, 2025

Hello,

First of all, thank you for your great work on FluentSMTP!

I would like to ask if it is possible to add support for an extra provider. Specifically, I would like to use my own API-based solution with FluentSMTP.

Would it be possible to integrate a custom provider option, or is there a recommended way to extend the plugin for such use? Any guidance on the necessary steps or requirements for implementation would be greatly appreciated.

Looking forward to your response.

@rahat1994
Copy link

rahat1994 commented Mar 3, 2025

Yes, you can integrate your own API-based solution as a custom provider in FluentSMTP. To do this, you can refer to the existing provider implementations located in:

📂 app/Services/Mailer/Providers

This folder contains the implementations for various email providers, which you can use as a reference when building your own integration. You can follow the structure and extend FluentSMTP to support your API-based solution.

If you have any specific questions during implementation, feel free to ask.

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

No branches or pull requests

2 participants