That does seem to be what's happened. As I consistently generate non-spam mail toward hotmail/outlook.com accounts, it has been un-blocked and now works without issues.
I'm particularly interested in your case however, since I plan to migrate to Comcast business myself. I'd prefer not to relay through their servers if possible, what with the shenanigans large ISPs seem to want to pull recently re: STARTTLS downgrade attacks, etc.
I have no idea about availability, but they're around, Jake Appelbaum was playing with one the other day in a recent talk.
For work, I've been trying WebPasswordSafe for the last several months. This is to get away from the melange of different un-sync'd password lists in various password managers people in the IT department had. So far it works well, it offers group policies, so theoretically it could be rolled out company wide and each user and group could have their separate password lists.
I'd been guided to look at SecretServer, but the features I need are in WPS, and it's easier to sell Free in my company than Several Hundred or Thousand dollars, for many things at least.
I started getting mail to my Yahoo account which wasn't spam, but clearly not for me, as part of a group of people participating in a medical imaging conference. For a while I just blew it off, but eventually the organizer mailed my actual non-yahoo address by mistake as well. So I decided to be swell about it and let her know that I'm not the person she's trying to reach. She said "Oh, I'm sorry, I meant to do (yourname)@yahoo.com, thanks!", and so I told her "well no, that's also me, sorry". I proceeded to tell her an address which would work for her intended recipient (work email for the person she was trying to mail, who isn't me).
Basically she refused to believe she has been sending to the wrong address, and said "I had no idea two people could have the same email address, I guess Yahoo must allow it or something". At that point, I gave up and just let it go again. It's not high-volume enough to matter.
I decided one day to fix all this, regardless of what that entailed. I lowered the threshold for SA to a score of 4 (which they bark at you not to do, but fuck 'em, I've seen maybe 6 legit mails with a score higher than 4.5, in my world anyway). The key components were: enabling remote checks, RAZOR and DCC, and having SA train its filters off of my false negatives. I use the Train SA script, so I drop any false negatives in a Train Spam folder, and this picks them up and runs them through SA's filters to train it.
My false negative rate dropped pretty much immediately from 20% to ~3% to 5% on weekdays, and zero to 1% on weekends, which I can live with. In the year or so since I actually put my back into fixing this, I've gotten maybe 2 false positives.
I don't see long processing times, mail comes through pretty much as I send it in my tests on my VPS, but again, I only get a few hundred mails/day. If I had volume over a few dozen thousand/day, I'd probably just bite the bullet and pay Google (Postini) to make it go away.
- My wife unboxing hers in the semi-sexual consumer garbage nerd way and having a hard time due to over-tight packaging.
- Me unboxing mine in a 5 second flash of steel from a boxcutter. I mean, the name kind of gives it away there. Cut. The box.
I sadly canceled movie time when the outer sleeves of both devices slid cleanly off as soon as we tipped them upright, and the inner box opened just as smoothly. I'm guessing that sometime between shipping devices to Gamestop and Staples, and the time they shipped to pre-order customers, the packaging problem was resolved.
Yet another reason for ubiquitous crypto usage in IM. Use a libpurple-based client with OTR (Pidgin, Adium) and you can avoid much of this mess.