333 |
allowed in both configuration files. |
allowed in both configuration files. |
334 |
@item RULE |
@item RULE |
335 |
Defines the rules that are used to alter the contents of the |
Defines the rules that are used to alter the contents of the |
336 |
messages. This is the core part of the user configuration file. |
messages (conditional and unconditional rules). |
|
It is not allowed in the system configuration file. |
|
337 |
@end table |
@end table |
338 |
|
|
339 |
@menu |
@menu |
352 |
the machine, but each user can specify its own @samp{CONTROL} section, |
the machine, but each user can specify its own @samp{CONTROL} section, |
353 |
to customize own settings. Of course, not all options can be set |
to customize own settings. Of course, not all options can be set |
354 |
or change by user. Some options can only be set in the system configuration |
or change by user. Some options can only be set in the system configuration |
355 |
file, and some only in user configuration file. Options specified in user |
file, and some only in user configuration file. By default, options |
356 |
configuration file have a @strong{higher} priority that those specified |
specified in user configuration file have a @strong{higher} priority |
357 |
in system configuration file. The @samp{CONTROL} section starts with the |
that those specified in system configuration file. |
|
@w{@code{---BEGIN CONTROL---}} line, and the @w{@code{---END---}} line |
|
|
ends it. |
|
358 |
|
|
359 |
All option names are case insensitive, so you can use |
All option names are case insensitive, so you can use |
360 |
for instance: @code{bind} or @code{BIND} or @code{BiNd}, and so on. |
for instance: @code{bind} or @code{BIND} or @code{BiNd}, and so on. |
500 |
|
|
501 |
@deffn Option ssl @var{yes-or-no} |
@deffn Option ssl @var{yes-or-no} |
502 |
@opindex ssl @var{yes-or-no} |
@opindex ssl @var{yes-or-no} |
503 |
This option enables the TLS/SSL encryption between the MUA (Mail User Agent) |
This option enables the TLS/SSL encryption between the MUA and the MTA. |
504 |
and the MTA (Mail Transport Agent). Value @samp{no} is the default, |
Value @samp{no} is the default, but using the TLS/SSL encryption |
505 |
but using the TLS/SSL encryption is recommended. You should also |
is recommended. You should also specify a private key and a certificate |
506 |
specify a private key and a certificate using the @samp{key} |
using the @samp{ssl-key} and @samp{ssl-cert} keywords (defined below). |
507 |
and @samp{cert} keywords (defined below). @xref{TLS/SSL}, for details. |
@xref{TLS/SSL}, for details. |
508 |
@end deffn |
@end deffn |
509 |
|
|
510 |
@deffn Option ssl-oneway @var{yes-or-no} |
@deffn Option ssl-oneway @var{yes-or-no} |
511 |
@opindex ssl-oneway @var{yes-or-no} |
@opindex ssl-oneway @var{yes-or-no} |
512 |
This option enables the @dfn{ONEWAY} encryption. Use this mode, |
This option enables the @dfn{ONEWAY} encryption. Use this mode, |
513 |
when you want to use the TLS/SSL, but your MUA (Mail User Agent) |
when you want to use the TLS/SSL, but your MUA doesn't provide |
514 |
doesn't provide a support for ESMTP TLS/SSL. Using this option |
a support for ESMTP TLS/SSL. Using this option doesn't require |
515 |
doesn't require using the @samp{key} and @samp{cert} keywords. |
using the @samp{ssl-key} and @samp{ssl-cert} keywords. |
516 |
@end deffn |
@end deffn |
517 |
|
|
518 |
@deffn Option ssl-cert @var{file-name} |
@deffn Option ssl-cert @var{file-name} |
617 |
The @samp{TRANSLATION} section specifies how to translate remote or local |
The @samp{TRANSLATION} section specifies how to translate remote or local |
618 |
user names, or host names or addresses, to local user names. |
user names, or host names or addresses, to local user names. |
619 |
The @samp{TRANSLATION} section is available @emph{only} in the system |
The @samp{TRANSLATION} section is available @emph{only} in the system |
620 |
configuration file. It starts with the @w{@code{---BEGIN TRANSLATION---}} |
configuration file. Syntax: |
|
line, and the @w{@code{---END---}} line ends it. Syntax: |
|
621 |
|
|
622 |
@smallexample |
@smallexample |
623 |
@group |
@group |
700 |
remove @samp{[}@var{key}@samp{]} |
remove @samp{[}@var{key}@samp{]} |
701 |
@end smallexample |
@end smallexample |
702 |
|
|
703 |
The rule system is defined in @dfn{RULE} section, which begins with a |
The rule system is defined in @dfn{RULE} section. |
|
@w{@code{---BEGIN RULE---}} and ends with an @w{@code{---END---}} |
|
|
statements. |
|
|
|
|
704 |
The statements within this section are executed sequentially. |
The statements within this section are executed sequentially. |
705 |
Each statement is either an @dfn{action} or a @dfn{conditional |
Each statement is either an @dfn{action} or a @dfn{conditional |
706 |
statement}. |
statement}. |
1886 |
GNU Anubis supports the TLS/SSL (via the GnuTLS, a Transport Layer Security |
GNU Anubis supports the TLS/SSL (via the GnuTLS, a Transport Layer Security |
1887 |
Library available at @w{@uref{http://www.gnutls.org/}}, or OpenSSL, |
Library available at @w{@uref{http://www.gnutls.org/}}, or OpenSSL, |
1888 |
a cryptographic package available at @w{@uref{http://www.openssl.org/}}), |
a cryptographic package available at @w{@uref{http://www.openssl.org/}}), |
1889 |
but your MTA (Mail Transport Agent) must provide the STARTTLS command first. |
but your MTA must provide the STARTTLS command first. This can be checked by: |
|
This can be checked by: |
|
1890 |
|
|
1891 |
@smallexample |
@smallexample |
1892 |
@group |
@group |
1898 |
@noindent |
@noindent |
1899 |
The server will response with all its available commands. |
The server will response with all its available commands. |
1900 |
If you see the STARTTLS, then you can use the TLS/SSL encryption. |
If you see the STARTTLS, then you can use the TLS/SSL encryption. |
1901 |
If your MUA (Mail User Agent) doesn't support the TLS/SSL encryption, |
If your MUA doesn't support the TLS/SSL encryption, but your MTA does, |
1902 |
but your MTA does, then you should use the @samp{oneway-ssl} keyword in your |
then you should use the @samp{oneway-ssl} keyword in your configuration |
1903 |
configuration file. Before using the TLS/SSL encryption, you must generate |
file. Before using the TLS/SSL encryption, you must generate a proper |
1904 |
a proper private key and a certificate. You can do it simply with: |
private key and a certificate. You can do it simply with: |
1905 |
|
|
1906 |
@smallexample |
@smallexample |
1907 |
@group |
@group |
1934 |
|
|
1935 |
@noindent |
@noindent |
1936 |
@strong{Caution:} Each client can specify its own private key |
@strong{Caution:} Each client can specify its own private key |
1937 |
and a certificate by adding the @samp{key} and @samp{cert} keywords |
and a certificate by adding the @samp{ssl-key} and @samp{ssl-cert} |
1938 |
in its own user configuration file. |
keywords in its own user configuration file. |
1939 |
|
|
1940 |
@noindent |
@noindent |
1941 |
@xref{Encryption Settings}, for details. |
@xref{Encryption Settings}, for details. |