aboutsummaryrefslogtreecommitdiff
path: root/doc/pies.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/pies.texi')
-rw-r--r--doc/pies.texi30
1 files changed, 20 insertions, 10 deletions
diff --git a/doc/pies.texi b/doc/pies.texi
index 22c0f83..3f9ec4b 100644
--- a/doc/pies.texi
+++ b/doc/pies.texi
@@ -153,7 +153,8 @@ described above. This mode of operation is similar to that of
@cindex smtps
The third type of components, supported by @command{pies} are
@dfn{meta1-style} components. As the name suggests this type is
-designed expressly as a support for MeTA1 components, namely
+designed expressly as a support for MeTA1@footnote{See
+@uref{http://www.meta1.org}} components, namely
@command{smtps}. This type can be regarded as a mixture of the above
two. For each meta1-style component @command{pies} opens a socket
after start-up, and then executes the component. Once the component
@@ -1210,9 +1211,16 @@ acl common @{
@node include-meta1
@section Using MeTA1 Configuration File
-@cindex /etc/meta1/meta1.conf
- @command{Pies} is able to take a list of components from MeTA1
-configuration file:
+@flindex /etc/meta1/meta1.conf
+ MeTA1 is a mail transfer agent of new generation, designed
+to replace Sendmail in the future (@uref{http://www.meta1.org}).
+It has a modular structure, each module being an independent
+program, which is responsible for a particular task. The components
+are configured in the MeTA1 configuration file
+@file{/etc/meta1/meta1.conf}.
+
+ @command{Pies} is able to take a list of components directly
+from MeTA1 configuration file:
@deffn {Config} include-meta1 @var{file}
Parse @var{file} as MeTA1 configuration file and incorporate
@@ -1224,12 +1232,14 @@ include-meta1 /etc/meta1/meta1.conf;
@end deffn
Thus, you can use @command{pies} instead of the default MeTA1 program
-manager @command{mcp}.
+manager @command{mcp}. This is particularly useful if you use
+@samp{Mailfromd} (@uref{http://mailfromd.software.gnu.org.ua}) to
+control the mail flow.
-To ensure compatibility with MeTA1, the components read from MeTA1
-configuration are started in the reverse order (i.e. from last to first),
-and stopped in the order of their appearance in @var{file}. Of course,
-this does not affect normal @command{pies} components.
+To ensure compatibility with MeTA1, the components read from its
+configuration file are started in the reverse order (i.e. from last to
+first), and stopped in the order of their appearance in @var{file}.
+Of course, this does not affect normal @command{pies} components.
The following @command{pies} statements are silently applied to
all MeTA1 components:
@@ -1711,7 +1721,7 @@ Display program version and license information and exit.
@node Reporting Bugs
@chapter How to Report a Bug
- Send bug-reports and suggestions to @email{bug-mailfromd@@gnu.org.ua}.
+ Send bug-reports and suggestions to @email{bug-pies@@gnu.org.ua}.
If you think you've found a bug, please be sure to include maximum
information needed to reliably reproduce it, or at least to analyze

Return to:

Send suggestions and report system problems to the System administrator.