[PREVIOUS CHAPTER] [NEXT CHAPTER]

7 To change the configuration of a mailing list

       /usr/local/fml/makefml config listname

    e.g.   /usr/local/fml/makefml config elena

    You can configure the "elena" mailing list interactively. You see the
    following recursive menu, so please select one and answer it.
    See 9.0 for more "config.ph".

    ~/.profile ~/.bash_profile (?)

      MAKEFML_LANG=euc; export MAKEFML_LANG

    ~/.cshrc ~/.tcshrc
      setenv MAKEFML_LANG euc

    7.1	TOP MENU

       === TOP MENU ===

       Mailing List Addresses
            FOR POST          elena@baycity.asia
            FOR COMMAND       elena-ctl@baycity.asia
       _______________________

       0    END
       1    POLICY OF ACCESS (WHO CAN POST AND USE COMMANDS)

            [POST]
              PERMIT_POST_FROM                 moderator
              WHEN POST FROM NOT MEMBER        reject

            [COMMAND]
              PERMIT_COMMAND_FROM              members_only
              WHEN COMMAND FROM NOT MEMBER     reject

       2    REGISTRATION METHOD TYPE

            AUTO_REGISTRATION_TYPE             confirmation
            UNSUBSCRIBE_AUTH_TYPE              address

       3    SETTINGS AROUND COMMANDS
                  address for command          elena-ctl@baycity.asia

       4    ML REMOTE ADMINISTRATION
                         PERMIT ?              NO
                         AUTH_TYPE             crypt

       5    HEADER_CONFIG
            SUBJECT_TAG_TYPE
            REWRITE_TO                         To: is original (pass through)

       6    OPTION

       7    SECURITY & FILTERING
       ************************************************************

       Which section? (0-7) [0]

    Please input the number you choose, you see the similar menu in the
    next hierarchy.  When you see "[y/n]", please input y(yes) or n(no).

       Mailing List Addresses

       1    POLICY OF ACCESS (WHO CAN POST AND USE COMMANDS)

    The list of choice is

    	post from anyone			anyone
    	post from only a member			members_only
    	post form only a moderator		moderator

    If mail comes from not a ML member, what action should be done?
    (=> Section 7.2)

    	send back "deny" file to notify "reject"	reject
    	automatic registration/subscription		auto_subscribe
    	ignore the mail					ignore

    In default, the mode of FML is
    	post from only a member			members_only
    and
    	send back "deny" file to notify "reject"	reject.

    Automatic registration is done when mail comes to an address form not
    member and the mode for the address is "auto_subscribe".

    * MANUAL REGISTRATION

    It is default. If fml receives subscribe request, fml sends back a
    confirmation to the user. If the user replies it and fml confirms it,
    fml sends "someone wants to join our ML" to ML maintainers. After
    this, ML maintainers adds the user.

    How to add depends on the configuration. In default fml expects a
    maintainer edit member lists by hand. If you use remote administration
    commands, please enable it explicitly.

       [COMMAND]

       3    PERMIT_COMMAND_FROM                members_only
       4    WHEN_COMMAND_FROM_NOT_MEMBER       auto_subscribe

       2    REGISTRATION METHOD TYPE

            AUTO_REGISTRATION_TYPE             confirmation
            UNSUBSCRIBE_AUTH_TYPE              address

    The automatic registration type. The default is "confirm" which
    requires the confirmation of subscription will.
     (=> Section 7.3)

       3    SETTINGS AROUND COMMANDS
                  address for command          elena-ctl@baycity.asia

    The address for command (=> Section 7.4).
    You can select e.g.
    	listname-ctl
    	listname
    	fmlserv (listserv style interface)

       4    ML REMOTE ADMINISTRATION
                         PERMIT ?              NO
                         AUTH_TYPE             crypt

    You maintain the ML in remote? or not. And the default type is
    "crypt". This is "password authentication" and the password is saved
    as a crypted. (=> Section 7.5)

                        AUTH_TYPE              crypt

    Header configuration, e.g. Subject Tag Type (=> Section 7.6).

       5    HEADER_CONFIG
            SUBJECT_TAG_TYPE
            REWRITE_TO                         To: is original (pass through)

    Other options (=> Section 7.7).

       6    OPTION

    Special functions for security (=> Section 7.8 17.0).

       7    SECURITY & FILTERING

    7.2	Manual/Automatic Registration and Access Control Policy

      MENU => POLICY OF ACCESS (WHO CAN POST AND USE COMMANDS)

       WHO CAN POST AND COMMAND

       0    END

       [POST]

       1    PERMIT_POST_FROM                   members_only
       2    WHEN_POST_FROM_NOT_MEMBER          reject

       [COMMAND]

       3    PERMIT_COMMAND_FROM                members_only
       4    WHEN_COMMAND_FROM_NOT_MEMBER       reject
       ************************************************************

          policy (0-4) [0]

    The permission for post address has the following choice:
    	post from anyone			anyone
    	post from only a member			members_only
    	post form only a moderator		moderator

    If mail comes from not a ML member, what action should be done?

    	send back "deny" file to notify "reject"	reject
    	automatic registration/subscription		auto_subscribe
    	ignore the mail					ignore

    Caution: you can use "auto_regist" but it is obsolete in fml 3.0.
             It works even in fml 3.0 for compatibility.
    http://www.fml.org/fml/UPGRADE-3.0-e/index.html

    The example of an automatic registration setting.

       3    PERMIT_COMMAND_FROM                members_only
       4    WHEN_COMMAND_FROM_NOT_MEMBER       auto_subscribe

    If you select 1,

       ************************************************************
       ADDRESSES FOR POST                  elena@baycity.asia
       PERMIT_POST_FROM                   members_only

       0    END
       1    members_only
       2    anyone
       3    moderator
       ************************************************************

             Permit post from  (0-3) [0]

    Please select one of them.

    * Restrict persons who can post to ML, but distribution list is
    automatic registered.

    $REJECT_COMMAND_HANDLER can have a value 'auto_asymmetric_regist'. If
    defined, FML uses delivery list controlled by automatic registration
    and authentication list edited by hand (or makefml).
    This configuration may be useful to make one way information delivery.
    But fml checks a poster by From:, so you may have to consider
    moderator or PGP authentication.

    	elena/actives	delivery list (automatic registration)
    	elena/members	authentication list (edit by hand)

    In all cases, even if "anyone" is selected, FML denies From: addresses
    which matches $REJECT_ADDR. $REJECT_ADDR is for example, "root",
    "MAILER-DAEMON". We reject these addresses since these are public and
    not personal since such an address may be a fake. If you permit anyone
    in fact, not define $REJECT_ADDR in config.ph.

    7.3	The type of Automatic Registration

    MENU => REGISTRATION METHOD TYPE => AUTO_REGISTRATION_TYPE

    If you select "auto_subscribe" in either REJECT_POST_HANDLER or
    REJECT_COMMAND_HANDLER, you can see the following menu

       ************************************************************
       AUTO_REGISTRATION_TYPE       confirm

       0    END
       1    confirmation
       2    body
       3    subject
       4    no-keyword
       ************************************************************

    [description]
    	confirmation
    			RECOMMENDED AGAINST SUBSCRIBE ATTACK!
    			the server asks the user (From:) the confirmation
    			of subscription will.
            body
    			A keyword "subscribe" in the body is required
    			to add him.
    			If the keyword not exists or is not matched,
    			not added.
            subject
    			A keyword "subscribe" in the subject is required
    			to add him.
    			e.g. Subject: subscribe
    			If the keyword not exists or is not matched,
    			not added.
            no-keyword	added if the mail comes from a not member.

    MENU => REGISTRATION METHOD TYPE => UNSUBSCRIBE_AUTH_TYPE

    enable confirmation in "unsubscribe" command?(default "NO")

    MENU => REGISTRATION METHOD TYPE => CHADDR_AUTH_TYPE

    enable confirmation in "chaddr" command?(default "NO")

    7.4	Address for ML commands

       3    COMMAND ADDRESS
                  address for command          elena-ctl@baycity.asia

    In default, fml sets up these addresses for elena ML

    	elena		for post
    	elena-ctl	for command
    	elena-admin	for maintainer. Human reads mails for this address.

    We suppose several environments,
    	* You can not control /etc/aliases freely.
    	  You have a few limited address.

    	* You DO NOT USE well-known addresses such as "listserv".
    	  You set up "elena" for post, "elena-ctl" for "elena" ML's command.
    	  For security and the concept "ML is a personal communication",
    	  I recommends this style

    	* You use listserv-style. Your choice is "fmlserv" listserv emulation.

       ************************************************************
       0    END
       1    CONTROL_ADDRESS                 elena-ctl@baycity.asia
       2    MAIL_LIST_ACCEPT_COMMAND        NOT USE
       ************************************************************

    * CONTROL_ADDRESS (gives the following menu)

       ************************************************************
       COMMAND ADDRESS                      elena-ctl@baycity.asia

       For command, which address you use?
       (here DOMAINNAME = baycity.asia);

       0    END
       1    elena-ctl@$DOMAINNAME
       2    elena@$DOMAINNAME
       3    fmlserv@$DOMAINNAME
       4    NOT USE

       In default, we use "listname-ctl" format address for command only.
       If you choice "listname" for commands,
       your mailing list address receive both posting and commands.
       "fmlserv" is the listserv/majordomo style interface of fml.
       ************************************************************

          which type (0-4) [0]

       COMMAND ADDRESS                      *** Command Unavailable ***

    *  MAIL_LIST_ACCEPT_COMMAND (default: NO)

    This menu enables both elena and elena-ctl accepts "# command" trap
    for backward compatibility.

    7.5	Remote Administration

    In default we do not permit remote administration for security.  You
    need to enable this function by yourself.  Please see file
    "help-admin" for remote administration commands.

       ************************************************************
       REMOTE ADMINISTRATION
       Do you maintain the ML in remote?        no

       0   END
       1   REMOTE ADMINISTRATION              NO
       2   REMOTE_ADMINISTRATION_AUTH_TYPE    crypt
       3   ADMIN_ADD_SEND_WELCOME_FILE        NO
       ************************************************************

          which (0-3) [0]

    *  REMOTE_ADMINISTRATION (default: NO)

    If you maintain the ML in remote, please select "yes". You can control
    ML to send "# admin command" or "# approve PASSWORD command" format
    commands.

    *  REMOTE_ADMINISTRATION_AUTH_TYPE (default: crypt)

    set up the authentication type in remote administration.

       ************************************************************
       REMOTE_ADMINISTRATION_AUTH_TYPE          crypt

       0    END
       1    pgp
       2    crypt
       3    md5
       4    address
       ************************************************************

    	pgp		PGP based authentication

    	crypt		password authentication
    			the password is saved in ML/etc/passwd in crypted form

    	md5		password authentication
    			the password is saved in ML/etc/passed in md5 form

    	address		From: field's address exists in members-admin
    			* members-admin is the default of $ADMIN_MEMBER_LIST

    *  ADMIN_ADD_SEND_WELCOME_FILE (default: no)

    When you do 'admin add' to add a user to your ML, do you want to send
    WELCOME_FILE to the user? In default, fml does nothing. It is your job
    to notify the registration.

    7.6	Header Configurations

       ************************************************************
       0  	END

       * Subject: TAG
       1  	SUBJECT_TAG_TYPE
       2  	SUBJECT_TAG_FIGURE                 6

       * To:
       3  	REWRITE_TO                         To: is original (pass through)

       * Date:
       4  	DATE_TYPE                          original-date

       5  	PASS_ALL_FIELDS                    YES
       6  	PASS_RECEIVED_THROUGH              YES

       ************************************************************

    *  SUBJECT TAG TYPE (default: nothing)

    You can configure the listname and the sequence number of the article
    in the subject.  e.g. You like Subject: [Elena:00010] ? (though I like
    such a syntax does not exists (I recommended)). You can select one of
    the following types.

              Subject: (Elena:00100)
              Subject: [Elena:00100]    (hml 1.6 compat)
              Subject: (Elena 00100)
              Subject: [Elena 00100]
              Subject: (Elena,00100)
              Subject: [Elena,00100]
              Subject: (Elena)
              Subject: [Elena]
              Subject: (00100)
              Subject: [00100]

    *  SUBJECT_TAG_FIGURE (default: nothing, which implies 5)

       0 padding figures in the Subject TAG.

    *  REWRITE_TO (default: 0, not rewrite and pass the original To:)

       *  To: elena@baycity.asia, NON-MAIL-LIST-ADDRESS

    	We always overwrite To: to To: $MAIL_LIST but not ignore original To:.
    	We rewrite To: to

       * To: elena@baycity.asia

    	always overwrite To: to To: $MAIL_LIST

       * pass through the original To:

    	original To: (fml 2.2 default)

    *  DATE_TYPE (default: original-date)

    	Date: is original? Date: is the time when fml is kicked off and
    	the original is in X-Posted: or X-Original-Date: ? and so on...

    *  PASS_ALL_FIELDS (default: yes)

    Do you pass all fields in the header or not? If you ignore superfluous
    X-* fields, please set this. The format of the header used by FML
    default is defined as @HdrFieldsOrder. Even in "yes", fml ignores
    $SKIP_FIELDS (Received: and Return-Receipt-To) fields to avoid loops
    and hop count expiration errors. see the next menu.

    *  PASS_RECEIVED_THROUGH (default: no)

    FYI: The following functions are prepared to customize the mail header
    more precisely.

    	&ADD_FIELD
    	&DELETE_FIELD
    	&COPY_FIELD
    	&MOVE_FIELD
    	&DEFINE_FIELD_FORCED
    	&DEFINE_FIELD_ORIGINAL
    	&DEFINE_FIELD_OF_REPORT_MAIL
    	&DEFINE_FIELD_PAT_TO_REJECT

    7.7	Other Optional Settings (e.g. MIME, Automatic Html Generation)

       ************************************************************
       0    END
       1    HTML_GENERATION               NO
       2    SPOOLING                      YES
       3    FLOCK                         YES
       4    SMTP
       5    USE_MEMBER_NAME               NO
       6    LANGUAGE
       7    VARIABLE_OFF_ON               off/on toggle variables
       ************************************************************

    *  HTML_GENERATION

       ************************************************************
       0    END
       1    AUTO_HTML_GEN
       2    HTML_THREAD_REF_TYPE   	prefer-in-reply-to
       3    HTML_STYLESHEET_BASENAME
       4    HTML_INDEX_UNIT
       5    HTML_INDENT_STYLE
       ************************************************************

    If you set AUTO_HTML_GEN to "yes", you will have the directory for
    elena ML /var/spool/ml/elena/htdocs/ which contains the html'ed
    articles here. In default articles are collected in each day directory
    below here.  Each directory has index.html and thread.html. index.html
    is the menu for the ML sequence order, thread.html is threaded menu
    for articles.

    *  SPOOLING (default: yes)

       articles is spooled in $DIR/spool or not?

    *  FLOCk (default: yes)

       flock or not for lock algorithm. If no, rename() based lock is done.

    *  SMTP

       USE_OUTGOING_ADDRESS (default: NO)
    	fml.pl => list-outgoing => expand

       USE_VERP (default: NO)
    	Variable Envelope Return-Paths

    *  USE_MEMBER_NAME
       relate "address" with "real name"

    *  LANGUAGE

       MESSAGE_LANGUAGE (default: Japanese or English determined in installation)
    	Message Language Extension

    Which language you use in error reply? Default language is the same as
    $LANGUAGE asked and determined in installation.

          7    VARIABLE_OFF_ON               off/on toggle variables

    7.8	Security

    *  set up several parameters related with security.
       If you run "make secure", you can get the same effect.
       See 17.0 for "more secure".

       MENU => SECURITY => MORE_SECURE => "y"

    *  FILTERING FOR MAIL BODY

    Reject empty mails or only "unsubscribe" mails.
    If MIME/Multipart mail is input, fml checks only the first block.

    *  USE_DISTRIBUTE_FILTER (default: NO)
       Do you use filter? answer "yes" if you use this (recommended).

    *  FILTER_ATTRIBUTE

     * FILTER_ATTR_REJECT_COMMAND (default: no)

     * FILTER_ATTR_REJECT_COMMAND (default: no)
       reject "#help" posted to a ML. ("yes" is recommended)

     * FILTER_ATTR_REJECT_2BYTES_COMMAND (default: no)

       Japanese specific

     * FILTER_ATTRIBUTE => FILTER_NOTIFY_REJECTION (default: no)

     * FILTER_ATTRIBUTE => FILTER_NOTIFY_REJECTION (default: no)
       report the rejection to the sender?

     * FILTER_ATTRIBUTE => FILTER_ATTR_REJECT_MS_GUID (default: no)

       reject files with M$ GUID, which may be a file with macro definition,
       e.g. Melissa virus.

    *  USE_MTI (Traffic Monitor; default NO)

    Inspect the ML traffic. If the traffic is over some threshold, fml
    regard it as mail bomb and rejects mails from the sender.

    *  MAX_MAIL_SIZE (default: nothing, == infinite)

    The maximum size of mail (for both article and command mail). This
    size must depend on the policy that your ML accepts mail with
    appended files.

    notify the rejection that your mail size is too big to the sender.  If
    not, the sender retries to send big mails. If the mail format is
    message/partial, fml guesses the total mail size and compare it with
    $MAX_MAIL_SIZE.

    send "it is rejected" to ML as a distribution.

    *  ADDR_CHECK_MAX (default: 3)

    How severe fml checks the address? If 3, fml identifies addresses in 3
    level domains. beth.fml.org and jo.fml.org differs but beth.lw.fml.org
    and jo.lw.fml.org is same in 3 level comparison.

    *  MAXNUM_COMMAND_INPUT (default: infinite)

       The max number of commands in on mail.

    *  REJECT_ADDR (the account name list to ignore against mail loop)
       see => 7.2

    *  USE_LOG_MAIL (default: NO)

    For debug (and against tricks), it may be useful to save the latest
    $USE_LOG_MAIL mails (2K bytes). The cache is stored in $DIR/var/Mail/

    *  USE_ENCRYPTED_DISTRIBUTION (default: no)

    PGP encrypted ML. Need pgp configuration.

[PREVIOUS CHAPTER] [NEXT CHAPTER]

    Copyright (C) 1993-2000 Ken'ichi Fukamachi
    All rights of this page is reserved.

    # This Document(html format) is automatically geneareted by fwix.pl.
    # fwix (Formatter of WIX Language) is fml document formatter system
    # designed to generate plaintext, html, texinfo and nroff from one file.