blob: 74486520de1c6e9f0cfee88a04826a98c4681721 (
plain)
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
|
<!--
$FML: qmail.sgml,v 1.2 2005/07/23 01:57:37 fukachan Exp $
$jaFML: qmail.sgml,v 1.2 2002/07/06 14:55:20 fukachan Exp $
-->
<sect1 id="setup.qmail.aliases">
<title>
MTA Configuration (qmail)
</title>
<para>
"makefml newml" creates the following files for qmail:
<screen>
~fml/.qmail-fml:org-elena
~fml/.qmail-fml:org-elena-admin
~fml/.qmail-fml:org-elena-ctl
~fml/.qmail-fml:org-elena-default
~fml/.qmail-fml:org-elena-request
</screen>
Hence, if /var/qmail/control/virtualdomains contains the following
definition
<screen>
fml.org:fml-fml.org
</screen>
you have only to run "makefml newml" to create an ML in the case of
qmail.
</para>
<warning>
<para>
This configuration assumuss
ML's uses the whole one domain only for mailing list.
</para>
</warning>
<sect2>
<title>
Virtual Domain
</title>
<para>
The logic is same as above. So you need to edit
/var/qmail/control/virtualdomains to make an ML effective
automatically when you runs "makefml newml". This edit needs root
priviledge. Please contact the administrator on it.
</para>
</sect1>
|
