-
Notifications
You must be signed in to change notification settings - Fork 161
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
Is this package actively maintained? #132
Comments
Yes, the package will be actively maintained and there will be no changes to the license for the time being, but expect the community to help maintain it as well |
Thank you for maintaining this repository. I'm building my SaaS application using it and will for sure contribute I noticed there are separate verification methods for Yahoo and Gmail APIs. I'm wondering:
Looking forward to your clarification |
Some providers have special requirements and they need to be satisfied
that’s why it’s handled separately
…On Mon, Oct 28, 2024 at 4:51 AM David Emiliano calzada morales < ***@***.***> wrote:
@lryong <https://github.com/lryong>
Thank you for maintaining this repository. I'm building my SaaS
application using it and will for sure contribute
I noticed there are separate verification methods for Yahoo and Gmail
APIs. I'm wondering:
1. Why are these implemented as separate methods?
2. Would standard SMTP verification work for these providers as well?
Looking forward to your clarification
—
Reply to this email directly, view it on GitHub
<#132 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEDTLKRTZ2MMD5RQWPEABK3Z5VRO3AVCNFSM6AAAAABQVIIX3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBQGIYTKMZWGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@emilianocalzada |
Hello!
what is the current state of this package, is it working well?
Looking forward to use it for a new saas, currently using “check-if-email-exists” but I would like to use this package since the license is MIT
The text was updated successfully, but these errors were encountered: