|
Sender: |
|
Date: |
Mon, 4 Sep 2006 00:51:19 -0400 |
Reply-To: |
|
Content-Transfer-Encoding: |
7bit |
Subject: |
|
From: |
|
Content-Type: |
text/plain; charset=ISO-8859-1; format=flowed |
In-Reply-To: |
|
Organization: |
University of Notre Dame |
MIME-Version: |
1.0 |
On 9/3/2006 11:14, Liz Marr wrote:
>
> The space behind the comma doesn't matter. I don't even think there needs to be
> a space behind the = but all of my lists have it, so I included it in my examples.
The space behind the comma *does* matter. If there is a space after a comma,
everything after the space will be treated as a comment and ignored by LISTSERV.
Example 1:
* Filter= Also,[log in to unmask]
Example 2:
* Filter= Also, [log in to unmask]
The Filter= statement in example 1 will add [log in to unmask] to the list of
addresses which are filtered by LISTSERV. The Filter= statement in example 2
will add nothing to the list of addresses which are filtered by LISTSERV.
I see this error from time to time, usually in a list header which a novice
list owner has attempted to make more readable by inserting a space after
every comma in every keyword. Shortly after completing these apparently
cosmetic changes, the list owner will contact the Help Desk or Messaging
Services to find out why his/her list is no longer working properly.
--
Paul Russell, Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame
[log in to unmask]
|
|
|