Displaying 20 results from an estimated 3000 matches similar to: "Error: sieve_execute_bytecode(/var/sieve/global.sievec) failed"
2009 Jul 11
1
sieve_execute_bytecode(/var/vmail/domain1/user/dovecot.sievec) failed
I am trying to implement vacation with sieve in dovecot, but each time
I try to use a sieve rule that sends a mail, like vacation or reject,
I obtain this error code_
sieve_execute_bytecode(/var/vmail/domain1/user/dovecot.sievec) failed
Checking syslog I found this message:
sieve runtime error: Reject: No return-path for reply
Googling I found a report of a problem like this but I can't
2012 Sep 14
1
sieve_execute_bytecode failed with squirrelmail
Hello all,
I'm using dovecot on CentOS 5.8 (official CentOS package) and have lot
of lock and "sieve_execute_bytecode error" in my dovecot.log.
$ cat /etc/redhat-release
CentOS release 5.8 (Final)
$ dovecot --version
1.0.13
The sieve scripts are generated by squirrelmail mail and are mostly mail
filters and vacations notices.
$ yum info squirrelmail.noarch
Installed Packages
2010 May 17
1
Configuring Dovecot SASL
Dovecot ver = 1.1.11
Dovecot -n =
mail:~# dovecot -n
# 1.1.11: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4 ext3
log_timestamp: %Y-%m-%d %H:%M:%S
protocols: imap imaps pop3 pop3s
login_dir: /var/run/dovecot/login
login_executable(default): /usr/lib/dovecot/imap-login
login_executable(imap): /usr/lib/dovecot/imap-login
login_executable(pop3):
2010 May 19
2
how to configure my scripts sieves for the home root
hello list
hello all reader of this list
how to configure my scripts sieves for the home root
I encounter these errors in the logs
2010-05-19 14:14:03 deliver(root): Info: sieve runtime error: Not a
bytecode file
2010-05-19 14:14:03 deliver(root): Error:
sieve_execute_bytecode(/root/.dovecot.sievec) failed
thanks for your advice
thanks
2008 Feb 21
3
sieve problem
Hi all!
Os : Fedora 6
Dovecot version : 1.0-0.1.rc7
Dovecot-sieve version: 1.0.2-6 (this is a problem?)
Config :
# dovecot -n
# /etc/dovecot.conf
protocols: imaps pop3s
disable_plaintext_auth: yes
login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap-login
login_executable(imap): /usr/libexec/dovecot/imap-login
login_executable(pop3):
2007 Aug 11
8
Sieve Vacation cause deliver to die
When a user enable vacation in sieve deliver die and the mail lost. I am
using 1.0.3
Thanks
-------------------------------------------------------------------------------------------------------------------------------------------
in syslog
postfix/pipe[16060]: 8E33017D4: to=<vivi at abc.com.hk>, relay=dovecot,
delay=0.17, delays=0.13/0.01/0/0.03, dsn=5.3.0, status=bounced (Command
2007 Sep 03
2
recipient delimiter results in sieve errors
Hello,
I'm using dovecot 1.0.3 and Dovecot Sieve plugin 1.0.2. Sieve script works
fine with normal addresses, like user at domain.., and messages marked with
"X-Spam-Flag: YES" are delivered directly to INBOX.Spam.
To make deliver understand recipient_delimiter I tried two methods, the
first one as per wiki (tweaking postfix master.cf), and the second one by
tweaking
2008 Jul 13
1
'include' feature in sieve 1.1.5
Hi, all.
I use dovecot-1.1.1 and dovecot-1.1.5 which built by atrpms, and i
use 'include' command to include two/several personal sieve rule file,
but if either of these personal sieve rule files is not exist,
sieve_execute_bytecode failed.
How can i make it just skip the non-exist personal sieve rule file,
and continue to try to include next sieve rule file?
Thanks very much. :)
In
2007 Sep 16
3
Dovecot Sieve crash
I just transferred the files in my home directory from an x86_64 machine
to an i686 machine. This included the .dovecot.sieve and .dovecot.sievec
files in my home root, and the Dovecot index files in my ~/Maildir
directory. Everything seemed to be working until I tried sending an email
that triggers a Sieve "redirect" command, then I got the following in the
logs. I then tried
2008 Oct 13
1
Unkown namespace / sieve
Hello,
I use dovecot + dspam and a very simple global sieve script :
require "fileinto";
if header :contains "X-DSPAM-Result" "Spam" {
fileinto "SPAM";
stop;
}
with dovecot 1.0 all run fine, but moving to 1.1 I experience this in
maillog :
Oct 13 10:31:52 h8h1 deliver(ml at sd2i.com): msgid=<8a24c15885037554724ff966f5458592 at
2009 Mar 24
1
Missing TMP folder - Dovecot 1.2 Beta3
Recently after upgrading to 1.2 Beta3 from 1.1.13, I started to defer
mail. After looking into it deeper, it looks like Dovecot/sieve now asks
for a tmp folder in the imap (maildir) folder. Once I added the tmp
folder as the logs indicants, the mail was processed normally.
I have split my Inbox and imap store to different folder. Looking at
what it's trying to do, it looks to me that
2008 Aug 19
1
sendmail permissions denied
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
With the sieve plugin trying to redirect or send vacation reply I'm
getting the following error:
Aug 19 13:12:52 goku deliver(joeblow): [ID 619685 mail.info] Module
loaded: /use
rM/mail-services/dovecot/lib/dovecot/lda/lib90_cmusieve_plugin.so
Aug 19 13:12:52 goku deliver(joeblow): [ID 848615 mail.info] mbox:
2011 Jan 17
3
Sieve 0.2.2 how to use sievec
Hello list,
How can I compile sieve script under new 0.2.2 version from comandline?
Under root:
#sievec default-before.sieve
sievec(root): Error: user root: Initialization failed: Namespace '': mkdir(/root/data) failed: Permission denied (euid=8(mail) egid=12(mail) missing +w perm: /root, euid is not dir owner)
sievec(root): Fatal: Invalid user settings. Refer to server log for more
2019 Nov 05
2
sievec *.sieve problem.
Hello!
For the second time I've tripped onto this banana peel. :)
I had 2 sieve files in a directory that I wanted to compile:
sievec *.sieve
The result of this is that first.sieve is compiled into second.sieve
instead of first.svbin, thus destroying the source of second.sieve.
Please consider this a bug report. :)
Good luck,
Reio
2017 Apr 07
2
Running sievec as user vmail
My sieve problem ended up a permissions problem. I ran sievec as root
and .svbin needs vmail:mail ownership.
I could always just add the chown command to my process, but I wonder if
there is some 'clean' way to run sievec as user vmail while logged in as
root?
thanks
2009 Oct 02
2
sievec fails when last line is a comment without trailing \n
Hi,
when switching from Dovecot 1.1 + cmusieve to Dovecot 1.2 + sieve
I stumbled upon the following problem:
My sieve files, generated with Dovecot 1.1's managesieve, did not
compile anymore with sieve's sievec.
The error message was:
error: end of file before end of hash comment.
Looking a bit closer I found that the last line, which was a comment,
did not have a trailing newline.
2010 May 03
1
exit codes for 'sievec'
As far as I can tell, 'sievec' always exits with '0' whether there is
an error or not. If that is correct, I believe it should be modified to
exit with some other code if the conversion and writing of the new file
are not completed successfully. I have written a few script files and a
'make' file specifically for sievec. The inability to get an accurate
exit code is
2010 Aug 26
1
Roff typo in sievec.1.in
There is a roff typo in pigeonhole's sievec.1.in. Roff treats the leading apostrophe on line 54 as an invalid command and produces bad output:
dump to be written to stdout. The out-file argument may
also be omitted, which has the same effect as for a com-
piled Sieve binary file. Note that this option is not
The output should be:
2018 Jun 12
1
sievec prints an error if no dovecot running with mail_plugins = stats
Dovecot 2.2.36 + Pigeonhole 0.4.24
Is this an intended behavior?
```
# service dovecot status
dovecot is stopped
# doveconf mail_plugins
mail_plugins = stats
# ls foo.*
foo.sieve
# sievec foo.sieve
sievec(root): Error: stats: open(/var/run/dovecot/stats-mail) failed: No such device or address
# echo $?
0
# ls foo.*
foo.sieve foo.svbin
```
--
-- Name: SATOH Fumiyasu @ OSS Technology Corp.
2019 Nov 05
0
sievec *.sieve problem.
> On 5 Nov 2019, at 9.53, Reio Remma via dovecot <dovecot at dovecot.org> wrote:
>
> Hello!
>
> For the second time I've tripped onto this banana peel. :)
>
> I had 2 sieve files in a directory that I wanted to compile:
>
> sievec *.sieve
>
> The result of this is that first.sieve is compiled into second.sieve instead of first.svbin, thus destroying