In my experience the SourceForge folk are not totally unresponsive. If the maintainers or weighty participants on this list ask SourceForge to consider front-ending lists with spam filtering, they might come closer to considering it.
Personally I'd rather they not do front-end filtering. From what I've heard their past (and possibly current) front-end spamfiltering mechanisms are causing problems for people who need to post to the list.
Clearly I'm capable of doing my own back-end filtering, and if I've got problems with it, I can fix it myself.
However if sourceforge does front-end filtering, if there's problems with it, I can do nothing.
I'm really of the opinion that filters belong on a MTA/MDA which is local to the recipient, and they never belong on a public list server.
Perhaps some very minimalist filters are OK, but in the general sense, filters just don't belong on listservs.. It offers no added value over back-end checks, and reduces flexibility for the end user by forcing someone else's filter config on them.
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
