zlacker

>>achyne+(OP)
Zoho CEO here.

Our domain was abruptly blocked by our registrar this morning. Our NOC team and myself tried to get in touch with them and they tell us "Contact our legal". Even I could not get in touch with anyone beyond their phone operator. The domain was restored, but as DNS takes time to restore, we are still facing issues. They later claimed there were abuse complaints about Zoho.com emails (which is our personal email service with millions of free and paid users). We received a total of 3 complaints from them and two of them have been acted upon and one is under investigation.

Once we dig our way out of this, we will find ways make sure no one takes down our domain again this way.

>>svembu+h3
The hell are you complaining about unreachable contacts when your own abuse@ address is dead -

    Arrival-Date: Thu, 30 Aug 2018 00:00:00 +0200 (CEST)

    Final-Recipient: rfc822; abuse@zohocorp.com
    Original-Recipient: rfc822;abuse@zohocorp.com
    Action: failed
    Status: 4.7.1
    Remote-MTA: dns; mx2.zohocorp.com
    Diagnostic-Code: smtp; 451 4.7.1 Greylisted, try again after some time

This is from our MTA after 5 (FIVE) days of trying to deliver you a spam report, with all delivery attempts originating from the same IP.

And that's without getting into why you have a filter on your abuse@ address to begin with.

>>huhten+391
If I had to guess they're probably rejecting the message further because it likely contains the spam itself.

This is a key error in their handling of their abuse@ address, it needs to be expected to receive spam.