1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
<!--
$FML: chapter.sgml,v 1.3 2005/07/20 10:37:45 fukachan Exp $
$jaFML: chapter.sgml,v 1.2 2003/04/15 14:51:47 fukachan Exp $
-->
<chapter id="virtualdomain">
<title>
Virtual Domain
</title>
<para>
2003/10: We enhanced fml8 to handle virtual domains as same way as
default domain.
</para>
<para>
It is difficult to handle virtual domains and the default domain in
the same way.
</para>
<para>
One proper enhancement is using "user@domain" form for the ML name as
an argument of commands. For example, for a virtual domain, use
makefml like this
<screen>
% makefml newml mlname@virtualdomain
</screen>
The following two syntaxes are acceptable for the default domain.
<screen>
% makefml newml mlname@defaultdomain
% makefml newml mlname
</screen>
Fml treats these properly as could as possible. But fml needs some
hints such as ml home directory information for each domain. You need
to prepare /usr/local/etc/fml/ml_home_prefix file for a hint on
mappping between domain and directory.
</para>
<para>
This file name is defined as $ml_home_prefix_maps (formerly
$virtual_maps) in main.cf. $virtual_maps is obsolete but effective
now for compatibility.
</para>
<para>
To handle $ml_home_prefix_maps, you can use "makefml newdomain" and
"makefml rmdomain".
</para>
<sect1 id="virtualdomain.fml8.overview">
<title>
Overview: virtual domain handling in &fml8;
</title>
<para>
It is easy in use.
For the first time to use a virtual domain,
run "newdomain" command to add {domain => directory} relation to
<link linkend="install.virtual">
ml_home_prefix_maps
</link>
(precisely primary_ml_home_prefix_map).
</para>
<para>
After that, you can use "user@domain" form in makefml arguments
in handling virtual domains.
<screen>
makefml newml ML@virtualdomain
makefml add ML@virtualdomain address
makefml bye ML@virtualdomain address
</screen>
Instead, for the default domain,
definitions in ml_home_prefix_maps is not needed
and either of user and user@domain is accpetable.
</para>
<para>
When you use CGI, you need not to use user@domain syntax
since config.cgi knows the domain name the cgi handles.
<screen>
http://lists/~fml/cgi-bin/fml/$domain/admin/config.cgi
</screen>
</para>
<warning>
<para>
The domain name is hard-coded within config.cgi since makefml injects
the domain name in creating config.cgi when "makefml newml" runs.
That is, "config.cgi" does not resolve its domain by the URL.
</para>
</warning>
</sect1>
<sect1 id="virtualdomain.movement">
<title>
Case study: movement ?
</title>
<para>
*** SORRY, NOT YET WRITTEN ***.
</para>
</sect1>
</chapter>
|
