1 |
To convert a sieve script into equivalent Scheme program, executable |
To convert a sieve script into equivalent Scheme program, run: |
|
by guimb, run: |
|
2 |
|
|
3 |
guile -s sieve.scm --file <sieve-script-name> --output <output-file-name> |
sieve.scm --file <sieve-script-name> --output <scm-file-name> |
4 |
|
|
5 |
To compile and execute a sieve script upon a mailbox, run: |
The produced script can then be run as: |
6 |
|
|
7 |
|
guile -s <scm-file-name> [MAILBOX] |
8 |
|
|
9 |
|
If MAILBOX is not given, the script will operate upon the user's system |
10 |
|
mailbox. |
11 |
|
|
12 |
|
To invoke the script directly by its name, add executable bit to its |
13 |
|
permissions. |
14 |
|
|
15 |
|
The same script may be used by mail.local to sieve the incoming mail upon |
16 |
|
its arrival, see node "Programs -> mail.local" in the accompanying |
17 |
|
documentation for more information on this. |
18 |
|
|
19 |
|
To execute the sieve script directly, without saving the produced Scheme |
20 |
|
text to a file, run: |
21 |
|
|
22 |
|
sieve.scm --file <sieve-script-name> [MAILBOX] |
23 |
|
|
24 |
|
The semantics of MAILBOX argument is described above. |
25 |
|
|
|
guimb -f sieve.scm -{ --file <sieve-script-name> -} --mailbox ~/mbox |
|