[...]talked about vulnerabilities in Microsoft[...]…

[...]talked about vulnerabilities in Microsoft[...]…

The following comment seems a little like a commercial but the product looks interesting, applicable, and useful so I’m going to allow it. -jm

Thanks for the great tips. I’m sure they will be useful for everybody. In addition I would secure SharePoint by checking and setting properly all security permissions. For doing this there is a new utility that was released just several days ago – security explorer for SharePoint. The most interesting thing about this tool that it represents SharePoint farm as a tree where you can see all your sites and easy manage security permissions, assign SharePoint groups and permission levels, perform permission backup and restore.

The comment below has been edited with phrases and links removed
to keep the focus on the design and operational issues of the technology
and solution (not on the people).

I found these links on Richi’s site to be very useful for my knowledge and
understanding, and in supporting his statement:
– http://richi.co.uk/blog/2006/12/another-challengeresponse-datapoint.html
– http://richi.co.uk/blog/2006/12/boxbe-another-cr-spamhaus.html (This
was of extra interest to me since I have a Boxbe address I use to
experience this technology myself).

And also this link to Justin Mason’s site, http://taint.org/2007/07/19/122638a.html,
which I think shows a valid consideration about the Spam Index referred
to in my post.

I think it’s interesting to reflect on my own situation, with a very low spam
index using gmail’s spam tool and not a challenge-response system (I
only get about 1 message per week in Boxbe).

====================
the edited comment follows:
====================
A very flawed study: challenge/response is a dreadful idea

Justin Mason and I have debunked this study [...].

More at [...]