{"id":442,"date":"2010-08-03T10:59:14","date_gmt":"2010-08-03T10:59:14","guid":{"rendered":"http:\/\/blog.stmellion.org\/?p=442"},"modified":"2010-08-03T10:59:14","modified_gmt":"2010-08-03T10:59:14","slug":"nildram-technical-support","status":"publish","type":"post","link":"https:\/\/blog.stmellion.org\/?p=442","title":{"rendered":"Nildram Technical Support"},"content":{"rendered":"

For the first time in ages today I had cause to contact Nildram<\/a>‘s Customer Support. First I tried to email support@nildram.net which has always worked in the past. It now bounces with:
\n554 : Recipient address rejected: User unknown<\/p>\n

Next I tried customercare@nildram.net and this one worked. I even got a reply, all be it, automated.<\/p>\n

To my surprise, the (automated) reply doesn’t come from Nildram<\/a>, it comes from rightnowtech.com<\/a> To futher complicate matters, the return address on their email is: nildram_customer_care@custhelp.com.<\/p>\n

In summary, I’ve sent an email to nildram.net, got a reply from rightnowtech.com and been instructed to reply to custhelp.com. What a mess. In this day and age where the majority of email is a scam of some kind, how are people ever expected to trust domains when they mess around in this manner? I use SpamAssassin<\/a> to filter my email and this kind of trickery is going to be frequently eaten by it.<\/p>\n

My next grump is the content of their reply. In it I’m instructed that should I wish to respond then I must type my reply between two cutmarks within their email, like this:
\n[===> Please enter your reply below this line <===]\n\n[===> Please enter your reply above this line <===]\nWhy must I do this? I'm simply using email as defined and refined for decades now and I don't see why all of a sudden, Nildram (or whoever the hell now does their support) wants to redefine it.\n\nRight, got that off my chest now. No doubt their reply to my simple request for a Reverse DNS change will be proof that their monster of a support mechanism actually does work. Maybe.\n<\/p>\n","protected":false},"excerpt":{"rendered":"

For the first time in ages today I had cause to contact Nildram‘s Customer Support. First I tried to email support@nildram.net which has always worked in the past. It now bounces with: 554 : Recipient address rejected: User unknown Next I tried customercare@nildram.net and this one worked. I even got a reply, all be it,… Continue reading Nildram Technical Support<\/span><\/a><\/p>\n","protected":false},"author":24,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"class_list":["post-442","post","type-post","status-publish","format-standard","hentry","category-service-providers","entry"],"_links":{"self":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts\/442","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=442"}],"version-history":[{"count":2,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts\/442\/revisions"}],"predecessor-version":[{"id":444,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts\/442\/revisions\/444"}],"wp:attachment":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=442"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=442"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=442"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}