blob: 87a13f32d1b787c1e079ad30bb8fd20a0f4caac1 (
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
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
|
<!--
$FML: command.sgml,v 1.2 2005/09/18 13:55:57 fukachan Exp $
$jaFML: command.sgml,v 1.7 2003/04/15 14:51:46 fukachan Exp $
-->
<sect1 id="fml.command.bymail">
<title>
Command Mail (Control fml By Sending Mail)
</title>
<para>
&fml8; accepts control commands which is sent as a mail.
It is called "command mail".
</para>
<important>
<para>
The use of CUI (makefml/fml) is basic in fml world. It is expected you
should use CUI if you can login the mailing list server.
</para>
<para>
The role of command mail is to delegate fml control priviledge to
users who cannot login the mailing list server.
</para>
</important>
<sect2 id="fml.command.bymail.flow">
<title>
Flow
</title>
<para>
Consider elena ML. Send the command mail to elena-ctl@fml.org which
is the address for command mail. MTA receives the mail and finally
kicks off /usr/local/libexec/fml/command program. This program
receives the mail (command mail) from STDIN , processes the requests
and sends back the result to the sender.
The mail to send back is passed to MTA for delivery via SMTP.
</para>
<warning>
<para>
The result is aggreagated to one msssage as MIME/Multipart. This is
different from &fml4; behaviour.
</para>
</warning>
</sect2>
<sect2>
<title>
Perl Modules For Command Mail
</title>
<para>
All modules which CUI, GUI and command mail uses are implented as
FML::Command:: class.
</para>
<para>
In fact, a sub set of FML::Command:: class is allowed as command mail.
$user_command_mail_allowed_commands,
$anonymous_command_mail_allowed_commands and
$admin_command_mail_allowed_commands variables defines it.
</para>
</sect2>
</sect1>
|
