- dovecot - dovecot.org

Archive key for the Dovecot Automatic Debian Package Archive (Xi) updated
by Stephan Bosch 28 Feb '17

28 Feb '17

Hi, I've updated the archive key for the Xi archive. So, when updating, you will initially get a key error. To fix this, either upgrade the debian-dovecot-auto-keyring package (preferred), or update your key manually from the archive.key located in the repository root. Regards, Stephan.

1 0

indexer-worker assert in v2.2.28 (fts-lucene)
by Daniel J. Luke 27 Feb '17

27 Feb '17

I upgraded to 2.2.28 and started seeing this logged: indexer-worker(dluke): Panic: file mailbox-list.c: line 1158 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) indexer-worker(dluke): Error: Raw backtrace: 2 libdovecot.0.dylib 0x000000010ec63d24 default_fatal_finish + 36 -> 3 libdovecot.0.dylib 0x000000010ec64b5b i_internal_fatal_handler + 43 -> 4 libdovecot.0.dylib 0x000000010ec64039 i_panic + 169 -> 5 libdovecot-storage.0.dylib 0x000000010eac0950 mailbox_list_try_mkdir_root + 1248 -> 6 libdovecot-storage.0.dylib 0x000000010eac0a39 mailbox_list_mkdir_root + 25 -> 7 lib21_fts_lucene_plugin.so 0x0000000110adc949 fts_backend_lucene_update_set_build_key + 73 -> 8 lib20_fts_plugin.so 0x000000010ee736cf fts_backend_update_set_build_key + 79 -> 9 lib20_fts_plugin.so 0x000000010ee74317 fts_build_mail + 599 -> 10 lib20_fts_plugin.so 0x000000010ee7981a fts_mail_precache + 794 -> 11 libdovecot-storage.0.dylib 0x000000010eaa71e9 mail_precache + 25 -> 12 indexer-worker 0x000000010ea9e503 master_connection_input + 1523 -> 13 libdovecot.0.dylib 0x000000010ec78b89 io_loop_call_io + 89 -> 14 libdovecot.0.dylib 0x000000010ec7a96d io_loop_handler_run_internal + 269 -> 15 libdovecot.0.dylib 0x000000010ec7907f io_loop_handler_run + 303 -> 16 libdovecot.0.dylib 0x000000010ec78e58 io_loop_run + 88 -> 17 libdovecot.0.dylib 0x000000010ec03458 master_service_run + 24 -> 18 indexer-worker 0x000000010ea9ddb4 main + 340 -> 19 libdyld.dylib 0x00007fffba7df255 start + 1 Anyone else? -- Daniel J. Luke

1 0

Released Pigeonhole v0.4.17 for Dovecot v2.2.28.
by Stephan Bosch 27 Feb '17

27 Feb '17

Hello Dovecot users, Here's the definitive 0.4.17 release. There were no changes since the release candidate. Changelog v0.4.17: - LDA Sieve plugin: Fixed handling of an early explicit keep during multiscript execution. Action side-effects and the message snapshot would be lost at the final stage where the implicit keep is evaluated. This could result in the IMAP flags assigned to the message to be forgotten or that headers modified by the "editheader" extension would revert to their original state. - file script storage: Amended the up-to-date time stamp comparison for on-disk binaries to include nanoseconds. This will fix problems occurring when both binary and script are saved within the same second. This fix is ineffective on older systems that have no support for nanoseconds in stat() timestamps, which should be pretty rare nowadays. - file script storage: Improve saving and listing permission error to include more details. - imapsieve plugin: Make sure "INBOX" is upper case in static mailbox rules. Otherwise, the mailbox name would never match, since matching is performed case-sensitively and Dovecot only returns the upper-cased "INBOX". - imapsieve plugin: Fixed assert failure occurring when used with virtual mailboxes. - doveadm sieve plugin: Fixed crash when setting Sieve script via attribute's string value. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.17.ta… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.17.ta… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Re: Sieve removeflag Action
by Stephan Bosch 26 Feb '17

26 Feb '17

Op 2/26/2017 om 4:02 PM schreef Thomas Leuxner: >> Am 26.02.2017 um 15:52 schrieb Thomas Leuxner <tlx(a)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(a)leuxner.net -p ./message.eml >> >> From: User <user(a)example.com> >> To: lists(a)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(a)rename-it.nl> RCPT TO:<stephan> DATA From: User <user(a)example.com> To: stephan(a)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.

2 1

Re: Dict quota calculation errors "remote disconnected"/"broken pipe" on 2.22.
by ygrishin-lists＠mail2.ca 26 Feb '17

26 Feb '17

Solved the problem, reporting back to the community. /etc/dovecot/dovecot-dict-sql-user.conf had been lacking dovecot group permissions. It was 700/root:root. However why it wasn't reported by Dovecot explicitly in the log -- the greatest mystery to me. Now, after deleting dovecot and all its packages via 'apt' and installing afresh makes "lacking permissions for the file" entry to appear in the log. I can confirm that Dict-quota works perfectly well with Dovecot 2.2.22.

