Closed deepsk79 closed 7 years ago
Can I get an email to verifyzoho@sweeting.me from a signed @zoho.com email address. This is needed because we're just trusting that you didn't have it on during the affected period, so we need some extra accountability by having a zoho employee confirm it.
Trying to figure out how this ended up in there in the first place.
I can't find where this came from. Checked:
% grep -iF zoho.com ipout nsout
ipout:2017-02-18: devzoho.com 184.168.221.8
ipout:2015-10-11: smtpzoho.com 50.116.40.252
ipout:2017-02-18: smtpzoho.com 71.19.144.145
nsout:austin zelda devzoho.com
nsout:charles jocelyn smtpzoho.com
nsout:coco ed zoho.com.ve
nsout:donna gerald teezoho.com
% grep -iF zoho.com certdoms.txt headers.txt readme.txt
certdoms.txt:devzoho.com sni61409
certdoms.txt:smtpzoho.com sni87387
certdoms.txt:teezoho.com sni167570
certdoms.txt:zoho.com.ve sni191708
No obvious CF headers on zoho.com.
Not sure if this could've been the cause, but many affected sites have Zoho in their MX records. Could that have caused it?
@pirate I'm going to merge this immediately because it's potentially an error, but you should take a look at it when you get a chance. I may be missing something. I'll open a new issue for it.
Update: Somewhere along the way, I believe this header was lost:
Some sources:
zoho.com fell under that.
git show
was just playing tricks on me. It was definitely in the affected site list and was introduced in 8053a438.
Posted in wrong issue; moved to https://github.com/pirate/sites-using-cloudflare/issues/157#issuecomment-282458165
Posted in wrong issue; moved to https://github.com/pirate/sites-using-cloudflare/issues/157#issuecomment-282458177
Zoho.com does not use Cloudflare - SSL termination is done at our own servers