new postfix style format configuration files (.cf files). usage of CUI is almost same as one of &fml4; (it is same as could as possible). You can use CUI (makefml and fml command) to create/remove an ML, to add/remove/change an addresse of ML members, to add/remove/change an address of remote administrators, to see log and member list, et.al. Makefml and fml are same programs except for argument order. CGI interface. The functions are a subset of CUI ones. article delivery, header rewriting and several filters. command mail for users. command mail (admin command) for remote administratoin by mail. automatic analyzer of error messages. IPv6 ready. tiny thread track system. built-in module for HTML converter of articles. support automatic conversion by default. main programs (fml/libexec): fml.pl distribute command error utilities: fmladdr fmlailas fmlconf fmldoc fmlhtmlify fmlsch makefml fml Abstracted IO to get member list in unified way from a file, /etc/group, NIS, SQL. You run GNU autoconf firstly, and "make install". It is standard in the world of open sources. This procedure is different from &fml4; installation steps. It may confuse you if you are customered with &fml4; But &fml8; is more friendly for package systems of free unix like systems. The main differece between &fml4; and &fml8; in installation is "work by root", "use of configure", and editing of configuration files: /usr/local/etc/fml/main.cf and /usr/local/etc/fml/site_default_config.cf. Suppose we create a new ML named elena ML (elena@fml.org). The brief flow of installation is as follows: Download &fml8; source and expand it on the disk. Install it by user root. Firstly, change user to "root" and create the user "fml" and the group "fml". Secondly, run configure and "make install". % su root # groupadd fml # useradd -m -g fml fml # ./configure # make install By default, main programs such as distribute, command, et.al. are installed into /usr/local/libexec/fml/. Also, installer installs utility programs to /usr/local/bin. You can control paths by configure options. These are wrappers to call real programs at /usr/local/libexec/fml/. Perl modules are installed into /usr/local/lib/fml/$fml_version/ and message templates et.al. are installed into /usr/local/share/fml/$fml_version/. Change user to "fml", create elena ML for test. % su fml % makefml newml elena You can use "fml" instead of makefml. Both are same except for the syntax. % su fml % fml elena newml Set up MTA. Test. Cutomize your ML. Please install by user root. It is different from &fml4;. Create an ML by CUI (makefml). To create elena@fml.org ML (fml.org is the default domain), run % su fml % makefml newml elena . See the section for more details. In the virtual domain case, specify the whole address as an argument. For example, to create an ML elena@nuinui.net, run the following command: % su fml % makefml newml elena@nuinui.net In the case of the default domain (fml.org) % su fml % makefml subscribe elena rudo@nuinui.net in the case of virtual domain (nuinui.net), specify the whole adress of ML. % su fml % makefml subscribe elena@nuinui.net fukachan@sapporo.iij.ad.jp In the case of the default domain (fml.org), % su fml % makefml unsubscribe elena rudo@nuinui.net in the case of virtual domain (nuinui.net), specify the whole adress of ML. % su fml % makefml unsubscribe elena@nuinui.net fukachan@sapporo.iij.ad.jp "makefml config" is a CUI to customize ML by menu form. BUT NOT yet implemented. Edit configuration files anyway. /usr/local/etc/fml/site_default_config.cf affects all ML on this host irrespective of the default domain or virtual domains. This corresponds to site_init.ph of &fml4;. The format of site_default_config.cf is same as config.cf described below. To customize elena ML, edit /var/spool/ml/elena/config.cf file. The format is a little modified postfix style. It is different from both &fml4;'s config.ph and cf. Add or modify the least variables. If unspecified, the default value is used. The default value depends fml version and is defined at /usr/local/etc/fml/defaults/${fml_version}/default_config.cf The library path depends fml version. This technique ensures the easy upgrade/downgrade procedure. This is a feature of &fml8;.