Displaying 20 results from an estimated 2000 matches similar to: "Dovecot sieve pigeonhole permission"
2015 Aug 05
1
Dovecot sieve pigeonhole permission
On 05.08.2015 13:06, Steffen Kaiser wrote:
> On Tue, 4 Aug 2015, Gerhard Wiesinger wrote:
>
>>
>> I'm running dovecot in a classical vmail.vmail setup with pigeonhole
>> and LMTP. Permission worked well in the initial setup but currently
>> (maybe after Fedora 22 update) I'm having the following permission
>> issue:
>>
>> lmtp(root):
2015 Aug 05
0
Dovecot sieve pigeonhole permission
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 4 Aug 2015, Gerhard Wiesinger wrote:
>
> I'm running dovecot in a classical vmail.vmail setup with pigeonhole and
> LMTP. Permission worked well in the initial setup but currently (maybe after
> Fedora 22 update) I'm having the following permission issue:
>
> lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary
2015 Aug 25
2
sieve_after seems to ignored ?
Michael Kliewe wrote:
> Hi Per,
>
> On 25.08.2015 11:40, Per Jessen wrote:
>> sieve and managesieve are both working fine, have been for years. Now
>> I want to add a sieve_after script:
>>
>> /etc/dovecot/conf.d/90-sieve.conf :
>>
>> plugin {
>> sieve = ~/.dovecot.sieve
>> sieve_dir = ~/sieve
>> sieve_before =
>>
2015 Aug 25
2
sieve_after seems to be ignored ?
Per Jessen wrote:
> Per Jessen wrote:
>
>> Michael Kliewe wrote:
>>
>>> Hi Per,
>>>
>>> On 25.08.2015 11:40, Per Jessen wrote:
>>>> sieve and managesieve are both working fine, have been for years.
>>>> Now I want to add a sieve_after script:
>>>>
>>>> /etc/dovecot/conf.d/90-sieve.conf :
2018 Mar 22
4
How to stop sieve processing to skip sieve_after scripts ?
Hello the list,
I am trying to achieve filter processing using sieve, but i am not sure I can do what I want.
I want to let the user decide to use my filtering script (sieve_after) or not.According to the documentation, i am trying to stop processing in user sieve script, but processing continue.
I am using dovecot 2.2 (CentOS).
My sieve configuration is:plugin {
? sieve =
2015 Aug 25
2
sieve_after seems to ignored ?
sieve and managesieve are both working fine, have been for years. Now I
want to add a sieve_after script:
/etc/dovecot/conf.d/90-sieve.conf :
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
sieve_before =
sieve_after = ~/sieve/personal.sieve
sieve_subaddress_sep = +
}
I have compiled ~/sieve/personal.sieve to ~/sieve/personal.svbin, but it
doesn't seem to be read. Any
2016 Jul 21
3
Replication sieve scripts.
Hello,
Thanks for the advice. I have looked for the libs and here is the
difference:
Dovecot production env 2.2.10:
/usr/lib/dovecot/modules/doveadm
rw-r--r-- 1 root root 18560 Jan 9 2014 lib10_doveadm_acl_plugin.so
-rw-r--r-- 1 root root 14256 Jan 9 2014
lib10_doveadm_expire_plugin.so
-rw-r--r-- 1 root root 10232 Jan 9 2014 lib10_doveadm_quota_plugin.so
-rw-r--r-- 1 root root
2011 Dec 12
3
simultaneous scripts not running via sieve_before
Hi again everyone,
So I've finally got sieve integration happening on my? REHL Postfix/Dovecot server, with private user scripts happily running when users create them. (we user SquirrelMail, so the avelsieve plugin runs the sieve integration).
Now I'd like to utilise additional per-user scripts (probably via sieve_before), but I've not been able to get my additional scripts to
2011 Aug 01
2
sievec - manual compile of global sieve scripts?
How do you compile global scripts using the sievec command without
making the script directory owned (and group writable) by the vmail user?
http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage
# cd /etc/dovecot/sieve/before/
# (edit some script like spam.sieve that runs for everyone)
# /usr/local/bin/sievec spam.sieve spam.svbin
sievec(root): Error: sieve: binary save: failed to create temporary
2015 Feb 12
2
Dovecot dsync not replicating ".dovecot.sieve -> .sieve/managesieve.sieve" / setactive
Hello,
I've ran into problem with Dovecot and dsync replication. Everything
works perfectly, including replication of sieve scripts, except fact
that if user activates the 'managesieve' ruleset (I'm using currently
Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2"
host, by creating symlink ".dovecot.sieve ->
2020 Oct 21
2
Sieve_before
On 10/21/20 2:12 PM, @lbutlr wrote:
> Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder.
RE: compile, fyi note @
https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts
https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Executing_Multiple_Scripts_Sequentially
the conditions under which you need to
2015 Feb 11
2
dovecot 2.2.15 script_after not executed
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello guys,
I'm having troubles making "script_after" to exec sieve scripts::
So:
plugin {
quota = maildir
quota_rule2 = INBOX.Trash:ignore
quota_rule3 = INBOX.Sent:ignore
sieve = ~/Maildir/sieve/dovecot1.sieve
sieve_before = /etc/dovecot/sieve/global.sieve
sieve_after =
2017 Mar 21
2
Problem with sieve_before
On 03/21/2017 09:06 AM, chaouche yacine wrote:
> Hi Ger,
>
> sieve_before should be a path to sieve script file, not to a directory.
> in your configuration, you set sieve_before to /var/lib/dovecot/sieve/before which is a directory.
I don't get that reading:
https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration
Either file or directory. If a file, it searches for the svbin
2015 May 21
1
sieve permission problem with dovecot.svbin
Hello list,
I am starting to see these in maillog:
dovecot: lmtp(31949, dwright): Error: kXK3KnTpXFXNfAAAU+Cu/Q: sieve:
binary open: failed to open:
open(/var/spool/mail/dwright/.dovecot.svbin) failed: Permission denied
(euid=520(dwright) egid=12(mail) missing +r perm:
/var/spool/mail/dwright/.dovecot.svbin, euid is not dir owner)
But the directory /var/spool/mail/dwright is owned by
2018 Aug 08
1
dovecot Panic: file mail-index-sync-update.c: line 1013
An email came to several users but one user didn't receive it and we got
'Mail delivery failed' message.
As I see from the log below, there were broken index file.
Then dovecot repaired that index and we got the error:
Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map):
assertion failed: (map->hdr.indexid == index->indexid || map->hdr.indexid
== 0)
It was
2016 Jul 20
3
Replication sieve scripts.
I did eventually was forced to do this and setup a 2 node test
environment with the latest dovecot:
/usr/dovecot/sbin/dovecot --version
2.2.25 (7be1766)
/usr/dovecot/sbin/dovecot --build-options
Build options: ioloop=epoll notify=inotify ipv6 openssl
io_block_size=8192
Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw
fail
SQL drivers: mysql
Passdb:
2016 Jan 15
2
sieve - configuration problem
Hello List,
first thanks for previous hints, you helped me a lot.
Unfortunately i have new problem with sieve and executing multiple
scripts sequentially.
This is current conf which is complete working :
#CONF1
plugin {
sieve = ~/sieve/.dovecot.sieve
sieve_plugins = sieve_extprograms
sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter
+vnd.dovecot.execute +editheader
2015 Feb 11
2
dovecot 2.2.15 script_after not executed
On 2/11/2015 8:41 PM, Stephan Bosch wrote:
> On 2/11/2015 7:34 PM, Florin Portase wrote:
>> Hello guys,
>>
>> I'm having troubles making "script_after" to exec sieve scripts::
>>
> Keep in mind that the sieve_after script is only executed when the
> "keep" action [1] is executed or when the implicit "keep" [2] is still
>
2012 Apr 09
2
per user sieve after filters
Hello,
Thanks for dovecot, as it's still the best mail server.
I'd like to use per users sieve_after scripts.
Can I put in my dovecot config file, something like that:
sieve_after = %h/Mails/Sieve/After/
It would be very useful for me, as I'd like to add vacation script to be
executed from this place.
Kind regards,
Andr?.
2015 Feb 12
2
dovecot 2.2.15 script_after not executed
On 2015-02-12 01:01, Stephan Bosch wrote:
> On 2/11/2015 10:37 PM, Portase Florin wrote: On 2/11/2015 8:41 PM, Stephan Bosch wrote: On 2/11/2015 7:34 PM, Florin Portase wrote: Hello guys,
>
> I'm having troubles making "script_after" to exec sieve scripts::
>
> Keep in mind that the sieve_after script is only executed when the
> "keep" action [1 [1]]