Op 2/22/2017 om 8:40 PM schreef Thomas Leuxner:> * Thomas Leuxner <tlx at leuxner.net> 2017.02.20 12:56: > >> Feb 20 07:00:23 nihlus dovecot: master: Dovecot v2.2.devel (8f42a89) starting up for imap, lmtp >> >> This one processed the dovecot-news mail for 2.2.28.rc1 fine which uses a similar sieve rule. I will monitor global rules with this build and report back. > The results seem to be arbitrary. Personal rules _always_ work for flag actions, global rules included do _sometimes_. This means one day the same rule may trigger, the next day it won't. I found no way to reproduce it for global rules in order to narrow down the issue.Could you show me your full configuration (`dovecot -n`)? Regards, Stephan
* Stephan Bosch <stephan at rename-it.nl> 2017.02.24 10:20:> Could you show me your full configuration (`dovecot -n`)? > > Regards, > > StephanLive configuration and scripts sent off-list. Regards Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20170224/b75d6266/attachment.sig>
Op 2/24/2017 om 10:30 AM schreef Thomas Leuxner:> * Stephan Bosch <stephan at rename-it.nl> 2017.02.24 10:20: > >> Could you show me your full configuration (`dovecot -n`)? >> >> Regards, >> >> Stephan > Live configuration and scripts sent off-list.Tried this with your full scripts, part of your public mailbox configuration and this test message: From: User <user at example.com> To: stephan at rename-it.nl Subject: Frop! List-Id: <debian-security-announce.lists.debian.org> Frop! Tried manual delivery several times, with equal results: stephan at drieka:~$ /usr/lib/dovecot/dovecot-lda -p ~/message.eml stephan at drieka:~$ doveadm -f table fetch "uid flags" mailbox ":public/Newsletters/Debian/Security" uid flags 1 \Recent 2 \Recent 3 \Recent stephan at drieka:~$ doveadm -f table fetch "uid flags" mailbox "INBOX" uid flags 14 \Flagged \Recent $MailFlagBit1 15 \Flagged \Recent $MailFlagBit1 16 \Flagged \Recent $MailFlagBit1 So, I cannot reproduce your problem. Could you try this at your end? Regards, Stephan.
Op 2/26/2017 om 4:02 PM schreef Thomas Leuxner:>> Am 26.02.2017 um 15:52 schrieb Thomas Leuxner <tlx at leuxner.net>: >> >>> So, I cannot reproduce your problem. >>> >>> Could you try this at your end? >> Hi Stephan, >> >> Tried with: >> >> $ /usr/lib/dovecot/dovecot-lda -d tlx at leuxner.net -p ./message.eml >> >> From: User <user at example.com> >> To: lists at example.org >> Subject: Frop! >> List-Id: <debian-security-announce.lists.debian.org> >> >> Frop! >> >> It goes right to the INBOX with no flags: >> > This time *with sieve* enabled in mail_plugins for LDA. (I?m using LMTP). The mail gets processed correctly. Does it make a difference for LMTP from the code?That should not matter normally. I tested this at my end, but I saw no different behavior. I created the following file in ~/message-lmtp.eml (substitute MAIL FROM/RCPT TO with whatever you need): LHLO frop MAIL FROM:<stephan at rename-it.nl> RCPT TO:<stephan> DATA From: User <user at example.com> To: stephan at rename-it.nl Subject: Frop! List-Id: <debian-security-announce.lists.debian.org> Frop! . Then I invoked LMTP through its unix socket (using socat tool): stephan at drieka:~$ cat ~/message-lmtp.eml | socat gopen:/var/run/dovecot/lmtp stdio 220 drieka.tds Dovecot ready. 250-drieka.tds 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING 250 2.1.0 OK 250 2.1.5 OK 354 OK 250 2.0.0 <stephan> 1D/3FPsfs1ge/QAASZWA2w Saved Evaluating the results shows that there is still no problem here, since the last delivery is fine (I initially forgot to enable Sieve for LMTP): stephan at drieka:~$ doveadm -f table fetch "uid flags" mailbox "INBOX" uid flags 14 \Flagged \Recent $MailFlagBit1 15 \Flagged \Recent $MailFlagBit1 16 \Flagged \Recent $MailFlagBit1 17 \Flagged \Recent $MailFlagBit1 18 \Flagged \Recent $MailFlagBit1 19 \Recent 20 \Flagged \Recent $MailFlagBit1 stephan at drieka:~$ doveadm -f table fetch "uid flags" mailbox ":public/Newsletters/Debian/Security" uid flags 1 \Recent 2 \Recent 3 \Recent 4 \Recent 5 \Recent 6 \Recent Regards, Stephan.
* Stephan Bosch <stephan at rename-it.nl> 2017.02.26 19:49:> I created the following file in ~/message-lmtp.eml (substitute MAIL > FROM/RCPT TO with whatever you need): > > LHLO frop > MAIL FROM:<stephan at rename-it.nl> > RCPT TO:<stephan> > DATA > From: User <user at example.com> > To: stephan at rename-it.nl > Subject: Frop! > List-Id: <debian-security-announce.lists.debian.org> > > Frop! > .I tested a couple of messages via the socket and it worked, _even_ with a message that previously has been delivered without flags but should have - which is odd to say at least... Still can't find a scheme to narrow it down except it only happens to rules on the included script. Regards Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20170226/5f99717b/attachment-0001.sig>