_______________________________________ From: [email protected] [[email protected]] On Behalf Of Arnim Sommer [[email protected]] Sent: Friday, 26 November 2010 11:11 PM To: [email protected] Subject: Mail.Global.FrontBridge.com
>Hello, >unfortunately, @work we are hosted at microsoftonline.com. > >Since monday, we are getting mail delays with one of our partners, and >I could track it down to address verification getting timeouts. > >Has anyone else seen that problem, or is it just one isolated problem? > >Thank you for your input. > Hello, In my experience....: Microsoft's b0rged hosted exchange and frontbridge system is very broken. Firstly from an MX (inward smtp) point of view, they smell very spammy, rDNS in one domain, helo in another, and envelope sender from yet another. Added to this sender verification does not work, and if you are using greylisting, the chances are very good that the triplet will never be seen again, which means a delivery failure for their customers. I have had to poke a lot of holes into our system to cope with frontbridge customers. This has meant that all the spammers that relay through microsofts customers, or even via Microsoft hosted exchange directly, get delivery to our system. The amount of spam in our mailboxes has trippled since i removed sender verification for frontbridge.com and bigfish.com (yep that is the Helo domain - and probably demonstrated Microsofts view of themselves.) Microsoft pay no heed to standards, they are a marketing machine. Open Source, and RFC's are unlikely to bring in the buck$ for them, so instead they invent their own. How to fix...: Put pressure on Microsofts customers. Microsoft is not interested in what you or I say, but they suddenly get interested when their customers vote with their checkbooks. When Microsofts customers complain that they cant send email to your users, be conforted in the knowledge that there are a lot of places they can not send email now, based on Microsofts brokenness. Microsoft doesnt care. My 2 bits. T
