Op 2/26/2017 om 4:02 PM schreef Thomas Leuxner:

...

Am 26.02.2017 um 15:52 schrieb Thomas Leuxner <tlx@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@leuxner.net -p ./message.eml

From: User <user@example.com> To: lists@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@rename-it.nl> RCPT TO:<stephan> DATA From: User <user@example.com> To: stephan@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@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@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@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.