On my LISTSERV list, what is the Local keyword, and how do I use it?
When the global definition is not suitable, a LISTSERV owner may decide to set the Service keyword to Local. The Local keyword defines the nodes which are to be considered local nodes for service area checking. For more information on the Service keyword, see On my LISTSERV list, what is the Service keyword, and how do I use it?
Note: To complete the steps in this document, you will need to edit the list header; see On my LISTSERV list, how can I modify the list header?
The LISTSERV machine is automatically considered a local node and does not have to appear in the list. Subscribers from any of the local nodes will receive separate pieces of mail with a single recipient in the "To:" field. In other words, they will never receive a grouped piece of mail (as non-local recipients would) if there is more than one recipient in their node.
Note: "Node" is a generic term that means "anything after the '@' sign in the network address". For instance, "SEARN" and "SEARN.SUNET.SE" are both valid node names. The general syntax is: Local = node1, node2, etc. For example: Local = indiana.edu, purdue.edu By default, this keyword takes its value from the LOCAL variable in LISTSERV's site configuration file. To find out which nodes are considered local, contact the LISTSERV system administrator; see Where can I get help for LISTSERV?
For Indiana University LISTSERV lists, the Local keyword is defined in the site configuration file for each campus:
| Campus | Setting |
|---|---|
| IU Bloomington |
Local= indiana.edu, *.indiana.edu
|
| IUPUI |
Local= iupui.edu, *.iupui.edu
|
| IU Kokomo |
Local= iuk.edu, *.iuk.edu
|
| IU Northwest |
Local= iun.edu, *.iun.edu
|
| IU South Bend |
Local= iusb.edu, *.iusb.edu
|
| IU Southeast |
Local= ius.edu, *.ius.edu
|
For more about LISTSERV, see L-Soft Documentation and Manuals.
This information came from Appendix B of the LISTSERV manual.
Last modified on September 19, 2011.







