smoe.org mailing lists

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
configset  GLOBAL  message_headers <<TAG
[VALUE LINES]
TAG
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
configset listname message_headers <<TAG
[VALUE LINES]
TAG
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Default Value : Reply-To: mj2@smoe.org ... (only first item is shown)
Data Type     : string_array
Category      : deliver
Password Notes: none
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

EXAMPLE:

configset listname message_headers << ENDTAG
X-Loop: msg $SEQNO from listname@example.org
ENDTAG

configset GLOBAL message_headers << ENDTAG
X-Loop: Mj2 server at Example.Org
Reply-To: mj2@smoe.org
ENDTAG


These headers will be appended to the headers of a posted message
when a regular list is specified, or to the headers of replies
from the server (such as token confirmation requests) when the
GLOBAL pseudo-list is specified.  They will not replace any
existing headers.  However, it is possible to use the delete_headers
setting or purge_received setting in combination with the 
message_headers setting if you wish to replace certain headers
in posted messages.

A "Reply-To" header is required for the GLOBAL pseudo-list to 
function properly.  Do not delete it if you change this setting.
Majordomo will normally put
  mj2-owner@smoe.org 
in the "From" header, and 
  mj2@smoe.org
in the "Reply-To" header to prevent mail loops between servers.
The "Reply-To" header allows people to respond to the server more
easily.

There are header traps in place:  see "help configset_block_headers"
for a description of headers which will cause Majordomo to reject 
a message without examining it for commands.  Using the GLOBAL 
block_headers and message_headers settings in tandem can reduce 
the likelihood of mail loops.

Whenever a posted message is approved by the moderators using the 
accept command, it is re-mailed to the list address with an Approved: 
header included.  This causes the message to be delivered immediately
without undergoing any access checks.  Any existing Delivered-To headers 
are removed from the message to reduce the chance of a bounce.

For regular lists, there are other settings that can be used to change
the headers of a message.  See "help configset_reply_to",
"help configset_sender", "help configset_precedence", and 
"help configset_subject_prefix"  for additional information. 

The text of each added header will undergo variable substitution as it
is added to the message.   The variables supported include the standard
substitutions, plus DATE, HOST, MSGNO, SENDER, SEQNO, SUBJECT,
SUBSCRIBED, and USER.  See "help variables" for more information.

Any headers with leading spaces, with control characters or spaces in
their names, or without a colon (':') will be ignored.

See Also:
   help admin_delivery
   help configset_block_headers (for how to block server commands)
   help configset_delete_headers
   help configset_precedence    (for how to add a special header)
   help configset_purge_received
   help configset_reply_to
   help configset_sender
   help configset_subject_prefix
   help variables (for a list of all possible variables and what they mean)

This is the "configset_message_headers" help document for 
Majordomo 2, version 0.1200401130.

For a list of all help documents, send the following command:
   help topics
in the body of a message to mj2@smoe.org.

For assistance, please contact the smoe.org administrators.

Sign In

Sign Out

Subscribe to Mailing Lists

Unsubscribe or Change Settings

Help