I recently created an account for readthedocs, but I am unable to get certain mail adresses, ending in either @gmx.de or @web.de verified. I tried re-sending the confirmation several times, also removing and adding the addreses back again does not change this behavior. The mail was also not placed in a spam folder or something similar. However, it worked fine with another provider, using my @gmail.com adress.
Confirmation links are sent out to @gmx.de and @web.de mail adresses.
There are no confirmation links sent to these adresses.
I'm not sure what we can do here from the Read the Docs side. The emails are definitely going out but maybe they are blocked by those providers for some reason? You may want to contact them and in case they tell you what's the potential reason, we could maybe change some config in our side.
Thanks for your fast reply. I will contact the mail providers for additional information, and come back to you once I know more about the issue.
+1 Same here, but with email and domain hosted by domainfactory.
This I got from local Mail IT group:
TL/DR: the group sending the message on behalf of RTD (sendgrid.net) has gained a bad reputation (spammer, or worse)
I am seeing about 15 emails everyday from this IP Address, up until the end of day on the 10th. After that there is nothing. I changed the search from look for messages to looking for rejected connection. Starting on the 11th, and ever since then, I see lots of rejected connections showing:
" REJECT sender group BLACKLIST match sbrs[-10.0:-1.5] SBRS -3.0 sender IP 149.72.39.137"
This indicates that on a reputation scale of -10 to 10, we block anything that is -1.5 and below. It appears ReadTheDocs uses a service called sendgrid.net to send out these emails. sendgrid.net somehow got their reputation dinged enough on the 10th to drop it below the -1.5 threshold.
Until the clean up their reputation we will not be able to get any mail from them.
This setting is controlled by the Information Security Office and was settled on after decades of following industry standards and then tweaking that depending on if we were getting too much garbage or getting too much valid stuff blocked. We have finally found a "sweet spot" that has served us well for the last few years. I don't think ISO will change that threshold at this point. However, if you want, we can petition them to whitelist this IP Address if we can vouch for them as a valid sender. But really the responsibility falls on them to maintain a good reputation score.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. Thanks!
This is still valid, I think we were trying to reach to sendgrid.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. Thanks!
Come on bot!
We are handling this internally with SendGrid support but there is no much we can do here. I don't think it worth to keep this issue open since there is nothing actionable from our side.
We, the affected, would like to know when this issue with SendGrid is resolved as we may need to inform our respective IT (mail) departments. And also we will need to initiate a new email confirmation.
This thread seem the appropriate place for this
On Oct 6, 2020, at 11:13 AM, Manuel Kaufmann notifications@github.com wrote:
We are handling this internally with SendGrid support but there is no much we can do here. I don't think it worth to keep this issue open since there is nothing actionable from our side.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/readthedocs/readthedocs.org/issues/7501#issuecomment-704423069, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACY7PAZ4TT6OQGVOTKE33TSJNF4ZANCNFSM4RVORH7A.
We just received an email from sengrid
Thank you very much for your patience while our compliance team has been in the works to resolve your IP issue with Spamhaus.
Can you check the emails are arriving now? (not sure if your IT dep need to update the list or something)
Can I let this sit for a couple days until local IT logs have had a chance to clear ’sengrid’ as a bad actor. After that I’ll re-request email confirmation.
Does that sound ok. Maybe Wednesday?
rjs
On Oct 13, 2020, at 10:02 AM, Santos Gallegos notifications@github.com wrote:
We just received an email from sengrid
Thank you very much for your patience while our compliance team has been in the works to resolve your IP issue with Spamhaus.
Can you check the emails are arriving now? (not sure if your IT dep need to update the list or something)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/readthedocs/readthedocs.org/issues/7501#issuecomment-707843240, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACY7PF4PMLIUO6H22DNOBDSKR2X7ANCNFSM4RVORH7A.
Sure
I just tried it with the @gmx.de mail address and one from work, which also did not work previously, and I can confirm that the mails are coming now.
Thanks a lot!
On seeing the success of others, I tried mine and it too works. Case
closed, imo.
On 10/13/20 12:26 PM, Sebastian Blauth wrote:
I just tried it with the @gmx.de mail address and one from work, which
also did not work previously, and I can confirm that the mails are
coming now.Thanks a lot!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/readthedocs/readthedocs.org/issues/7501#issuecomment-707927302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACY7PALRCNISUT44GFGQ4LSKSLWBANCNFSM4RVORH7A.
Most helpful comment
I just tried it with the @gmx.de mail address and one from work, which also did not work previously, and I can confirm that the mails are coming now.
Thanks a lot!