From 0f8a45b45d759f9e192b8ea3e0865ef31e697b78 Mon Sep 17 00:00:00 2001 From: fukachan Date: Sat, 26 Jul 2003 04:29:12 +0000 Subject: translated --- fml/doc/en/tutorial/usage/command.sgml | 63 ++++++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 fml/doc/en/tutorial/usage/command.sgml (limited to 'fml/doc/en/tutorial/usage/command.sgml') diff --git a/fml/doc/en/tutorial/usage/command.sgml b/fml/doc/en/tutorial/usage/command.sgml new file mode 100644 index 00000000..7d10919a --- /dev/null +++ b/fml/doc/en/tutorial/usage/command.sgml @@ -0,0 +1,63 @@ + + + + + command mail (control fml by sendmail mails) + + + +fml accepts control commands which is sent as a mail. +It is called "command mail". + + + + +The use of CUI (makefml/fml) is basic in fml world. + + + + + + + + flow + + + +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. + + + + +The result is aggreagated to one msssage as + +MIME/Multipart + +. This is different from &fml4; behaviour. + + + + + + + + + perl modules of command mails + + + +All modules which CUI, GUI and command mail uses are implented as +FML::Command:: class. + + + + + -- cgit v1.2.1