AndrewR's dashboard

doneal:
Sunbelt replied to me off these forums, and provided a temp work-around. It's a known issue that they are working on, apparently.
To fix the Outlook Hang problem, unregister the following DLL by running this command;
regsvr32 -u "C:\program files\sunbelt software\sbeagent\sbamoutlook.dll"

I've had some success with some clients by running this, and some others not.

I have, since this question, upgraded my exchange to 2007 with server 2008. I have also created the Global AntiSpam rule, as well as duplicating it in the Default AntiSpam policy with the same addresses for the block, and it doesn't seem to be working. People are still getting email from it.
I'm trying to block a certain email/domain from getting to my users, but they still are. I one case, when trying to troubleshoot, I read in the email header that the email passed through because it was in the users "allowed senders" list (or in their contacts, I guess).
This is a global block, so should not matter, correct?
If someone else can confirm that this way to block an email address works?

PS: again, as a work around, I added a transport rule from exchange to deal with this, and it works alright, but I'd rather do it through Ninja.

Spankey, are you Beta-testing this for them? I'm wondering if your success with Windows 2008/Exchange 2007 means we'll see a fully supported version soon?
Here's hoping - I've have no spam controls for a week now and it's incredible how much we are receiving without it.

I've had this same issue with my exchange 2000 install as well. Mail flow stopped, due to Ninja hanging somehow (When ninja isn't working, everything stops). The quickest fix for me in that situation, unfortunately, was to uninstall ninja and then reinstall the current build.
Sometimes unbinding/rebinding it from the message store and restarting exchange services helps.
I have a small network, though with only 50 users, so that option was the best at the time.

Is ninja officially supported on Server 2008 now? We are moving to this set up very soon as well.
It's not listed as an option on the main product page.

Thanks Zachary - I have this exact thing set up in the default antispam policy, which all members of exchange belong to, and it did not help. I'll try recreating those rules in the global settings, and see how that goes.
On the other hand, setting up the message filters in Exchange is pretty easy, already worked, and tells the unwanted person that they're not allowed to send, which is kind of nice.
I'll let you know how it goes.