1 0

Sieve removeflag Action
by Thomas Leuxner 26 Feb '17

26 Feb '17

Hi, I recently noticed that some of my automatically processed mails do no longer show flags with current Dovecot builds. This used to work before, not sure what broke it or whether I used it in the wrong way. When the removeflag line is dropped *both* messages get flagged in the client, one in INBOX and one in Trash. With removeflag in place, *both* messages are unflagged, the one in INBOX and the one in Trash. This used to work differently before if memory doesn't fail me. #Test if address :is "From" "user(a)example.com" { addflag "\\Flagged $MailFlagBit1"; keep; removeflag "\\Flagged $MailFlagBit1"; fileinto "Trash"; } # 2.2.devel (01867a4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (3c071a4) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 Regards Thomas

4 18

Sieve Script Replication Gliches (Report #2)
by Reuben Farrelly 26 Feb '17

26 Feb '17

Hi, I've observed some odd behaviour with dsync replication between two hosts, specifically to do with sieve script replication. In short, I have two hosts which replicate in a master-master type setup where almost all of the reads and writes happen to just one of the two hosts. They are both running 2.2.devel (9dc6403), which is close to the latest 2.2 -git . Pigeonhole is running master-0.4 . This is on x86_64 Gentoo. Normal mail replication between Maildir's for all users works fine, however it appears that something recently committed to the code has broken sieve script replication between the two. I am sure this did once work. Replication is via tcps: . Sieve scripts on the lesser-used host are not up to date by an order of days/weeks with the main host and they don't seem to re-replicate - even if the rules don't exist at all on the replica. The symptoms and effects look to be the same as this (unanswered) post from December: http://dovecot.org/list/dovecot/2015-December/102690.html I am not sure how to view the transaction log files, but I am seeing the same symptoms, ie no live replication, and on the lesser-used host almost all the scripts were old and some had the 1970 date on them. Even after forcing a [dsync replication replicate '*'] the scripts are not replicated. As it stands now there are no sieve scripts on one of the two members and the system seems unable to replicate by itself. Secondly, I am also seeing some doubled up outputs if I run 'doveadm sieve list -A': thunderstorm reuben # doveadm sieve list -A reuben rules ACTIVE liam rules ACTIVE kaylene rules ACTIVE reuben rules ACTIVE liam rules ACTIVE kaylene rules ACTIVE ... Has anyone else experienced the replication problem? Are sieve scripts actually replicating in live time for other 2.2.24/2.2.25 users as well? For me I didn't notice this till I went looking so I wonder if other people are experiencing this but just not aware of it yet...? Reuben

4 9

Replication sieve scripts.
by Luescher Claude 26 Feb '17

26 Feb '17

Hello, Following up on old thread: http://www.dovecot.org/pipermail/dovecot/2014-December/099003.html I have the exact same issue with 2.2.10: ii dovecot-antispam 2.0+20130822-2 amd64 Dovecot plugins for training spam filters ii dovecot-core 1:2.2.10-1 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.10-1 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-ldap 1:2.2.10-1 amd64 secure POP3/IMAP server - LDAP support ii dovecot-lmtpd 1:2.2.10-1 amd64 secure POP3/IMAP server - LMTP server ii dovecot-managesieved 1:2.2.10-1 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 1:2.2.10-1 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 1:2.2.10-1 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 1:2.2.10-1 amd64 secure POP3/IMAP server - Sieve filters support As even his version should already support sieve replication through dsync mine would have to support it for sure but I would like to hear a confirmation from the developers. The mail sync just works perfectly between the 2 nodes, it is only the sieve scripts which don't get replicated. I have tried to add additional sieve related options to the replicator: service replicator { process_min_avail = 1 } plugin { mail_replica = tcp:1.2.3.4 replication_full_sync_interval = 1 hours #Added (makes no difference) sieve = ~/.dovecot.sieve sieve_dir = ~/sieve_after sieve_extensions = +vnd.dovecot.duplicate sieve_duplicate_period = 1h #Added (makes no difference) } service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } It did not help. If there is one way I would like to get this work without upgrading dovecot. Thank you.

4 12

v2.2.28: var-expand.c
by Ruga 26 Feb '17

26 Feb '17

var-expand.c:687:17: warning: passing an object that undergoes default argument promotion to 'va_start' has undefined behavior [-Wvarargs] va_start(args, key2); ^ var-expand.c:674:58: note: parameter of type 'char' is declared here var_expand_table_build(char key, const char *value, char key2, ...) ^

2 1

v2.2.28: patches (to use libressl 2.4.5) and test error (strftime)
by Ruga 26 Feb '17

26 Feb '17

t_strftime and variants now .......................................... : ok test-time-util.c:123: Assert failed: strcmp(t_strftime(RFC2822_FMT, gmtime(&ts)), exp) == 0 test-time-util.c:124: Assert failed: strcmp(t_strfgmtime(RFC2822_FMT, ts), exp) == 0 t_strftime and variants fixed timestamp .............................. : FAILED timings 0 ............................................................ : ok

4 7