Note also that not every command is filtered. The filter is very liberal in what it allows through, for the simple reason that it is difficult to determine when (for instance) "set" is meant as a command word as opposed to when "set" is actually part of the first sentence of the message, ie, "I was trying to set my project to do x when y". But if you type "unsubscribe" in the first line (assuming that it really <is> the first line--no MIME stuff coming before it), LISTSERV <will> bounce the message back to you. If we were to tighten up the filter there would probably be as many complaints asking us to loosen it up as there are now asking us to tighten it up :) One thing I discovered just last week is that LISTSERV will not ignore the MIME bits in a message for the purposes of filtering the first line unless you have "Language= NoMIME" set in the list header (which of course requires 1.8d). When "Language= NoMIME" is set, the MIME bits get stripped and the first line of what the user actually types is seen by LISTSERV as the first line of the message. Otherwise LISTSERV reads the first line of the first MIME part delimiter as the first line of the message. Nathan