Compliance will be spotty.  With certain topics relating to JOBS or its
similar POSITIONS, it is best to define them in their plural form - that
way their properly enter singular form with wildcard match e.g.,

SUBJECT: JOB: patron services

would match the defined JOBS: topic (assuming you did not also have a
defined topic of JOBTRAINING).

It goes w/o saying that you must have a well-defined and understood
document on how to use topics and the context in which they should be used.

Some topics might be permanent like JOBS, and others transient (topic du
jour).  Knowing how to handle that as a list-owner would be useful.

Here is something I wrote quite a while ago -- feel free to plagarize or
improve upon it:

It takes 3 things to accomplish your task via Revised LISTSERV techology:

1) list-owner has setup the list's TOPICS feature in the definition (see
example below)

2) you, the subscriber, have done a LISTSERV

   SET listname TOPICS: -FWD

   which only is effective for mail distributions, and not
   for DIGEST/INDEX mailings

3) the sender uses a valid Subject: in their posting

   SUBJECT: FWD: xxxxxxx

Here is an example syntax using HEPROC-L topics=

* Topics=          HEJ,Con1,Con2,Con3,Con4,Con5,Con6,Con7,Con8,Con9

Notice that there is nothing magical about FWD and is not a valid
explicit topic for this list (thus it would be treated as the reserved
OTHER: topic).