Tuesday, 12 May 2009

IronPort integration - crap

Here's an email I sent to senderbase after banging my head on a brick wall for nearly two days with their closed-loop spam solution. You get on the list for some reason, but there's no way to get off. iiNet's solution to the problem is: "Wait and see." - as in, give it 24/48 hours from some nebulous start point, rinse and repeat.

As an IT administrator of a mail system I crashed into your solution yesterday morning at 7am. A local ISP has implemented IronPort hardware and uses senderbase.org as it's block list.

The ISP's response is: "That's not our problem."

Your site tells me that the reputation for my server is "poor", but doesn't indicate what caused that ranking, nor does it help me determine what to actually do about this.

The server in question sends out two email messages, once a week, to three addresses, namely, me - the administrator, and the owner of the server - using two of his own email addresses - one of which is operated by the ISP.

You've created a wonderful closed loop solution that does nothing for legitimate operators of mail services and makes it simple for the owner of the IronPort hardware to just drop problems caused by your implementation into the too hard basket.

I'm not impressed and as an IT consultant will not recommend your solution to any of my clients in SME/Gov.

I'm not going to hold my breath, but in case you're actually interested in resolving the issue, the ISP is iiNet in Australia, the trouble ticket number in their system is: 60416585

I'll not waste your time telling you about the various pieces of advice provided by iiNet, suffice to say that the problem is not because the email account is on a dynamic IP address because it's on an ADSL link. Or should the support technician have advised me that it was because of another BOFH reason, say: "BOFH excuse #246: It must have been the lightning storm we had (yesterday) (last week) (last month)"

No comments: