AfterShip
Is this package actively maintained?
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
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
@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:
- Why are these implemented as separate methods?
- Would standard SMTP verification work for these providers as well?
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:
- Why are these implemented as separate methods?
- Would standard SMTP verification work for these providers as well?
Looking forward to your clarification
— Reply to this email directly, view it on GitHub https://github.com/AfterShip/email-verifier/issues/132#issuecomment-2440215364, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEDTLKRTZ2MMD5RQWPEABK3Z5VRO3AVCNFSM6AAAAABQVIIX3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBQGIYTKMZWGQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
@emilianocalzada Yes, as @NexaVerse-AI said just now, some service providers have some ways to check, so that is why the community is needed to help build this library. The second problem is yes, but there may be problems in the use process need to be solved by the users themselves