check (also) for email providers to determine if valid email is /not/ a company address

[clysss]

Hello,
https://gist.github.com/ammarshah/f5c2624d767f91a7cbdc4e54db8dd0bf
maintain a list of email providers (free, paid...)

could we add a second validation like
isFromProvider (if isValid) to check if the email is (not) a company address

The interest to implement it on mailchecker is that no more tools will be needed
Of course, if you seems that this idea is interesting, I can create a PR

[YasharF]

Can you expand on the use case?

[clysss]

yes :) with pleasure we use mailchecker to verify data/email from sign-in form our "service" is for IT professionals mainly for large companies : so they are supposed to have a "professionnal" email and in our case mostly @gmail @yahoo... address are scam more or less like drop emails more precisely, if it's an email from "provider", we want to add an extra layer of questions/checks in the form to verify the "trust" of the user so idealy, we need to have the current isValid() and a another command to check if not in the second list if it's easier we can also imaginate 2 calls : one to isValid() and one to isValid( , includeProvider=true) tell me what could be the best way to handle it in the code, I should be able to write the code and can make a PR if needed after your advice The interest to have only one tool for this 2 functions is that all the updates are in the same place when I search for this tool, I have found several "solutions" that combine 2 seperate tools but for this reason, most of them are outdated regards

…

On Thu, 16 Jan 2025 at 07:47, Yashar Fakhari ***@***.***> wrote: Can you expand on the use case? — Reply to this email directly, view it on GitHub <#508 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANKVWKUPA4C2L75ZW5XRIJL2K5IWVAVCNFSM6AAAAABVDTAPMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJUGY2TQMRYGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[harshit-budhraja]

@clysss here's a simple free tool that compares different publicly available blocklists (including this one): https://unfake.dev/compare-blocklists

[clysss]

Hello thanks! The idea is not to check a list but implement other functions to mail checker Le lun. 3 févr. 2025, 17:48, Harshit Budhraja ***@***.***> a écrit :

…

@clysss <https://github.com/clysss> here's a simple free tool that compares different publicly available blocklists (including this one): https://unfake.dev/compare-blocklists — Reply to this email directly, view it on GitHub <#508 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANKVWKS5NC3J74ZSUZRSWLT2N6MUJAVCNFSM6AAAAABVDTAPMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZRGUZTIMRUG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[clysss]

Can you expand on the use case?

@YasharF : an opinion ?

[YasharF]

Just my personal opinion, but I feel like it is hard to define what is considered a professional email address. At the same time, the list of known major/popular free email providers is fairly small if you want to implement your own blacklist which you can expand on if you run into more bad actors. Who knows you may end up creating your own opensource package that is the list of such providers to share. Another suggestion that I have in terms of your use case is to request submitters to provide their LinkedIn link, which you can use to weed out bogus submissions. By the way in terms of your use case you may also have end customers that may not want to use their professional email when initially requesting information. For example, in one of my prior roles I didn't want my work email to get spam so I always used my yahoo email address for the initial contact and would leave it to yahoo to deal with the potential spam. Later on, if I felt that the provider was someone that I could have put in front of others at work, then I would pass my work-related info or would email them from my work info to continue there.

[clysss]

Thanks a lot for your input, we already have planned to ask for LinkedIn;) But we wanted also an easy way for checking email. We already have a list of emails provider. What I don't really have seen in this repo is how you maintain the list. My idea was to add it to it with a special option Le mer. 5 mars 2025, 20:59, Yashar Fakhari ***@***.***> a écrit :

…

Just my personal opinion, but I feel like it is hard to define what is considered a professional email address. At the same time, the list of known major/popular free email providers is fairly small if you want to implement your own blacklist which you can expand on if you run into more bad actors. Who knows you may end up creating your own opensource package that is the list of such providers to share. Another suggestion that I have in terms of your use case is to request submitters to provide their LinkedIn link, which you can use to weed out bogus submissions. By the way in terms of your use case you may also have end customers that may not want to use their professional email when initially requesting information. For example, in one of my prior roles I didn't want my work email to get spam so I always used my yahoo email address for the initial contact and would leave it to yahoo to deal with the potential spam. Later on, if I felt that the provider was someone that I could have put in front of others at work, then I would pass my work-related info or would email them from my work info to continue there. — Reply to this email directly, view it on GitHub <#508 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANKVWKVSW77XKMFE2ATZZ6D2S5JSBAVCNFSM6AAAAABVDTAPMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBRHEZTINBXHE> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: YasharF]*YasharF* left a comment (FGRibreau/mailchecker#508) <#508 (comment)> Just my personal opinion, but I feel like it is hard to define what is considered a professional email address. At the same time, the list of known major/popular free email providers is fairly small if you want to implement your own blacklist which you can expand on if you run into more bad actors. Who knows you may end up creating your own opensource package that is the list of such providers to share. Another suggestion that I have in terms of your use case is to request submitters to provide their LinkedIn link, which you can use to weed out bogus submissions. By the way in terms of your use case you may also have end customers that may not want to use their professional email when initially requesting information. For example, in one of my prior roles I didn't want my work email to get spam so I always used my yahoo email address for the initial contact and would leave it to yahoo to deal with the potential spam. Later on, if I felt that the provider was someone that I could have put in front of others at work, then I would pass my work-related info or would email them from my work info to continue there. — Reply to this email directly, view it on GitHub <#508 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANKVWKVSW77XKMFE2ATZZ6D2S5JSBAVCNFSM6AAAAABVDTAPMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBRHEZTINBXHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[YasharF]

