BUY FIRM BACK 29.12
Being Holmes S4: A Study in Treason (Sign Up Open)
MITTALs CASE 30.12
Let's make if official
Love And War Budget Shoots up ,now eyeing Aug/Sep release
Hrithik Roshan is the most beautiful man to ever exist
Tara Veer are now being compared with the OG Deepika Ranveer ☠️
📚Book Talk January Reading Challenge: Let us Read, Review & Revel📚
Kartik Aryan to start work on Bhool Bhulaiyaa 4 / Kabie Khan film!
This actress was the original choice of Chalte Chalte opp Shah!
🏏India Women vs Sri Lanka Women, 5th T20I 🏏
💋Lets Sorts out Piano Hindi Songs
Salman fans are having fan wars in Mandarin with Chinese
Hi All,
First of all my apologies on not able to fix the problem earlier. We did recieve a lot of complaints on this and many topics were created in the Suggestions / Comments Forum.
Well I dont know if I shared this in any of my earlier posts that this error was due to a time mismatch between the database server and the web server and everytime we had to manually update the time with a common time server. But due to strange reasons in a few days it would again had a difference of around 30-90 seconds mismatch.
To over come this we have rewritten the code and this time it should solve this particular problem as it will reference the time of the Database server only so even in the event of a small mismatch it will not be saying "Spam Error" to most of the users. I will be posting more detailed errors so that its clear why the system identifies a post as "Spam"
Do let me know if you are still facing the issue so that I can check this thread and resolve the issue.
Regards,
Vijay Bhatter