9
The \fBsieved\fP command is part of the Sieve implementation for the Dovecot secure
10
IMAP server. Sieve (RFC 5228) is a simple and highly extensible language for filtering
11
e\-mail messages. It can be implemented for any type of mail access protocol, mail
12
architecture and operating system. The language cannot execute external programs and in
13
its basic form it does not provide the means to cause infinite loops, making it suitable
9
The \fBsieved\fP command is part of the Sieve implementation for the Dovecot secure
10
IMAP server. Sieve (RFC 5228) is a simple and highly extensible language for filtering
11
e\-mail messages. It can be implemented for any type of mail access protocol, mail
12
architecture and operating system. The language cannot execute external programs and in
13
its basic form it does not provide the means to cause infinite loops, making it suitable
14
14
for running securely on mail servers where mail users have no permission run arbitrary programs.
16
16
Using the \fBsieved\fP command, Sieve binaries, which are produced for instance by
17
\fBsievec\fP(1), can be transformed into a human\-readable textual representation. This can
18
provide valuable insight in how the Sieve script is executed. This is also particularly useful
19
to view corrupt binaries that can result from bugs in the Sieve implementation. This tool is
20
intended mainly for development purposes, so normally system administrators and users will not
17
\fBsievec\fP(1), can be transformed into a human\-readable textual representation. This can
18
provide valuable insight in how the Sieve script is executed. This is also particularly useful
19
to view corrupt binaries that can result from bugs in the Sieve implementation. This tool is
20
intended mainly for development purposes, so normally system administrators and users will not
21
21
need to use this tool.
23
23
The \fIsieve\-binary\fR argument specifies the Sieve binary file that needs to be dumped. The
29
29
arbitrary data. For the base language implementation two blocks are used: the first containing
30
30
a specification of all required language extensions and the second containing the main Sieve
31
31
program. Compiled Sieve programs are represented as flat byte code and therefore the dump of
32
the main program is a disassembly listing of the interpreter operations. Extensions can define
32
the main program is a disassembly listing of the interpreter operations. Extensions can define
33
33
new operations and use additional blocks. Therefore, the output of \fBsieved\fP depends greatly
34
on the language extensions used when compiling the binary.
34
on the language extensions used when compiling the binary.
37
37
\fB\-x\fP "\fIextension extension ...\fP"
38
38
Set the available extensions. The parameter is a space\-separated list of the active extensions. By
39
39
prepending the extension identifiers with \fB+\fP or \fB\-\fP, extensions can be included or excluded
40
relative to the default set of extensions. If no extensions have a \fB+\fP or \fB\-\fP prefix, only
41
those extensions that are explicitly listed will be enabled. Unknown extensions are ignored and a
40
relative to the default set of extensions. If no extensions have a \fB+\fP or \fB\-\fP prefix, only
41
those extensions that are explicitly listed will be enabled. Unknown extensions are ignored and a
42
42
warning is produced. By default, all supported extensions are available, except for deprecated
43
43
extensions or those that are still under development.