What I don't really have seen in this repo is how you maintain the list.

The list that this package uses is in list.txt
It is updated as part of the package, with PRs like these: #514 , #513 , #520 , #521

list.txt gets loaded from the file here: lib/loader.js#L13 and the lib/generator.js uses to create the code for each target package using templates under platform

If you are using nodejs, you can use something like patch-package to just patch the npm module to add a few more entries that are specific to your use case. I am guessing your patch would be something like:

var blacklist = new Set(["0-00.usa.cc", "0-30-24.com", "0-attorney.com", ...]) // existing line in the module
// new lines to add:
const blacklistExpansion = new Set(["gmail.com", "yahoo.com", ...])
blacklist = new Set([...blacklist, ...blacklistExpansion])

[clysss]

Thanks a lot, I'll have a deeper look with this next month. I'll try to make a proposal following these guides Le mer. 5 mars 2025, 22:36, Yashar Fakhari ***@***.***> a écrit :

…

What I don't really have seen in this repo is how you maintain the list. The list that this package uses is in list.txt <https://github.com/FGRibreau/mailchecker/blob/master/list.txt> It is updated as part of the package, with PRs like these: #514 <#514> , #513 <#513> , #520 <#520> , #521 <#521> list.txt gets loaded from the file here: lib/loader.js#L13 <https://github.com/FGRibreau/mailchecker/blob/b2f9b84e5b7211de3d91320cf591a266570354e2/lib/loader.js#L13> and the lib/generator.js <https://github.com/FGRibreau/mailchecker/blob/master/lib/generator.js> uses to create the code for each target package using templates under platform <https://github.com/FGRibreau/mailchecker/tree/master/platform> If you are using nodejs, you can use something like patch-package to just patch the npm module to add a few more entries that are specific to your use case. I am guessing your patch would be something like: var blacklist = new Set(["0-00.usa.cc", "0-30-24.com", "0-attorney.com", ...]) // existing line in the module // new lines to add: const blacklistExpansion = new Set(["gmail.com", "yahoo.com", ...]) blacklist = new Set([...blacklist, ...blacklistExpansion]) — Reply to this email directly, view it on GitHub <#508 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANKVWKSTID4BZ5KDN56RWRD2S5U7BAVCNFSM6AAAAABVDTAPMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBSGEZTGOBSGE> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: YasharF]*YasharF* left a comment (FGRibreau/mailchecker#508) <#508 (comment)> What I don't really have seen in this repo is how you maintain the list. The list that this package uses is in list.txt <https://github.com/FGRibreau/mailchecker/blob/master/list.txt> It is updated as part of the package, with PRs like these: #514 <#514> , #513 <#513> , #520 <#520> , #521 <#521> list.txt gets loaded from the file here: lib/loader.js#L13 <https://github.com/FGRibreau/mailchecker/blob/b2f9b84e5b7211de3d91320cf591a266570354e2/lib/loader.js#L13> and the lib/generator.js <https://github.com/FGRibreau/mailchecker/blob/master/lib/generator.js> uses to create the code for each target package using templates under platform <https://github.com/FGRibreau/mailchecker/tree/master/platform> If you are using nodejs, you can use something like patch-package to just patch the npm module to add a few more entries that are specific to your use case. I am guessing your patch would be something like: var blacklist = new Set(["0-00.usa.cc", "0-30-24.com", "0-attorney.com", ...]) // existing line in the module // new lines to add: const blacklistExpansion = new Set(["gmail.com", "yahoo.com", ...]) blacklist = new Set([...blacklist, ...blacklistExpansion]) — Reply to this email directly, view it on GitHub <#508 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANKVWKSTID4BZ5KDN56RWRD2S5U7BAVCNFSM6AAAAABVDTAPMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBSGEZTGOBSGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>