On the host which serves ML driver, you can use CUI and edit all configuration files as you like. It implies you are the greatest administrator :) You need no confirmation in using makefml. Person who can login the host of mailing list server has all priviledge for all ML's on the host. So, He/She can edit all configuration files. But He/She may do wrong operations. To avoid careless miss operations, in usual cases you should use CUI (makefml or fml) to configure fml. Of course you can edit files directly if you can understand fml structures. By default we recommend you should use CUI even on the host. fml command is same as makefml command except for the argument order. makefml COMMAND ML OPTIONS fml ML COMMAND OPTIONS Please either as you like. &fmldevel; provides command for each function. Except for some special cases, we should unify all functions into makefml/fml command since such commands can be shared among CUI, GUI and commmnd mail. We should implement sub-command of makefml when some operation may modify the specific ML. you should implement it as a makefml command since it is related to the specific ML. If the data is not related to the specific ML, for example, see the module manual, aliases on the host, we implement specific commands other than makefml/fml. This command begins with ^fml. fmladdr [-n] fmlalias [-n] fmldoc MODULE fmlconf [-n] ML we implement specific commands other than makefml/fml. This command begins with ^fml. The conveter from text to html form. This command is used to convert both fml spool and MH folders. fmlhtmlify [-I DIR] $src_dir $dst_dir §.usage.makefml; §.usage.fml; §.usage.fmladdr; §.usage.fmlalias; §.usage.fmlconf; §.usage.fmldoc; §.usage.fmlhtmlify;