📄 read-me
字号:
MH MH-GEN(8) Now install the configured files into the source areas. (On SYSTEM 5 systems you may need to use "make sys5" to compile mhconfig.) % make % ./mhconfig MH You now proceed based on your choice of a transport system (the setting for mts above). The best interface is achieved with "sendmail" followed by "mmdf" or ("mmdf2"), and then "mh" (stand-alone delivery, not recom- mended). SENDMAIL If you want _S_e_n_d_M_a_i_l to transport messages for _M_H, then go to the mts/sendmail/ directory. % cd ../mts/sendmail/ This directory contains files whose definitions correspond to the confi- guration of your _S_e_n_d_M_a_i_l system. If you have enabled BBoards or POP service, then you will need to re-configure _S_e_n_d_M_a_i_l. First, in the "local info" section of your site's _S_e_n_d_M_a_i_l configuration file, choose a free macro/class (B is used in this distribution), and add these lines: # BBoards support DBbboards CBbboards Second, immediately after the inclusion of the zerobase file, in the "machine dependent part of ruleset zero" section, add these lines: # resolve names for the BBoards system R$+<@$=B> $#bboards$@$2$:$1 topic@bboards Be sure to use tabs when separating these fields. Third, add the line include(bboardsMH.m4) after the line include(localm.m4) in your site's _S_e_n_d_M_a_i_l configuration file. Finally, you should link the file mts/sendmail/bboardsMH.m4 into your _S_e_n_d_M_a_i_l cf/ directory and re-configure _S_e_n_d_M_a_i_l. If you have enabled POP service, a similar procedure must be used on the POP service host, to re-configure _S_e_n_d_M_a_i_l. First, in the "local info" section of your site's _S_e_n_d_M_a_i_l configuration file, choose a free macro/class (P is used in this distribution), and add these lines: # POP support DPpop [mh.6] 11 MH-GEN(8) MH CPpop Second, immediately after the inclusion of the zerobase file, in the "machine dependent part of ruleset zero" section, add these lines: # resolve names for the POP system R$+<@$=P> $#pop$@$2$:$1 subscriber@pop Be sure to use tabs when separating these fields. Third, add the line include(popMH.m4) after the line include(localm.m4) in your site's _S_e_n_d_M_a_i_l configuration file. Finally, you should link the file mts/sendmail/popMH.m4 into your _S_e_n_d_M_a_i_l cf/ directory and re-configure _S_e_n_d_M_a_i_l. MMDF If you want _M_M_D_F to be your transport service, and have NOT specified "mmdf/smtp" (or "mmdf2/smtp") as your mts setting, then go to the mmdf/ directory. (If you're using "mmdf/smtp" or "mmdf2/smtp" as your mts setting, then skip to the next section.) % cd ../mts/mmdf/ This directory contains files whose definitions correspond to the confi- guration of your _M_M_D_F system. If you're running _M_M_D_F-_I, then copy the following files from wherever you keep the _M_M_D_F sources to this directory: mmdf/h/ch.h, mmdf/h/conf.h, utildir/conf_util.h, utildir/ll_log.h, mmdf/h/mmdf.h, utildir/util.h, mmdf/mmdf_lib.a, and utildir/util_lib.a. If you're running _M_M_D_F-_I_I, then copy the following files from where you keep the _M_M_D_F sources to this directory: h/ch.h, h/conf.h, h/dm.h, h/ll_log.h, h/mmdf.h, h/util.h, and lib/libmmdf.a If you have enabled bboards, then the directories support/bboards/mmdfI and support/bboards/mmdfII contain information you'll need to put a UCI BBoards channel in your _M_M_D_F configuration. Similarly, if you have enabled option "mf" and are running _M_M_D_F-_I, then the zotnet/mf/mmdfI/ directory contains information you'll need to put a _U_U_C_P channel in your _M_M_D_F-_I configuration. Finally, the directory support/pop/mmdfII con- tains information you'll need to put a POP channel in your _M_M_D_F-_I_I con- figuration. Note that _M_M_D_F-_I_I is distributed with the BBoards channel, although the version in the _M_H distribution might be more current, the version in the _M_M_D_F-_I_I distribution has been tested with that revision of _M_M_D_F. 12 [mh.6] MH MH-GEN(8) MMDF/SMTP If you are using "mmdf/smtp" as your mts setting, then no further MTS-specific action is required on your part! MMDF2/SMTP If you are using "mmdf2/smtp" as your mts setting, then no futher MTS-specific action is required on your part! STAND-ALONE DELIVERY If, instead, you want _M_H to handle its own mail delivery, then no futher MTS-specific action is required on your part! GENERATION Go to the mh.6/ directory and generate the system. % cd ../; make This will cause a complete generation of the _M_H system. If all goes well, proceed with installation. If not, complain, as there "should be no problems" at this step. INSTALLATION If the directories you chose for the user-programs and support-programs ("bin" and "etc" in the conf/MH file) don't exist, you should create them at this point. Before proceeding, you should familiarize yourself with the _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e. To generate an _n_r_o_f_f version, go to the doc/ directory and type: % (cd doc/; make ADMIN.doc) To generate a _t_r_o_f_f version, type % (cd doc/; make guide) instead. If you're already running _M_H at your site, you should also read the _m_h._6 changes documents. The sources are in papers/mh6.5/ and papers/mh6.7/. Next, if you enabled support for the UCI BBoards facility, then create a login called "bboards" with the following characteristics: home direc- tory is /usr/spool/bboards/ with mode 755 (actually, use the value for "bbhome" given in the _M_H configuration file), login shell is /bin/csh (or /bin/sh), and, encrypted password field is "*". The "bboards" login should own the /usr/spool/bboards/ directory. In addition to creating /usr/spool/bboards/, also create /usr/spool/bboards/etc/ and /usr/spool/bboards/archive/. These directories should also be owned by the "bboards" login. [mh.6] 13 MH-GEN(8) MH If you enabled support for POP, then on the POP service host, create a login called "pop" with the following characteristics: home directory is /usr/spool/pop/ with mode 755, login shell is /bin/csh, and, encrypted password field is "*". If you don't have /bin/csh on your system (V7), then /bin/sh is just fine. The "pop" login should own the /usr/spool/pop/ directory. You'll also need to add a line to the /etc/services file and the /etc/rc.local file, see the _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e for more details. If this is not the first time you have installed _M_H, these files will need particular attention: _D_i_r_e_c_t_o_r_y _F_i_l_e_s "etc/" MailAliases, BBoardAliases, mtstailor /usr/spool/bboards/ BBoards, .cshrc, .mh_profile /usr/spool/bboards/etc/ * The MailAliases, BBoardAliases, mtstailor and BBoards files will not be installed over existing copies; you will need to edit these by hand and merge in any changes from your previous _M_H release. The other files under /usr/spool/bboards/ will be overwritten if they exist. You may wish to preserve your old versions of these before installing _M_H. As the super-user, and from the mh.6/ directory, install the system. # make inst-all This will cause the _M_H processes and files to be transferred to the appropriate areas with the appropriate attributes. TAILORING See the _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e for information on tailoring _M_H for the MTS, BBoards, and POP. DOCUMENTATION In addition to this document, the administrator's guide, and the user's manual, there are several documents referenced by the user's manual which may be useful. The sources for all of these can be found under the papers/ directory. OTHER THINGS Consult the directory miscellany/ for the sources to a number of things which aren't part of the mainstream _M_H distribution, but which are still quite useful. FILES Too numerous to mention. Really. SEE ALSO make(1) 14 [mh.6] MH MH-GEN(8) BUGS The _m_h_c_o_n_f_i_g program should be smarter. The Makefiles should know when _m_h_c_o_n_f_i_g has been run and force "make clean" behavior. [mh.6] 1599
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -