On Fri, 6 Feb 2015, Eugene M. Zheganin wrote:
Hi.
On 06.02.2015 17:05, Niels Dettenbach wrote:
The sieve script is (depending from where or what it should do) in a global
place (or domain) - logged in as cyrus admin - - like imap/sieve/global or by
SIEVE shell - within the cyrus system and the
Hi.
On 06.02.2015 18:05, Niels Dettenbach wrote:
> But btw: Depending of what your filter should do, may be it makes more sense
> in your target scenario to do the filter / rule task on all incoming mail in
> your mailer/MDA/MTA before cyrus - i.e. by your mailers SIEVE implementation
> or othe
Am Freitag, 6. Februar 2015, 17:13:14 schrieb Eugene M. Zheganin:
> Do I understand correctly that now, in order to create a default script
> for each already existing uses I should link the default script for them ?
afaik this is NOT the intention of cyrus "default scripts". technically it
shoul
Hi.
On 06.02.2015 17:05, Niels Dettenbach wrote:
> The sieve script is (depending from where or what it should do) in a global
> place (or domain) - logged in as cyrus admin - - like imap/sieve/global or by
> SIEVE shell - within the cyrus system and then INCLUDED by user scripts which
> should
Am Freitag, 6. Februar 2015, 16:20:22 schrieb Eugene M. Zheganin:
> I really do. The most sad thing - is that I have to read the part that
> isn't yet written. The thought of the author of this particular article
> was dwelling for some reason, there's no explanation about how the
> global script c
Hi,
First, apologies for the top-post. The client I'm responding from doesn't
allow me to quote inline because apparently in 2015 we no longer need to do
that. But I digress...
I think everyone agrees that the state of Cyrus documentation is deplorable,
but it's very understandable. The peo
Hi.
On 06.02.2015 14:46, Niels Dettenbach wrote:
> did you still have read the manual?:
I really do. The most sad thing - is that I have to read the part that
isn't yet written. The thought of the author of this particular article
was dwelling for some reason, there's no explanation about how the
Am Freitag, 6. Februar 2015, 14:20:48 schrieb Eugene M. Zheganin:
> Hi.
>
> How do I assign a default sieve script to each existing user (I can
> write a script and symlink the default sieve script to each sieve user's
> folder, but it seems way rude) ? I have set the
> autocreate_sieve_compiledsc
Hi.
How do I assign a default sieve script to each existing user (I can
write a script and symlink the default sieve script to each sieve user's
folder, but it seems way rude) ? I have set the
autocreate_sieve_compiledscript, but since imapd continues to complain
about the /var/imap/sieve/u/user/d
