Skip to content

Remove cloudflare.com/net from disposable_email_domains.txt #294

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

Merged
merged 1 commit into from
Mar 7, 2025

Conversation

StanBright
Copy link
Contributor

cloudflare.com/net provides valid email forwarding services. The MX domains are on .cloudflare.net.

This should be affecting a lot of people and treating so many emails as disposable. For example, I have non-disposable emails @saashub.com & @libhunt.com that are being regarded as "disposable" because of including cloudflare.net to the list.

@phoet
Copy link
Collaborator

phoet commented Mar 4, 2025

I agree with cloudflare.net but not necessarily with dotcom. https://check-mail.org/domain/cloudflare.com/

For now, put them on your allow list until a new version comes out.

@StanBright
Copy link
Contributor Author

I still don't get it why cloudflare.com should be blocked. For example, I received valid notifications and invoices from emails coming from cloudflare.com. I'd argue that this check-mail.org service is wrong in this particular case.

@phoet
Copy link
Collaborator

phoet commented Mar 5, 2025

I don't think your example is valid. The question is wether this is a valid domain for user sign up.

If you don't think they are right use their contact form and get in touch.

@micke
Copy link
Owner

micke commented Mar 6, 2025

To me this feels a lot like previous scenarios with Simplelogin in #211 and mozmail in #202
Because of this i wouldn't necessarily consider it as a true throw-away email provider and that we should try our best to treat the services equally.
I'm okay with removing cloudflare.com from the list and whitelisting it so that it's not added in the future when pulling from upstream lists.

These are my own two cents and I'm interested to hear if users of the gem agrees with this?

@phoet
Copy link
Collaborator

phoet commented Mar 7, 2025

I got in touch via the feedback form:

Hi,

Thanks for the report. This domain shouldn't be blocked, and our automatic systems "shouldn't be able to block it".

We've located an issue where some domains could be automatically flagged by our systems, even though they've been verified to be okay previously.

We've located the underlying issue, and are working on implementing a fix for this, which should be live within a few days.

Again, thanks a lot for the report!

--
Best regards,
Anders

@phoet phoet merged commit 1353c01 into micke:main Mar 7, 2025
10 checks passed
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

Successfully merging this pull request may close these issues.

3 participants