response 35 of 40:

Mar 4 03:57 UTC 2010

Yes, I'm using a short whitelist right now with spamassassin.  And a
very short blacklist.  As to whether it works, it's hard to say right
now.  I still get spam which spamassassin almost always throws out
correctly.

response 37 of 40:

Mar 5 15:06 UTC 2010

I don't think that we want a system-wide whitelist or a system-wide
blacklist.  It'd be better to leave what gets tossed out to the
individual.  That's just my opinion, though.

Most corporate spam software just puts potential spam in a separate
location and informs the user so they can decide if it's a false
positive.  If the user doesn't rescue the message in a certain amount of
time, it gets nuked.  Of course, I have no idea how much egregious spam
is deleted before that point.

Definitely the web pages need updating (it's a never-ending job, I'm
sure).  We need to have them be in line with what we are offering and
with our policies.  Making it easier for new users to find what they
need would help if it isn't obvious already.

Having easy to follow instructions for beginners is a great idea.  I
think Grex offered some sort of help manual in the past.  Perhaps, in
addition to the web page updates, that manual needs updating?

Here's an on-line spamassassin configuration generator for users:

   http://www.yrex.com/spam/spamconfig.php 

I don't know how useful that is, but it might help (or it might let
people shoot themselves in the foot more easily).

Oh, and from what I've read about spamassassin whitelisting, it doesn't
reject e-mails from people not in the whitelist per se, it gives e-mails
from the whitelist addresses a very low spam score (-100) so that it is
unlikely they will be marked as spam.  Thus, e-mails still go through
the usual spam filtering.

response 39 of 40:

Mar 6 01:29 UTC 2010

Heh.  Read the man page.  Of course the word assassin is in there too, so
that conjures up other images, I'm sure.