On 1/14/2010 18:24, David Phillips wrote:
> On Thu, Jan 14, 2010 at 3:37 PM, Eric Thomas <[log in to unmask]> wrote:
>> The only reason not to put LISTSERV behind your spam filter is if the spam filter in question is notoriously trigger-happy. I can immediately think of two examples ;-) The first is when a LISTSERV log was bounced because it contained the string 13:45:18 and the seconds field clearly identified the log as spam of the worst sort. Admittedly, that was several years ago. The second and very recent example is a message that got rejected because it contained the word SPECIALIST. I don't want to type it and get filtered, but cut the first three and last character and you will understand why specialist discussions must be banned ;-)
>
> Participants in a list related to prostate cancer would have
> difficulty with spam filters that stopped email containing
> "SPECIALIST" :-)
>

The solution to these problems is not to bypass the spam filters; the solution
is to fine-tune the spam filters so they do not make brain-dead mistakes like
rejecting messages solely because they contain words like "specialists" or
"cumulative".

--
Paul Russell, Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame