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 ;-) But if you are using a reasonably cautious spam filter, I would consider it "best practice" to put LISTSERV behind the spam filter (and of course monitor it carefully the first few days).

  Eric