[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dovecot
Subject:    Tracing Sieve actions
From:       aki.tuomi () open-xchange ! com (Aki Tuomi)
Date:       2022-07-20 6:58:17
Message-ID: 511414365.12372.1658300297137 () appsuite-dev-gw1 ! open-xchange ! com
[Download RAW message or body]

Then you should probably look at ManageSieve protocol, available in Dovecot and some \
of clients, especially webmail ones and recently even discussed on this list.

Aki

> On 20/07/2022 09:55 EEST justina colmena ~biz <justina at colmena.biz> wrote:
> 
> 
> Thank you. I will have to look at "basic configuration" for sieving although I \
> don't want things crashing on production. 
> I get too much mail at a publicly available address -- and while SPF+DKIM+DMARC \
> does cut down on the bulk of obvious spam -- the spam that does get through is a \
> little bit too "legitimate" to eliminate without special sieving rules. 
> This stuff really needs to be configurable per user without abusing root privileges \
> and without futzing at the command line, or else it just isn't useful to the end \
> user on the desktop or mobile device. Sieving needs to be either an email client \
> thing, or else a standard interface for rules that can be configured and uploaded \
> to Dovecot from the email client / reader software. 
> https://doc.dovecot.org/configuration_manual/sieve/configuration/#basic-configuration
>  
> 
> On July 19, 2022 10:35:40 PM AKDT, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
> > 
> > 
> > > On 20/07/2022 09:34 EEST Doug Hardie <bc979 at lafn.org> wrote:
> > > 
> > > 
> > > I encountered an interesting problem that one originator was being dumped into \
> > > the Deleted file directly by my sieve.  The sieve file was quite large and it \
> > > was not obvious which entry was causing the issue.  I recall there was a way to \
> > > get sieve-test to show what is going on and which lines it used, but I could \
> > > not replicate it tonight for anything.  I ended up having to change all the \
> > > deliver to the Deleted files to something else and test one at a time to find \
> > > the offending entry.  It took a long time.  How do you get sieve-test to show \
> > > the actual path it took through the file? 
> > > -- Doug
> > 
> > Hi Doug, take a loot at \
> > https://doc.dovecot.org/configuration_manual/sieve/configuration/#trace-debugging \
> >  It might help.
> > 
> > Kind regards,
> > Aki
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.


[prev in list] [next in list] [prev in thread] [next in thread]