在FreeBSD上使用minimalist组建邮件列表( 四 )


# recipients.
#
# Allowed value from 1 to 50, default to 10
#
# Be careful when using high values, because this may lead to lost some
# recipients in mailing if total length of addresses will exceed allowed
# length of command line, passed to MTA.
#
#maxrcpts = 15
# Delay (in seconds) between deliveries, if there are few ones per message.
#
# Default to none
#
#delay = 15
# Maximal size of message
# Default to none
#
#maxsize = 100000
# Include list information headers (RFC 2369) in outgoing mail. These
# directives are: List-Help, List-Subscribe, List-Unsubscribe, List-Post,
# List-Owner and, optionally, List-Archive.
#
# Available values are: 'no', 'yes' or URL, which points to archive, in
# form: (Comment)
#
# Example:
# list information = (Archive of everything)
#
# Note: comment is optional and may be avoided. Using URL as value in this
# directive implies 'yes' to all rest List-* headers and available only in
# per-list config.
#
# Default value is 'yes'
#
#list information = no
# Strip various "Receipt Request" headers. Currently there are:
#
# . Return-Receipt-To
# . Disposition-Notification-To
# . X-Confirm-Reading-To
#
# Default not to strip
#
#strip rrq = yes
# Add extra headers. It is possible to use this option two and more times -
# Minimalist will glue all these headers, when producing final message.
# Also it is possible to use Macroses (if applicable) a (admin), d
# (domain), l (list), o (owner), n (newline), t (tab) and s (space) in
# these headers.
#
# WARNING! Minimalist doesn't check validity of these headers nor their
# duplicating! Be carefull while using this option.
#
#extra header = X-BeenThere: l@d
#
# By using n, t and s it is possible to construct multiline headers, for
# example:
#
#extra header = X-Multline: first linent second linent third line
#
# the same result may be achieved by combining few directives:
#
#extra header = X-Multilne: first line
#extra header = t second line
#extra header = t third line
# Remove 'Resent-*' headers in incoming mail. These headers are not
# important for message understanding and processing, but some MUA's
# generate incorrect these ones.
#
# Default not to remove.
#
#remove resent = yes
# Modify Message-ID in outgoing message.
#
# If somefirstbody subscribed on two lists on same server and
# somesecondbody crossposts message to these lists and
# somefirstbody's MTA doesn't allow two and more messages with
# same Message-ID, then this first body will receive message only
# once. In this case modification of original message's Message-ID
# will solve this problem.
#
# Modification is done by adding token 'MMLID_xxxxx-' before the
# original Message-ID, where xxxxx is some number between 0 and 99999
#
# Default do not touch Message-ID.
#
#modify message-id = yes
# Send message on subscribe/unsubscribe event to list owner
#
# Default to no
#
#cc on subscribe = yes
#------------------------------------------------------------------#
# These directives can be used in local configs only #
#------------------------------------------------------------------#
# Authentication scheme for list.
#
# NOTE: By default there is 'password' scheme with undefined password, so
# if you want to make administrative requests to list, you must define this
# scheme explicitly.
#
# Examples:
#
# auth = mailfrom doka@kiev.sovam.com:@/usr/local/etc/list.admins
# List users, allowed to make administrative requests. Their e-mails

推荐阅读