2) This is in line with the address harvesting. Since all incomming harvest attacks had the Postini SMTP addresses in the logs, we could no longer act to prevent Dictionary attacks directed at our server. We were at the mercy of Postini, who said this "We are stopping about 2,000 per day" (Not good when that is only 20%)
Didn't postini have a list of your users, so they could block harvesting to unknown users? This is key defensive advantage of IMGate.
3) Many users had trouble understanding the front end that Postini used. This is not necessarily Postini's Fault, just that most people aren't ready for that level of interaction yet.
confirms my observation that businesses don't want their employees futzing around with spam filters that are often beyond their abilities, causing lost time and lost mail.
This is insane for employees: reject nothing (waste bandwidth + resources), flag it into a folder, WASTE YOUR TIME GOING THROUGH THE FOLDER, to discover that 99.9% of it really is a spam (assuming such a system is a accurate as advertised)
I know a rural telco co-op that is also ISP paying Postini about $8K / month for 13K accounts.
I bet anybody $1000 that I could save the co-op $90K/year with IMgate and after the users got past the "change hurts" false problem, the anti-spam effectives would be equal. But once you get something setup as "structural overhead" at the user level (like not requiring SMTP AUTH from day one), it's nearly impossible to back it out. But I'm trying. :)
Len
_____________________________________________________________________ http://MenAndMice.com/DNS-training: London; San Jose; Wash DC IMGate.MEIway.com: anti-spam gateway, effective on 1000's of sites, free
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
