Amazon’s managers told me to provide proof.
So I did. I recorded video evidence showing—step by step—that their claim was false. Two-Step Verification had not been disabled, and I remained locked out of my account.
I attached the video to my reply. I hit send.
And then?
Amazon’s own system spat the email straight back at me.
Message not delivered.
That’s the banner Gmail showed me. The technical details beneath made it even clearer: “The recipient server did not accept our requests to connect.”
In other words, Amazon KDP’s inbox refused to receive the very evidence their manager, Nidheesh, had just asked me to send.
Let’s be clear: this isn’t a glitch. This is a wall.
You ask the customer for proof. The customer provides it. Your system refuses delivery. Then you carry on insisting that the problem is unsolved, because—conveniently—you never “received” the evidence.
Kafka’s call centre? No. This is worse. This is Kafka with corporate servers and sentiment dashboards, where “resolution” is a performance and the customer is forced to play along.
And Andy Jassy, CEO of Amazon, this is on your watch.
Every bounce, every failure, every “Message not delivered” lands at your door.
I’m not going away. Veterans don’t quit.
I’ll keep publishing the paper trail you can’t seem to hold. Every undelivered email becomes another delivered post. Every refusal becomes another record.
Because silence doesn’t erase evidence—it multiplies it.
