From moseleymark at gmail.com Thu Dec 1 00:22:55 2016 From: moseleymark at gmail.com (Mark Moseley) Date: Wed, 30 Nov 2016 16:22:55 -0800 Subject: Implementing secondary quota w/ "Archive" namespace In-Reply-To: References: <7A1901CE-A893-41A3-8F07-A17E29DF6BC9@c5consulting.net> <55B9483E-3A6D-492C-82FA-B0B0292865FA@iki.fi> <6934C0A8-0A9F-4DA8-952B-742029E23277@c5consulting.net> <26D5AD33-92E0-4879-846A-BA5ACC86C128@iki.fi> <12B174AF-788B-4D1C-962F-11F7FF50F1C3@iki.fi> Message-ID: On Thu, Nov 24, 2016 at 9:10 PM, Mark Moseley wrote: > On Thu, Nov 24, 2016 at 10:52 AM, Timo Sirainen wrote: > >> On 24 Nov 2016, at 9.33, Mark Moseley wrote: >> > >> > On Wed, Nov 23, 2016 at 6:05 PM, Timo Sirainen wrote: >> > >> >> On 23 Nov 2016, at 0.49, Mark Moseley wrote: >> >>> >> >>> If I move messages between namespaces, it appears to ignore the quotas >> >> I've >> >>> set on them. A *copy* will trigger the quota error. But a *move* just >> >>> happily piles on to the overquota namespace. Is that normal? >> >> >> >> Probably needs a bit more thinking, but I guess the attached patch >> would >> >> help. >> >> >> >> >> > I appreciate the patch! Esp on a Weds night. I applied and rerolled >> > dovecot, but I can still move messages into the over-quota namespace. >> >> How about this updated patch? >> >> > Nope, still lets me move messages into the over-quota namespace. > > Both these are true in quota_check: > > ctx->moving > quota_move_requires_check > > > > >> > Out of curiosity, in the Quota wiki page, it mentions that 'in theory >> there >> > could be e.g. "user quota" and "domain quota" roots'. That's also super >> > interesting to me. Does anyone have any experience with that? I.e. any >> > gotchas? >> >> >> There's no automatic quota recalculation for domain quotas, because it >> would have to somehow sum up all the users' quotas. Also I think that it >> still does do the automatic quota recalculation if it gets into a situation >> where it realizes that quotas are wrong, but it'll then just use the single >> user's quota as the entire domain quota. So maybe it would work if you >> externally sum up all the users' quotas and update it to the domain quota >> in cronjob, e.g. once per hour. I guess it would be also nice if the >> internal quota recalculation could be disabled and maybe execute an >> external script to do it (similar to quota-warnings). >> >> Anything else I can try? I'm not sure how the logic in the quota system works, so I'm not sure what to suggest. What's the gist of the patch (i.e. what's it trying to do that it wasn't before)? If I can get a handle on that, I can start littering things with debug statements to try to track stuff down. From nick at cpanel.net Thu Dec 1 07:44:03 2016 From: nick at cpanel.net (J. Nick Koston) Date: Wed, 30 Nov 2016 21:44:03 -1000 Subject: Multiple names in local_name for UCC certificates (was lazy-load SNI?) In-Reply-To: References: Message-ID: <2FC3D49D-A55B-4B44-B8DB-74241078CA21@cpanel.net> Hi Aki & Felipe, Attached is an implementation of supporting multiple domains in local_name. Example local_name "mail.domain.tld domain.tld mx.domain.tld" { ... } This can significantly reduce memory usage when using a UCC certificate with multiple names by only loading the certificate and key once. And the pull request?.. https://github.com/dovecot/core/pull/24 Thanks -Nick > On Nov 17, 2016, at 5:27 AM, J. Nick Koston wrote: > > Aki, > > Multiple local_names would be ideal to accommodate certificates that have multiple names. The way I?m reading the code it looks like its having to pay for the memory for every name on the certificate because a unique CTX is being created for each name even if they are all on a single certificate. > > This would be a big memory win for anyone using a certificate with multiple names on it. > > Thanks > -Nick > cPanel Inc > > >>> >> >> Dear Aki et al., >> >> How straightforward would it be to implement the following or similar syntax: >> >> local_name foo.tld www.foo.tld mail.foo.tld bar.tld { >> ... >> } >> >> ?? >> >> Thank you! >> >> -FG >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> dovecot mailing list >> dovecot at dovecot.org >> http://dovecot.org/cgi-bin/mailman/listinfo/dovecot >> >> ------------------------------ >> >> End of dovecot Digest, Vol 163, Issue 34 >> **************************************** > -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-config-Match-multiple-names-in-local_name.patch Type: application/octet-stream Size: 1579 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3569 bytes Desc: not available URL: From aki.tuomi at dovecot.fi Thu Dec 1 07:45:16 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Thu, 1 Dec 2016 09:45:16 +0200 Subject: Multiple names in local_name for UCC certificates (was lazy-load SNI?) In-Reply-To: <2FC3D49D-A55B-4B44-B8DB-74241078CA21@cpanel.net> References: <2FC3D49D-A55B-4B44-B8DB-74241078CA21@cpanel.net> Message-ID: Thank you, we'll start looking at this. Aki On 01.12.2016 09:44, J. Nick Koston wrote: > Hi Aki & Felipe, > > Attached is an implementation of supporting multiple domains in local_name. > > Example > > local_name "mail.domain.tld domain.tld mx.domain.tld" { ... } > > This can significantly reduce memory usage when using > a UCC certificate with multiple names by only loading > the certificate and key once. > > > > And the pull request?.. > > https://github.com/dovecot/core/pull/24 > > Thanks > -Nick > > >> On Nov 17, 2016, at 5:27 AM, J. Nick Koston wrote: >> >> Aki, >> >> Multiple local_names would be ideal to accommodate certificates that have multiple names. The way I?m reading the code it looks like its having to pay for the memory for every name on the certificate because a unique CTX is being created for each name even if they are all on a single certificate. >> >> This would be a big memory win for anyone using a certificate with multiple names on it. >> >> Thanks >> -Nick >> cPanel Inc >> >> >>> Dear Aki et al., >>> >>> How straightforward would it be to implement the following or similar syntax: >>> >>> local_name foo.tld www.foo.tld mail.foo.tld bar.tld { >>> ... >>> } >>> >>> ?? >>> >>> Thank you! >>> >>> -FG >>> >>> ------------------------------ >>> >>> Subject: Digest Footer >>> >>> _______________________________________________ >>> dovecot mailing list >>> dovecot at dovecot.org >>> http://dovecot.org/cgi-bin/mailman/listinfo/dovecot >>> >>> ------------------------------ >>> >>> End of dovecot Digest, Vol 163, Issue 34 >>> **************************************** > From aki.tuomi at dovecot.fi Thu Dec 1 10:45:32 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Thu, 1 Dec 2016 12:45:32 +0200 Subject: Multiple names in local_name for UCC certificates (was lazy-load SNI?) In-Reply-To: References: <2FC3D49D-A55B-4B44-B8DB-74241078CA21@cpanel.net> Message-ID: This has been merged, and hopefully will make it still to 2.2.27 release. Aki Tuomi Dovecot oy On 01.12.2016 09:45, Aki Tuomi wrote: > Thank you, we'll start looking at this. > > Aki > > On 01.12.2016 09:44, J. Nick Koston wrote: >> Hi Aki & Felipe, >> >> Attached is an implementation of supporting multiple domains in local_name. >> >> Example >> >> local_name "mail.domain.tld domain.tld mx.domain.tld" { ... } >> >> This can significantly reduce memory usage when using >> a UCC certificate with multiple names by only loading >> the certificate and key once. >> >> >> >> And the pull request?.. >> >> https://github.com/dovecot/core/pull/24 >> >> Thanks >> -Nick >> >> >>> On Nov 17, 2016, at 5:27 AM, J. Nick Koston wrote: >>> >>> Aki, >>> >>> Multiple local_names would be ideal to accommodate certificates that have multiple names. The way I?m reading the code it looks like its having to pay for the memory for every name on the certificate because a unique CTX is being created for each name even if they are all on a single certificate. >>> >>> This would be a big memory win for anyone using a certificate with multiple names on it. >>> >>> Thanks >>> -Nick >>> cPanel Inc >>> >>> >>>> Dear Aki et al., >>>> >>>> How straightforward would it be to implement the following or similar syntax: >>>> >>>> local_name foo.tld www.foo.tld mail.foo.tld bar.tld { >>>> ... >>>> } >>>> >>>> ?? >>>> >>>> Thank you! >>>> >>>> -FG >>>> >>>> ------------------------------ >>>> >>>> Subject: Digest Footer >>>> >>>> _______________________________________________ >>>> dovecot mailing list >>>> dovecot at dovecot.org >>>> http://dovecot.org/cgi-bin/mailman/listinfo/dovecot >>>> >>>> ------------------------------ >>>> >>>> End of dovecot Digest, Vol 163, Issue 34 >>>> **************************************** From tss at iki.fi Thu Dec 1 12:37:41 2016 From: tss at iki.fi (Timo Sirainen) Date: Thu, 1 Dec 2016 14:37:41 +0200 Subject: Implementing secondary quota w/ "Archive" namespace In-Reply-To: References: <7A1901CE-A893-41A3-8F07-A17E29DF6BC9@c5consulting.net> <55B9483E-3A6D-492C-82FA-B0B0292865FA@iki.fi> <6934C0A8-0A9F-4DA8-952B-742029E23277@c5consulting.net> <26D5AD33-92E0-4879-846A-BA5ACC86C128@iki.fi> <12B174AF-788B-4D1C-962F-11F7FF50F1C3@iki.fi> Message-ID: <73BC0792-4C28-4431-99CC-A061C8B044E7@iki.fi> On 1 Dec 2016, at 2.22, Mark Moseley wrote: > >>> How about this updated patch? >>> >>> >> Nope, still lets me move messages into the over-quota namespace. >> >> Both these are true in quota_check: >> >> ctx->moving >> quota_move_requires_check .. > Anything else I can try? I'm not sure how the logic in the quota system > works, so I'm not sure what to suggest. What's the gist of the patch (i.e. > what's it trying to do that it wasn't before)? > > If I can get a handle on that, I can start littering things with debug > statements to try to track stuff down. I just messed up the if-check. This one is now committed and should work: https://github.com/dovecot/core/commit/2ec4ab6f5a1172e86afc72c0f29f470d6fd2bd9a.diff From kalle.erlacher at doag.org Thu Dec 1 15:23:28 2016 From: kalle.erlacher at doag.org (Kalle Erlacher) Date: Thu, 1 Dec 2016 16:23:28 +0100 Subject: AW: User unknown in local recipient table In-Reply-To: <20161201143755.yjizskipmmuaozg6@charite.de> References: <11ff01d24bda$7f5730e0$7e0592a0$@doag.org> <20161201143755.yjizskipmmuaozg6@charite.de> Message-ID: <121501d24be6$dddcc4c0$99964e40$@doag.org> Hallo Liste, hallo Ralf, danke schon mal. Ja die Whitespaces sind beim Rausl?schen entstanden. Ich verstand das so, dass das nun durch die address_verify_map erledigt w?rde. Muss ich dann entsprechend einfach auf die verweisen? Ich versuchte gerade die address_verify_map = btree:$data_directory/verify_cache auf local_recipient_maps = btree:$data_directory/verify_cache verweisen zu lassen. Leider ohne Erfolg. Bisher ist verify_cache n?mlich leider noch unbef?llt. Entsprechend bekomme ich folgende Fehler: Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache is unavailable. open database /var/lib/postfix/verify_cache.db: No such file or directory Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache lookup error for "juergen @domain.org" Dec 1 16:16:29 test-mail postfix/smtpd[5550]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.0 : Temporary lookup failure; from= to= proto=ESMTP helo= Auch ein plumpes touch auf /var/lib/postfix/verify_cache.db bringt danach den selben Fehler. Liebe Gr??e Kalle -----Urspr?ngliche Nachricht----- Von: Dovecot [mailto:dovecot-bounces at listen.jpberlin.de] Im Auftrag von Ralf Hildebrandt Gesendet: Donnerstag, 1. Dezember 2016 15:38 An: dovecot at listen.jpberlin.de Betreff: Re: User unknown in local recipient table * Kalle Erlacher : > Dec 1 14:38:44 test-mail postfix/smtpd[3366]: NOQUEUE: reject: RCPT > from > localhost[127.0.0.1]: 550 5.1.1 : Recipient > address > rejected: User unknown in local recipient table; > from= to= proto=ESMTP > helo= ... local recipient table = domain ist in mydestination > mydestination = test-mail.domain.org mail. domain.org domain.org > localhost Ich hoffe das Leerzeichen zwischen "mail." und "domain.org" ist nicht wirklich da Explizit ist da nix gesetzt, laut "postconf -n", ergo defaults f?r local_recipient_maps: local_recipient_maps = proxy:unix:passwd.byname $alias_maps Aber die Domain domain.org soll doch sicher im dovecot landen, oder? -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de From r at sys4.de Thu Dec 1 15:37:41 2016 From: r at sys4.de (Ralf Hildebrandt) Date: Thu, 1 Dec 2016 16:37:41 +0100 Subject: User unknown in local recipient table In-Reply-To: <121501d24be6$dddcc4c0$99964e40$@doag.org> References: <11ff01d24bda$7f5730e0$7e0592a0$@doag.org> <20161201143755.yjizskipmmuaozg6@charite.de> <121501d24be6$dddcc4c0$99964e40$@doag.org> Message-ID: <20161201153741.GB21868@sys4.de> * Kalle Erlacher : > Hallo Liste, hallo Ralf, > > danke schon mal. Ja die Whitespaces sind beim Rausl?schen entstanden. > > Ich verstand das so, dass das nun durch die address_verify_map erledigt w?rde. Muss ich dann entsprechend einfach auf die verweisen? Nein. > Ich versuchte gerade die > address_verify_map = btree:$data_directory/verify_cache > auf > local_recipient_maps = btree:$data_directory/verify_cache > verweisen zu lassen. Leider ohne Erfolg. Bisher ist verify_cache n?mlich leider noch unbef?llt. Entsprechend bekomme ich folgende Fehler: neee > Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache is unavailable. open database /var/lib/postfix/verify_cache.db: No such file or directory > Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache lookup error for "juergen @domain.org" > Dec 1 16:16:29 test-mail postfix/smtpd[5550]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.0 : Temporary lookup failure; from= to= proto=ESMTP helo= > > Auch ein plumpes touch auf /var/lib/postfix/verify_cache.db bringt danach den selben Fehler. Das ist der falsche Ansatz! Die Domain ist eine relay_domain und du musst mit den relay_recipient_maps arbeiten ODER er muss recipient_verification gegen den LMTP des Dovecot machen. Ich weiss jetzt nicht was im Buch dazu steht -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schlei?heimer Stra?e 26/MG, 80333 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From sami.ketola at dovecot.fi Thu Dec 1 15:41:20 2016 From: sami.ketola at dovecot.fi (Sami Ketola) Date: Thu, 1 Dec 2016 17:41:20 +0200 Subject: User unknown in local recipient table In-Reply-To: <20161201153741.GB21868@sys4.de> References: <11ff01d24bda$7f5730e0$7e0592a0$@doag.org> <20161201143755.yjizskipmmuaozg6@charite.de> <121501d24be6$dddcc4c0$99964e40$@doag.org> <20161201153741.GB21868@sys4.de> Message-ID: Hi, Can you please keep this mailing list in english? Sami > On 1 Dec 2016, at 17.37, Ralf Hildebrandt wrote: > > * Kalle Erlacher : >> Hallo Liste, hallo Ralf, >> >> danke schon mal. Ja die Whitespaces sind beim Rausl?schen entstanden. >> >> Ich verstand das so, dass das nun durch die address_verify_map erledigt w?rde. Muss ich dann entsprechend einfach auf die verweisen? > > Nein. > >> Ich versuchte gerade die >> address_verify_map = btree:$data_directory/verify_cache >> auf >> local_recipient_maps = btree:$data_directory/verify_cache >> verweisen zu lassen. Leider ohne Erfolg. Bisher ist verify_cache n?mlich leider noch unbef?llt. Entsprechend bekomme ich folgende Fehler: > > neee > >> Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache is unavailable. open database /var/lib/postfix/verify_cache.db: No such file or directory >> Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache lookup error for "juergen @domain.org" >> Dec 1 16:16:29 test-mail postfix/smtpd[5550]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.0 : Temporary lookup failure; from= to= proto=ESMTP helo= >> >> Auch ein plumpes touch auf /var/lib/postfix/verify_cache.db bringt danach den selben Fehler. > > Das ist der falsche Ansatz! > > > Die Domain ist eine relay_domain und du musst mit den > relay_recipient_maps arbeiten > > ODER > > er muss recipient_verification gegen den LMTP des Dovecot machen. Ich > weiss jetzt nicht was im Buch dazu steht > > > > -- > [*] sys4 AG > > http://sys4.de, +49 (89) 30 90 46 64 > Schlei?heimer Stra?e 26/MG, 80333 M?nchen > > Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 > Vorstand: Patrick Ben Koetter, Marc Schiffbauer > Aufsichtsratsvorsitzender: Florian Kirstein From r at sys4.de Thu Dec 1 15:55:58 2016 From: r at sys4.de (Ralf Hildebrandt) Date: Thu, 1 Dec 2016 16:55:58 +0100 Subject: User unknown in local recipient table In-Reply-To: References: <11ff01d24bda$7f5730e0$7e0592a0$@doag.org> <20161201143755.yjizskipmmuaozg6@charite.de> <121501d24be6$dddcc4c0$99964e40$@doag.org> <20161201153741.GB21868@sys4.de> Message-ID: <20161201155557.GC21868@sys4.de> * Sami Ketola : > Hi, > > Can you please keep this mailing list in english? Sorry, somebody crossposted this from a german language list :/ -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schlei?heimer Stra?e 26/MG, 80333 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From rarylson at gmail.com Thu Dec 1 17:08:02 2016 From: rarylson at gmail.com (Rarylson Freitas) Date: Thu, 1 Dec 2016 15:08:02 -0200 Subject: maildir-size-fix.pl - The file command can wrongly detect gzipped mails as being Minix filesystems Message-ID: Hi, Some days ago, I have used the maildir-size-fix.pl script (cited in this mail thread: http://www.dovecot.org/list/dovecot/2013-January/087942.html, in available here: http://dovecot.org/tools/maildir-size-fix.pl). This is a very good script and helped me a lot! However, some compressed mails where misdetected as non-compressed mail. So I discovered that some versions of the file command (some old versions) can wrongly detect gzipped files as being Minix filesystems. Actually, the error was occurring in about 1 gzipped mail for each 60000 or 100000 mails. I reported this file command bug here: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233. But I think it's worth to make a small improvement in maildir-size-fix.pl, making it more error prone. What do you, guys, think about this? This is the patch I'm proposing: ``` --- maildir-size-fix.pl.orig 2016-12-01 14:41:30.044689101 -0200 +++ maildir-size-fix.pl 2016-12-01 14:49:42.971197715 -0200 @@ -37,7 +37,10 @@ return $stat[7]; } - my $type=`file "$path"`; + # Detecting all possible types (keep going) since some versions of the file + # command can wrong detect gzip files as Minix filesystems. + # See: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233 + my $type=`file -k "$path"`; my $program = ""; if ($type =~ /gzip/) { $program = "gunzip"; ``` -- *Rarylson Freitas* From moseleymark at gmail.com Thu Dec 1 18:37:35 2016 From: moseleymark at gmail.com (Mark Moseley) Date: Thu, 1 Dec 2016 10:37:35 -0800 Subject: Implementing secondary quota w/ "Archive" namespace In-Reply-To: <73BC0792-4C28-4431-99CC-A061C8B044E7@iki.fi> References: <7A1901CE-A893-41A3-8F07-A17E29DF6BC9@c5consulting.net> <55B9483E-3A6D-492C-82FA-B0B0292865FA@iki.fi> <6934C0A8-0A9F-4DA8-952B-742029E23277@c5consulting.net> <26D5AD33-92E0-4879-846A-BA5ACC86C128@iki.fi> <12B174AF-788B-4D1C-962F-11F7FF50F1C3@iki.fi> <73BC0792-4C28-4431-99CC-A061C8B044E7@iki.fi> Message-ID: On Thu, Dec 1, 2016 at 4:37 AM, Timo Sirainen wrote: > On 1 Dec 2016, at 2.22, Mark Moseley wrote: > > > How about this updated patch? > > > Nope, still lets me move messages into the over-quota namespace. > > Both these are true in quota_check: > > ctx->moving > quota_move_requires_check > > .. > > Anything else I can try? I'm not sure how the logic in the quota system > works, so I'm not sure what to suggest. What's the gist of the patch (i.e. > what's it trying to do that it wasn't before)? > > If I can get a handle on that, I can start littering things with debug > statements to try to track stuff down. > > > I just messed up the if-check. This one is now committed and should work: > https://github.com/dovecot/core/commit/2ec4ab6f5a1172e86afc72c0f29f47 > 0d6fd2bd9a.diff > > that looks good. When I apply it, I get: quota-storage.c: In function ?quota_save_finish?: quota-storage.c:337:15: error: ?struct mail_save_context? has no member named ?copy_src_mail? quota-storage.c:337:51: error: ?struct mail_save_context? has no member named ?copy_src_mail? make[4]: *** [quota-storage.lo] Error 1 But if I then also apply the previous patch you gave, though it fails in a number of sections: # patch -p1 < ~moseley/diff2 (Stripping trailing CRs from patch.) patching file src/lib-storage/mail-storage-private.h (Stripping trailing CRs from patch.) patching file src/lib-storage/mail-storage.c Hunk #1 succeeded at 2238 (offset -20 lines). Hunk #2 succeeded at 2255 (offset -20 lines). (Stripping trailing CRs from patch.) patching file src/plugins/quota/quota-storage.c Hunk #1 FAILED at 185. Hunk #2 FAILED at 242. Hunk #3 FAILED at 297. 3 out of 3 hunks FAILED -- saving rejects to file src/plugins/quota/quota-storage.c.rej BUT, it then compiles. I haven't tested it extensively, but with this latest patch, when I try to move mail to the over-quota Archive mailbox, it correctly fails! Awesome! From tss at iki.fi Fri Dec 2 00:18:59 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 2 Dec 2016 02:18:59 +0200 Subject: maildir-size-fix.pl - The file command can wrongly detect gzipped mails as being Minix filesystems In-Reply-To: References: Message-ID: <6A287A12-B09E-4AA1-AF40-823E12EEA53C@iki.fi> On 1 Dec 2016, at 19.08, Rarylson Freitas wrote: > > Hi, > > Some days ago, I have used the maildir-size-fix.pl script (cited in this > mail thread: http://www.dovecot.org/list/dovecot/2013-January/087942.html, > in available here: > http://dovecot.org/tools/maildir-size-fix.pl). > > This is a very good script and helped me a lot! > > However, some compressed mails where misdetected as non-compressed mail. So > I discovered that some versions of the file command (some old versions) can > wrongly detect gzipped files as being Minix filesystems. > > Actually, the error was occurring in about 1 gzipped mail for each 60000 or > 100000 mails. > > I reported this file command bug here: > https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233. > > But I think it's worth to make a small improvement in maildir-size-fix.pl, > making it more error prone. What do you, guys, think about this? > > This is the patch I'm proposing: > > ``` > --- maildir-size-fix.pl.orig 2016-12-01 14:41:30.044689101 -0200 > +++ maildir-size-fix.pl 2016-12-01 14:49:42.971197715 -0200 > @@ -37,7 +37,10 @@ > > return $stat[7]; > } > - my $type=`file "$path"`; > + # Detecting all possible types (keep going) since some versions of the > file > + # command can wrong detect gzip files as Minix filesystems. > + # See: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233 > + my $type=`file -k "$path"`; > my $program = ""; > if ($type =~ /gzip/) { > $program = "gunzip"; > > ``` Added, thanks! From aki.tuomi at dovecot.fi Fri Dec 2 07:00:58 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Fri, 2 Dec 2016 09:00:58 +0200 Subject: CVE-2016-8562 in dovecot Message-ID: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> We are sorry to report that we have a bug in dovecot, which merits a CVE. See details below. If you haven't configured any auth_policy_* settings you are ok. This is fixed with https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f34be960cff13a5a725ae and https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d57351fd42c67a8612fc Important vulnerability in Dovecot (CVE-2016-8562) CVSS score: 7.4 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H) Affected version(s): 2.2.25.1 up to 2.2.26.1 Fixed in: 2.2.27.1rc1 Short summary: Dovecot auth component can be crashed by remote user when auth-policy component is activated. If auth-policy component has been activated in Dovecot, then remote user can use SASL authentication to crash auth component. Workaround is to disable auth-policy component until fix is in place. This can be done by commenting out all auth_policy_* settings. Aki Tuomi Dovecot oy From jonas at wielicki.name Fri Dec 2 08:45:53 2016 From: jonas at wielicki.name (Jonas Wielicki) Date: Fri, 02 Dec 2016 09:45:53 +0100 Subject: CVE-2016-8562 in dovecot In-Reply-To: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> Message-ID: <31506634.MIXb7Dh5U9@sinistra> On Freitag, 2. Dezember 2016 09:00:58 CET Aki Tuomi wrote: > We are sorry to report that we have a bug in dovecot, which merits a > CVE. See details below. If you haven't configured any auth_policy_* > settings you are ok. This is fixed with > https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f34be960cff13 > a5a725ae and > https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d57351fd42c6 > 7a8612fc > > Important vulnerability in Dovecot (CVE-2016-8562) Are you sure about the CVE number? According to Debian [1] and mitre [2], it?s for SIEMENS something, not Dovecot. best regards, Jonas Wielicki [1]: https://security-tracker.debian.org/tracker/CVE-2016-8562 [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8562 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: From aki.tuomi at dovecot.fi Fri Dec 2 08:48:15 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Fri, 2 Dec 2016 10:48:15 +0200 Subject: CVE-2016-8652 in dovecot In-Reply-To: <31506634.MIXb7Dh5U9@sinistra> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> <31506634.MIXb7Dh5U9@sinistra> Message-ID: <7ea5f46c-a9ae-690c-29f6-d90375cf7e17@dovecot.fi> On 02.12.2016 10:45, Jonas Wielicki wrote: > On Freitag, 2. Dezember 2016 09:00:58 CET Aki Tuomi wrote: >> We are sorry to report that we have a bug in dovecot, which merits a >> CVE. See details below. If you haven't configured any auth_policy_* >> settings you are ok. This is fixed with >> https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f34be960cff13 >> a5a725ae and >> https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d57351fd42c6 >> 7a8612fc >> >> Important vulnerability in Dovecot (CVE-2016-8562) > Are you sure about the CVE number? According to Debian [1] and mitre [2], it?s > for SIEMENS something, not Dovecot. > > best regards, > Jonas Wielicki > > [1]: https://security-tracker.debian.org/tracker/CVE-2016-8562 > [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8562 Ups, sent wrong number, correct is CVE-2016-8652. Aki From aki.tuomi at dovecot.fi Fri Dec 2 11:03:05 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Fri, 2 Dec 2016 13:03:05 +0200 Subject: Defining INDEX target to other location than maildir seems to have no effect. In-Reply-To: <1650017749.1313.1478382033507@appsuite-dev.open-xchange.com> References: <6B7A7E1E-C2ED-47C9-94B1-CC85E8D9EF01@ispire.me> <1650017749.1313.1478382033507@appsuite-dev.open-xchange.com> Message-ID: <2657cf27-e138-9d27-0d0a-c846bf316c4d@dovecot.fi> Hi! Sorry it took a while. I tested with 2.2.26.0, and it seems to work ok, can you try with later release? I tried both INDEX=MEMORY and INDEX=~/indexes Aki On 05.11.2016 23:40, Aki Tuomi wrote: > Hi! > > Thank you for reporting this, we'll look into it. > > Aki Tuomi > Dovecot oy. > > >> On November 5, 2016 at 11:31 PM Jules wrote: >> >> >> How can i commit this as bug report? >> >>> Am 30.10.2016 um 11:04 schrieb Julian Sternberg : >>> >>> Dovecot Version 2.2.13 >>> Linux Distribution: Debian Jessie >>> CPU Architecture: x64 >>> Filesystem: GlusterFS/NFS, XFS for Base System/Index Files. >>> Two Dovecot/Postfix nodes accessing same GlusterFS/NFS Maildir. >>> >>> Regardless what i choose in mail_location (:INDEX=MEMORY or :INDEX=/var/indexes/%d/%n) all Mailbox index files will still get created within the users mail_location maildir: ~/Maildir >>> >>> My mail_location Maildir directory is shared on GlusterFS mount so i need to get index files away from this share due locking mechanism and faster caching. >>> >>> The weird is, if i set INDEX to /var/indexes, the index files getting created sometimes but then not updated frequently and exist parallel on Maildir which are mostly newer than on /var/indexes. If you delete the dovecot.index* files from Maildir, they will get recreated immediatly on Imap access but not on the alternative set INDEX location, they are getting recreated within Maildir again. >>> >>> Here is doveconf -n Output: >>> >>> # 2.2.13: /etc/dovecot/dovecot.conf >>> # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 >>> auth_mechanisms = plain login cram-md5 >>> disable_plaintext_auth = no >>> first_valid_uid = 2000 >>> hostname = censored.hostname.com >>> last_valid_uid = 2000 >>> lda_mailbox_autocreate = yes >>> lda_mailbox_autosubscribe = yes >>> listen = * >>> lock_method = dotlock >>> mail_fsync = always >>> mail_gid = 2000 >>> mail_home = /storage/vmail/%d/%n >>> mail_location = maildir:~/Maildir:LAYOUT=fs:INDEX=MEMORY >>> mail_nfs_storage = yes >>> mail_privileged_group = vmail >>> mail_temp_dir = /var/tmp >>> mail_uid = 2000 >>> maildir_very_dirty_syncs = yes >>> managesieve_notify_capability = mailto >>> managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave >>> mmap_disable = yes >>> namespace inbox { >>> inbox = yes >>> location = >>> mailbox Archive { >>> auto = no >>> special_use = \Archive >>> } >>> mailbox Archives { >>> auto = no >>> special_use = \Archive >>> } >>> mailbox "Deleted Items" { >>> auto = no >>> special_use = \Trash >>> } >>> mailbox "Deleted Messages" { >>> auto = no >>> special_use = \Trash >>> } >>> mailbox Drafts { >>> auto = no >>> special_use = \Drafts >>> } >>> mailbox Sent { >>> auto = subscribe >>> special_use = \Sent >>> } >>> mailbox "Sent Items" { >>> auto = no >>> special_use = \Sent >>> } >>> mailbox "Sent Messages" { >>> auto = no >>> special_use = \Sent >>> } >>> mailbox Spam { >>> auto = create >>> special_use = \Junk >>> } >>> mailbox Trash { >>> auto = subscribe >>> special_use = \Trash >>> } >>> mailbox virtual/All { >>> auto = no >>> special_use = \All >>> } >>> prefix = >>> separator = / >>> type = private >>> } >>> passdb { >>> args = /etc/dovecot/dovecot-sql.conf.ext >>> driver = sql >>> } >>> plugin { >>> quota = maildir:User quota >>> quota_rule = *:storage=1G >>> quota_rule2 = Trash:storage=+100M >>> quota_rule3 = Sent:storage=+100M >>> quota_warning = storage=95%% quota-warning 95 %u >>> quota_warning2 = storage=80%% quota-warning 80 %u >>> sieve = /storage/vmail/%d/%n/sieve/dovecot.sieve >>> sieve_before = /storage/vmail/sieve/dovecot.sieve >>> sieve_dir = /storage/vmail/%d/%n/sieve >>> sieve_global = /storage/vmail/sieve >>> } >>> postmaster_address = postmaster at censored.hostname.com >>> protocols = " imap lmtp sieve pop3" >>> quota_full_tempfail = yes >>> service auth { >>> unix_listener /var/spool/postfix/private/auth { >>> group = postfix >>> mode = 0660 >>> user = postfix >>> } >>> unix_listener auth-userdb { >>> group = vmail >>> mode = 0666 >>> user = vmail >>> } >>> } >>> service imap-login { >>> inet_listener imaps { >>> port = 993 >>> ssl = yes >>> } >>> service_count = 0 >>> } >>> service lmtp { >>> unix_listener /var/spool/postfix/private/dovecot-lmtp { >>> group = postfix >>> mode = 0666 >>> user = postfix >>> } >>> } >>> service managesieve-login { >>> inet_listener sieve { >>> port = 4190 >>> } >>> service_count = 1 >>> } >>> service pop3-login { >>> inet_listener pop3 { >>> port = 110 >>> } >>> inet_listener pop3s { >>> port = 995 >>> ssl = yes >>> } >>> } >>> service quota-warning { >>> executable = script /usr/local/bin/quota-warning.sh >>> unix_listener quota-warning { >>> user = vmail >>> } >>> user = vmail >>> } >>> ssl = required >>> ssl_ca = >> ssl_cert = >> ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA >>> ssl_key = >> ssl_protocols = !SSLv2 !SSLv3 >>> ssl_require_crl = no >>> userdb { >>> args = uid=2000 gid=2000 home=/storage/vmail/%d/%n allow_all_users=yes >>> driver = static >>> } >>> protocol lmtp { >>> mail_plugins = " quota sieve" >>> } >>> protocol lda { >>> mail_plugins = " sieve quota" >>> } >>> protocol imap { >>> imap_client_workarounds = tb-extra-mailbox-sep >>> mail_plugins = " quota imap_quota" >>> } >>> protocol sieve { >>> mail_max_userip_connections = 10 >>> } >>> protocol pop3 { >>> mail_plugins = " quota" >>> pop3_client_workarounds = outlook-no-nuls oe-ns-eoh >>> pop3_uidl_format = %08Xu%08Xv >>> } From sk at tyrion.de Fri Dec 2 16:23:47 2016 From: sk at tyrion.de (=?utf-8?B?U2ViYXN0aWFuIEvDtmhsZXI=?=) Date: Fri, 02 Dec 2016 16:23:47 +0000 Subject: Too many references: cannot splice Message-ID: Hello, multiple times per day one of our Dovecot servers has the problem that it suddenly refuses to accept new connections and then floods the logs with these messages: Dec 2 12:43:06 alfa3201 dovecot: pop3-login: Error: fd_send(pop3, 18) failed: Too many references: cannot splice Dec 2 12:43:07 alfa3201 dovecot: pop3-login: Error: fd_send(pop3, 18) failed: Too many references: cannot splice Dec 2 12:43:07 alfa3201 dovecot: imap-login: Error: fd_send(imap, 16) failed: Too many references: cannot splice Dec 2 12:43:07 alfa3201 dovecot: imap-login: Error: fd_send(imap, 16) failed: Too many references: cannot splice We have to either do a restart of the server or a doveadm kick on all users to make it reachable again. On my search for a solution I found a similar report from March[1] however without a fix. [1] http://dovecot.org/pipermail/dovecot/2016-March/103514.html dovecot -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.17-040417-generic x86_64 Debian 8.6 auth_mechanisms = plain login debug_log_path = /var/log/dovecot-debug.log default_client_limit = 8003 default_process_limit = 2000 default_vsz_limit = 512 M disable_plaintext_auth = no listen = * login_greeting = [CENSORED] - ready. mail_location = maildir:~/Maildir:CONTROL=/opt/dovecot/control/%n-control:INDEX=/opt/dovecot/index/%n mail_plugins = " stats quota" namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . } passdb { args = dovecot-%s driver = pam } plugin { quota = fs:%n(soft quota) sieve = ~/.dovecot.sieve sieve_dir = ~/sieve stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 16 M stats_refresh = 30 secs stats_session_min_time = 15 mins stats_track_cmds = no stats_user_min_time = 24 hours } protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imaps { ssl = yes } } service imap-postlogin { executable = script-login /etc/dovecot/post-login/expire.sh } service imap { executable = imap imap-postlogin } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3-postlogin { executable = script-login /etc/dovecot/post-login/expire.sh } service pop3 { executable = pop3 pop3-postlogin } service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota { group = postfix mode = 0660 user = postfix } } service stats { fifo_listener stats-mail { mode = 0666 user = dovecot } } ssl_ca = References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> Message-ID: <765f2a7b-d7cf-26d0-f7c1-7dfcf41870ad@andreasschulze.de> Am 02.12.2016 um 08:00 schrieb Aki Tuomi: > Workaround is to disable auth-policy component until fix is in place. > This can be done by commenting out all auth_policy_* settings. Hello, could you be more verbose on how to verify if administrators are affected? # doveconf -n | grep auth_policy_ | wc -l 0 but there /are/ default settings: # doveconf -d | grep auth_policy_ auth_policy_hash_mech = sha256 auth_policy_hash_nonce = auth_policy_hash_truncate = 12 auth_policy_reject_on_fail = no auth_policy_request_attributes = login=%{orig_username} pwhash=%{hashed_password} remote=%{real_rip} auth_policy_server_api_header = auth_policy_server_timeout_msecs = 2000 auth_policy_server_url = Is such setup vulnerable? Thanks for clarification, Andreas From forondarena at gmail.com Fri Dec 2 17:57:38 2016 From: forondarena at gmail.com (Luis Ugalde) Date: Fri, 2 Dec 2016 18:57:38 +0100 Subject: Too many references: cannot splice In-Reply-To: References: Message-ID: Sebastian, On October 13th I sent a new email with subject "Too many references: cannot splice" with a reference to a lklm post. You will find more info. and a patch there. I can confirm the patch is working for us. Regards, Luis Ugalde On Fri, Dec 2, 2016 at 5:23 PM, Sebastian K?hler wrote: > Hello, > > multiple times per day one of our Dovecot servers has the problem that it > suddenly refuses to accept new connections and then floods the logs with > these messages: > > Dec 2 12:43:06 alfa3201 dovecot: pop3-login: Error: fd_send(pop3, 18) > failed: Too many references: cannot splice > Dec 2 12:43:07 alfa3201 dovecot: pop3-login: Error: fd_send(pop3, 18) > failed: Too many references: cannot splice > Dec 2 12:43:07 alfa3201 dovecot: imap-login: Error: fd_send(imap, 16) > failed: Too many references: cannot splice > Dec 2 12:43:07 alfa3201 dovecot: imap-login: Error: fd_send(imap, 16) > failed: Too many references: cannot splice > > > We have to either do a restart of the server or a doveadm kick on all > users to make it reachable again. On my search for a solution I found a > similar report from March[1] however without a fix. > > > [1] http://dovecot.org/pipermail/dovecot/2016-March/103514.html > > > dovecot -n > > # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.13 (7b14904) > # OS: Linux 4.4.17-040417-generic x86_64 Debian 8.6 > auth_mechanisms = plain login > debug_log_path = /var/log/dovecot-debug.log > default_client_limit = 8003 > default_process_limit = 2000 > default_vsz_limit = 512 M > disable_plaintext_auth = no > listen = * > login_greeting = [CENSORED] - ready. > mail_location = maildir:~/Maildir:CONTROL=/opt/dovecot/control/%n- > control:INDEX=/opt/dovecot/index/%n > mail_plugins = " stats quota" > namespace inbox { > inbox = yes > location = > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Spam { > auto = subscribe > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > auto = subscribe > special_use = \Trash > } > prefix = INBOX. > separator = . > } > passdb { > args = dovecot-%s > driver = pam > } > plugin { > quota = fs:%n(soft quota) > sieve = ~/.dovecot.sieve > sieve_dir = ~/sieve > stats_command_min_time = 1 mins > stats_domain_min_time = 12 hours > stats_ip_min_time = 12 hours > stats_memory_limit = 16 M > stats_refresh = 30 secs > stats_session_min_time = 15 mins > stats_track_cmds = no > stats_user_min_time = 24 hours > } > protocols = " imap pop3" > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0666 > user = postfix > } > } > service imap-login { > inet_listener imaps { > ssl = yes > } > } > service imap-postlogin { > executable = script-login /etc/dovecot/post-login/expire.sh > } > service imap { > executable = imap imap-postlogin > } > service pop3-login { > inet_listener pop3 { > port = 110 > } > inet_listener pop3s { > port = 995 > ssl = yes > } > } > service pop3-postlogin { > executable = script-login /etc/dovecot/post-login/expire.sh > } > service pop3 { > executable = pop3 pop3-postlogin > } > service quota-status { > executable = quota-status -p postfix > unix_listener /var/spool/postfix/private/quota { > group = postfix > mode = 0660 > user = postfix > } > } > service stats { > fifo_listener stats-mail { > mode = 0666 > user = dovecot > } > } > ssl_ca = ssl_cert = ssl_key = ssl_protocols = !SSLv2 !SSLv3 > userdb { > driver = passwd > } > protocol imap { > imap_capability = +XLIST +NAMESPACE METADATA QUOTA > imap_idle_notify_interval = 1 mins > mail_max_userip_connections = 500 > mail_plugins = " stats quota imap_quota imap_stats" > } > protocol pop3 { > mail_max_userip_connections = 500 > mail_plugins = " stats quota" > pop3_client_workarounds = outlook-no-nuls oe-ns-eoh > } > From sk at tyrion.de Fri Dec 2 19:27:25 2016 From: sk at tyrion.de (=?utf-8?B?U2ViYXN0aWFuIEvDtmhsZXI=?=) Date: Fri, 02 Dec 2016 19:27:25 +0000 Subject: Too many references: cannot splice In-Reply-To: References: Message-ID: <3f821f8c8adcf8ac14dbd232015988a4@mail.tyrion.de> December 2, 2016 6:58 PM, "Luis Ugalde" wrote: > On October 13th I sent a new email with subject "Too many references: > cannot splice" with a reference to a lklm post. Thanks Luis for the info. I wonder why I did not find that post... > You will find more info. and a patch there. I can confirm the patch is > working for us. I have applied that patch to the server and I will report back in a couple of days if it is also working for us. -- Sebastian From aki.tuomi at dovecot.fi Fri Dec 2 19:45:36 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Fri, 2 Dec 2016 21:45:36 +0200 (EET) Subject: CVE-2016-8562 in dovecot In-Reply-To: <765f2a7b-d7cf-26d0-f7c1-7dfcf41870ad@andreasschulze.de> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> <765f2a7b-d7cf-26d0-f7c1-7dfcf41870ad@andreasschulze.de> Message-ID: <959027752.2869.1480707937696@appsuite-dev.open-xchange.com> > On December 2, 2016 at 7:50 PM "A. Schulze" wrote: > > > > > Am 02.12.2016 um 08:00 schrieb Aki Tuomi: > > Workaround is to disable auth-policy component until fix is in place. > > This can be done by commenting out all auth_policy_* settings. > > Hello, > > could you be more verbose on how to verify if administrators are affected? > > # doveconf -n | grep auth_policy_ | wc -l > 0 > > but there /are/ default settings: > # doveconf -d | grep auth_policy_ > auth_policy_hash_mech = sha256 > auth_policy_hash_nonce = > auth_policy_hash_truncate = 12 > auth_policy_reject_on_fail = no > auth_policy_request_attributes = login=%{orig_username} pwhash=%{hashed_password} remote=%{real_rip} > auth_policy_server_api_header = > auth_policy_server_timeout_msecs = 2000 > auth_policy_server_url = > > Is such setup vulnerable? > > Thanks for clarification, > Andreas Your setup is not vulnerable, the critical values are auth_policy_server_url and auth_policy_hash_nonce. Those are unset in your config. Aki From mrobti at insiberia.net Fri Dec 2 20:51:06 2016 From: mrobti at insiberia.net (MRob) Date: Fri, 02 Dec 2016 12:51:06 -0800 Subject: LMTP delivery honours .forward by default? Message-ID: I was under the impression that Dovecot does not look at .forward by default, since of course, Sieve is where that kind of logic should go. However, I'm seeing a .forward file being honoured by the LMTP delivery agent. Is this to be expected? From petehodur at gmail.com Sat Dec 3 00:19:52 2016 From: petehodur at gmail.com (Peter Hodur) Date: Sat, 3 Dec 2016 01:19:52 +0100 Subject: Virtual mailboxes, please help Message-ID: Hi, I'm trying to setup virtual mailboxes. My setup: - migrated from Courier, so: separator = . prefix = INBOX. inbox = yes In doc i have read, thant i need to create separate namespace. namespace { prefix = virtual/ separator = / location = virtual:~/Maildir/virtual So i need to change / with . (Dot) in prefix and separator? Do i need to append LAYOUT=maildir++ to location? Where must location point? To the same directory where mail_location? Or do i need to create separate hierarchy for virtual mailboxes? Thanks for any answer ;) Peter ml. From jeremiah at jeremiahfoster.com Sat Dec 3 02:08:58 2016 From: jeremiah at jeremiahfoster.com (Jeremiah C. Foster) Date: Fri, 02 Dec 2016 21:08:58 -0500 Subject: CVE-2016-8652 in dovecot In-Reply-To: <7ea5f46c-a9ae-690c-29f6-d90375cf7e17@dovecot.fi> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> <31506634.MIXb7Dh5U9@sinistra> <7ea5f46c-a9ae-690c-29f6-d90375cf7e17@dovecot.fi> Message-ID: <1480730938.8339.6.camel@jeremiahfoster.com> On Fri, 2016-12-02 at 10:48 +0200, Aki Tuomi wrote: > > On 02.12.2016 10:45, Jonas Wielicki wrote: > > On Freitag, 2. Dezember 2016 09:00:58 CET Aki Tuomi wrote: > > > We are sorry to report that we have a bug in dovecot, which > > > merits a > > > CVE. See details below. If you haven't configured any > > > auth_policy_* > > > settings you are ok. This is fixed with > > > https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f3 > > > 4be960cff13 > > > a5a725ae and > > > https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d > > > 57351fd42c6 > > > 7a8612fc > > > > > > Important vulnerability in Dovecot (CVE-2016-8562) > > > > Are you sure about the CVE number? According to Debian [1] and > > mitre [2], it?s? > > for SIEMENS something, not Dovecot. > > > > best regards, > > Jonas Wielicki > > > > ???[1]: https://security-tracker.debian.org/tracker/CVE-2016-8562 > > ???[2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-856 > > 2 > > Ups, sent wrong number, correct is CVE-2016-8652. That is the same number, no? From noel.butler at ausics.net Sat Dec 3 02:23:25 2016 From: noel.butler at ausics.net (Noel Butler) Date: Sat, 03 Dec 2016 12:23:25 +1000 Subject: CVE-2016-8652 in dovecot In-Reply-To: <1480730938.8339.6.camel@jeremiahfoster.com> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> <31506634.MIXb7Dh5U9@sinistra> <7ea5f46c-a9ae-690c-29f6-d90375cf7e17@dovecot.fi> <1480730938.8339.6.camel@jeremiahfoster.com> Message-ID: <4d925c8b024a3034eb848a6bae4adf4a@ausics.net> On 03/12/2016 12:08, Jeremiah C. Foster wrote: > On Fri, 2016-12-02 at 10:48 +0200, Aki Tuomi wrote: > On 02.12.2016 10:45, Jonas Wielicki wrote: On Freitag, 2. Dezember 2016 09:00:58 CET Aki Tuomi wrote: We are sorry to report that we have a bug in dovecot, which > merits a > CVE. See details below. If you haven't configured any > auth_policy_* > settings you are ok. This is fixed with > https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f3 > 4be960cff13 > a5a725ae and > https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d > 57351fd42c6 > 7a8612fc > > Important vulnerability in Dovecot (CVE-2016-8562) > Are you sure about the CVE number? According to Debian [1 [1]] and > mitre [2 [2]], it's > for SIEMENS something, not Dovecot. > > best regards, > Jonas Wielicki > > [1]: https://security-tracker.debian.org/tracker/CVE-2016-8562 > [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-856 > 2 Ups, sent wrong number, correct is CVE-2016-8652. That is the same number, no? No, read it again. the wrong and pasted copie are 8 5 62, his revised is 8 6 52 -- Kind Regard, Noel Butler This Email, including any attachments, may contain legally privileged information, therefore remains confidential and subject to copyright protected under international law. You may not disseminate, discuss, or reveal, any part, to anyone, without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments, immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message. Only PDF [3] and ODF [4] documents accepted, please do not send proprietary formatted documents Links: ------ [1] https://security-tracker.debian.org/tracker/CVE-2016-8562 [2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-856 [3] http://www.adobe.com/ [4] http://en.wikipedia.org/wiki/OpenDocument From tss at iki.fi Sat Dec 3 17:48:30 2016 From: tss at iki.fi (Timo Sirainen) Date: Sat, 3 Dec 2016 19:48:30 +0200 Subject: v2.2.27 released Message-ID: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig Note that the download URLs are now https with a certificate from Let's Encrypt. * dovecot.list.index.log rotation sizes/times were changed so that the .log file stays smaller and .log.2 is deleted sooner. + Added mail_crypt plugin that allows encryption of stored emails. See http://wiki2.dovecot.org/Plugins/MailCrypt + stats: Global stats can be sent to Carbon server by setting stats_carbon_server=ip:port + imap/pop3 proxy: If passdb returns proxy_not_trusted, don't send ID/XCLIENT + Added generic hash modifier for %variables: %{;rounds=,truncate=,salt=s>:field} Hash algorithm is any of the supported ones, e.g. md5, sha1, sha256. Also "pkcs5" is supported using SHA256. For example: %{sha256:user} or %{md5;truncate=32:user}. + Added support for SHA3-256 and SHA3-512 hashes. + config: Support DNS wildcards in local_name, e.g. local_name *.example.com { .. } matches anything.example.com, but not multiple.anything.example.com. + config: Support multiple names in local_name, e.g. local_name "1.example.com 2.example.com" { .. } - Fixed crash in auth process when auth-policy was configured and authentication was aborted/failed without a username set. - director: If two users had different tags but the same hash, the users may have been redirected to the wrong tag's hosts. - Index files may have been thought incorrectly lost, causing "Missing middle file seq=.." to be logged and index rebuild. This happened more easily with IMAP hibernation enabled. - Various fixes to restoring state correctly in un-hibernation. - dovecot.index files were commonly 4 bytes per email too large. This is because 3 bytes per email were being wasted that could have been used for IMAP keywords. - Various fixes to handle dovecot.list.index corruption better. - lib-fts: Fixed assert-crash in address tokenizer with specific input. - Fixed assert-crash in HTML to text parsing with specific input (e.g. for FTS indexing or snippet generation) - doveadm sync -1: Fixed handling mailbox GUID conflicts. - sdbox, mdbox: Perform full index rebuild if corruption is detected inside lib-index, which runs index fsck. - quota: Don't skip quota checks when moving mails between different quota roots. - search: Multiple sequence sets or UID sets in search parameters weren't handled correctly. They were incorrectly merged together. From lists at merit.unu.edu Sat Dec 3 18:47:22 2016 From: lists at merit.unu.edu (mj) Date: Sat, 3 Dec 2016 19:47:22 +0100 Subject: SAML | Input buffer full (no auth attempts in 0 secs) Message-ID: Hi, In my journey to enable SAML auth for our webmail (sogo.nu) I have created a password-less dovecot imap listener on 127.0.0.1/32, so that once a user is SAML authenticated for the SOGo webmail, SOGo can connect to dovecot on 127.0.0.1:143 with something like "01 LOGIN username randompassword". Watching this (tcpflow) as it happens,i can see the following auth attempt coming from sogo: > 1 login "username" "eF7VVm1vmzAQ/iuI77wY8kJQEy1t2inSukpJVU37UhlzJN7AjmyzZPv1Owfgkdjfkgkfldlkfjg9jQNMvaNZMm7RvifC/Pc/ecfaFpkcdTrUEZLoW1K3Kh4+rn2C6ViCXVXMeCFqBjw+Ll9PZDHLh+TFsPu3ERmozttTGb2PO22627DV2pVl7g+8T7dPthydZQUIcLbahgYFsPoDQmHNsYzbbms7E9nz32B8kIEuY7oxFETi8bpE6U9MAZjiiLUiABzdB1rnUJ8zqSQX+fDBwSOH54T6I49GPiu2Q4+GxPLmps9Wk1qUrTWBtP3QIUN24pShfS0qOlWXsKaF5or7ZceId++yDLMvkCzDQhPyId85l1I1VBsYLf8URcUjPHUyerj8al0BtgPOOQ2pM1lBsuvjbp9jGbBE26KykyXjlWnbkFs5bpy11hRZwAVaBa8CcCzaih1kdp7sSdmmYG1C8U9mM/2lNoLbDaDYeK55ZALVcyPOJwefde1qwFjuYrIYWzkdpgp8QC9EYKDfdybD/eDC9JQAbX08tr0huSYBDOZv3+VUD6/evQJ4HtTRo2TtR9ZGqYQopSXvGjK0yXgETDiZnoAL0InHTAm+jTMkXwDBCFUZxVeY4s9VzhWL3CSgGGpkh8A6+N22I6mWc/hk8Au8xmLZaGGiiwL9YUx1e8LgZrCbrS21yksBvbgzDssWGUOQFLe04vooDwoscmtAwGpIBBEHYzlCdAcswsGsFcPjrKsddsIBs8uK6YDGrzuEWOdBAx8ZTgi7aCdsTW4cMtLQY7FBSGuioOTZYlcRQPzy16X5FuvOYxaSbgTsOK2daNwKNL8+z4edokyJkthqoMdaW05DzQvwcLtGJvvGzy+w+" Note, the actual 'password' is even longer. This connection attempt is causing dovecot to throw the following error: > Dec 02 22:34:33 imap-login: Info: Disconnected: Input buffer full (no > auth attempts in 0 secs): user=<>, rip=x.y.z.32, lip=x.y.z.68, > session= and > BYE Input buffer full, aborting So this doesn't work. :-( The question: is there a way to make this work? (make the input buffer larger, for example..?) Or any other ideas to make this work? Thanks in advance, MJ From tss at iki.fi Sat Dec 3 19:04:47 2016 From: tss at iki.fi (Timo Sirainen) Date: Sat, 3 Dec 2016 21:04:47 +0200 Subject: SAML | Input buffer full (no auth attempts in 0 secs) In-Reply-To: References: Message-ID: <12DAAD5B-9118-410D-AE03-C4B549841029@iki.fi> On 3 Dec 2016, at 20.47, mj wrote: > > Hi, > > In my journey to enable SAML auth for our webmail (sogo.nu) I have > created a password-less dovecot imap listener on 127.0.0.1/32, so that > once a user is SAML authenticated for the SOGo webmail, SOGo can connect to dovecot on 127.0.0.1:143 with something like "01 LOGIN username randompassword". > > Watching this (tcpflow) as it happens,i can see the following auth attempt coming from sogo: .. > > Dec 02 22:34:33 imap-login: Info: Disconnected: Input buffer full (no > > auth attempts in 0 secs): user=<>, rip=x.y.z.32, lip=x.y.z.68, > > session= If SOGo used AUTHENTICATE PLAIN instead of LOGIN, it should work. The SASL authentication buffer is larger (8 kB) than regular commands' buffer (~1 kB). > The question: is there a way to make this work? (make the input buffer larger, for example..?) You could also increase this: src/lib-master/master-auth.h:#define MASTER_AUTH_MAX_DATA_SIZE (1024 + 128 + 64 + 2) From jeremiah at jeremiahfoster.com Sat Dec 3 19:11:09 2016 From: jeremiah at jeremiahfoster.com (Jeremiah C. Foster) Date: Sat, 03 Dec 2016 14:11:09 -0500 Subject: CVE-2016-8652 in dovecot In-Reply-To: <4d925c8b024a3034eb848a6bae4adf4a@ausics.net> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> <31506634.MIXb7Dh5U9@sinistra> <7ea5f46c-a9ae-690c-29f6-d90375cf7e17@dovecot.fi> <1480730938.8339.6.camel@jeremiahfoster.com> <4d925c8b024a3034eb848a6bae4adf4a@ausics.net> Message-ID: <1480792269.13755.0.camel@jeremiahfoster.com> On Sat, 2016-12-03 at 12:23 +1000, Noel Butler wrote: > On 03/12/2016 12:08, Jeremiah C. Foster wrote: > > > On Fri, 2016-12-02 at 10:48 +0200, Aki Tuomi wrote:? > > On 02.12.2016 10:45, Jonas Wielicki wrote: On Freitag, 2. Dezember > > 2016 09:00:58 CET Aki Tuomi wrote: We are sorry to report that we > > have a bug in dovecot, which > > merits a > > CVE. See details below. If you haven't configured any > > auth_policy_* > > settings you are ok. This is fixed with > > https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f3 > > 4be960cff13 > > a5a725ae and > > https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d > > 57351fd42c6 > > 7a8612fc > > > > Important vulnerability in Dovecot (CVE-2016-8562)? > > Are you sure about the CVE number? According to Debian [1 [1]] and > > mitre [2 [2]], it's? > > for SIEMENS something, not Dovecot. > > > > best regards, > > Jonas Wielicki > > > > [1]: https://security-tracker.debian.org/tracker/CVE-2016-8562 > > [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-856 > > 2 > > Ups, sent wrong number, correct is CVE-2016-8652.? > That is the same number, no?? > > No, read it again. the wrong and pasted copie are 8 5 62, his revised > is > 8 6 52? Ah, thank you. So I guess the CVE is then here: https://cve.mitre.org/c gi-bin/cvename.cgi?name=CVE-2016-8652 but this doesn't provide a whole lot more information yet. Cheers, Jeremiah From aki.tuomi at dovecot.fi Sat Dec 3 19:25:56 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Sat, 3 Dec 2016 21:25:56 +0200 (EET) Subject: CVE-2016-8652 in dovecot In-Reply-To: <1480792269.13755.0.camel@jeremiahfoster.com> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> <31506634.MIXb7Dh5U9@sinistra> <7ea5f46c-a9ae-690c-29f6-d90375cf7e17@dovecot.fi> <1480730938.8339.6.camel@jeremiahfoster.com> <4d925c8b024a3034eb848a6bae4adf4a@ausics.net> <1480792269.13755.0.camel@jeremiahfoster.com> Message-ID: <1928660436.3076.1480793157168@appsuite-dev.open-xchange.com> > On December 3, 2016 at 9:11 PM "Jeremiah C. Foster" wrote: > > > On Sat, 2016-12-03 at 12:23 +1000, Noel Butler wrote: > > On 03/12/2016 12:08, Jeremiah C. Foster wrote: > > > > > On Fri, 2016-12-02 at 10:48 +0200, Aki Tuomi wrote: > > > On 02.12.2016 10:45, Jonas Wielicki wrote: On Freitag, 2. Dezember > > > 2016 09:00:58 CET Aki Tuomi wrote: We are sorry to report that we > > > have a bug in dovecot, which > > > merits a > > > CVE. See details below. If you haven't configured any > > > auth_policy_* > > > settings you are ok. This is fixed with > > > https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f3 > > > 4be960cff13 > > > a5a725ae and > > > https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d > > > 57351fd42c6 > > > 7a8612fc > > > > > > Important vulnerability in Dovecot (CVE-2016-8562) > > > Are you sure about the CVE number? According to Debian [1 [1]] and > > > mitre [2 [2]], it's > > > for SIEMENS something, not Dovecot. > > > > > > best regards, > > > Jonas Wielicki > > > > > > [1]: https://security-tracker.debian.org/tracker/CVE-2016-8562 > > > [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-856 > > > 2 > > > > Ups, sent wrong number, correct is CVE-2016-8652. > > That is the same number, no? > > > > No, read it again. the wrong and pasted copie are 8 5 62, his revised > > is > > 8 6 52 > > Ah, thank you. So I guess the CVE is then here: https://cve.mitre.org/c > gi-bin/cvename.cgi?name=CVE-2016-8652 but this doesn't provide a whole > lot more information yet. > > Cheers, > > Jeremiah Hi! What piece of information are you missing? Aki From jeremiah at jeremiahfoster.com Sat Dec 3 21:00:56 2016 From: jeremiah at jeremiahfoster.com (Jeremiah C. Foster) Date: Sat, 03 Dec 2016 16:00:56 -0500 Subject: CVE-2016-8652 in dovecot In-Reply-To: <1928660436.3076.1480793157168@appsuite-dev.open-xchange.com> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> <31506634.MIXb7Dh5U9@sinistra> <7ea5f46c-a9ae-690c-29f6-d90375cf7e17@dovecot.fi> <1480730938.8339.6.camel@jeremiahfoster.com> <4d925c8b024a3034eb848a6bae4adf4a@ausics.net> <1480792269.13755.0.camel@jeremiahfoster.com> <1928660436.3076.1480793157168@appsuite-dev.open-xchange.com> Message-ID: <1480798856.13755.4.camel@jeremiahfoster.com> On Sat, 2016-12-03 at 21:25 +0200, Aki Tuomi wrote: > > On December 3, 2016 at 9:11 PM "Jeremiah C. Foster" > iahfoster.com> wrote: > > > > On Sat, 2016-12-03 at 12:23 +1000, Noel Butler wrote: > > > On 03/12/2016 12:08, Jeremiah C. Foster wrote: > > > > > > > On Fri, 2016-12-02 at 10:48 +0200, Aki Tuomi wrote:? > > > > On 02.12.2016 10:45, Jonas Wielicki wrote: On Freitag, 2. > > > > Dezember > > > > 2016 09:00:58 CET Aki Tuomi wrote: > > > > Important vulnerability in Dovecot (CVE-2016-8562)? > > > > Are you sure about the CVE number? According to Debian [1 [1]] > > > > and > > > > mitre [2 [2]], it's? > > > > for SIEMENS something, not Dovecot. > > > > > > > > best regards, > > > > Jonas Wielicki > > > > > > > > [1]: > > > > [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-85 > > > > 6 > > > > 2 > > > > > > Ups, sent wrong number, correct is CVE-2016-8652.? > > > That is the same number, no?? > > > > > > No, read it again. the wrong and pasted copie are 8 5 62, his > > > revised > > > is > > > 8 6 52? > > > > Ah, thank you. So I guess the CVE is then here: https://cve.mitre.o > > rg/c > > gi-bin/cvename.cgi?name=CVE-2016-8652 but this doesn't provide a > > whole > > lot more information yet. > > > > Cheers, > > > > Jeremiah > > Hi! > > What piece of information are you missing? Well the CVE web page says in the description: '** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided." Looking at this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84660 5 in Debian's bug tracker it appears there is not yet a fix. I guess ideally I'm looking for a way to determine if I am affected, and if I am affected to mitigate or patch the problem. In this thread there was a discussion about checking via the doveconf tool; doveconf -n | grep auth_policy_ | wc -l. Is this the best approach? Then I imagine I need to check "the critical values auth_policy_server_url and auth_policy_hash_nonce" to see if those are set. If they are set what does one do? I guess that question is better asked once I've determined that I'm affected. Thanks, Jeremiah > > Aki From vijay at ericavijay.net Sat Dec 3 21:16:03 2016 From: vijay at ericavijay.net (Vijay Sarvepalli) Date: Sat, 3 Dec 2016 16:16:03 -0500 Subject: Simple way to get mailbox size by folder. Message-ID: Is there a simple way to get each mailbox size using dovecot's IMAP interface? The GETQUOTAROOT and GETQUOTA seems to work with the full maildir size and not the individual folders. I am finding a simple way for the webmail client to show usage of each folder. Thanks Vijay From ricardomachini at gmail.com Sat Dec 3 21:20:05 2016 From: ricardomachini at gmail.com (Ricardo Machini) Date: Sat, 3 Dec 2016 19:20:05 -0200 Subject: RES: v2.2.27 released In-Reply-To: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> Message-ID: <015b01d24dab$06b1fd00$1415f700$@gmail.com> Helo Timo, I tried to compile and got one error on Centos 6.8: checking that generated files are newer than configure... done configure: error: conditional "SSL_VERSION_GE_102" was never defined. Usually this means the macro was only invoked conditionally. # configure ./configure with-ldap=yes --with-zlib --with-bzlib --with-solr # uname -a Linux host 2.6.32-573.26.1.el6.x86_64 #1 SMP Wed May 4 00:57:44 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Regards, Ricado Machini -----Mensagem original----- De: dovecot [mailto:dovecot-bounces at dovecot.org] Em nome de Timo Sirainen Enviada em: s?bado, 3 de dezembro de 2016 15:49 Para: dovecot-news at dovecot.org; Dovecot Mailing List Assunto: v2.2.27 released https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig Note that the download URLs are now https with a certificate from Let's Encrypt. * dovecot.list.index.log rotation sizes/times were changed so that the .log file stays smaller and .log.2 is deleted sooner. + Added mail_crypt plugin that allows encryption of stored emails. See http://wiki2.dovecot.org/Plugins/MailCrypt + stats: Global stats can be sent to Carbon server by setting stats_carbon_server=ip:port + imap/pop3 proxy: If passdb returns proxy_not_trusted, don't send ID/XCLIENT + Added generic hash modifier for %variables: %{;rounds=,truncate=,salt=s>:field} Hash algorithm is any of the supported ones, e.g. md5, sha1, sha256. Also "pkcs5" is supported using SHA256. For example: %{sha256:user} or %{md5;truncate=32:user}. + Added support for SHA3-256 and SHA3-512 hashes. + config: Support DNS wildcards in local_name, e.g. local_name *.example.com { .. } matches anything.example.com, but not multiple.anything.example.com. + config: Support multiple names in local_name, e.g. local_name "1.example.com 2.example.com" { .. } - Fixed crash in auth process when auth-policy was configured and authentication was aborted/failed without a username set. - director: If two users had different tags but the same hash, the users may have been redirected to the wrong tag's hosts. - Index files may have been thought incorrectly lost, causing "Missing middle file seq=.." to be logged and index rebuild. This happened more easily with IMAP hibernation enabled. - Various fixes to restoring state correctly in un-hibernation. - dovecot.index files were commonly 4 bytes per email too large. This is because 3 bytes per email were being wasted that could have been used for IMAP keywords. - Various fixes to handle dovecot.list.index corruption better. - lib-fts: Fixed assert-crash in address tokenizer with specific input. - Fixed assert-crash in HTML to text parsing with specific input (e.g. for FTS indexing or snippet generation) - doveadm sync -1: Fixed handling mailbox GUID conflicts. - sdbox, mdbox: Perform full index rebuild if corruption is detected inside lib-index, which runs index fsck. - quota: Don't skip quota checks when moving mails between different quota roots. - search: Multiple sequence sets or UID sets in search parameters weren't handled correctly. They were incorrectly merged together. From aki.tuomi at dovecot.fi Sat Dec 3 21:42:39 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Sat, 3 Dec 2016 23:42:39 +0200 (EET) Subject: CVE-2016-8652 in dovecot In-Reply-To: <1480798856.13755.4.camel@jeremiahfoster.com> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> <31506634.MIXb7Dh5U9@sinistra> <7ea5f46c-a9ae-690c-29f6-d90375cf7e17@dovecot.fi> <1480730938.8339.6.camel@jeremiahfoster.com> <4d925c8b024a3034eb848a6bae4adf4a@ausics.net> <1480792269.13755.0.camel@jeremiahfoster.com> <1928660436.3076.1480793157168@appsuite-dev.open-xchange.com> <1480798856.13755.4.camel@jeremiahfoster.com> Message-ID: <2145632847.3139.1480801360032@appsuite-dev.open-xchange.com> > On December 3, 2016 at 11:00 PM "Jeremiah C. Foster" wrote: > > > On Sat, 2016-12-03 at 21:25 +0200, Aki Tuomi wrote: > > > On December 3, 2016 at 9:11 PM "Jeremiah C. Foster" > > iahfoster.com> wrote: > > > > > > On Sat, 2016-12-03 at 12:23 +1000, Noel Butler wrote: > > > > On 03/12/2016 12:08, Jeremiah C. Foster wrote: > > > > > > > > > On Fri, 2016-12-02 at 10:48 +0200, Aki Tuomi wrote: > > > > > On 02.12.2016 10:45, Jonas Wielicki wrote: On Freitag, 2. > > > > > Dezember > > > > > 2016 09:00:58 CET Aki Tuomi wrote: > > > > > > > > Important vulnerability in Dovecot (CVE-2016-8562) > > > > > Are you sure about the CVE number? According to Debian [1 [1]] > > > > > and > > > > > mitre [2 [2]], it's > > > > > for SIEMENS something, not Dovecot. > > > > > > > > > > best regards, > > > > > Jonas Wielicki > > > > > > > > > > [1]: > > > > > [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-85 > > > > > 6 > > > > > 2 > > > > > > > > Ups, sent wrong number, correct is CVE-2016-8652. > > > > That is the same number, no? > > > > > > > > No, read it again. the wrong and pasted copie are 8 5 62, his > > > > revised > > > > is > > > > 8 6 52 > > > > > > Ah, thank you. So I guess the CVE is then here: https://cve.mitre.o > > > rg/c > > > gi-bin/cvename.cgi?name=CVE-2016-8652 but this doesn't provide a > > > whole > > > lot more information yet. > > > > > > Cheers, > > > > > > Jeremiah > > > > Hi! > > > > What piece of information are you missing? > > Well the CVE web page says in the description: '** RESERVED ** This > candidate has been reserved by an organization or individual that will > use it when announcing a new security problem. When the candidate has > been publicized, the details for this candidate will be provided." > Yes, it can take some time for that to update, what with this being unembargoed on Friday in first place. > Looking at this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84660 > 5 in Debian's bug tracker it appears there is not yet a fix. > Interesting, there is a fix. Debian has probably not yet updated their page, for similar reasons as above. > I guess ideally I'm looking for a way to determine if I am affected, > and if I am affected to mitigate or patch the problem. > > In this thread there was a discussion about checking via the doveconf > tool; doveconf -n | grep auth_policy_ | wc -l. Is this the best > approach? > > Then I imagine I need to check "the critical values > auth_policy_server_url and auth_policy_hash_nonce" to see if those are > set. If they are set what does one do? I guess that question is better > asked once I've determined that I'm affected. > If they are set, either apply the mentioned patch, upgrade to 2.2.27, or ensure their value is empty or they are commented out. Otherwise you are at risk. Aki > Thanks, > > Jeremiah > > > > > > Aki From aki.tuomi at dovecot.fi Sat Dec 3 21:43:23 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Sat, 3 Dec 2016 23:43:23 +0200 (EET) Subject: RES: v2.2.27 released In-Reply-To: <015b01d24dab$06b1fd00$1415f700$@gmail.com> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> <015b01d24dab$06b1fd00$1415f700$@gmail.com> Message-ID: <1226529079.3141.1480801403777@appsuite-dev.open-xchange.com> > On December 3, 2016 at 11:20 PM Ricardo Machini wrote: > > > Helo Timo, > > I tried to compile and got one error on Centos 6.8: > > checking that generated files are newer than configure... done > configure: error: conditional "SSL_VERSION_GE_102" was never defined. > Usually this means the macro was only invoked conditionally. > > # configure > ./configure with-ldap=yes --with-zlib --with-bzlib --with-solr > Is this with the distribution tarball, or from git? If it's from git, you need to re-run ./autogen.sh to make sure everything is up to date. Aki From aki.tuomi at dovecot.fi Sat Dec 3 21:53:42 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Sat, 3 Dec 2016 23:53:42 +0200 (EET) Subject: Simple way to get mailbox size by folder. In-Reply-To: References: Message-ID: <2101756398.3143.1480802022598@appsuite-dev.open-xchange.com> > On December 3, 2016 at 11:16 PM Vijay Sarvepalli wrote: > > > Is there a simple way to get each mailbox size using dovecot's IMAP > interface? The GETQUOTAROOT and GETQUOTA seems to work with the full > maildir size and not the individual folders. > > I am finding a simple way for the webmail client to show usage of each > folder. > > Thanks > Vijay $ doveadm mailbox status -u cmouse all INBOX INBOX messages=9206 recent=0 uidnext=33115 uidvalidity=1451655531 unseen=7 highestmodseq=39954 vsize=538582181 guid=d595a62d65818656f72c000074be03de $ doveadm -fjson mailbox status -u cmouse at cmouse.fi all INBOX [{"mailbox":"INBOX","messages":"9206","recent":"0","uidnext":"33115","uidvalidity":"1451655531","unseen":"7","highestmodseq":"39954","vsize":"538582181","guid":"d595a62d65818656f72c000074be03de"}] JSON support might not be available in your version, if it's old enough. Aki From ricardomachini at gmail.com Sat Dec 3 23:38:20 2016 From: ricardomachini at gmail.com (Ricardo Machini) Date: Sat, 3 Dec 2016 21:38:20 -0200 Subject: RES: RES: v2.2.27 released In-Reply-To: <1226529079.3141.1480801403777@appsuite-dev.open-xchange.com> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> <015b01d24dab$06b1fd00$1415f700$@gmail.com> <1226529079.3141.1480801403777@appsuite-dev.open-xchange.com> Message-ID: <016401d24dbe$56ddb0e0$049912a0$@gmail.com> >From tarball distribution: https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz Ricardo -----Mensagem original----- De: Aki Tuomi [mailto:aki.tuomi at dovecot.fi] Enviada em: s?bado, 3 de dezembro de 2016 19:43 Para: Dovecot Mailing List ; Ricardo Machini ; dovecot-news at dovecot.org Assunto: Re: RES: v2.2.27 released > On December 3, 2016 at 11:20 PM Ricardo Machini wrote: > > > Helo Timo, > > I tried to compile and got one error on Centos 6.8: > > checking that generated files are newer than configure... done > configure: error: conditional "SSL_VERSION_GE_102" was never defined. > Usually this means the macro was only invoked conditionally. > > # configure > ./configure with-ldap=yes --with-zlib --with-bzlib --with-solr > Is this with the distribution tarball, or from git? If it's from git, you need to re-run ./autogen.sh to make sure everything is up to date. Aki From tss at iki.fi Sun Dec 4 00:10:44 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 4 Dec 2016 02:10:44 +0200 Subject: RES: RES: v2.2.27 released In-Reply-To: <016401d24dbe$56ddb0e0$049912a0$@gmail.com> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> <015b01d24dab$06b1fd00$1415f700$@gmail.com> <1226529079.3141.1480801403777@appsuite-dev.open-xchange.com> <016401d24dbe$56ddb0e0$049912a0$@gmail.com> Message-ID: <133FF839-B8A3-47D9-AF0D-1CF1999D00AB@iki.fi> I don't see it, and can't really think of a good reason why it would happen. This happens in configure? And the first thing you ran was configure, right? No autogen.sh or autoconf/automake? -bash-4.1# cat /etc/redhat-release CentOS release 6.8 (Final) -bash-4.1# uname -a Linux test-centos6.dovecot.net 2.6.32-642.6.1.el6.x86_64 #1 SMP Wed Oct 5 00:36:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -bash-4.1# tar xzf dovecot-2.2.27.tar.gz -bash-4.1# cd dovecot-2.2.27 -bash-4.1# ./configure --with-ldap=yes --with-zlib --with-bzlib --with-solr > foo -bash-4.1# grep 102 foo -bash-4.1# > On 4 Dec 2016, at 1.38, Ricardo Machini wrote: > > From tarball distribution: > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz > > Ricardo > > -----Mensagem original----- > De: Aki Tuomi [mailto:aki.tuomi at dovecot.fi] > Enviada em: s?bado, 3 de dezembro de 2016 19:43 > Para: Dovecot Mailing List ; Ricardo Machini ; dovecot-news at dovecot.org > Assunto: Re: RES: v2.2.27 released > > >> On December 3, 2016 at 11:20 PM Ricardo Machini wrote: >> >> >> Helo Timo, >> >> I tried to compile and got one error on Centos 6.8: >> >> checking that generated files are newer than configure... done >> configure: error: conditional "SSL_VERSION_GE_102" was never defined. >> Usually this means the macro was only invoked conditionally. >> >> # configure >> ./configure with-ldap=yes --with-zlib --with-bzlib --with-solr >> > > Is this with the distribution tarball, or from git? If it's from git, you need to re-run ./autogen.sh to make sure everything is up to date. > > Aki From ricardomachini at gmail.com Sun Dec 4 01:22:14 2016 From: ricardomachini at gmail.com (Ricardo Machini) Date: Sat, 3 Dec 2016 23:22:14 -0200 Subject: RES: RES: RES: v2.2.27 released In-Reply-To: <133FF839-B8A3-47D9-AF0D-1CF1999D00AB@iki.fi> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> <015b01d24dab$06b1fd00$1415f700$@gmail.com> <1226529079.3141.1480801403777@appsuite-dev.open-xchange.com> <016401d24dbe$56ddb0e0$049912a0$@gmail.com> <133FF839-B8A3-47D9-AF0D-1CF1999D00AB@iki.fi> Message-ID: <017001d24dcc$dab926c0$902b7440$@gmail.com> This happens on configure, I only ran ./configure. This error is logged to stderr: [root at host1 dovecot]# wget https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz [root at host1 dovecot]# tar xzf dovecot-2.2.27.tar.gz [root at host1 dovecot]# cd dovecot-2.2.27 [root at host1 dovecot-2.2.27]# ./configure --with-ldap=yes --with-zlib --with-bzlib --with-solr > foo configure: error: conditional "SSL_VERSION_GE_102" was never defined. Usually this means the macro was only invoked conditionally. [root at host1 dovecot-2.2.27]# tail foo checking for library containing quota_open... no checking for XML_Parse in -lexpat... yes checking expat.h usability... yes checking expat.h presence... yes checking for expat.h... yes checking for sb_stemmer_new in -lstemmer... no checking for special_textcat_Init in -lexttextcat... no checking for special_textcat_Init in -ltextcat... no checking for valgrind... no checking that generated files are newer than configure... done About openssl: [root at host1 dovecot-2.2.27]# rpm -qa | grep openssl openssl-1.0.1e-48.el6_8.3.x86_64 -----Mensagem original----- De: Timo Sirainen [mailto:tss at iki.fi] Enviada em: s?bado, 3 de dezembro de 2016 22:11 Para: Ricardo Machini Cc: Dovecot Mailing List Assunto: Re: RES: RES: v2.2.27 released I don't see it, and can't really think of a good reason why it would happen. This happens in configure? And the first thing you ran was configure, right? No autogen.sh or autoconf/automake? -bash-4.1# cat /etc/redhat-release CentOS release 6.8 (Final) -bash-4.1# uname -a Linux test-centos6.dovecot.net 2.6.32-642.6.1.el6.x86_64 #1 SMP Wed Oct 5 00:36:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -bash-4.1# tar xzf dovecot-2.2.27.tar.gz -bash-4.1# cd dovecot-2.2.27 -bash-4.1# ./configure --with-ldap=yes --with-zlib --with-bzlib --with-solr > foo -bash-4.1# grep 102 foo -bash-4.1# > On 4 Dec 2016, at 1.38, Ricardo Machini wrote: > > From tarball distribution: > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz > > Ricardo > > -----Mensagem original----- > De: Aki Tuomi [mailto:aki.tuomi at dovecot.fi] Enviada em: s?bado, 3 de > dezembro de 2016 19:43 > Para: Dovecot Mailing List ; Ricardo Machini > ; dovecot-news at dovecot.org > Assunto: Re: RES: v2.2.27 released > > >> On December 3, 2016 at 11:20 PM Ricardo Machini wrote: >> >> >> Helo Timo, >> >> I tried to compile and got one error on Centos 6.8: >> >> checking that generated files are newer than configure... done >> configure: error: conditional "SSL_VERSION_GE_102" was never defined. >> Usually this means the macro was only invoked conditionally. >> >> # configure >> ./configure with-ldap=yes --with-zlib --with-bzlib --with-solr >> > > Is this with the distribution tarball, or from git? If it's from git, you need to re-run ./autogen.sh to make sure everything is up to date. > > Aki From tss at iki.fi Sun Dec 4 01:42:06 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 4 Dec 2016 03:42:06 +0200 Subject: RES: RES: RES: v2.2.27 released In-Reply-To: <017001d24dcc$dab926c0$902b7440$@gmail.com> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> <015b01d24dab$06b1fd00$1415f700$@gmail.com> <1226529079.3141.1480801403777@appsuite-dev.open-xchange.com> <016401d24dbe$56ddb0e0$049912a0$@gmail.com> <133FF839-B8A3-47D9-AF0D-1CF1999D00AB@iki.fi> <017001d24dcc$dab926c0$902b7440$@gmail.com> Message-ID: <188614F6-D7EB-47A3-8F06-519C39591082@iki.fi> Oh, you have no openssl-devel installed. Looks like the build is broken if trying to build without OpenSSL. I wonder if this is worth the effort to create a fixed release.. Nobody really should be building without OpenSSL nowadays anyway, but the error message is a bit confusing. > On 4 Dec 2016, at 3.22, Ricardo Machini wrote: > > This happens on configure, I only ran ./configure. > This error is logged to stderr: > > [root at host1 dovecot]# wget https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz > [root at host1 dovecot]# tar xzf dovecot-2.2.27.tar.gz > [root at host1 dovecot]# cd dovecot-2.2.27 > [root at host1 dovecot-2.2.27]# ./configure --with-ldap=yes --with-zlib --with-bzlib --with-solr > foo > configure: error: conditional "SSL_VERSION_GE_102" was never defined. > Usually this means the macro was only invoked conditionally. > [root at host1 dovecot-2.2.27]# tail foo > checking for library containing quota_open... no > checking for XML_Parse in -lexpat... yes > checking expat.h usability... yes > checking expat.h presence... yes > checking for expat.h... yes > checking for sb_stemmer_new in -lstemmer... no > checking for special_textcat_Init in -lexttextcat... no > checking for special_textcat_Init in -ltextcat... no > checking for valgrind... no > checking that generated files are newer than configure... done > > About openssl: > [root at host1 dovecot-2.2.27]# rpm -qa | grep openssl > openssl-1.0.1e-48.el6_8.3.x86_64 > > > > -----Mensagem original----- > De: Timo Sirainen [mailto:tss at iki.fi] > Enviada em: s?bado, 3 de dezembro de 2016 22:11 > Para: Ricardo Machini > Cc: Dovecot Mailing List > Assunto: Re: RES: RES: v2.2.27 released > > I don't see it, and can't really think of a good reason why it would happen. This happens in configure? And the first thing you ran was configure, right? No autogen.sh or autoconf/automake? > > -bash-4.1# cat /etc/redhat-release > CentOS release 6.8 (Final) > -bash-4.1# uname -a > Linux test-centos6.dovecot.net 2.6.32-642.6.1.el6.x86_64 #1 SMP Wed Oct 5 00:36:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -bash-4.1# tar xzf dovecot-2.2.27.tar.gz -bash-4.1# cd dovecot-2.2.27 -bash-4.1# ./configure --with-ldap=yes --with-zlib --with-bzlib --with-solr > foo -bash-4.1# grep 102 foo -bash-4.1# > > >> On 4 Dec 2016, at 1.38, Ricardo Machini wrote: >> >> From tarball distribution: >> https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz >> >> Ricardo >> >> -----Mensagem original----- >> De: Aki Tuomi [mailto:aki.tuomi at dovecot.fi] Enviada em: s?bado, 3 de >> dezembro de 2016 19:43 >> Para: Dovecot Mailing List ; Ricardo Machini >> ; dovecot-news at dovecot.org >> Assunto: Re: RES: v2.2.27 released >> >> >>> On December 3, 2016 at 11:20 PM Ricardo Machini wrote: >>> >>> >>> Helo Timo, >>> >>> I tried to compile and got one error on Centos 6.8: >>> >>> checking that generated files are newer than configure... done >>> configure: error: conditional "SSL_VERSION_GE_102" was never defined. >>> Usually this means the macro was only invoked conditionally. >>> >>> # configure >>> ./configure with-ldap=yes --with-zlib --with-bzlib --with-solr >>> >> >> Is this with the distribution tarball, or from git? If it's from git, you need to re-run ./autogen.sh to make sure everything is up to date. >> >> Aki From ebroch at whitehorsetc.com Sun Dec 4 05:53:28 2016 From: ebroch at whitehorsetc.com (Eric Broch) Date: Sat, 3 Dec 2016 22:53:28 -0700 Subject: CentOS 7 Message-ID: Hello List, I'm building a dovecot-2.2.27 RPM for CentOS 7 and running into some issues The dovecot.spec (http://pkgs.fedoraproject.org/cgit/rpms/dovecot.git/tree/dovecot.spec) file runs 'autoreconf -I . -fiv' for aarch64 support just before the %configure option but is failing This worked fine on <= 2.2.26.0 when there was an m4/*.m4 directory (with *.m4 in it) in the sources. Is there something I should be aware of? Was the m4 directory removed for a reason? As a workaround I created the m4 directory and everything worked out, but is this the best solution? Eric From lists at alex-at.ru Sun Dec 4 07:29:58 2016 From: lists at alex-at.ru (Alexey Asemov (Alex/AT)) Date: Sun, 4 Dec 2016 10:29:58 +0300 Subject: CentOS 7 In-Reply-To: References: Message-ID: Hello Eric, For me, aclocal --install -I m4 preparation step helps and seems to be correct. Certain autoconf version scripts perform this step later than needed. From ebroch at whitehorsetc.com Sun Dec 4 07:34:00 2016 From: ebroch at whitehorsetc.com (Eric Broch) Date: Sun, 4 Dec 2016 00:34:00 -0700 Subject: CentOS 7 In-Reply-To: References: Message-ID: <5d736cb5-fa82-1012-8b23-927523baa889@whitehorsetc.com> Thanks Alexey! Worked a charm. On 12/4/2016 12:29 AM, Alexey Asemov (Alex/AT) wrote: > Hello Eric, > > For me, > > aclocal --install -I m4 > > preparation step helps and seems to be correct. Certain autoconf > version scripts perform this step later than needed. From mrobti at insiberia.net Sun Dec 4 10:08:18 2016 From: mrobti at insiberia.net (MRob) Date: Sun, 04 Dec 2016 02:08:18 -0800 Subject: doveadm edit headers? Message-ID: Hello, is there a way to edit a message header using doveadm? I see how I can fetch the things I need, but even if I can't edit in place; if I extract the full message, edit it, there doesn't seem to be a way to append it back again? From lists at alex-at.ru Sun Dec 4 10:42:58 2016 From: lists at alex-at.ru (Alexey Asemov (Alex/AT)) Date: Sun, 4 Dec 2016 13:42:58 +0300 Subject: v2.2.27 released In-Reply-To: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> Message-ID: <99bc34c3-8e46-e9c7-2278-e5a4f3c3538d@alex-at.ru> Thanks a lot for indexing fixes, Dovecot team. Any news for Pigeonhole? Currently had to rollup some commits from GIT to make it pass vacation test set with 2.2.27. --- On 03.12.2016 20:48, Timo Sirainen wrote: > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig > From trashcan at ellael.org Sun Dec 4 11:46:42 2016 From: trashcan at ellael.org (Michael Grimm) Date: Sun, 4 Dec 2016 12:46:42 +0100 Subject: No stats under FreeBSD 10.3 In-Reply-To: References: <12BC0BB8-8A18-43CD-879A-02DF43F701F3@iki.fi> Message-ID: <92D01379-0334-458B-A655-990D7346AB22@ellael.org> Larry Rosenman wrote: > fifo_listener stats-mail { > group = > mode = 0666 > user = > } > fifo_listener stats-user { > group = > mode = 0666 > user = > } BTW: What is "stats-user" used for? I cannot find a reference in http://wiki2.dovecot.org/Statistics Thanks and regards, Michael From mrobti at insiberia.net Sun Dec 4 12:20:22 2016 From: mrobti at insiberia.net (MRob) Date: Sun, 04 Dec 2016 04:20:22 -0800 Subject: Show pigeonhole version? Message-ID: <5ef7ebd5f19ddea1e0e870d128861c58@insiberia.net> How can I query the current pigeonhole version from a running instance to verify it is what I expect? Possible to get `dovecot --version` to show things like that? From tss at iki.fi Sun Dec 4 14:46:18 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 4 Dec 2016 16:46:18 +0200 Subject: Show pigeonhole version? In-Reply-To: <5ef7ebd5f19ddea1e0e870d128861c58@insiberia.net> References: <5ef7ebd5f19ddea1e0e870d128861c58@insiberia.net> Message-ID: <5CDC45BD-3477-4532-9E0B-C781035C6CCF@iki.fi> On 4 Dec 2016, at 14.20, MRob wrote: > > How can I query the current pigeonhole version from a running instance to verify it is what I expect? > > Possible to get `dovecot --version` to show things like that? doveconf -n header shows the installed version (practically the same as the running version). From ruga at protonmail.com Sun Dec 4 15:01:05 2016 From: ruga at protonmail.com (Ruga) Date: Sun, 04 Dec 2016 10:01:05 -0500 Subject: v2.2.27 released In-Reply-To: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> Message-ID: var-expand.c:686:17: warning: passing an object that undergoes default argument promotion to 'va_start' has undefined behavior [-Wvarargs] va_start(args, key2); ^ var-expand.c:673:58: note: parameter of type 'char' is declared here var_expand_table_build(char key, const char *value, char key2, ...) ^ -------- Original Message -------- Subject: v2.2.27 released Local Time: 3 December 2016 6:48 PM UTC Time: 3 December 2016 17:48 From: tss at iki.fi To: dovecot-news at dovecot.org, Dovecot Mailing List https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig Note that the download URLs are now https with a certificate from Let's Encrypt. * dovecot.list.index.log rotation sizes/times were changed so that the .log file stays smaller and .log.2 is deleted sooner. + Added mail_crypt plugin that allows encryption of stored emails. See http://wiki2.dovecot.org/Plugins/MailCrypt + stats: Global stats can be sent to Carbon server by setting stats_carbon_server=ip:port + imap/pop3 proxy: If passdb returns proxy_not_trusted, don't send ID/XCLIENT + Added generic hash modifier for %variables: %{;rounds=,truncate=,salt=s>:field} Hash algorithm is any of the supported ones, e.g. md5, sha1, sha256. Also "pkcs5" is supported using SHA256. For example: %{sha256:user} or %{md5;truncate=32:user}. + Added support for SHA3-256 and SHA3-512 hashes. + config: Support DNS wildcards in local_name, e.g. local_name *.example.com { .. } matches anything.example.com, but not multiple.anything.example.com. + config: Support multiple names in local_name, e.g. local_name "1.example.com 2.example.com" { .. } - Fixed crash in auth process when auth-policy was configured and authentication was aborted/failed without a username set. - director: If two users had different tags but the same hash, the users may have been redirected to the wrong tag's hosts. - Index files may have been thought incorrectly lost, causing "Missing middle file seq=.." to be logged and index rebuild. This happened more easily with IMAP hibernation enabled. - Various fixes to restoring state correctly in un-hibernation. - dovecot.index files were commonly 4 bytes per email too large. This is because 3 bytes per email were being wasted that could have been used for IMAP keywords. - Various fixes to handle dovecot.list.index corruption better. - lib-fts: Fixed assert-crash in address tokenizer with specific input. - Fixed assert-crash in HTML to text parsing with specific input (e.g. for FTS indexing or snippet generation) - doveadm sync -1: Fixed handling mailbox GUID conflicts. - sdbox, mdbox: Perform full index rebuild if corruption is detected inside lib-index, which runs index fsck. - quota: Don't skip quota checks when moving mails between different quota roots. - search: Multiple sequence sets or UID sets in search parameters weren't handled correctly. They were incorrectly merged together. From anic297 at mac.com Sun Dec 4 15:11:12 2016 From: anic297 at mac.com (Marnaud) Date: Sun, 04 Dec 2016 16:11:12 +0100 Subject: First steps in Dovecot; IMAP not working In-Reply-To: <4D2382EAA7F462AB046BF3BF@ritz.innovate.net> References: <4D2382EAA7F462AB046BF3BF@ritz.innovate.net> Message-ID: <990B5850-965D-4FCA-9ADC-EC49CB560046@mac.com> Le 18 oct. 2016 ? 13:32, Richard a ?crit: > Assuming that "barbu.sytes.net" is the intended hostname (not > something made up to obscure the real name), there is an MX-record > for that that points to "mail.barbu.sytes.net", but there is no > A-record for the "mail." hostname. There is an A-record for > "mail.sytes.net", in case that is what you were intending, in which > case you'd need to fix the MX on "barbu.sytes.net". Hello, Sorry for the delay in responding, I?ve been busy with something else. I just wanted to thank you for your answer. I have to admit I don?t have enough knowledge in that matter; I?ll stay with my existing mail provider and stop playing with things I don?t understand. Regards, Arnaud From ruga at protonmail.com Sun Dec 4 15:15:21 2016 From: ruga at protonmail.com (Ruga) Date: Sun, 04 Dec 2016 10:15:21 -0500 Subject: v2.2.27 released --- libressl Message-ID: >openssl version Libressl 2.4.4 Patch for dovecot: perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER < 0x10100000L\s*)$/$1 || defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-dcrypt/dcrypt-openssl.c; perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER < 0x10100000L\s*)$/$1 || defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-ssl-iostream/dovecot-openssl-common.c; perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER >= 0x10100000L\s*)$/$1 && !defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-dcrypt/dcrypt-openssl.c; perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER >= 0x10100000L\s*)$/$1 && !defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-ssl-iostream/dovecot-openssl-common.c; Both configuration and compilation are OK. The test fails as follows: [...] test_load_v1_public_key .............................................. : ok Panic: file randgen.c: line 21 (random_fill): assertion failed: (init_refcount > 0) Error: Raw backtrace: 2 libdcrypt_openssl.so 0x0000000103413d24 default_fatal_finish + 36 -> 3 libdcrypt_openssl.so 0x0000000103413afd default_fatal_handler + 61 -> 4 libdcrypt_openssl.so 0x0000000103414069 i_panic + 169 -> 5 libdcrypt_openssl.so 0x000000010344110c random_fill + 220 -> 6 libdcrypt_openssl.so 0x000000010340a63d dcrypt_openssl_store_private_key + 1037 -> 7 test-crypto 0x0000000103387f54 test_load_v2_key + 580 -> 8 test-crypto 0x000000010338990e test_run + 142 -> 9 test-crypto 0x0000000103386921 main + 81 -> 10 libdyld.dylib 0x00007fff9da95255 start + 1 /bin/sh: line 1: 56954 Abort trap: 6 ./$bin make[2]: *** [check-test] Error 1 make[1]: *** [check-recursive] Error 1 make: *** [check-recursive] Error 1 -------- Original Message -------- Subject: v2.2.27 released Local Time: 3 December 2016 6:48 PM UTC Time: 3 December 2016 17:48 From: tss at iki.fi To: dovecot-news at dovecot.org, Dovecot Mailing List https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig Note that the download URLs are now https with a certificate from Let's Encrypt. * dovecot.list.index.log rotation sizes/times were changed so that the .log file stays smaller and .log.2 is deleted sooner. + Added mail_crypt plugin that allows encryption of stored emails. See http://wiki2.dovecot.org/Plugins/MailCrypt + stats: Global stats can be sent to Carbon server by setting stats_carbon_server=ip:port + imap/pop3 proxy: If passdb returns proxy_not_trusted, don't send ID/XCLIENT + Added generic hash modifier for %variables: %{;rounds=,truncate=,salt=s>:field} Hash algorithm is any of the supported ones, e.g. md5, sha1, sha256. Also "pkcs5" is supported using SHA256. For example: %{sha256:user} or %{md5;truncate=32:user}. + Added support for SHA3-256 and SHA3-512 hashes. + config: Support DNS wildcards in local_name, e.g. local_name *.example.com { .. } matches anything.example.com, but not multiple.anything.example.com. + config: Support multiple names in local_name, e.g. local_name "1.example.com 2.example.com" { .. } - Fixed crash in auth process when auth-policy was configured and authentication was aborted/failed without a username set. - director: If two users had different tags but the same hash, the users may have been redirected to the wrong tag's hosts. - Index files may have been thought incorrectly lost, causing "Missing middle file seq=.." to be logged and index rebuild. This happened more easily with IMAP hibernation enabled. - Various fixes to restoring state correctly in un-hibernation. - dovecot.index files were commonly 4 bytes per email too large. This is because 3 bytes per email were being wasted that could have been used for IMAP keywords. - Various fixes to handle dovecot.list.index corruption better. - lib-fts: Fixed assert-crash in address tokenizer with specific input. - Fixed assert-crash in HTML to text parsing with specific input (e.g. for FTS indexing or snippet generation) - doveadm sync -1: Fixed handling mailbox GUID conflicts. - sdbox, mdbox: Perform full index rebuild if corruption is detected inside lib-index, which runs index fsck. - quota: Don't skip quota checks when moving mails between different quota roots. - search: Multiple sequence sets or UID sets in search parameters weren't handled correctly. They were incorrectly merged together. From lists at merit.unu.edu Sun Dec 4 19:37:30 2016 From: lists at merit.unu.edu (mj) Date: Sun, 4 Dec 2016 20:37:30 +0100 Subject: SAML | Input buffer full (no auth attempts in 0 secs) In-Reply-To: <12DAAD5B-9118-410D-AE03-C4B549841029@iki.fi> References: <12DAAD5B-9118-410D-AE03-C4B549841029@iki.fi> Message-ID: <22deb88a-4aa1-6b41-2aab-33a92a25d328@merit.unu.edu> On 12/03/2016 08:04 PM, Timo Sirainen wrote: > > If SOGo used AUTHENTICATE PLAIN instead of LOGIN, it should work. The > SASL authentication buffer is larger (8 kB) than regular commands' > buffer (~1 kB). Thanks Timo, that worked! :-) MJ From stephan at rename-it.nl Sun Dec 4 20:06:36 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Sun, 4 Dec 2016 21:06:36 +0100 Subject: v2.2.27 released In-Reply-To: <99bc34c3-8e46-e9c7-2278-e5a4f3c3538d@alex-at.ru> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> <99bc34c3-8e46-e9c7-2278-e5a4f3c3538d@alex-at.ru> Message-ID: <065a39ef-35de-f018-f873-d9d857dc1d1b@rename-it.nl> Op 12/4/2016 om 11:42 AM schreef Alexey Asemov (Alex/AT): > Thanks a lot for indexing fixes, Dovecot team. > > Any news for Pigeonhole? Currently had to rollup some commits from GIT > to make it pass vacation test set with 2.2.27. > What problem are you seeing? No Pigeonhole release is currently planned. > --- > > On 03.12.2016 20:48, Timo Sirainen wrote: >> https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz >> https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig >> From curtis at npc-usa.com Thu Dec 1 20:40:07 2016 From: curtis at npc-usa.com (Curtis Vaughan) Date: Thu, 1 Dec 2016 12:40:07 -0800 Subject: Mail marked read upon download Message-ID: Just set up a new server with postfix and dovecot. I don't know why, but as soon as mail is accessed it is marked read. I'll see emails momentarily marked unread, but then switch to read later although I haven't opened them. This has never been an issue before. Any ideas why? Thanks. Curtis From bjlockie at lockie.ca Sun Dec 4 17:30:27 2016 From: bjlockie at lockie.ca (James) Date: Sun, 4 Dec 2016 12:30:27 -0500 Subject: move IMAP folder Message-ID: I am trying to move an IMAP folder from Thunderbird and nothing happens. What /var/log file should I look in? From skdovecot at smail.inf.fh-brs.de Mon Dec 5 07:18:27 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 5 Dec 2016 08:18:27 +0100 (CET) Subject: LMTP delivery honours .forward by default? In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 2 Dec 2016, MRob wrote: > I was under the impression that Dovecot does not look at .forward by default, > since of course, Sieve is where that kind of logic should go. However, I'm > seeing a .forward file being honoured by the LMTP delivery agent. Is this to > be expected? What version of Dovecot are you using? In my installation the MTA handles .forward. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWEUUw3z1H7kL/d9rAQI18Af+PErZBLD76iIaPitbT2dimCgkTAc1jnxT jYsi85LF2QILdWGvqE3KETzSD8U8zx0Nf0krqU7Lj7WgaVnxdMWR2+kt+HsMdsz8 Px8pywSYQWYOwO/I3ELSouZlBuJgMEga/itT9zklLi/NOXQr0qQ9BACAjbk3HdpU 7Mwdx986sBctD6+R+nOaMCj1gB+FHTVmsdktveG9kViyXTGbHJbRFKmZg25T8bir j1c/V4KzsRIjF0pC9Jcxj66rPLdMWKpQqu9jc7MSSC2bdVxnjerRgMdH4xIj/tqV LUjtDqV35/q48kWj814eQ8Hz4exXQ0js55wUPA4dRegwMyVFx73HpQ== =blfZ -----END PGP SIGNATURE----- From skdovecot at smail.inf.fh-brs.de Mon Dec 5 07:34:52 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 5 Dec 2016 08:34:52 +0100 (CET) Subject: doveadm edit headers? In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 4 Dec 2016, MRob wrote: > Hello, is there a way to edit a message header using doveadm? I guess not. > I see how I can fetch the things I need, but even if I can't edit in place; > if I extract the full message, edit it, there doesn't seem to be a way to > append it back again? check out doveadm import http://wiki2.dovecot.org/Tools/Doveadm/Import it should be easy to fake a maildir or mbox structure. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWEUYnHz1H7kL/d9rAQIefgf/aO5IqfQsI7Xu4Xy6/wzxrMw8aAkDyf3j RNa58av4udtZtNufSA9Im95lt3cTK6cAeRn0ccBTYNwaWKA4L45WDJkrgtfbRjYu ZRlJJ1Z3FvbFtn/89ywgndU3qYo/5lwxPL1IssjX2LrHmg+zPUYR5dwlahWyfp92 UQpHL3z4z714mEc2Qdd9rZS+axSEJIAbYG3Yz1XODxLotnMC2umT9ulKLzxoNcQr 5Ini/XcYH/zlR9/DMAsRxESR77Rj5/5k/ecxO+oY9s1UfZmlrv7UUItIJ2hwv+z6 Ncw+j0KoyDQmhLzxuw1XR5+m3i4F8eRXLJitvDiDR2nwn/BBz1QmkA== =mDfu -----END PGP SIGNATURE----- From aki.tuomi at dovecot.fi Mon Dec 5 07:36:31 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 5 Dec 2016 09:36:31 +0200 Subject: doveadm edit headers? In-Reply-To: References: Message-ID: <41463682-8bf3-5f41-ff95-f5235afc5637@dovecot.fi> On 05.12.2016 09:34, Steffen Kaiser wrote: > On Sun, 4 Dec 2016, MRob wrote: > > > Hello, is there a way to edit a message header using doveadm? > > I guess not. > > > I see how I can fetch the things I need, but even if I can't edit in > place; if I extract the full message, edit it, there doesn't seem to > be a way to append it back again? > > check out doveadm import > http://wiki2.dovecot.org/Tools/Doveadm/Import > > it should be easy to fake a maildir or mbox structure. > > -- Steffen Kaiser Hi! You can edit message in a roundabout way: 1. Use doveadm fetch to retrieve the message 2. Edit the message 3. Use doveadm delete to delete the original message 4. Use doveadm save to save the message You cannot directly edit a message Aki From skdovecot at smail.inf.fh-brs.de Mon Dec 5 07:40:07 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 5 Dec 2016 08:40:07 +0100 (CET) Subject: Virtual mailboxes, please help In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 3 Dec 2016, Peter Hodur wrote: > I'm trying to setup virtual mailboxes. My setup: > > - migrated from Courier, so: > > separator = . > prefix = INBOX. > inbox = yes > > > In doc i have read, thant i need to create separate namespace. > > namespace { prefix = virtual/ separator = / location = > virtual:~/Maildir/virtual > > So i need to change / with . (Dot) in prefix and separator? > > Do i need to append LAYOUT=maildir++ to location? > > Where must location point? To the same directory where mail_location? Or do > i need to create separate hierarchy for virtual mailboxes? Do you mix virtual users with virtual mailboxes? A virtual mailbox displays messages according some search / selection expressions, hence, there is no layout. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWEUZ13z1H7kL/d9rAQKO3wf/VaPNWwPu2cnzTboV6Mj+JFmjDZ9Q4Vqp IgNbLU9XHfb5mEVxoRm9yOJbPdnQqE1o3rh7NRPkP/89uzXQRYzzMIYXV/ozTHo7 DA0KdLm15fri1B+w4DTxa1aX51O/AwNOW8hMgPn0qQC/zsyPVnnmuPh4gn7TTXgH YScYWDftPVoX7MPuKXfo4IYFl6K1PeYy1pi7evFGvhfBVw0HWI+msCvrFSb6c8QE qQ1D91n5u4dO1QK3aZO9JdfEpY1rXMUx79Tx7zxzlKRPo7g2BDRdkfepRj1ke3VN q1/nOLI5jAVQVGAQgVTrCMA8/D5EsX7/ZVd/yieu94Ywznp1xfpo0w== =qOpD -----END PGP SIGNATURE----- From skdovecot at smail.inf.fh-brs.de Mon Dec 5 07:43:34 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 5 Dec 2016 08:43:34 +0100 (CET) Subject: doveadm edit headers? In-Reply-To: <41463682-8bf3-5f41-ff95-f5235afc5637@dovecot.fi> References: <41463682-8bf3-5f41-ff95-f5235afc5637@dovecot.fi> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 5 Dec 2016, Aki Tuomi wrote: > On 05.12.2016 09:34, Steffen Kaiser wrote: >> On Sun, 4 Dec 2016, MRob wrote: >> >>> Hello, is there a way to edit a message header using doveadm? >> >> I guess not. >> >>> I see how I can fetch the things I need, but even if I can't edit in >> place; if I extract the full message, edit it, there doesn't seem to >> be a way to append it back again? >> >> check out doveadm import >> http://wiki2.dovecot.org/Tools/Doveadm/Import >> >> it should be easy to fake a maildir or mbox structure. > 4. Use doveadm save to save the message Oh, "save" is not documented on: http://wiki2.dovecot.org/Tools/Doveadm There seems to be no man page either. :-) - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWEUapnz1H7kL/d9rAQJHKAf9HzgdzqZlNKso7kSxInIMBV/ccS2V07ni XnlKVWVueNjY43DQbOPod3MUXmWu8RZOa5IMFlOCrh42MxjZGLJRkPa7SAxdCVDk RocTifagUNWpvK+j6Hqs3z8tXPikBQ61wS5rFUEAGjFBbk8Ei0YuSV/PyOcrWe04 qy2QDXvOAUwJbfVJfFHv1Zq6MrQy04Qmpqar56nCA/hHo5pIP9LwkHmJEQHYcrio YpVtiwS+6BB6UZXMloluJh6gL4ycWDi92CLoQU8VrS18+rpnu4Vm837QUqzgllPl E+XEauYYHQzQ9AqPQUBreSyuVds4yeouzXl9bryVs4NuG4Fh0BfSAA== =6eXV -----END PGP SIGNATURE----- From m at sys4.de Mon Dec 5 07:53:57 2016 From: m at sys4.de (Marc Schiffbauer) Date: Mon, 5 Dec 2016 08:53:57 +0100 Subject: CVE-2016-8562 in dovecot In-Reply-To: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> Message-ID: <20161205075357.GA27248@schiffbauer.net> * Aki Tuomi schrieb am 02.12.16 um 08:00 Uhr: Hi Aki, > We are sorry to report that we have a bug in dovecot, which merits a > CVE. See details below. If you haven't configured any auth_policy_* > settings you are ok. This is fixed with > https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f34be960cff13a5a725ae > and > https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d57351fd42c67a8612fc > > Important vulnerability in Dovecot (CVE-2016-8562) > CVSS score: 7.4 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H) > Affected version(s): 2.2.25.1 up to 2.2.26.1 > Fixed in: 2.2.27.1rc1 I think either it should read "up to 2.2.27" or "Fixed in: 2.2.27" Or how about version 2.2.27? (without .1) TIA -Marc -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schlei?heimer Stra?e 26/MG, 80333 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From aki.tuomi at dovecot.fi Mon Dec 5 08:02:08 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 5 Dec 2016 10:02:08 +0200 Subject: doveadm edit headers? In-Reply-To: References: <41463682-8bf3-5f41-ff95-f5235afc5637@dovecot.fi> Message-ID: <71892575-8a53-96f1-0965-d8cd40fe4275@dovecot.fi> On 05.12.2016 09:43, Steffen Kaiser wrote: > On Mon, 5 Dec 2016, Aki Tuomi wrote: > > On 05.12.2016 09:34, Steffen Kaiser wrote: > >> On Sun, 4 Dec 2016, MRob wrote: > >> > >>> Hello, is there a way to edit a message header using doveadm? > >> > >> I guess not. > >> > >>> I see how I can fetch the things I need, but even if I can't edit in > >> place; if I extract the full message, edit it, there doesn't seem to > >> be a way to append it back again? > >> > >> check out doveadm import > >> http://wiki2.dovecot.org/Tools/Doveadm/Import > >> > >> it should be easy to fake a maildir or mbox structure. > > > 4. Use doveadm save to save the message > > Oh, "save" is not documented on: > http://wiki2.dovecot.org/Tools/Doveadm > > There seems to be no man page either. > > :-) > > -- Steffen Kaiser So it would seem. Aki From aki.tuomi at dovecot.fi Mon Dec 5 08:48:04 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 5 Dec 2016 10:48:04 +0200 Subject: CVE-2016-8562 in dovecot In-Reply-To: <20161205075357.GA27248@schiffbauer.net> References: <1e5cbafd-cbf1-205d-7de7-475ce8a99c79@dovecot.fi> <20161205075357.GA27248@schiffbauer.net> Message-ID: <34f8f31b-2196-ab2e-53ed-5788dce78d59@dovecot.fi> On 05.12.2016 09:53, Marc Schiffbauer wrote: > * Aki Tuomi schrieb am 02.12.16 um 08:00 Uhr: > > Hi Aki, > >> We are sorry to report that we have a bug in dovecot, which merits a >> CVE. See details below. If you haven't configured any auth_policy_* >> settings you are ok. This is fixed with >> https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f34be960cff13a5a725ae >> and >> https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d57351fd42c67a8612fc >> >> Important vulnerability in Dovecot (CVE-2016-8562) >> CVSS score: 7.4 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H) >> Affected version(s): 2.2.25.1 up to 2.2.26.1 >> Fixed in: 2.2.27.1rc1 > I think either it should read "up to 2.2.27" > or > "Fixed in: 2.2.27" > > Or how about version 2.2.27? (without .1) > > TIA > -Marc > I guess so, we'll take note of this. Aki From secadm2007 at gmail.com Mon Dec 5 08:55:54 2016 From: secadm2007 at gmail.com (GP) Date: Mon, 5 Dec 2016 10:55:54 +0200 Subject: Virtual mailboxes, please help In-Reply-To: References: Message-ID: <85357eaf-c6b4-10e7-876a-414820759b3c@gmail.com> On 12/03/2016 02:19 AM, Peter Hodur wrote: > Hi, > > I'm trying to setup virtual mailboxes. My setup: > > - migrated from Courier, so: > > separator = . > prefix = INBOX. > inbox = yes > > > In doc i have read, thant i need to create separate namespace. > > namespace { prefix = virtual/ separator = / location = > virtual:~/Maildir/virtual Yes you must create a separate namespace like this : namespace { prefix = Somename. separator = . location = virtual:~/Maildir/virtual type = private list = yes } > > So i need to change / with . (Dot) in prefix and separator? The separator must be the same for ALL namespaces , as the documentation states. > > Do i need to append LAYOUT=maildir++ to location? > > Where must location point? To the same directory where mail_location? Or do > i need to create separate hierarchy for virtual mailboxes? This is tricky . I tried to create a virtual folder namespace for use with a public namespace , but got into file system permission trouble. For Individual users works OK , but you will need to administer it, because it's not manageable from a users perspective (it's complicated). George P. > > Thanks for any answer ;) > > Peter ml. From dovecot-ml at seichter.de Mon Dec 5 11:57:45 2016 From: dovecot-ml at seichter.de (Ralph Seichter) Date: Mon, 5 Dec 2016 12:57:45 +0100 Subject: Mail marked read upon download In-Reply-To: References: Message-ID: On 01.12.2016 21:40, Curtis Vaughan wrote: > Just set up a new server with postfix and dovecot. I don't know why, > but as soon as mail is accessed it is marked read. I'll see emails > momentarily marked unread, but then switch to read later although I > haven't opened them. Accessed how? It is usually the MUA that's signalling the IMAP server to mark messages as read, so I suggest you look there first. Postfix (the MTA) has nothing to do with this. -Ralph From mrobti at insiberia.net Mon Dec 5 12:28:11 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 04:28:11 -0800 Subject: imapsieve environment variables missing? Message-ID: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> RFC6785 says imap.user and imap.email environment variables should be made available but I can't access them no matter what I try. Are they not implemented because vnd.dovecot.environment already provides the username? (which does work for me) If imap.user and imap.email are there, can you provide an example how to access them so I can see what I did wrong? From stephan at rename-it.nl Mon Dec 5 12:38:49 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 5 Dec 2016 13:38:49 +0100 Subject: imapsieve environment variables missing? In-Reply-To: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> Message-ID: Op 5-12-2016 om 13:28 schreef MRob: > RFC6785 says imap.user and imap.email environment variables should be > made available but I can't access them no matter what I try. Are they > not implemented because vnd.dovecot.environment already provides the > username? (which does work for me) > > If imap.user and imap.email are there, can you provide an example how > to access them so I can see what I did wrong? That should work. Do you have an example script demonstrating what your trying to do? Regards, Stephan. From stephan at rename-it.nl Mon Dec 5 12:41:29 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 5 Dec 2016 13:41:29 +0100 Subject: imapsieve environment variables missing? In-Reply-To: References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> Message-ID: <8f5b59dd-6f3d-ff38-d629-65fe2bbf7bc9@rename-it.nl> Ugh. s/your/you're/. Op 5-12-2016 om 13:38 schreef Stephan Bosch: > > Op 5-12-2016 om 13:28 schreef MRob: >> RFC6785 says imap.user and imap.email environment variables should be >> made available but I can't access them no matter what I try. Are they >> not implemented because vnd.dovecot.environment already provides the >> username? (which does work for me) >> >> If imap.user and imap.email are there, can you provide an example how >> to access them so I can see what I did wrong? > > That should work. > > Do you have an example script demonstrating what your trying to do? > > Regards, > > Stephan. From mrobti at insiberia.net Mon Dec 5 13:32:16 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 05:32:16 -0800 Subject: imapsieve environment variables missing? In-Reply-To: References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> Message-ID: <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> On 2016-12-05 04:38, Stephan Bosch wrote: > Op 5-12-2016 om 13:28 schreef MRob: >> RFC6785 says imap.user and imap.email environment variables should be >> made available but I can't access them no matter what I try. Are they >> not implemented because vnd.dovecot.environment already provides the >> username? (which does work for me) >> >> If imap.user and imap.email are there, can you provide an example how >> to access them so I can see what I did wrong? > > That should work. > > Do you have an example script demonstrating what your trying to do? Trying to access as a variable: \${imap.user} Also tried: if environment :matches "imap.user" "*" { set "username" "${1}"; } Also tried prefixing with "env." or removing "imap." Result is always empty string (dumped with debug_log) Script is run during COPY operations, newest tarball releases installed for dovecot and pigeonhole. From mrobti at insiberia.net Mon Dec 5 13:36:11 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 05:36:11 -0800 Subject: COPY vs APPEND for imapsieve? Message-ID: <825b7a320bca2a9ca33391d1c4726db5@insiberia.net> The examples on the imapsieve documentation page use COPY but not APPEND to watch messages coming into a folder. Are there not circumstances that a client would APPEND a message to a folder instead of COPY? Is APPEND only used by most clients for adding a sent message to the sent folder? I'm not familiar enough with IMAP clients to know if by leaving off APPEND I am safe or I am at risk to miss some actions I shouldn't. From mrobti at insiberia.net Mon Dec 5 13:40:29 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 05:40:29 -0800 Subject: v2.2.27 released In-Reply-To: <065a39ef-35de-f018-f873-d9d857dc1d1b@rename-it.nl> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> <99bc34c3-8e46-e9c7-2278-e5a4f3c3538d@alex-at.ru> <065a39ef-35de-f018-f873-d9d857dc1d1b@rename-it.nl> Message-ID: On 2016-12-04 12:06, Stephan Bosch wrote: > Op 12/4/2016 om 11:42 AM schreef Alexey Asemov (Alex/AT): >> Thanks a lot for indexing fixes, Dovecot team. >> >> Any news for Pigeonhole? Currently had to rollup some commits from GIT >> to make it pass vacation test set with 2.2.27. >> > > What problem are you seeing? No Pigeonhole release is currently > planned. FWIW, vacation works for me on the newest release. REALLY GREAT fully featured software. Incredible work! From secadm2007 at gmail.com Mon Dec 5 13:42:07 2016 From: secadm2007 at gmail.com (GP) Date: Mon, 5 Dec 2016 15:42:07 +0200 Subject: Virtual mailboxes, please help In-Reply-To: References: Message-ID: <47d8f0f8-6d57-3af8-c952-a0e02e21f037@gmail.com> I didn't see my reply on the list , so I'm fw again direct to you On 12/03/2016 02:19 AM, Peter Hodur wrote: > Hi, > > I'm trying to setup virtual mailboxes. My setup: > > - migrated from Courier, so: > > separator = . > prefix = INBOX. > inbox = yes > > > In doc i have read, thant i need to create separate namespace. > > namespace { prefix = virtual/ separator = / location = > virtual:~/Maildir/virtual Yes you must create a separate namespace like this : namespace { prefix = Somename. separator = . location = virtual:~/Maildir/virtual type = private list = yes } > > So i need to change / with . (Dot) in prefix and separator? The separator must be the same for ALL namespaces , as the documentation states. > > Do i need to append LAYOUT=maildir++ to location? > > Where must location point? To the same directory where mail_location? Or do > i need to create separate hierarchy for virtual mailboxes? This is tricky . I tried to create a virtual folder namespace for use with a public namespace , but got into file system permission trouble. For Individual users works OK , but you will need to administer it, because it's not manageable from a users perspective (it's complicated). George P. > > Thanks for any answer ;) > > Peter ml. From mrobti at insiberia.net Mon Dec 5 13:53:09 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 05:53:09 -0800 Subject: LMTP delivery honours .forward by default? In-Reply-To: References: Message-ID: <5c021203ea62e33738145ae7e648f862@insiberia.net> On 2016-12-04 23:18, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 2 Dec 2016, MRob wrote: > >> I was under the impression that Dovecot does not look at .forward by >> default, since of course, Sieve is where that kind of logic should go. >> However, I'm seeing a .forward file being honoured by the LMTP >> delivery agent. Is this to be expected? > > What version of Dovecot are you using? 2.2.22 > In my installation the MTA handles .forward. Using with postfix connected to dovecot's LMTP for delivery. So what you are saying is that postfix first looks at the .forward in the user's home before handing off to dovecot LMTP? Why would it do such a thing? From mrobti at insiberia.net Mon Dec 5 13:57:44 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 05:57:44 -0800 Subject: doveadm edit headers? In-Reply-To: <71892575-8a53-96f1-0965-d8cd40fe4275@dovecot.fi> References: <41463682-8bf3-5f41-ff95-f5235afc5637@dovecot.fi> <71892575-8a53-96f1-0965-d8cd40fe4275@dovecot.fi> Message-ID: <9268b2bad41d25024e2c1365afd57147@insiberia.net> On 2016-12-05 00:02, Aki Tuomi wrote: > On 05.12.2016 09:43, Steffen Kaiser wrote: >> On Mon, 5 Dec 2016, Aki Tuomi wrote: >> > On 05.12.2016 09:34, Steffen Kaiser wrote: >> >> On Sun, 4 Dec 2016, MRob wrote: >> >> >> >>> Hello, is there a way to edit a message header using doveadm? >> >> >> >> I guess not. >> >> >> >>> I see how I can fetch the things I need, but even if I can't edit in >> >> place; if I extract the full message, edit it, there doesn't seem to >> >> be a way to append it back again? >> >> >> >> check out doveadm import >> >> http://wiki2.dovecot.org/Tools/Doveadm/Import >> >> >> >> it should be easy to fake a maildir or mbox structure. >> >> > 4. Use doveadm save to save the message >> >> Oh, "save" is not documented on: >> http://wiki2.dovecot.org/Tools/Doveadm >> >> There seems to be no man page either. >> >> :-) >> >> -- Steffen Kaiser > > So it would seem. Indeed, as I had scoured all the doc pages I could find. Good thing the mailing list is so helpful! :) From stephan at rename-it.nl Mon Dec 5 14:13:32 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 5 Dec 2016 15:13:32 +0100 Subject: imapsieve environment variables missing? In-Reply-To: <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> Message-ID: <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> Op 5-12-2016 om 14:32 schreef MRob: > On 2016-12-05 04:38, Stephan Bosch wrote: >> Op 5-12-2016 om 13:28 schreef MRob: >>> RFC6785 says imap.user and imap.email environment variables should >>> be made available but I can't access them no matter what I try. Are >>> they not implemented because vnd.dovecot.environment already >>> provides the username? (which does work for me) >>> >>> If imap.user and imap.email are there, can you provide an example >>> how to access them so I can see what I did wrong? >> >> That should work. >> >> Do you have an example script demonstrating what your trying to do? > > Trying to access as a variable: > > \${imap.user} > > Also tried: > > if environment :matches "imap.user" "*" { > set "username" "${1}"; > } > > Also tried prefixing with "env." or removing "imap." > > Result is always empty string (dumped with debug_log) > > Script is run during COPY operations, newest tarball releases > installed for dovecot and pigeonhole. Could you show me your full script? I am mainly interested in the require statements involved. Regards, Stephan. From stephan at rename-it.nl Mon Dec 5 14:16:48 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 5 Dec 2016 15:16:48 +0100 Subject: COPY vs APPEND for imapsieve? In-Reply-To: <825b7a320bca2a9ca33391d1c4726db5@insiberia.net> References: <825b7a320bca2a9ca33391d1c4726db5@insiberia.net> Message-ID: Op 5-12-2016 om 14:36 schreef MRob: > The examples on the imapsieve documentation page use COPY but not > APPEND to watch messages coming into a folder. Are there not > circumstances that a client would APPEND a message to a folder instead > of COPY? Is APPEND only used by most clients for adding a sent message > to the sent folder? I'm not familiar enough with IMAP clients to know > if by leaving off APPEND I am safe or I am at risk to miss some > actions I shouldn't. Depends on the application. E.g., if you're trying to detect messages being moved into the Junk folder, COPY is usually involved. Instead, if you're trying to detect messages being put in the Sent folder, APPEND is usually involved. Regards, Stephan. From mrobti at insiberia.net Mon Dec 5 15:10:19 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 07:10:19 -0800 Subject: imapsieve environment variables missing? In-Reply-To: <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> Message-ID: On 2016-12-05 06:13, Stephan Bosch wrote: > Op 5-12-2016 om 14:32 schreef MRob: >> On 2016-12-05 04:38, Stephan Bosch wrote: >>> Op 5-12-2016 om 13:28 schreef MRob: >>>> RFC6785 says imap.user and imap.email environment variables should >>>> be made available but I can't access them no matter what I try. Are >>>> they not implemented because vnd.dovecot.environment already >>>> provides the username? (which does work for me) >>>> >>>> If imap.user and imap.email are there, can you provide an example >>>> how to access them so I can see what I did wrong? >>> >>> That should work. >>> >>> Do you have an example script demonstrating what your trying to do? >> >> Trying to access as a variable: >> >> \${imap.user} >> >> Also tried: >> >> if environment :matches "imap.user" "*" { >> set "username" "${1}"; >> } >> >> Also tried prefixing with "env." or removing "imap." >> >> Result is always empty string (dumped with debug_log) >> >> Script is run during COPY operations, newest tarball releases >> installed for dovecot and pigeonhole. > > Could you show me your full script? I am mainly interested in the > require statements involved. I don't know how I managed to compile only using direct access of ${imap.user} before since now I get an unknown namespace error on my test script. But doing it this way compiles: require ["environment", "variables", "vnd.dovecot.debug"]; if environment :matches "imap.user" "*" { set "u" "${1}"; } debug_log "Found username: \${u}"; if environment :matches "name" "*" { set "n" "${1}"; } debug_log "Found product name: \${n}"; The output is: DEBUG: Found username: DEBUG: Found product name: Pigeonhole Sieve From stephan at rename-it.nl Mon Dec 5 15:22:21 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 5 Dec 2016 16:22:21 +0100 Subject: imapsieve environment variables missing? In-Reply-To: References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> Message-ID: Op 5-12-2016 om 16:10 schreef MRob: > On 2016-12-05 06:13, Stephan Bosch wrote: >> Op 5-12-2016 om 14:32 schreef MRob: >> >> Could you show me your full script? I am mainly interested in the >> require statements involved. > > I don't know how I managed to compile only using direct access of > ${imap.user} before since now I get an unknown namespace error on my > test script. > > But doing it this way compiles: > > require ["environment", "variables", "vnd.dovecot.debug"]; > > if environment :matches "imap.user" "*" { > set "u" "${1}"; } > debug_log "Found username: \${u}"; > if environment :matches "name" "*" { > set "n" "${1}"; } > debug_log "Found product name: \${n}"; > > The output is: > > DEBUG: Found username: > DEBUG: Found product name: Pigeonhole Sieve - For the "imap.user" environment item, you need to add: require "imapsieve"; This also means that this script will only run from IMAP. - For the "${imap.user}" variable, you need to add: require "vnd.dovecot.environment"; This implicitly requires "environment", so that could be removed. It is all in the specifications. :) Regards, Stephan. From stephan at rename-it.nl Mon Dec 5 15:26:11 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 5 Dec 2016 16:26:11 +0100 Subject: imapsieve environment variables missing? In-Reply-To: References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> Message-ID: <5133e84d-c3e8-8b72-421e-4cd93caca01f@rename-it.nl> Op 5-12-2016 om 16:22 schreef Stephan Bosch: > > > Op 5-12-2016 om 16:10 schreef MRob: >> On 2016-12-05 06:13, Stephan Bosch wrote: >>> Op 5-12-2016 om 14:32 schreef MRob: >>> >>> Could you show me your full script? I am mainly interested in the >>> require statements involved. >> >> I don't know how I managed to compile only using direct access of >> ${imap.user} before since now I get an unknown namespace error on my >> test script. >> >> But doing it this way compiles: >> >> require ["environment", "variables", "vnd.dovecot.debug"]; >> >> if environment :matches "imap.user" "*" { >> set "u" "${1}"; } >> debug_log "Found username: \${u}"; >> if environment :matches "name" "*" { >> set "n" "${1}"; } >> debug_log "Found product name: \${n}"; >> >> The output is: >> >> DEBUG: Found username: >> DEBUG: Found product name: Pigeonhole Sieve > > - For the "imap.user" environment item, you need to add: > > require "imapsieve"; > > This also means that this script will only run from IMAP. > > - For the "${imap.user}" variable, you need to add: Uhm, this should be ${env.imap.user} of course. Regards, Stephan. From lists at alex-at.ru Mon Dec 5 17:42:55 2016 From: lists at alex-at.ru (Alexey Asemov (Alex/AT)) Date: Mon, 5 Dec 2016 20:42:55 +0300 Subject: v2.2.27 released In-Reply-To: <065a39ef-35de-f018-f873-d9d857dc1d1b@rename-it.nl> References: <6117AD0F-7F96-4367-90A0-3DF45452C321@iki.fi> <99bc34c3-8e46-e9c7-2278-e5a4f3c3538d@alex-at.ru> <065a39ef-35de-f018-f873-d9d857dc1d1b@rename-it.nl> Message-ID: <3a56c605-e093-5131-1276-37327fd399ff@alex-at.ru> Hello Stephan, I have double-checked, and indeed I don't see any problems with 2.2.27 even without patches I applied to 2.2.27.rc1. So seems to have been 2.2.27.rc1 related only. Sorry for bothering. From toni at solu.fi Mon Dec 5 18:28:52 2016 From: toni at solu.fi (Toni Mattila) Date: Mon, 5 Dec 2016 20:28:52 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) Message-ID: Hi, Dec 5 20:24:31 dovecot: imap(xx at yy.zz,7ckWZu1CuZFVTILa): Fatal: master: service(imap): child 7292 killed with signal 6 (core dumped) Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Panic: file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x32416f] -> /usr/lib/dovecot/libdovecot.so.0 [0x3241ed] -> /usr/lib/dovecot/libdovecot.so.0 [0x323e0b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map_lookup_seq_range+0xf1) [0x234c61] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x249c2c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_lookup_seq_range+0x2c) [0x24963c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_seq_range+0x3f) [0x1aa39f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_arg_init+0x26f) [0x1997af] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_init+0x6f) [0x19996f] -> dovecot/imap(imap_search_args_build+0x91) [0x8066c91] -> dovecot/imap(cmd_search+0xb9) [0x8058219] -> dovecot/imap(command_exec+0x83) [0x805f2b3] -> dovecot/imap [0x805d28f] -> dovecot/imap [0x805d30a] -> dovecot/imap(client_handle_input+0x45) [0x805d515] -> dovecot/imap(client_input+0x71) [0x805da (gdb) bt #0 0x00635402 in __kernel_vsyscall () #1 0x00949d70 in raise () from /lib/i686/nosegneg/libc.so.6 #2 0x0094b751 in abort () from /lib/i686/nosegneg/libc.so.6 #3 0x00224164 in default_fatal_finish (type=, status=0) at failures.c:201 #4 0x002241ed in i_internal_fatal_handler (ctx=0xbf8627d0, format=0x5b7fac "file %s: line %d (%s): assertion failed: (%s)", args=0xbf8627f4 "?\\") at failures.c:670 #5 0x00223e0b in i_panic (format=0x5b7fac "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 #6 0x00594c61 in mail_index_map_lookup_seq_range (map=0x89afc50, first_uid=0, last_uid=4294967295, first_seq_r=0xbf8628e4, last_seq_r=0xbf8628e0) at mail-index-map.c:550 #7 0x005a9c2c in view_lookup_seq_range (view=0x89af670, first_uid=0, last_uid=4294967295, first_seq_r=0xbf8628e4, last_seq_r=0xbf8628e0) at mail-index-view.c:252 #8 0x005a963c in mail_index_lookup_seq_range (view=0x89af670, first_uid=0, last_uid=4294967295, first_seq_r=0xbf8628e4, last_seq_r=0xbf8628e0) at mail-index-view.c:513 #9 0x0050a39f in mailbox_get_seq_range (box=0x8995418, uid1=0, uid2=4294967295, seq1_r=0xbf8628e4, seq2_r=0xbf8628e0) at mailbox-get.c:11 #10 0x004f97af in mailbox_uidset_change (args=0x89b4d40, arg=0x89b4e10, change_uidsets=true, search_saved_uidset=0x8991e7c) at mail-search.c:45 #11 mail_search_arg_init (args=0x89b4d40, arg=0x89b4e10, change_uidsets=true, search_saved_uidset=0x8991e7c) at mail-search.c:72 #12 0x004f996f in mail_search_args_init (args=0x89b4d40, box=0x8995418, change_uidsets=true, search_saved_uidset=0x8991e7c) at mail-search.c:142 #13 0x08066c91 in imap_search_args_build (cmd=0x8992800, args=0x8995030, charset=0x8070f89 "UTF-8", search_args_r=0xbf862998) at imap-search-args.c:71 #14 0x08058219 in cmd_search (cmd=0x8992800) at cmd-search.c:42 #15 0x0805f2b3 in command_exec (cmd=0x8992800) at imap-commands.c:181 #16 0x0805d28f in client_command_input (cmd=0x8992800) at imap-client.c:986 #17 0x0805d30a in client_command_input (cmd=0x8992800) at imap-client.c:1046 #18 0x0805d515 in client_handle_next_command (client=0x8991db8) at imap-client.c:1088 #19 client_handle_input (client=0x8991db8) at imap-client.c:1100 #20 0x0805dae1 in client_input (client=0x8991db8) at imap-client.c:1147 #21 0x0023aa88 in io_loop_call_io (io=0x8992778) at ioloop.c:599 #22 0x0023c62f in io_loop_handler_run_internal (ioloop=0x8979498) at ioloop-epoll.c:222 #23 0x0023ac0f in io_loop_handler_run (ioloop=0x8979498) at ioloop.c:648 #24 0x0023aef8 in io_loop_run (ioloop=0x8979498) at ioloop.c:623 #25 0x001bb49d in master_service_run (service=0x89793c8, callback=0x806af90 ) at master-service.c:641 #26 0x0806b927 in main (argc=Cannot access memory at address 0x0 ) at main.c:460 (gdb) Panicing stopped when all index files where deleted. Cheers, Toni Mattila From jtam.home at gmail.com Mon Dec 5 19:55:24 2016 From: jtam.home at gmail.com (Joseph Tam) Date: Mon, 5 Dec 2016 11:55:24 -0800 (PST) Subject: v2.2.27 released In-Reply-To: References: Message-ID: Timo announced: > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig > > Note that the download URLs are now https with a certificate from Let's Encrypt. wget complained about ERROR: certificate common name `wiki.dovecot.org' doesn't match requested host name `dovecot.org'. and indeed, the certificate CN and download URL is mismatched. The nice thing about Let's Encrypt is that it's easy to (re)generate the certitcate with SANs to get rid of this mismatch. Browser didn't complain though. Joseph Tam From aki.tuomi at dovecot.fi Mon Dec 5 20:14:05 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 5 Dec 2016 22:14:05 +0200 (EET) Subject: v2.2.27 released In-Reply-To: References: Message-ID: <1692896700.3969.1480968846691@appsuite.open-xchange.com> > On December 5, 2016 at 9:55 PM Joseph Tam wrote: > > > > Timo announced: > > > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz > > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig > > > > Note that the download URLs are now https with a certificate from Let's Encrypt. > > wget complained about > > ERROR: certificate common name `wiki.dovecot.org' doesn't match requested host name `dovecot.org'. > > and indeed, the certificate CN and download URL is mismatched. The nice thing > about Let's Encrypt is that it's easy to (re)generate the certitcate with SANs > to get rid of this mismatch. > > Browser didn't complain though. > > Joseph Tam Despite what wget says the cert does have subject alternate name correctly specified. Try adding cacert dir or file option. I recall wget being "helpful" and reporting this for all cert errors if primary CN and requested name disagree. Aki From jtam.home at gmail.com Mon Dec 5 20:40:18 2016 From: jtam.home at gmail.com (Joseph Tam) Date: Mon, 5 Dec 2016 12:40:18 -0800 (PST) Subject: v2.2.27 released In-Reply-To: <1692896700.3969.1480968846691@appsuite.open-xchange.com> References: <1692896700.3969.1480968846691@appsuite.open-xchange.com> Message-ID: On Mon, 5 Dec 2016, Aki Tuomi wrote: >> >> wget complained about >> >> ERROR: certificate common name `wiki.dovecot.org' doesn't match requested host name `dovecot.org'. >> > > Despite what wget says the cert does have subject alternate name correctly specified. Ah, you're right, "wget" lied to me $ openssl s_client -connect dovecot.org:443 &1 | openssl x509 -noout -text | grep DNS: DNS:dovecot.org, DNS:hg.dovecot.org, DNS:imapwiki.org, DNS:master.wiki.dovecot.org, DNS:master.wiki1.dovecot.org, DNS:master.wiki2.dovecot.org, DNS:pigeonhole.dovecot.nl, DNS:pigeonhole.dovecot.org, DNS:wiki.dovecot.org, DNS:wiki1.dovecot.org, DNS:wiki2.dovecot.org, DNS:www.dovecot.org, DNS:www.imapwiki.org > Try adding cacert dir or file option. I recall wget being "helpful" > and reporting this for all cert errors if primary CN and requested name > disagree. The CN is supposed to be ignored in the presence of SANs. Looks like I need to update wget https://bugzilla.redhat.com/show_bug.cgi?id=903756 Thanks for setting me straight. Joseph Tam From mrobti at insiberia.net Mon Dec 5 21:25:12 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 13:25:12 -0800 Subject: imapsieve environment variables missing? In-Reply-To: References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> Message-ID: On 2016-12-05 07:22, Stephan Bosch wrote: > Op 5-12-2016 om 16:10 schreef MRob: >> On 2016-12-05 06:13, Stephan Bosch wrote: >>> Op 5-12-2016 om 14:32 schreef MRob: >>> >>> Could you show me your full script? I am mainly interested in the >>> require statements involved. >> >> I don't know how I managed to compile only using direct access of >> ${imap.user} before since now I get an unknown namespace error on my >> test script. >> >> But doing it this way compiles: >> >> require ["environment", "variables", "vnd.dovecot.debug"]; >> >> if environment :matches "imap.user" "*" { >> set "u" "${1}"; } >> debug_log "Found username: \${u}"; >> if environment :matches "name" "*" { >> set "n" "${1}"; } >> debug_log "Found product name: \${n}"; >> >> The output is: >> >> DEBUG: Found username: >> DEBUG: Found product name: Pigeonhole Sieve > > - For the "imap.user" environment item, you need to add: > > require "imapsieve"; Hmm, I had tried that and get this: error: require command: unknown Sieve capability `imapsieve' I've already got imapsieve working (per above output, which was triggered by a COPY action) so it clearly is installed and configured. > This also means that this script will only run from IMAP. Seems as though it won't compile outside of IMAP either :) > - For the "${imap.user}" variable, you need to add: > > require "vnd.dovecot.environment"; > > This implicitly requires "environment", so that could be removed. > > It is all in the specifications. :) You're saying that to access the new imap. namespace vars for imapsieve that vnd.dovecot.environment is required? I don't find anything in the specifications that say this. The RFC says those vars MUST be made available, so presumably it would be referring to the RFC-standard environment extension and not some vendor specific one. Of course it's easy to work with that if this is how it's been built, but as noted above I can't get it to compile anyway. Though what's the point of trying to figure out imap.user or imap.email if I'm required to use vnd.dovecot.environment which already has "username"? :) From stephan at rename-it.nl Mon Dec 5 21:42:33 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 5 Dec 2016 22:42:33 +0100 Subject: imapsieve environment variables missing? In-Reply-To: References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> Message-ID: Op 12/5/2016 om 10:25 PM schreef MRob: > On 2016-12-05 07:22, Stephan Bosch wrote: >> Op 5-12-2016 om 16:10 schreef MRob: >>> On 2016-12-05 06:13, Stephan Bosch wrote: >>>> Op 5-12-2016 om 14:32 schreef MRob: >>>> >>>> Could you show me your full script? I am mainly interested in the >>>> require statements involved. >>> >>> I don't know how I managed to compile only using direct access of >>> ${imap.user} before since now I get an unknown namespace error on my >>> test script. >>> >>> But doing it this way compiles: >>> >>> require ["environment", "variables", "vnd.dovecot.debug"]; >>> >>> if environment :matches "imap.user" "*" { >>> set "u" "${1}"; } >>> debug_log "Found username: \${u}"; >>> if environment :matches "name" "*" { >>> set "n" "${1}"; } >>> debug_log "Found product name: \${n}"; >>> >>> The output is: >>> >>> DEBUG: Found username: >>> DEBUG: Found product name: Pigeonhole Sieve >> >> - For the "imap.user" environment item, you need to add: >> >> require "imapsieve"; > > Hmm, I had tried that and get this: > > error: require command: unknown Sieve capability `imapsieve' > > I've already got imapsieve working (per above output, which was > triggered by a COPY action) so it clearly is installed and configured. > >> This also means that this script will only run from IMAP. > > Seems as though it won't compile outside of IMAP either :) Not if you're not using the sieve_imapsieve plugin for the Sieve interpreter (sieve_plugins = sieve_imapsieve). > - For the "${imap.user}" variable, you need to add: >> >> require "vnd.dovecot.environment"; >> >> This implicitly requires "environment", so that could be removed. >> >> It is all in the specifications. :) > > You're saying that to access the new imap. namespace vars for > imapsieve that vnd.dovecot.environment is required? I don't find > anything in the specifications that say this. > > The RFC says those vars MUST be made available, so presumably it would > be referring to the RFC-standard environment extension and not some > vendor specific one. > > Of course it's easy to work with that if this is how it's been built, > but as noted above I can't get it to compile anyway. Though what's the > point of trying to figure out imap.user or imap.email if I'm required > to use vnd.dovecot.environment which already has "username"? :) The standard "environment" extension [1] does not register a variables namespace [2] for environment items. So, using a "${env.imap.user}" variable requires the Dovecot-specific "vnd.dovecot.environment" extension [3]. In contrast, the normal alternative for this variable using the "imap.user" environment item will work once the "imapsieve" extension [4] is require'd. That is a bit cumbersome though, since you need to put that in a variable with a statement like: if environment :matches "imap.user" "*" { set "imap_user" "${1}"; }. The standard [1] provides no alternative. Relevant specifications: [1] http://tools.ietf.org/html/rfc5183/ [2] http://tools.ietf.org/html/rfc5229/ [3] https://raw.githubusercontent.com/dovecot/pigeonhole/master/doc/rfc/spec-bosch-sieve-dovecot-environment.txt [4] https://tools.ietf.org/html/rfc6785 Regards, Stephan. From mrobti at insiberia.net Mon Dec 5 23:23:03 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 15:23:03 -0800 Subject: imapsieve environment variables missing? In-Reply-To: References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> Message-ID: <10383295c1895ab75b8ae400c5b0b15c@insiberia.net> >>>> I don't know how I managed to compile only using direct access of >>>> ${imap.user} before since now I get an unknown namespace error on my >>>> test script. >>>> >>>> But doing it this way compiles: >>>> >>>> require ["environment", "variables", "vnd.dovecot.debug"]; >>>> >>>> if environment :matches "imap.user" "*" { >>>> set "u" "${1}"; } >>>> debug_log "Found username: \${u}"; >>>> if environment :matches "name" "*" { >>>> set "n" "${1}"; } >>>> debug_log "Found product name: \${n}"; >>>> >>>> The output is: >>>> >>>> DEBUG: Found username: >>>> DEBUG: Found product name: Pigeonhole Sieve >>> >>> - For the "imap.user" environment item, you need to add: >>> >>> require "imapsieve"; >> >> Hmm, I had tried that and get this: >> >> error: require command: unknown Sieve capability `imapsieve' >> >> I've already got imapsieve working (per above output, which was >> triggered by a COPY action) so it clearly is installed and configured. >> >>> This also means that this script will only run from IMAP. >> >> Seems as though it won't compile outside of IMAP either :) > > Not if you're not using the sieve_imapsieve plugin for the Sieve > interpreter (sieve_plugins = sieve_imapsieve). Forgive me, but what other way is there to set it up? Is there any way to successfully compile a script with a require of "imapsieve" from the command line? >> - For the "${imap.user}" variable, you need to add: >>> >>> require "vnd.dovecot.environment"; >>> >>> This implicitly requires "environment", so that could be removed. >>> >>> It is all in the specifications. :) >> >> You're saying that to access the new imap. namespace vars for >> imapsieve that vnd.dovecot.environment is required? I don't find >> anything in the specifications that say this. >> >> The RFC says those vars MUST be made available, so presumably it would >> be referring to the RFC-standard environment extension and not some >> vendor specific one. >> >> Of course it's easy to work with that if this is how it's been built, >> but as noted above I can't get it to compile anyway. Though what's the >> point of trying to figure out imap.user or imap.email if I'm required >> to use vnd.dovecot.environment which already has "username"? :) > > The standard "environment" extension [1] does not register a variables > namespace [2] for environment items. So, using a "${env.imap.user}" > variable requires the Dovecot-specific "vnd.dovecot.environment" > extension [3]. But this doesn't work: require ["environment", "variables", "vnd.dovecot.debug", "vnd.dovecot.environment"]; debug_log "Username: ${env.imap.user}"; Output when running from a COPY event is: DEBUG: Username: What did I do wrong here? > In contrast, the normal alternative for this variable > using the "imap.user" environment item will work once the "imapsieve" > extension [4] is require'd. That is a bit cumbersome though, since you > need to put that in a variable with a statement like: if environment > :matches "imap.user" "*" { set "imap_user" "${1}"; }. I don't see that being too cumbersome, as it's the standard way the environment extension is used, and it's what I expect from reading the RFC. But I understand your point that it's more lengthy than just accessing the variable directly. So the only issue I see is that the script won't compile on the CLI with the needed require. Is it simply a requirement to have Sieve do run-time compilation for this to work? From stephan at rename-it.nl Mon Dec 5 23:26:22 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Tue, 6 Dec 2016 00:26:22 +0100 Subject: imapsieve environment variables missing? In-Reply-To: <10383295c1895ab75b8ae400c5b0b15c@insiberia.net> References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> <10383295c1895ab75b8ae400c5b0b15c@insiberia.net> Message-ID: <9c4e1ff9-4a1b-e753-a86f-b81bca7d4491@rename-it.nl> Op 12/6/2016 om 12:23 AM schreef MRob: >>>>> I don't know how I managed to compile only using direct access of >>>>> ${imap.user} before since now I get an unknown namespace error on my >>>>> test script. >>>>> >>>>> But doing it this way compiles: >>>>> >>>>> require ["environment", "variables", "vnd.dovecot.debug"]; >>>>> >>>>> if environment :matches "imap.user" "*" { >>>>> set "u" "${1}"; } >>>>> debug_log "Found username: \${u}"; >>>>> if environment :matches "name" "*" { >>>>> set "n" "${1}"; } >>>>> debug_log "Found product name: \${n}"; >>>>> >>>>> The output is: >>>>> >>>>> DEBUG: Found username: >>>>> DEBUG: Found product name: Pigeonhole Sieve >>>> >>>> - For the "imap.user" environment item, you need to add: >>>> >>>> require "imapsieve"; >>> >>> Hmm, I had tried that and get this: >>> >>> error: require command: unknown Sieve capability `imapsieve' >>> >>> I've already got imapsieve working (per above output, which was >>> triggered by a COPY action) so it clearly is installed and configured. >>> >>>> This also means that this script will only run from IMAP. >>> >>> Seems as though it won't compile outside of IMAP either :) >> >> Not if you're not using the sieve_imapsieve plugin for the Sieve >> interpreter (sieve_plugins = sieve_imapsieve). > > Forgive me, but what other way is there to set it up? Is there any way > to successfully compile a script with a require of "imapsieve" from > the command line? I mean that adding "sieve_imapsieve" to sieve_plugins should fix it for you: plugin { sieve_plugins = sieve_imapsieve } Regards, Stephan. From michael.slusarz at dovecot.fi Mon Dec 5 23:27:24 2016 From: michael.slusarz at dovecot.fi (Michael Slusarz) Date: Mon, 5 Dec 2016 16:27:24 -0700 Subject: Simple way to get mailbox size by folder. In-Reply-To: <2101756398.3143.1480802022598@appsuite-dev.open-xchange.com> References: <2101756398.3143.1480802022598@appsuite-dev.open-xchange.com> Message-ID: On 12/3/2016 2:53 PM, Aki Tuomi wrote: > >> On December 3, 2016 at 11:16 PM Vijay Sarvepalli wrote: >> >> >> Is there a simple way to get each mailbox size using dovecot's IMAP >> interface? The GETQUOTAROOT and GETQUOTA seems to work with the full >> maildir size and not the individual folders. >> >> I am finding a simple way for the webmail client to show usage of each >> folder. >> >> Thanks >> Vijay > > $ doveadm mailbox status -u cmouse all INBOX > INBOX messages=9206 recent=0 uidnext=33115 uidvalidity=1451655531 unseen=7 highestmodseq=39954 vsize=538582181 guid=d595a62d65818656f72c000074be03de > > $ doveadm -fjson mailbox status -u cmouse at cmouse.fi all INBOX > [{"mailbox":"INBOX","messages":"9206","recent":"0","uidnext":"33115","uidvalidity":"1451655531","unseen":"7","highestmodseq":"39954","vsize":"538582181","guid":"d595a62d65818656f72c000074be03de"}] If you want an IMAP specific method (rather than doveadm), you are stuck with "FETCH 1:* (RFC822.SIZE)". With the nasty requirement - if you want 100% full accuracy - that you need to track responses to ensure that each size is only counted once. Practically speaking this shouldn't happen by any reasonable server, but the warning needs to be made. michael From mrobti at insiberia.net Mon Dec 5 23:29:32 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 15:29:32 -0800 Subject: imapsieve environment variables missing? In-Reply-To: <9c4e1ff9-4a1b-e753-a86f-b81bca7d4491@rename-it.nl> References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> <10383295c1895ab75b8ae400c5b0b15c@insiberia.net> <9c4e1ff9-4a1b-e753-a86f-b81bca7d4491@rename-it.nl> Message-ID: <67db16d6855afdd4024e0d52e43120fc@insiberia.net> On 2016-12-05 15:26, Stephan Bosch wrote: > Op 12/6/2016 om 12:23 AM schreef MRob: >>>>>> I don't know how I managed to compile only using direct access of >>>>>> ${imap.user} before since now I get an unknown namespace error on >>>>>> my >>>>>> test script. >>>>>> >>>>>> But doing it this way compiles: >>>>>> >>>>>> require ["environment", "variables", "vnd.dovecot.debug"]; >>>>>> >>>>>> if environment :matches "imap.user" "*" { >>>>>> set "u" "${1}"; } >>>>>> debug_log "Found username: \${u}"; >>>>>> if environment :matches "name" "*" { >>>>>> set "n" "${1}"; } >>>>>> debug_log "Found product name: \${n}"; >>>>>> >>>>>> The output is: >>>>>> >>>>>> DEBUG: Found username: >>>>>> DEBUG: Found product name: Pigeonhole Sieve >>>>> >>>>> - For the "imap.user" environment item, you need to add: >>>>> >>>>> require "imapsieve"; >>>> >>>> Hmm, I had tried that and get this: >>>> >>>> error: require command: unknown Sieve capability `imapsieve' >>>> >>>> I've already got imapsieve working (per above output, which was >>>> triggered by a COPY action) so it clearly is installed and >>>> configured. >>>> >>>>> This also means that this script will only run from IMAP. >>>> >>>> Seems as though it won't compile outside of IMAP either :) >>> >>> Not if you're not using the sieve_imapsieve plugin for the Sieve >>> interpreter (sieve_plugins = sieve_imapsieve). >> >> Forgive me, but what other way is there to set it up? Is there any way >> to successfully compile a script with a require of "imapsieve" from >> the command line? > > I mean that adding "sieve_imapsieve" to sieve_plugins should fix it for > you: > > plugin { > sieve_plugins = sieve_imapsieve > } Darn, botched configuration settings. I apologize for the unnecessary thread. From mrobti at insiberia.net Mon Dec 5 23:38:39 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 15:38:39 -0800 Subject: imapsieve environment variables missing? In-Reply-To: <67db16d6855afdd4024e0d52e43120fc@insiberia.net> References: <96f0022a69c9a3cbda5a8e32f65aeb73@insiberia.net> <6da35d98e0a5f0b5a338db806604cda1@insiberia.net> <1d8f9e1f-38e1-5549-22d1-5546bd3cc3ec@rename-it.nl> <10383295c1895ab75b8ae400c5b0b15c@insiberia.net> <9c4e1ff9-4a1b-e753-a86f-b81bca7d4491@rename-it.nl> <67db16d6855afdd4024e0d52e43120fc@insiberia.net> Message-ID: <320d4dc00b10fb852674843b3a2b2f0b@insiberia.net> On 2016-12-05 15:29, MRob wrote: > On 2016-12-05 15:26, Stephan Bosch wrote: >> Op 12/6/2016 om 12:23 AM schreef MRob: >>>>>>> I don't know how I managed to compile only using direct access of >>>>>>> ${imap.user} before since now I get an unknown namespace error on >>>>>>> my >>>>>>> test script. >>>>>>> >>>>>>> But doing it this way compiles: >>>>>>> >>>>>>> require ["environment", "variables", "vnd.dovecot.debug"]; >>>>>>> >>>>>>> if environment :matches "imap.user" "*" { >>>>>>> set "u" "${1}"; } >>>>>>> debug_log "Found username: \${u}"; >>>>>>> if environment :matches "name" "*" { >>>>>>> set "n" "${1}"; } >>>>>>> debug_log "Found product name: \${n}"; >>>>>>> >>>>>>> The output is: >>>>>>> >>>>>>> DEBUG: Found username: >>>>>>> DEBUG: Found product name: Pigeonhole Sieve >>>>>> >>>>>> - For the "imap.user" environment item, you need to add: >>>>>> >>>>>> require "imapsieve"; >>>>> >>>>> Hmm, I had tried that and get this: >>>>> >>>>> error: require command: unknown Sieve capability `imapsieve' >>>>> >>>>> I've already got imapsieve working (per above output, which was >>>>> triggered by a COPY action) so it clearly is installed and >>>>> configured. >>>>> >>>>>> This also means that this script will only run from IMAP. >>>>> >>>>> Seems as though it won't compile outside of IMAP either :) >>>> >>>> Not if you're not using the sieve_imapsieve plugin for the Sieve >>>> interpreter (sieve_plugins = sieve_imapsieve). >>> >>> Forgive me, but what other way is there to set it up? Is there any >>> way >>> to successfully compile a script with a require of "imapsieve" from >>> the command line? >> >> I mean that adding "sieve_imapsieve" to sieve_plugins should fix it >> for you: >> >> plugin { >> sieve_plugins = sieve_imapsieve >> } > > Darn, botched configuration settings. I apologize for the unnecessary > thread. What a supreme waste of your time. I'm sorry this probably happens to you all the time. I had had this set up but for various reasons, commented it out temporarily. When I put it back, the software works as advertised - little surprise. Can't say enough how much the software and support is appreciated. From mrobti at insiberia.net Tue Dec 6 00:05:54 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 16:05:54 -0800 Subject: COPY vs APPEND for imapsieve? In-Reply-To: References: <825b7a320bca2a9ca33391d1c4726db5@insiberia.net> Message-ID: <71d3b91b2385f3eecb0fc8b702acc84a@insiberia.net> On 2016-12-05 06:16, Stephan Bosch wrote: > Op 5-12-2016 om 14:36 schreef MRob: >> The examples on the imapsieve documentation page use COPY but not >> APPEND to watch messages coming into a folder. Are there not >> circumstances that a client would APPEND a message to a folder instead >> of COPY? Is APPEND only used by most clients for adding a sent message >> to the sent folder? I'm not familiar enough with IMAP clients to know >> if by leaving off APPEND I am safe or I am at risk to miss some >> actions I shouldn't. > > Depends on the application. E.g., if you're trying to detect messages > being moved into the Junk folder, COPY is usually involved. Instead, > if you're trying to detect messages being put in the Sent folder, > APPEND is usually involved. So it shouldn't hurt to add APPEND in an example as on the documentation page right? However I believe you would only add it to the first "mailbox1" whereas adding the APPEND cause to "mailbox2" should not be correct, because it is impossible to APPEND from one folder to another? From mrobti at insiberia.net Tue Dec 6 00:37:42 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 16:37:42 -0800 Subject: LMTP delivery honours .forward by default? In-Reply-To: <5c021203ea62e33738145ae7e648f862@insiberia.net> References: <5c021203ea62e33738145ae7e648f862@insiberia.net> Message-ID: <4d826791856ae1a1f803a506688a6c79@insiberia.net> On 2016-12-05 05:53, MRob wrote: > On 2016-12-04 23:18, Steffen Kaiser wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Fri, 2 Dec 2016, MRob wrote: >> >>> I was under the impression that Dovecot does not look at .forward by >>> default, since of course, Sieve is where that kind of logic should >>> go. However, I'm seeing a .forward file being honoured by the LMTP >>> delivery agent. Is this to be expected? >> >> What version of Dovecot are you using? > > 2.2.22 > >> In my installation the MTA handles .forward. > > Using with postfix connected to dovecot's LMTP for delivery. So what > you are saying is that postfix first looks at the .forward in the > user's home before handing off to dovecot LMTP? Why would it do such a > thing? After asking on the postfix list, I learned that postfix only inspects .forward if you use the postfix local delivery agent. So Dovecot LMTP is doing this - when and why? It's not unwelcome, but I'd like to know how it is configured. From mrobti at insiberia.net Tue Dec 6 01:56:30 2016 From: mrobti at insiberia.net (MRob) Date: Mon, 05 Dec 2016 17:56:30 -0800 Subject: LMTP delivery honours .forward by default? In-Reply-To: <4d826791856ae1a1f803a506688a6c79@insiberia.net> References: <5c021203ea62e33738145ae7e648f862@insiberia.net> <4d826791856ae1a1f803a506688a6c79@insiberia.net> Message-ID: On 2016-12-05 16:37, MRob wrote: > On 2016-12-05 05:53, MRob wrote: >> On 2016-12-04 23:18, Steffen Kaiser wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Fri, 2 Dec 2016, MRob wrote: >>> >>>> I was under the impression that Dovecot does not look at .forward by >>>> default, since of course, Sieve is where that kind of logic should >>>> go. However, I'm seeing a .forward file being honoured by the LMTP >>>> delivery agent. Is this to be expected? >>> >>> What version of Dovecot are you using? >> >> 2.2.22 >> >>> In my installation the MTA handles .forward. >> >> Using with postfix connected to dovecot's LMTP for delivery. So what >> you are saying is that postfix first looks at the .forward in the >> user's home before handing off to dovecot LMTP? Why would it do such a >> thing? > > > After asking on the postfix list, I learned that postfix only inspects > .forward if you use the postfix local delivery agent. > > So Dovecot LMTP is doing this - when and why? It's not unwelcome, but > I'd like to know how it is configured. Never mind. Turns out this IS postfix after all. From skdovecot at smail.inf.fh-brs.de Tue Dec 6 07:25:09 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 6 Dec 2016 08:25:09 +0100 (CET) Subject: LMTP delivery honours .forward by default? In-Reply-To: References: <5c021203ea62e33738145ae7e648f862@insiberia.net> <4d826791856ae1a1f803a506688a6c79@insiberia.net> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 5 Dec 2016, MRob wrote: > On 2016-12-05 16:37, MRob wrote: >> On 2016-12-05 05:53, MRob wrote: >>> On 2016-12-04 23:18, Steffen Kaiser wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> On Fri, 2 Dec 2016, MRob wrote: >>>> >>>>> I was under the impression that Dovecot does not look at .forward by >>>>> default, since of course, Sieve is where that kind of logic should go. >>>>> However, I'm seeing a .forward file being honoured by the LMTP delivery >>>>> agent. Is this to be expected? >>>> >>>> What version of Dovecot are you using? >>> >>> 2.2.22 >>> >>>> In my installation the MTA handles .forward. >>> >>> Using with postfix connected to dovecot's LMTP for delivery. So what >>> you are saying is that postfix first looks at the .forward in the >>> user's home before handing off to dovecot LMTP? Why would it do such a >>> thing? The why: ".forward" is a way to let an user specify a forward address, IMHO, it origins from the times, when sendmail delivered the messages to mailboxes in the user's home and when users could manage the mail flow from their home directory as well. Maybe just to redirect local deliveries to somewhere else. > Never mind. Turns out this IS postfix after all. fine you found it. :) - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWEZn1Xz1H7kL/d9rAQL9tQgAgBOgK7oM8Ay2f0DdNpKrgRr3CLELRHva hTuiYHWWXB44uK4+04tMUP1TuiJUFknO6r7MiNHVNR6CFDEUrlrQAjzaCSOk9nkP EWX14gyMthxe8JsLkpFFK8ORvdsbMsrfMYIl7fHGFPD/cVlmZd18Hx6ZjXHU1SXD 5dsI2YVX8kE8A+W3VkIpiee9/B+FKgYrxL+Yq0E2OxEMcPxappkNxDD1MHw/Mb7I v17eB0yXlePH7Ka7d09iYVpgYMZgSu7of0wNKgXeDHQCrIbmD/TYkEl3E9DiI6g8 b386j02f7ay9kWVA8ObM+dTGAKsFMyHcFYbWSswaVNw6wmwqj+UdMQ== =JSVy -----END PGP SIGNATURE----- From toni at solu.fi Tue Dec 6 07:32:15 2016 From: toni at solu.fi (Toni Mattila) Date: Tue, 6 Dec 2016 09:32:15 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) In-Reply-To: References: Message-ID: Hi, On 05-Dec-16 20:28, Toni Mattila wrote: > Panicing stopped when all index files where deleted. It happens again in same user account, so rebuilding indexes didn't fix it. Here's bt full instead of just bt: #0 0x001d4402 in __kernel_vsyscall () No symbol table info available. #1 0x00949d70 in raise () from /lib/i686/nosegneg/libc.so.6 No symbol table info available. #2 0x0094b751 in abort () from /lib/i686/nosegneg/libc.so.6 No symbol table info available. #3 0x003b7164 in default_fatal_finish (type=, status=0) at failures.c:201 backtrace = 0x85c0268 "/usr/lib/dovecot/libdovecot.so.0 [0x3b716f] -> /usr/lib/dovecot/libdovecot.so.0 [0x3b71ed] -> /usr/lib/dovecot/libdovecot.so.0 [0x3b6e0b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map_loo"... #4 0x003b71ed in i_internal_fatal_handler (ctx=0xbfe82a50, format=0x527fac "file %s: line %d (%s): assertion failed: (%s)", args=0xbfe82a74 "?S") at failures.c:670 status = 0 #5 0x003b6e0b in i_panic (format=0x527fac "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0, timestamp_usecs = 0} args = 0xbfe82a74 "?S" #6 0x00504c61 in mail_index_map_lookup_seq_range (map=0x85ffe18, first_uid=0, last_uid=4294967295, first_seq_r=0xbfe82b64, last_seq_r=0xbfe82b60) at mail-index-map.c:550 __FUNCTION__ = "mail_index_map_lookup_seq_range" #7 0x00519c2c in view_lookup_seq_range (view=0x85ffd50, first_uid=0, last_uid=4294967295, first_seq_r=0xbfe82b64, last_seq_r=0xbfe82b60) at mail-index-view.c:252 No locals. #8 0x0051963c in mail_index_lookup_seq_range (view=0x85ffd50, first_uid=0, last_uid=4294967295, first_seq_r=0xbfe82b64, last_seq_r=0xbfe82b60) at mail-index-view.c:513 No locals. #9 0x0047a39f in mailbox_get_seq_range (box=0x85e4418, uid1=0, uid2=4294967295, seq1_r=0xbfe82b64, seq2_r=0xbfe82b60) at mailbox-get.c:11 No locals. #10 0x004697af in mailbox_uidset_change (args=0x8602500, arg=0x86025d0, change_uidsets=true, search_saved_uidset=0x85e0e7c) at mail-search.c:45 i = 1 seq1 = 1 seq2 = 78 #11 mail_search_arg_init (args=0x8602500, arg=0x86025d0, change_uidsets=true, search_saved_uidset=0x85e0e7c) at mail-search.c:72 _data_stack_cur_id = 4 thread_args = keywords = {0xbfe82b78 "?+?o\231F", 0x46b936 "\204?u?\211?\204?u?\203?\020^_]?\213E\b\211?\213P\b\213@\f?\004$\001"} __FUNCTION__ = "mail_search_arg_init" #12 0x0046996f in mail_search_args_init (args=0x8602500, box=0x85e4418, change_uidsets=true, search_saved_uidset=0x85e0e7c) at mail-search.c:142 __FUNCTION__ = "mail_search_args_init" #13 0x08066c91 in imap_search_args_build (cmd=0x85e1800, args=0x85e4030, charset=0x8070f89 "UTF-8", search_args_r=0xbfe82c18) at imap-search-args.c:71 parser = 0x0 sargs = 0x8602500 error = ret = 0 #14 0x08058219 in cmd_search (cmd=0x85e1800) at cmd-search.c:42 ctx = 0x85e18e8 sargs = args = 0x85e4030 charset = 0x8070f89 "UTF-8" ret = #15 0x0805f2b3 in command_exec (cmd=0x85e1800) at imap-commands.c:181 hook = 0x85c89b0 finished = cmd_start_timeval = {tv_sec = 1481007511, tv_usec = 140244} cmd_start_bytes_in = 29 cmd_start_bytes_out = 712 cmd_start_lock_waits = 0 __FUNCTION__ = "command_exec" #16 0x0805d28f in client_command_input (cmd=0x85e1800) at imap-client.c:986 ---Type to continue, or q to quit--- client = 0x85e0db8 command = __FUNCTION__ = "client_command_input" #17 0x0805d30a in client_command_input (cmd=0x85e1800) at imap-client.c:1046 client = 0x85e0db8 command = 0x701e __FUNCTION__ = "client_command_input" #18 0x0805d515 in client_handle_next_command (client=0x85e0db8) at imap-client.c:1088 No locals. #19 client_handle_input (client=0x85e0db8) at imap-client.c:1100 _data_stack_cur_id = 3 remove_io = handled_commands = false __FUNCTION__ = "client_handle_input" #20 0x0805dae1 in client_input (client=0x85e0db8) at imap-client.c:1147 cmd = output = 0x85e16f8 bytes = 31 __FUNCTION__ = "client_input" #21 0x003cda88 in io_loop_call_io (io=0x85e1778) at ioloop.c:599 ioloop = 0x85c8498 t_id = 2 __FUNCTION__ = "io_loop_call_io" #22 0x003cf62f in io_loop_handler_run_internal (ioloop=0x85c8498) at ioloop-epoll.c:222 ctx = event = 0x85ca230 list = 0x85cab10 io = 0x6 tv = {tv_sec = 1799, tv_usec = 999295} msecs = 1800000 ret = 1 i = 0 j = 0 call = false __FUNCTION__ = "io_loop_handler_run_internal" #23 0x003cdc0f in io_loop_handler_run (ioloop=0x85c8498) at ioloop.c:648 No locals. #24 0x003cdef8 in io_loop_run (ioloop=0x85c8498) at ioloop.c:623 __FUNCTION__ = "io_loop_run" #25 0x0034e49d in master_service_run (service=0x85c83c8, callback=0x806af90 ) at master-service.c:641 No locals. #26 0x0806b927 in main (argc=Cannot access memory at address 0x0 ) at main.c:460 login_set = {auth_socket_path = 0x85c0038 "P", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x806b320 , failure_callback = 0x806b030 , request_auth_token = 1} service_flags = storage_service_flags = 4097 username = 0x0 auth_socket_path = 0x8074c39 "auth-master" c = set_roots = {0x8073e80, 0x807b220, 0x0} Cheers, Toni Mattila From aki.tuomi at dovecot.fi Tue Dec 6 08:00:37 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Tue, 6 Dec 2016 10:00:37 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) In-Reply-To: References: Message-ID: On 06.12.2016 09:32, Toni Mattila wrote: > Hi, > > On 05-Dec-16 20:28, Toni Mattila wrote: >> Panicing stopped when all index files where deleted. > > It happens again in same user account, so rebuilding indexes didn't > fix it. > > Here's bt full instead of just bt: > #0 0x001d4402 in __kernel_vsyscall () > No symbol table info available. > #1 0x00949d70 in raise () from /lib/i686/nosegneg/libc.so.6 > No symbol table info available. > #2 0x0094b751 in abort () from /lib/i686/nosegneg/libc.so.6 > No symbol table info available. > #3 0x003b7164 in default_fatal_finish (type=, > status=0) at failures.c:201 > backtrace = 0x85c0268 "/usr/lib/dovecot/libdovecot.so.0 > [0x3b716f] -> /usr/lib/dovecot/libdovecot.so.0 [0x3b71ed] -> > /usr/lib/dovecot/libdovecot.so.0 [0x3b6e0b] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map_loo"... > #4 0x003b71ed in i_internal_fatal_handler (ctx=0xbfe82a50, > format=0x527fac "file %s: line %d (%s): assertion failed: (%s)", > args=0xbfe82a74 "?S") at failures.c:670 > status = 0 > #5 0x003b6e0b in i_panic (format=0x527fac "file %s: line %d (%s): > assertion failed: (%s)") at failures.c:275 > ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = > 0x0, timestamp_usecs = 0} > args = 0xbfe82a74 "?S" > #6 0x00504c61 in mail_index_map_lookup_seq_range (map=0x85ffe18, > first_uid=0, last_uid=4294967295, first_seq_r=0xbfe82b64, > last_seq_r=0xbfe82b60) at mail-index-map.c:550 > __FUNCTION__ = "mail_index_map_lookup_seq_range" > #7 0x00519c2c in view_lookup_seq_range (view=0x85ffd50, first_uid=0, > last_uid=4294967295, first_seq_r=0xbfe82b64, last_seq_r=0xbfe82b60) at > mail-index-view.c:252 > No locals. > #8 0x0051963c in mail_index_lookup_seq_range (view=0x85ffd50, > first_uid=0, last_uid=4294967295, first_seq_r=0xbfe82b64, > last_seq_r=0xbfe82b60) at mail-index-view.c:513 > No locals. > #9 0x0047a39f in mailbox_get_seq_range (box=0x85e4418, uid1=0, > uid2=4294967295, seq1_r=0xbfe82b64, seq2_r=0xbfe82b60) at > mailbox-get.c:11 > No locals. > #10 0x004697af in mailbox_uidset_change (args=0x8602500, > arg=0x86025d0, change_uidsets=true, search_saved_uidset=0x85e0e7c) at > mail-search.c:45 > i = 1 > seq1 = 1 > seq2 = 78 > #11 mail_search_arg_init (args=0x8602500, arg=0x86025d0, > change_uidsets=true, search_saved_uidset=0x85e0e7c) at mail-search.c:72 > _data_stack_cur_id = 4 > thread_args = > keywords = {0xbfe82b78 "?+?o\231F", 0x46b936 > "\204?u?\211?\204?u?\203?\020^_]?\213E\b\211?\213P\b\213@\f?\004$\001"} > __FUNCTION__ = "mail_search_arg_init" > #12 0x0046996f in mail_search_args_init (args=0x8602500, > box=0x85e4418, change_uidsets=true, search_saved_uidset=0x85e0e7c) at > mail-search.c:142 > __FUNCTION__ = "mail_search_args_init" > #13 0x08066c91 in imap_search_args_build (cmd=0x85e1800, > args=0x85e4030, charset=0x8070f89 "UTF-8", search_args_r=0xbfe82c18) > at imap-search-args.c:71 > parser = 0x0 > sargs = 0x8602500 > error = > ret = 0 > #14 0x08058219 in cmd_search (cmd=0x85e1800) at cmd-search.c:42 > ctx = 0x85e18e8 > sargs = > args = 0x85e4030 > charset = 0x8070f89 "UTF-8" > ret = > #15 0x0805f2b3 in command_exec (cmd=0x85e1800) at imap-commands.c:181 > hook = 0x85c89b0 > finished = > cmd_start_timeval = {tv_sec = 1481007511, tv_usec = 140244} > cmd_start_bytes_in = 29 > cmd_start_bytes_out = 712 > cmd_start_lock_waits = 0 > __FUNCTION__ = "command_exec" > #16 0x0805d28f in client_command_input (cmd=0x85e1800) at > imap-client.c:986 > ---Type to continue, or q to quit--- > client = 0x85e0db8 > command = > __FUNCTION__ = "client_command_input" > #17 0x0805d30a in client_command_input (cmd=0x85e1800) at > imap-client.c:1046 > client = 0x85e0db8 > command = 0x701e > __FUNCTION__ = "client_command_input" > #18 0x0805d515 in client_handle_next_command (client=0x85e0db8) at > imap-client.c:1088 > No locals. > #19 client_handle_input (client=0x85e0db8) at imap-client.c:1100 > _data_stack_cur_id = 3 > remove_io = > handled_commands = false > __FUNCTION__ = "client_handle_input" > #20 0x0805dae1 in client_input (client=0x85e0db8) at imap-client.c:1147 > cmd = > output = 0x85e16f8 > bytes = 31 > __FUNCTION__ = "client_input" > #21 0x003cda88 in io_loop_call_io (io=0x85e1778) at ioloop.c:599 > ioloop = 0x85c8498 > t_id = 2 > __FUNCTION__ = "io_loop_call_io" > #22 0x003cf62f in io_loop_handler_run_internal (ioloop=0x85c8498) at > ioloop-epoll.c:222 > ctx = > event = 0x85ca230 > list = 0x85cab10 > io = 0x6 > tv = {tv_sec = 1799, tv_usec = 999295} > msecs = 1800000 > ret = 1 > i = 0 > j = 0 > call = false > __FUNCTION__ = "io_loop_handler_run_internal" > #23 0x003cdc0f in io_loop_handler_run (ioloop=0x85c8498) at ioloop.c:648 > No locals. > #24 0x003cdef8 in io_loop_run (ioloop=0x85c8498) at ioloop.c:623 > __FUNCTION__ = "io_loop_run" > #25 0x0034e49d in master_service_run (service=0x85c83c8, > callback=0x806af90 ) at master-service.c:641 > No locals. > #26 0x0806b927 in main (argc=Cannot access memory at address 0x0 > ) at main.c:460 > login_set = {auth_socket_path = 0x85c0038 "P", > postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = > 0x806b320 , > failure_callback = 0x806b030 , > request_auth_token = 1} > service_flags = > storage_service_flags = 4097 > username = 0x0 > auth_socket_path = 0x8074c39 "auth-master" > c = > set_roots = {0x8073e80, 0x807b220, 0x0} > > > Cheers, > Toni Mattila Hi! Any chance to get the core file? Do you know what command was issued on wire? Aki From aki.tuomi at dovecot.fi Tue Dec 6 08:10:54 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Tue, 6 Dec 2016 10:10:54 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) In-Reply-To: References: Message-ID: <0e96a9c5-07c4-663a-9ed3-db62cc7ce83d@dovecot.fi> On 06.12.2016 10:00, Aki Tuomi wrote: > > > On 06.12.2016 09:32, Toni Mattila wrote: >> Hi, >> >> On 05-Dec-16 20:28, Toni Mattila wrote: >>> Panicing stopped when all index files where deleted. >> >> It happens again in same user account, so rebuilding indexes didn't >> fix it. >> >> #14 0x08058219 in cmd_search (cmd=0x85e1800) at cmd-search.c:42 >> ctx = 0x85e18e8 >> sargs = >> args = 0x85e4030 >> charset = 0x8070f89 "UTF-8" >> ret = >> >> Cheers, >> Toni Mattila > > Hi! > > Any chance to get the core file? Do you know what command was issued > on wire? > > Aki Alternatively if you could try and print the args array in cmd_search? f 14 p args[0] p args[1] ... until NULL Aki From toni at solu.fi Tue Dec 6 08:44:14 2016 From: toni at solu.fi (Toni Mattila) Date: Tue, 6 Dec 2016 10:44:14 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) In-Reply-To: <0e96a9c5-07c4-663a-9ed3-db62cc7ce83d@dovecot.fi> References: <0e96a9c5-07c4-663a-9ed3-db62cc7ce83d@dovecot.fi> Message-ID: Hi, On 06-Dec-16 10:10, Aki Tuomi wrote: > Alternatively if you could try and print the args array in cmd_search? > > f 14 > p args[0] > p args[1] > ... > until NULL My hand got sore at first 100 and they are below. I will mail you the binary and core in seperate mail. (gdb) f 14 #14 0x08058219 in cmd_search (cmd=0x85e1800) at cmd-search.c:42 42 ret = imap_search_args_build(cmd, args, charset, &sargs); (gdb) p args[0] $1 = {type = IMAP_ARG_ATOM, parent = 0x0, str_len = 3, _data = {str = 0x85e40f8 "ALL", literal_size = 140394744, list = {arr = {buffer = 0x85e40f8, element_size = 0}, v = 0x85e40f8, v_modifiable = 0x85e40f8}}, literal8 = 0} (gdb) p args[1] $2 = {type = IMAP_ARG_ATOM, parent = 0x0, str_len = 3, _data = {str = 0x85e4100 "NOT", literal_size = 140394752, list = {arr = {buffer = 0x85e4100, element_size = 0}, v = 0x85e4100, v_modifiable = 0x85e4100}}, literal8 = 0} (gdb) p args[2] $3 = {type = IMAP_ARG_ATOM, parent = 0x0, str_len = 3, _data = {str = 0x85e4108 "UID", literal_size = 140394760, list = {arr = {buffer = 0x85e4108, element_size = 0}, v = 0x85e4108, v_modifiable = 0x85e4108}}, literal8 = 0} (gdb) p args[3] $4 = {type = IMAP_ARG_ATOM, parent = 0x0, str_len = 4, _data = {str = 0x85e4110 "79:*", literal_size = 140394768, list = {arr = {buffer = 0x85e4110, element_size = 0}, v = 0x85e4110, v_modifiable = 0x85e4110}}, literal8 = 0} (gdb) p args[4] $5 = {type = IMAP_ARG_EOL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[5] $6 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[6] $7 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[7] $8 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 51, _data = {str = 0x0, literal_size = 19220927837372416, list = {arr = {buffer = 0x0, element_size = 4475221}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[8] $9 = {type = 1380009299, parent = 0x4843, str_len = 5000257, _data = {str = 0x0, literal_size = 23731094469738496, list = {arr = {buffer = 0x0, element_size = 5525326}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[9] $10 = {type = 4475221, parent = 0x0, str_len = 708458807, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[10] $11 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[11] $12 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[12] $13 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[13] $14 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[14] $15 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[15] $16 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[16] $17 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[17] $18 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[18] $19 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[19] $20 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[20] $21 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[21] $22 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[22] $23 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[23] $24 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[24] $25 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[25] $26 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[26] $27 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[27] $28 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[28] $29 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[29] $30 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[30] $31 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[31] $32 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[32] $33 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[33] $34 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[34] $35 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[35] $36 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[36] $37 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[37] $38 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[38] $39 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[39] $40 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[40] $41 = {type = IMAP_ARG_NIL, parent = 0xc09, str_len = 0, _data = {str = 0xbf0
, literal_size = 7009386630128, list = {arr = {buffer = 0xbf0, element_size = 1632}, v = 0xbf0, v_modifiable = 0xbf0}}, literal8 = 0} (gdb) p args[41] $42 = {type = 4415584, parent = 0x1, str_len = 1, _data = {str = 0x85e43f8 "", literal_size = 602996366068564984, list = {arr = {buffer = 0x85e43f8, element_size = 140396032}, v = 0x85e43f8, v_modifiable = 0x85e43f8}}, literal8 = 0} (gdb) p args[42] $43 = {type = 140367432, parent = 0x85d7490, str_len = 4835952, _data = {str = 0x4f2c30 "U\211?S\203?\004\213E\b??\034??\201?e?\006", literal_size = 21798367781661744, list = {arr = {buffer = 0x4f2c30, element_size = 5075328}, v = 0x4f2c30, v_modifiable = 0x4f2c30}}, literal8 = 0} (gdb) p args[43] $44 = {type = 5214864, parent = 0x4f9570, str_len = 5086624, _data = {str = 0x4d98e0 "U\211?\203?\030\211]??)???\201?X\b", literal_size = 7185995687368928, list = {arr = {buffer = 0x4d98e0, element_size = 1673120}, v = 0x4d98e0, v_modifiable = 0x4d98e0}}, literal8 = 0} (gdb) p args[44] $45 = {type = 5077664, parent = 0x4d7630, str_len = 1672816, _data = {str = 0x4e1360 "U\211?WVS\201?\214", literal_size = 21975595312092000, list = {arr = {buffer = 0x4e1360, element_size = 5116592}, v = 0x4e1360, v_modifiable = 0x4e1360}}, literal8 = 0} (gdb) p args[45] $46 = {type = 5115216, parent = 0x4e15a0, str_len = 4842016, _data = {str = 0x49d7f0 "U\211?\203?H\213E\020\211]??\026q??\201?\031\f", literal_size = 20843579371542512, list = {arr = {buffer = 0x49d7f0, element_size = 4853024}, v = 0x49d7f0, v_modifiable = 0x49d7f0}}, literal8 = 0} (gdb) p args[46] $47 = {type = 5076368, parent = 0x0, str_len = 4833904, _data = {str = 0x199040 "U\211?VS?-???\201?\"\037", literal_size = 21802147349368896, list = {arr = {buffer = 0x199040, element_size = 5076208}, v = 0x199040, v_modifiable = 0x199040}}, literal8 = 0} (gdb) p args[47] $48 = {type = 4833664, parent = 0x4e76e0, str_len = 5167712, _data = {str = 0x4ed340 "U\211?WVS\203?\034\213U\b??u??\201?S\036\a", literal_size = 22188694409499456, list = {arr = {buffer = 0x4ed340, element_size = 5166208}, v = 0x4ed340, v_modifiable = 0x4ed340}}, literal8 = 0} (gdb) p args[48] $49 = {type = 4827280, parent = 0x198b10, str_len = 4827088, _data = {str = 0x198a60 "U\211?\203?\030\211]??\t???\201??$", literal_size = 20731978938157664, list = {arr = {buffer = 0x198a60, element_size = 4827040}, v = 0x198a60, v_modifiable = 0x198a60}}, literal8 = 0} (gdb) p args[49] $50 = {type = 4828864, parent = 0x499d50, str_len = 4828624, _data = {str = 0x4f2500 "U\211?S\203?\004\213E\b?\b$??\201?\225?\006", literal_size = 602998083920274688, list = {arr = {buffer = 0x4f2500, element_size = 140396432}, v = 0x4f2500, v_modifiable = 0x4f2500}}, literal8 = 0} (gdb) p args[50] $51 = {type = 140395528, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 603438197803843584, list = {arr = {buffer = 0x0, element_size = 140498904}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[51] $52 = {type = 140508200, parent = 0x0, str_len = 0, _data = {str = 0x59
, literal_size = 382252089433, list = {arr = {buffer = 0x59, element_size = 89}, v = 0x59, v_modifiable = 0x59}}, literal8 = 0} (gdb) p args[52] $53 = {type = 448, parent = 0xffffffff, str_len = 140396896, _data = {str = 0x101
, literal_size = 602999595743576321, list = {arr = {buffer = 0x101, element_size = 140396784}, v = 0x101, v_modifiable = 0x101}}, literal8 = 0} (gdb) p args[53] $54 = {type = 5644576, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 602996400287907840, list = {arr = {buffer = 0x0, element_size = 140396040}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[54] $55 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[55] $56 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x3
, literal_size = 21474836483, list = {arr = {buffer = 0x3, element_size = 5}, v = 0x3, v_modifiable = 0x3}}, literal8 = 0} (gdb) p args[56] $57 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[57] $58 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 4294967296, list = {arr = {buffer = 0x0, element_size = 1}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[57] $59 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 4294967296, list = {arr = {buffer = 0x0, element_size = 1}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[58] $60 = {type = IMAP_ARG_LITERAL, parent = 0x85e4680, str_len = 4, _data = {str = 0x1301
, literal_size = 602873529863508737, list = {arr = {buffer = 0x1301, element_size = 140367432}, v = 0x1301, v_modifiable = 0x1301}}, literal8 = 0} (gdb) p args[59] $61 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 140292960, _data = {str = 0x85fd158 "\030D^\bH?]\b??_\b??_\b??_\b\004", literal_size = 6360871489211715928, list = {arr = {buffer = 0x85fd158, element_size = 1481005803}, v = 0x85fd158, v_modifiable = 0x85fd158}}, literal8 = 0} (gdb) p args[60] $62 = {type = 692193634, parent = 0x58465aeb, str_len = 1481005534, _data = {str = 0x29420962
, literal_size = 6360870338712176994, list = {arr = {buffer = 0x29420962, element_size = 1481005535}, v = 0x29420962, v_modifiable = 0x29420962}}, literal8 = 0} (gdb) p args[61] $63 = {type = 4727, parent = 0x2, str_len = 4294967295, _data = {str = 0x15
, literal_size = 5711213352898789397, list = {arr = {buffer = 0x15, element_size = 1329745481}, v = 0x15, v_modifiable = 0x15}}, literal8 = 0} (gdb) p args[62] $64 = {type = 1329745481, parent = 0x58, str_len = 1702260580, _data = {str = 0x2e746f63
, literal_size = 7306085893531791203, list = {arr = {buffer = 0x2e746f63, element_size = 1701080681}, v = 0x2e746f63, v_modifiable = 0x2e746f63}}, literal8 = 0} (gdb) p args[63] $65 = {type = 140396088, parent = 0x0, str_len = 140396088, _data = {str = 0x0, literal_size = 279172874240, list = {arr = {buffer = 0x0, element_size = 65}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[64] $66 = {type = IMAP_ARG_LIST, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[65] $67 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[66] $68 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[67] $69 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 140396192, _data = {str = 0x10
, literal_size = 602997053122936848, list = {arr = {buffer = 0x10, element_size = 140396192}, v = 0x10, v_modifiable = 0x10}}, literal8 = 0} (gdb) p args[68] $70 = {type = 21, parent = 0x85e4408, str_len = 3, _data = {str = 0x0, literal_size = 602997156202151936, list = {arr = {buffer = 0x0, element_size = 140396216}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[69] $71 = {type = 140396608, parent = 0x85ffa68, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[70] $72 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[71] $73 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[72] $74 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[73] $75 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[74] $76 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[75] $77 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[76] $78 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[77] $79 = {type = 17, parent = 0x584661b5, str_len = 0, _data = {str = 0x85fd874 "@?_\b\004", literal_size = 603474619267012724, list = {arr = {buffer = 0x85fd874, element_size = 140507384}, v = 0x85fd874, v_modifiable = 0x85fd874}}, literal8 = 0} (gdb) p args[78] $80 = {type = IMAP_ARG_NIL, parent = 0x58466197, str_len = 4294967295, _data = {str = 0x0, literal_size = 20770255685025792, list = {arr = {buffer = 0x0, element_size = 4835952}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[79] $81 = {type = 4835552, parent = 0x49ce60, str_len = 4835120, _data = {str = 0x4f25a0 "U\211?\213E\b]?\227\215?&", literal_size = 20777539954746784, list = {arr = {buffer = 0x4f25a0, element_size = 4837648}, v = 0x4f25a0, v_modifiable = 0x4f25a0}}, literal8 = 0} (gdb) p args[80] $82 = {type = 5188208, parent = 0x4f2040, str_len = 5184944, _data = {str = 0x49c310 "U\211?\203?\030\211]?\213E\b??\205??\201?\203.\f", literal_size = 22270195708576528, list = {arr = {buffer = 0x49c310, element_size = 5185184}, v = 0x49c310, v_modifiable = 0x49c310}}, literal8 = 0} (gdb) p args[81] $83 = {type = 5116592, parent = 0x4e1200, str_len = 5115216, _data = {str = 0x4e15a0 "U\211?\203?\030\211}?\213}\b\211]?\211u??`3??\201???\a", literal_size = 20796300371826080, list = {arr = { buffer = 0x4e15a0, element_size = 4842016}, v = 0x4e15a0, v_modifiable = 0x4e15a0}}, literal8 = 0} (gdb) p args[82] $84 = {type = 4853024, parent = 0x4f5e40, str_len = 5202112, _data = {str = 0x0, literal_size = 20761459592003584, list = {arr = {buffer = 0x0, element_size = 4833904}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[83] $85 = {type = 5217376, parent = 0x4f9660, str_len = 4833664, _data = {str = 0x4e76e0 "U\211?\203?(\211]??)???\201?z\a", literal_size = 22195154040288992, list = {arr = {buffer = 0x4e76e0, element_size = 5167712}, v = 0x4e76e0, v_modifiable = 0x4e76e0}}, literal8 = 0} (gdb) p args[84] $86 = {type = 5166208, parent = 0x4eb180, str_len = 4827280, _data = {str = 0x49bc90 "U\211?WVS\203?<\213E\b?v\214??\201?\003\065\f", literal_size = 20732185099746448, list = {arr = {buffer = 0x49bc90, element_size = 4827088}, v = 0x49bc90, v_modifiable = 0x49bc90}}, literal8 = 0} (gdb) p args[85] $87 = {type = 4827040, parent = 0x496830, str_len = 4828864, _data = {str = 0x499d50 "U\211?\203?\030\211u?\213u\b\211]????\201?@T\f", literal_size = 20738782169505104, list = {arr = {buffer = 0x499d50, element_size = 4828624}, v = 0x499d50, v_modifiable = 0x499d50}}, literal8 = 0} (gdb) p args[86] $88 = {type = 4835952, parent = 0x4f2c30, str_len = 4835552, _data = {str = 0x49ce60 "U\211?\201??", literal_size = 20766682277072480, list = {arr = {buffer = 0x49ce60, element_size = 4835120}, v = 0x49ce60, v_modifiable = 0x49ce60}}, literal8 = 0} (gdb) p args[87] $89 = {type = 1673392, parent = 0x198830, str_len = 1673120, _data = {str = 0x198710 "U\211?\203?\030\211]??Y???\201?N(", literal_size = 22269164913264400, list = {arr = {buffer = 0x198710, element_size = 5184944}, v = 0x198710, v_modifiable = 0x198710}}, literal8 = 0} (gdb) p args[88] $90 = {type = 1672816, parent = 0x4e1360, str_len = 5116592, _data = {str = 0x4e1200 "U\211?WVS?\f7??\201?\231?\a", literal_size = 21969685437092352, list = {arr = {buffer = 0x4e1200, element_size = 5115216}, v = 0x4e1200, v_modifiable = 0x4e1200}}, literal8 = 0} (gdb) p args[89] $91 = {type = 4842016, parent = 0x49d7f0, str_len = 4853024, _data = {str = 0x4f5e40 "U1?\211?\203?\b\211\064$\211|$\004\213M\b\213}\f\200y8", literal_size = 22342900915330624, list = {arr = { buffer = 0x4f5e40, element_size = 5202112}, v = 0x4f5e40, v_modifiable = 0x4f5e40}}, literal8 = 0} (gdb) p args[90] $92 = {type = 4833904, parent = 0x199040, str_len = 1673552, _data = {str = 0x199110 "U\211?\203?\030\211]??Y???\201?N\036", literal_size = 20760428801528080, list = {arr = {buffer = 0x199110, element_size = 4833664}, v = 0x199110, v_modifiable = 0x199110}}, literal8 = 0} (gdb) p args[91] $93 = {type = 5167712, parent = 0x4ed340, str_len = 5166208, _data = {str = 0x4eb180 "U\211?WVS\203?,\213u\b?\206\227??\201?\023@\a", literal_size = 20733009733792128, list = {arr = {buffer = 0x4eb180, element_size = 4827280}, v = 0x4eb180, v_modifiable = 0x4eb180}}, literal8 = 0} (gdb) p args[92] $94 = {type = 4827088, parent = 0x198a60, str_len = 4827040, _data = {str = 0x198c10 "U\211?WVS?\\???\201?Q#", literal_size = 20739812958506000, list = {arr = {buffer = 0x198c10, element_size = 4828864}, v = 0x198c10, v_modifiable = 0x198c10}}, literal8 = 0} (gdb) p args[93] $95 = {type = 4828624, parent = 0x4f2500, str_len = 2053726767, _data = {str = 0x616d762f
, literal_size = 7219107927560123951, list = {arr = {buffer = 0x616d762f, element_size = 1680829545}, v = 0x616d762f, v_modifiable = 0x616d762f}}, literal8 = 1} (gdb) p args[94] $96 = {type = 959411054, parent = 0x73616c2f, str_len = 1634234981, _data = {str = 0x74696c6c
, literal_size = 3416374142044826732, list = {arr = {buffer = 0x74696c6c, element_size = 795436590}, v = 0x74696c6c, v_modifiable = 0x74696c6c}}, literal8 = 0} (gdb) p args[95] $97 = {type = 1632448367, parent = 0x69646c69, str_len = 114, _data = {str = 0x0, literal_size = 8820689299184812032, list = {arr = {buffer = 0x0, element_size = 2053726767}, v = 0x0, v_modifiable = 0x0}}, literal8 = 1} (gdb) p args[96] $98 = {type = 1680829545, parent = 0x69616d6f, str_len = 959411054, _data = {str = 0x73616c2f
, literal_size = 7018985799309945903, list = {arr = {buffer = 0x73616c2f, element_size = 1634234981}, v = 0x73616c2f, v_modifiable = 0x73616c2f}}, literal8 = 0} (gdb) p args[97] $99 = {type = 795436590, parent = 0x6d696568, str_len = 1632448367, _data = {str = 0x69646c69
, literal_size = 491394460777, list = {arr = {buffer = 0x69646c69, element_size = 114}, v = 0x69646c69, v_modifiable = 0x69646c69}}, literal8 = 0} (gdb) p args[98] $100 = {type = 2053726767, parent = 0x616d762f, str_len = 1680829545, _data = {str = 0x69616d6f
, literal_size = 4120639102118882671, list = {arr = {buffer = 0x69616d6f, element_size = 959411054}, v = 0x69616d6f, v_modifiable = 0x69616d6f}}, literal8 = 1} (gdb) p args[99] $101 = {type = 1634234981, parent = 0x74696c6c, str_len = 795436590, _data = {str = 0x6d696568
, literal_size = 7011312350509229416, list = {arr = {buffer = 0x6d696568, element_size = 1632448367}, v = 0x6d696568, v_modifiable = 0x6d696568}}, literal8 = 1} (gdb) p args[100] $102 = {type = 114, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[101] $103 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[102] $104 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[103] $105 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[104] $106 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = Cheers, Toni From aki.tuomi at dovecot.fi Tue Dec 6 08:47:46 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Tue, 6 Dec 2016 10:47:46 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) In-Reply-To: References: <0e96a9c5-07c4-663a-9ed3-db62cc7ce83d@dovecot.fi> Message-ID: <0376a44e-245b-65bf-a479-93727e06fae6@dovecot.fi> On 06.12.2016 10:44, Toni Mattila wrote: > Hi, > > On 06-Dec-16 10:10, Aki Tuomi wrote: >> Alternatively if you could try and print the args array in cmd_search? >> >> f 14 >> p args[0] >> p args[1] >> ... >> until NULL > > My hand got sore at first 100 and they are below. I will mail you the > binary and core in seperate mail. > > Cheers, > > Toni Thanks. I should've probably said until EOL. $5 = {type = IMAP_ARG_EOL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} Aki From plataleas at gmail.com Tue Dec 6 09:05:29 2016 From: plataleas at gmail.com (plataleas) Date: Tue, 6 Dec 2016 10:05:29 +0100 Subject: Dovecot: Mails flagged as read get flagged as unread Message-ID: Hi all We experience some unexpected behavior with dovecot. It happens that emails marked as read get marked as unread (MUA is Thunderbird on port 143). Unfortunately this happens randomly, reproducing this issue is difficult. We could not find any pattern, it happens rarely. We are running dovecot version 2.2.24 on Debian Jessie (backports repository). /root at dovecot01:~# dovecot --version// //2.2.24 (a82c823)/ Our Setup: /ha-proxy01 -> dovecot-proxy01 (proxy=yes) -> dovecot01 (proxy=no) * IP is used for multiple services (ports). We use the haproxy to send traffic on different ports to different servers. / Below the configuration (IMAPC is active for migration purposes). Do you have any recommendations where we could focus for troubleshooting? I found some posts about mbox_lazy_writes causing similar issues. However we use mdbox in our setup. If we enable rawlog for what log patterns should we search? Your Inputs are highly appreciated! Thanks and Regards plataleas *----- haproxy configuration ------ *frontend frontend_mail.company.org-143 bind 10.100.189.34:143 mode tcp default_backend backend_mail.company.org-143 backend backend_mail.company.org-143 mode tcp balance source server dovecot-proxy01.company.org dovecot-proxy01.company.org:10143 check send-proxy-v2 server dovecot-proxy02.company.org dovecot-proxy02.company.org:10143 check send-proxy-v2 backup *----- config Dovecot Proxy -----* /root at dovecot-proxy01:~# dovecot -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.5 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@* default_client_limit = 5000 default_process_limit = 500 disable_plaintext_auth = no haproxy_trusted_networks = 10.10.189.28,10.10.189.29 imap_capability = IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS listen = 10.10.189.25 mail_location = mdbox:%h/mdbox mail_max_userip_connections = 0 mail_plugins = zlib mdbox_rotate_size = 10 M namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { gzip_save_level = 6 pop3_migration_mailbox = POP3-MIGRATION-NS/INBOX sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz } protocols = imap pop3 lmtp service imap-login { inet_listener imap_haproxy { address = 10.10.189.25 haproxy = yes port = 10143 } inet_listener imaps_haproxy { address = 10.10.189.25 haproxy = yes port = 10993 ssl = yes } } service lmtp { inet_listener lmtp { address = 10.10.189.25 port = 24 } } service pop3-login { inet_listener pop3_haproxy { address = 10.10.189.25 haproxy = yes port = 10110 } inet_listener pop3s_haproxy { address = 10.10.189.25 haproxy = yes port = 10995 ssl = yes } } ssl_ca = References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 6 Dec 2016, plataleas wrote: > We experience some unexpected behavior with dovecot. It happens that > emails marked as read get marked as unread (MUA is Thunderbird on port > 143). Unfortunately this happens randomly, reproducing this issue is > difficult. We could not find any pattern, it happens rarely. does your user(s) access these mailboxes from two or more clients simultaneously - either from the same account or as shared mailboxes? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWEaBc3z1H7kL/d9rAQI71gf/Y0U/GNaxJO2nEQFfTjXMzb68NfH4x7Nn lMFhb+HJjqLIb8VfBFbEEMx2fTcxH0Aq4QxdapnCpT8GSJWx6Eu2/XycnothrXpV y96UUMcCP4CGS5w6ezdJyFQxmapp6XNCZ3FU+tm5J54Vpe2dX5q60+xAY+yPog3E obf1/VXjfLy++ubUcv0LGhgkBbmYlsAR4v5Ht2Er8ArfyIOzNhbbmneDAemL+nIE IdzXmeLuEEY0xTrp5K6jFWe4Q+h6Zt+Q/R+5PXSj67s0e6wPeO/0/bPXdnDJHITJ DqT1vrMZpCXD5fInNVU85mjhjrY/1iu1AbbJCjRuMkHCfJz2YwCi4Q== =YcKj -----END PGP SIGNATURE----- From plataleas at gmail.com Tue Dec 6 09:24:17 2016 From: plataleas at gmail.com (plataleas) Date: Tue, 6 Dec 2016 10:24:17 +0100 Subject: Dovecot: Mails flagged as read get flagged as unread In-Reply-To: References: Message-ID: <2ac2906b-f53e-c088-eb32-7b0167c5e495@gmail.com> Hi Steffen Thanks for the reply! - Users are accessing from multiple devices simultaneously - Each user has his own mailbox, we do not use shared mailboxes regards On 12/06/2016 10:14 AM, Steffen Kaiser wrote: > On Tue, 6 Dec 2016, plataleas wrote: > > > We experience some unexpected behavior with dovecot. It happens that > > emails marked as read get marked as unread (MUA is Thunderbird on port > > 143). Unfortunately this happens randomly, reproducing this issue is > > difficult. We could not find any pattern, it happens rarely. > > does your user(s) access these mailboxes from two or more clients > simultaneously - either from the same account or as shared mailboxes? > > -- Steffen Kaiser From aki.tuomi at dovecot.fi Tue Dec 6 10:11:23 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Tue, 6 Dec 2016 12:11:23 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) In-Reply-To: <0376a44e-245b-65bf-a479-93727e06fae6@dovecot.fi> References: <0e96a9c5-07c4-663a-9ed3-db62cc7ce83d@dovecot.fi> <0376a44e-245b-65bf-a479-93727e06fae6@dovecot.fi> Message-ID: <7c8e74c5-cb78-266b-283d-c23cc1add971@dovecot.fi> On 06.12.2016 10:47, Aki Tuomi wrote: > > > On 06.12.2016 10:44, Toni Mattila wrote: >> Hi, >> >> On 06-Dec-16 10:10, Aki Tuomi wrote: >>> Alternatively if you could try and print the args array in cmd_search? >>> >>> f 14 >>> p args[0] >>> p args[1] >>> ... >>> until NULL >> >> My hand got sore at first 100 and they are below. I will mail you the >> binary and core in seperate mail. >> >> Cheers, >> >> Toni > > Thanks. I should've probably said until EOL. > > $5 = {type = IMAP_ARG_EOL, parent = 0x0, str_len = 0, _data = {str = > 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, > v = 0x0, v_modifiable = 0x0}}, literal8 = 0} > > Aki I was able to repeat this bug, thank you for your report. Aki From pch at myzel.net Tue Dec 6 10:34:10 2016 From: pch at myzel.net (Peter Chiochetti) Date: Tue, 6 Dec 2016 11:34:10 +0100 Subject: Dovecot: Mails flagged as read get flagged as unread In-Reply-To: <2ac2906b-f53e-c088-eb32-7b0167c5e495@gmail.com> References: <2ac2906b-f53e-c088-eb32-7b0167c5e495@gmail.com> Message-ID: <3e7882c8-057f-cdfc-5b28-0a88955f2265@myzel.net> Hi, There is a plugin "mail_log" that you can use to audit what users/user agents are doing, probably mail_log_events flag_change is helpful? -- peter Am 2016-12-06 um 10:24 schrieb plataleas: > Hi Steffen > > Thanks for the reply! > > - Users are accessing from multiple devices simultaneously > - Each user has his own mailbox, we do not use shared mailboxes > > regards > > > > On 12/06/2016 10:14 AM, Steffen Kaiser wrote: >> On Tue, 6 Dec 2016, plataleas wrote: >> >>> We experience some unexpected behavior with dovecot. It happens that >>> emails marked as read get marked as unread (MUA is Thunderbird on port >>> 143). Unfortunately this happens randomly, reproducing this issue is >>> difficult. We could not find any pattern, it happens rarely. >> >> does your user(s) access these mailboxes from two or more clients >> simultaneously - either from the same account or as shared mailboxes? >> >> -- Steffen Kaiser From gilles.chauvin at univ-rouen.fr Tue Dec 6 12:58:01 2016 From: gilles.chauvin at univ-rouen.fr (Gilles Chauvin) Date: Tue, 6 Dec 2016 13:58:01 +0100 Subject: Panic: file dsync-mailbox-tree-sync.c: line 576 (node_mailbox_trees_cmp): assertion failed: (ret != 0) Message-ID: <5c41b151-1ff1-4649-a4eb-25bfb25a1a33@univ-rouen.fr> Hi, Here is a crash that's happening using the latest Dovecot version (v2.2.27 on CentOS7 x86_64): We are using replication. Judging by the second server's logs, I believe this has something to do with the fact that we're using the lazy_expunge plugin. Every night after midnight, we purge the lazy_expunge namespace by running a command similar to following one on the main server (server01 in the logs below): # doveadm expunge -A MAILBOX 'EXPUNGED/*' SAVEDBEFORE "$(date +'%F')" The lazy_expunge namespace is configured as follows: namespace expunged { disabled = no hidden = yes ignore_on_failure = no inbox = no list = no location = sdbox:/srv/mail/expunged/%1n/%n:SUBSCRIPTIONS=subscriptions-expunged order = 0 prefix = EXPUNGED/ separator = / subscriptions = no type = private } plugin { lazy_expunge = EXPUNGED/ } First server's logs: 2016-12-06T13:09:31.212620+01:00 server01 dovecot: dsync-server(user01): Panic: file dsync-mailbox-tree-sync.c: line 576 (node_mailbox_trees_cmp): assertion failed: (ret != 0) 2016-12-06T13:09:31.213473+01:00 server01 dovecot: dsync-server(user01): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x92d70) [0x7f57cc18ad70] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x92e4e) [0x7f57cc18ae4e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f57cc1264e0] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x447584] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x447a57] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x447849] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x447849] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes](dsync_mailbox_trees_sync_init+0x1f9) [0x447cc9] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes](dsync_brain_recv_mailbox_tree_deletes+0x207) [0x43a477] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes](dsync_brain_run+0x5fe) [0x436e4e] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x437280] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x44c5af] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f57cc19e4d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f57cc19fa07] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f57cc19e56c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f57cc19e728] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x41faae] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x421316] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x433b64] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f57cc19e4d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f57cc19fa07] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f57cc19e56c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f57cc19e728] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f57cc12c513] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes](main+0x197) [0x413b57] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f57cbd57b15] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x413bf5] 2016-12-06T13:09:31.214076+01:00 server01 dovecot: dsync-server(user01): Fatal: master: service(doveadm): child 6837 killed with signal 6 (core dumps disabled) 2016-12-06T13:11:42.880516+01:00 server01 dovecot: dsync-local(user01): Error: read(server02.localdomain) failed: EOF (last sent=mailbox_delete, last recv=mailbox_tree_node) Second server's logs: 2016-12-06T12:09:36.220591+01:00 server02 dovecot: doveadm(user01): Error: Duplicate mailbox GUID eab35824e49b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/Demissions C2i and EXPUNGED/Trash/C2i - Coordination/Demissions C2i - giving a new GUID c4ffaf08709c465813ae0000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/Demissions C2i 2016-12-06T12:09:36.220859+01:00 server02 dovecot: doveadm(user01): Error: Duplicate mailbox GUID 2ab10a2bee9b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2014-2015 and EXPUNGED/Trash/C2i - Coordination/2014-2015 - giving a new GUID c6ffaf08709c465813ae0000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2014-2015 2016-12-06T12:09:36.221091+01:00 server02 dovecot: doveadm(user01): Error: Duplicate mailbox GUID eeb35824e49b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2012-2013 and EXPUNGED/Trash/C2i - Coordination/2012-2013 - giving a new GUID c8ffaf08709c465813ae0000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2012-2013 2016-12-06T12:09:36.284224+01:00 server02 dovecot: dsync-local(user01): Error: Mailbox EXPUNGED/Trash/C2i - Coordination/2008-2009/Formation FC sync: mailbox_rename failed: Can't rename mailboxes to/from expunge namespace. 2016-12-06T12:09:45.469706+01:00 server02 dovecot: dsync-server(user01): Error: Duplicate mailbox GUID eab35824e49b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/Demissions C2i and EXPUNGED/Trash/C2i - Coordination/Demissions C2i - giving a new GUID 671ae30f799c465882b00000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/Demissions C2i 2016-12-06T12:09:45.470389+01:00 server02 dovecot: dsync-server(user01): Error: Duplicate mailbox GUID 2ab10a2bee9b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2014-2015 and EXPUNGED/Trash/C2i - Coordination/2014-2015 - giving a new GUID 691ae30f799c465882b00000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2014-2015 2016-12-06T12:09:45.471214+01:00 server02 dovecot: dsync-server(user01): Error: Duplicate mailbox GUID eeb35824e49b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2012-2013 and EXPUNGED/Trash/C2i - Coordination/2012-2013 - giving a new GUID 6b1ae30f799c465882b00000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2012-2013 2016-12-06T12:09:45.485663+01:00 server02 dovecot: dsync-server(user01): Error: Mailbox EXPUNGED/Trash/C2i - Coordination/2008-2009/Formation FC sync: mailbox_rename failed: Can't rename mailboxes to/from expunge namespace. [... Previous line repeated numerous times ...] 2016-12-06T12:14:32.583382+01:00 server02 dovecot: dsync-server(user01): Error: Mailbox EXPUNGED/Trash/C2i - Coordination/2008-2009/Formation FC sync: mailbox_rename failed: Can't rename mailboxes to/from expunge namespace. 2016-12-06T12:14:36.778278+01:00 server02 dovecot: dsync-local(user01): Error: Mailbox EXPUNGED/Trash/C2i - Coordination/2008-2009/Formation FC sync: mailbox_rename failed: Can't rename mailboxes to/from expunge namespace. [... / ...] 2016-12-06T12:19:30.677497+01:00 sauto dovecot: dsync-server(user01): Panic: file dsync-mailbox-tree-sync.c: line 576 (node_mailbox_trees_cmp): assertion failed: (ret != 0) 2016-12-06T12:19:30.678991+01:00 sauto dovecot: dsync-server(user01): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x92d70) [0x7f40f3cd1d70] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x92e4e) [0x7f40f3cd1e4e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f40f3c6d4e0] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x447584] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x447a57] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x447849] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x447849] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes](dsync_mailbox_trees_sync_init+0x1f9) [0x447cc9] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes](dsync_brain_recv_mailbox_tree_deletes+0x207) [0x43a477] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes](dsync_brain_run+0x5fe) [0x436e4e] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x437280] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x44c5af] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f40f3ce54d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f40f3ce6a07] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f40f3ce556c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f40f3ce5728] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x41faae] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x421316] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x433b64] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f40f3ce54d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f40f3ce6a07] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f40f3ce556c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f40f3ce5728] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f40f3c73513] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes](main+0x197) [0x413b57] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f40f389eb15] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x413bf5] 2016-12-06T12:19:30.689038+01:00 sauto dovecot: dsync-server(user01): Fatal: master: service(doveadm): child 96318 killed with signal 6 (core dumps disabled) 2016-12-06T12:19:30.749074+01:00 sauto dovecot: dsync-local(user01): Error: read(server01.localdomain) failed: EOF (last sent=mailbox_delete, last recv=mailbox_tree_node) Thanks, Kind regards, Gilles. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3086 bytes Desc: S/MIME Cryptographic Signature URL: From lists at alex-at.ru Tue Dec 6 17:40:41 2016 From: lists at alex-at.ru (Alexey Asemov (Alex/AT)) Date: Tue, 6 Dec 2016 20:40:41 +0300 Subject: Dovecot: Mails flagged as read get flagged as unread In-Reply-To: <3e7882c8-057f-cdfc-5b28-0a88955f2265@myzel.net> References: <2ac2906b-f53e-c088-eb32-7b0167c5e495@gmail.com> <3e7882c8-057f-cdfc-5b28-0a88955f2265@myzel.net> Message-ID: <88def665-74e0-bffd-a018-567e0203b6ce@alex-at.ru> Does this correspond with some index damage in logs? We did have some of these in 2.2.6.0 ("Missing middle file seq=.." followed by reindexing and "lost Recent state" message), with 2.2.7 these seem to have stopped appearing. On 06.12.2016 13:34, Peter Chiochetti wrote: > Hi, There is a plugin "mail_log" that you can use to audit what > users/user agents are doing, probably mail_log_events flag_change is > helpful? > From ruga at protonmail.com Tue Dec 6 19:35:29 2016 From: ruga at protonmail.com (Ruga) Date: Tue, 06 Dec 2016 14:35:29 -0500 Subject: v2.2.27 released --- libressl In-Reply-To: References: Message-ID: Results from the application of the following patch from Aki. perl -i -ple 's|^(\s*#include \s*)$|$1\n\t#if OPENSSL_VERSION_NUMBER == 0x20000000L\n\t#define OPENSSL_VERSION_NUMBER 0x10001000L\n\t#endif|' configure.ac; -------------- next part -------------- A non-text attachment was scrubbed... Name: compiler-stderr.log Type: application/octet-stream Size: 16045 bytes Desc: not available URL: From mihai.craiu at gmail.com Tue Dec 6 14:03:30 2016 From: mihai.craiu at gmail.com (Mihai Craiu) Date: Tue, 6 Dec 2016 16:03:30 +0200 Subject: Segmentation fault in imap_bodystructure_is_plain_7bit Message-ID: Hi, I have a lot of errors like this in my log: Fatal: master: service(imap): child 26049 killed with signal 11 (core dumped) Dovecot 2.2.18 build from sources ./configure --prefix=/opt/dovecot2 --with-mysql --with-sqlite --with-solr --with-ssl --disable-rpath --disable-static. Debian Wheezy 3.2.63-2 x86_64. Filesystem is ZFS. All the core files are similar: $ gdb /opt/dovecot2/libexec/dovecot/imap core GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /opt/dovecot2/libexec/dovecot/imap...done. [New LWP 11635] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/opt/dovecot2/libexec/dovecot/imap imap-postlogin'. Program terminated with signal 11, Segmentation fault. #0 imap_bodystructure_is_plain_7bit (part=part at entry=0x234cd50) at imap-bodystructure.c:458 458 if (data->content_subtype != NULL && (gdb) bt #0 imap_bodystructure_is_plain_7bit (part=part at entry=0x234cd50) at imap-bodystructure.c:458 #1 0x00007f920a0fbfaf in index_mail_body_parsed_cache_flags (mail=0x234be60) at index-mail.c:587 #2 index_mail_parse_body_finish (mail=mail at entry=0x234be60, field=field at entry=MAIL_CACHE_IMAP_BODYSTRUCTURE, success=success at entry=true) at index-mail.c:1007 #3 0x00007f920a0fc369 in index_mail_parse_body (mail=mail at entry=0x234be60, field=field at entry=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:1081 #4 0x00007f920a0fc498 in index_mail_parse_bodystructure (mail=mail at entry=0x234be60, field=field at entry=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:1222 #5 0x00007f920a0fcf1c in index_mail_get_special (_mail=_mail at entry=0x234be60, field=field at entry=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=value_r at entry=0x7ffc1518fde8) at index-mail.c:1379 #6 0x00007f920a0b29cd in dbox_mail_get_special (_mail=_mail at entry=0x234be60, field=field at entry=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=value_r at entry=0x7ffc1518fde8) at dbox-mail.c:229 #7 0x00007f920a0a83f0 in mdbox_mail_get_special (_mail=0x234be60, field=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=0x7ffc1518fde8) at mdbox-mail.c:213 #8 0x00007f920a08f96d in mail_get_special (mail=, field=field at entry=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=value_r at entry=0x7ffc1518fde8) at mail.c:317 #9 0x0000000000419a6a in fetch_bodystructure (ctx=0x232bbd8, mail=, context=) at imap-fetch.c:690 #10 0x0000000000419f9f in imap_fetch_more_int (ctx=ctx at entry=0x232bbd8, cancel=false) at imap-fetch.c:506 #11 0x000000000041af07 in imap_fetch_more (ctx=0x232bbd8, cmd=cmd at entry=0x232ba00) at imap-fetch.c:558 #12 0x000000000040f0c9 in cmd_fetch (cmd=0x232ba00) at cmd-fetch.c:286 #13 0x0000000000418aec in command_exec (cmd=cmd at entry=0x232ba00) at imap-commands.c:167 #14 0x0000000000417ad0 in client_command_input (cmd=cmd at entry=0x232ba00) at imap-client.c:814 #15 0x0000000000417b64 in client_command_input (cmd=0x232ba00) at imap-client.c:874 #16 0x0000000000417e45 in client_handle_next_command (remove_io_r=, client=0x232ade0) at imap-client.c:912 #17 client_handle_input (client=client at entry=0x232ade0) at imap-client.c:924 #18 0x0000000000418212 in client_input (client=0x232ade0) at imap-client.c:966 #19 0x00007f9209df134b in io_loop_call_io (io=0x232b8f0) at ioloop.c:501 #20 0x00007f9209df1e5b in io_loop_handler_run_internal (ioloop=ioloop at entry=0x22ec790) at ioloop-epoll.c:220 #21 0x00007f9209df13d9 in io_loop_handler_run (ioloop=ioloop at entry=0x22ec790) at ioloop.c:548 #22 0x00007f9209df1458 in io_loop_run (ioloop=0x22ec790) at ioloop.c:525 #23 0x00007f9209d92993 in master_service_run (service=0x22ec620, callback=callback at entry=0x421140 ) at master-service.c:581 #24 0x000000000040c60b in main (argc=2, argv=0x22ec390) at main.c:431 (gdb) q Thanks. From listaccount at starionline.com Wed Dec 7 04:21:02 2016 From: listaccount at starionline.com (SH Development) Date: Tue, 6 Dec 2016 22:21:02 -0600 Subject: Setting up replication - First steps... Message-ID: <3F31434B-F01A-4847-8F4A-F758528BBBEF@starionline.com> Just had my first (non-Dovecot) server failure due to dried out caps on the motherboard. Got me to thinking about my single-point-of-failure mail server. Currently running Dovecot and Postfix with no issues, but want to start taking steps just to be safe. I currently run a filesystem backup every 24 hours to a tar file over NFS to another server in our rack. I am backing up: /home/vmail /etc/dovecot /etc/postfix Unfortunately, the vmail directory has grown to 27GB and takes around 7 hours now to backup as described above. Which leads me to start thinking about how quickly I could restore the server from a backup if need be, and that time is at least 7 hours just to copy and untar the files onto another hard drive. I?m sure I could hook up a HD up directly to the backup server, then I could considerably reduce the time, but I?m making the assumption that I won?t always have quick physical access to the location. So I believe my first step is to set up another server, on another IP, different hostname, with Dovecot and Postfix, and simply use the files from the /etc directories of the existing server to configure it (changing the IP and hostname of course). Am I on the right track so far? Next steps involve setting up replication with dsync? If I have successfully setup replication between the two servers, does this mean users can then actually log into either server and have their ?stuff? intact? So I could set up DNS failover in case the primary server fails? Would this make the setup acceptable for secondary MX as everything should sync to the primary server when it comes back online? Sorry for thinking out loud, but I want to make sure I?m understanding the bigger picture here. Jeff From mpeters at domblogger.net Wed Dec 7 05:30:31 2016 From: mpeters at domblogger.net (Michael A. Peters) Date: Tue, 6 Dec 2016 21:30:31 -0800 Subject: v2.2.27 released --- libressl In-Reply-To: References: Message-ID: <8ccf46ae-e722-ee8f-4854-93d8e935059f@domblogger.net> On 12/06/2016 11:35 AM, Ruga wrote: > Results from the application of the following patch from Aki. > > perl -i -ple 's|^(\s*#include \s*)$|$1\n\t#if OPENSSL_VERSION_NUMBER == 0x20000000L\n\t#define OPENSSL_VERSION_NUMBER 0x10001000L\n\t#endif|' configure.ac; > I use a different method of patching but similar in end result concept, but I too have an error - I haven't looked at why yet, that's on my todo list, just saw the build fails. I might see if I can get it to build tonight. My personal use of dovecot is rather limited, three low volume servers, so I can't be of much use in finding problems that are not compile related, but I'll try to figure out the LibreSSL needed build tweaking tonight. From cedric.bassaget.ml at gmail.com Wed Dec 7 10:22:00 2016 From: cedric.bassaget.ml at gmail.com (=?UTF-8?Q?C=c3=a9dric_ML?=) Date: Wed, 7 Dec 2016 11:22:00 +0100 Subject: Dovecot migration via dsync : mail_location problem (INBOX) ? Message-ID: Hello, I'm trying to migrate mail accounts from an old dovecot 1.0.15 to a new dovecot 2.2.26. I've set up a master-user on old dovecot, and I run dsync on new server, like this : # doveadm -D -o mail_fsync=never sync -R -u user at domain.tld imapc: my user at domain.tld looks like this (on the new server): # doveadm user user at domain.tld field value uid 2000 gid 2000 home /home/vmail/domain.tld/user mail maildir:/home/vmail/domain.tld/user/mail quota_rule *:bytes=0 User mail folder on the old server looks like this : # ls -la /home/virtual/user at domain.tld/ total 64 drwx------ 11 vmail vmail 4096 2016-12-06 16:26 ./ drwxrwx--- 234 vmail vmail 12288 2016-12-05 12:57 ../ drwx------ 2 vmail vmail 89 2016-12-06 15:29 cur/ -rw------- 1 vmail vmail 352 2016-12-06 16:26 dovecot.index -rw------- 1 vmail vmail 19456 2016-12-06 16:26 dovecot.index.cache -rw------- 1 vmail vmail 2220 2016-12-06 16:26 dovecot.index.log -rw------- 1 vmail vmail 10 2016-12-06 15:14 dovecot-keywords -rw------- 1 vmail vmail 170 2016-12-06 16:21 dovecot-uidlist drwx------ 5 vmail vmail 148 2016-12-05 16:52 .Drafts/ drwx------ 5 vmail vmail 148 2016-12-05 16:52 .FauxIndesirable/ drwx------ 5 vmail vmail 148 2016-12-05 16:52 .Indesirable/ -rw-r----- 1 vmail vmail 293 2016-12-06 15:29 maildirsize drwx------ 2 vmail vmail 85 2016-12-06 15:29 new/ drwx------ 5 vmail vmail 148 2016-12-05 16:52 .Sent/ drwx------ 5 vmail vmail 148 2016-12-05 16:52 .Spam/ drwx------ 2 vmail vmail 6 2016-12-07 10:46 tmp/ drwx------ 5 vmail vmail 4096 2016-12-06 15:36 .Trash/ When I run the sync, with "doveadm -D -o mail_fsync=never sync -R -u user at domain.tld imapc:" on the new server, the new server synchronises the mail from the new server, and the file system on the new server looks like this : root at dovecot-pa3:/home/vmail/domain.tld# ls -la /home/vmail/domain.tld/user/mail/ total 84 drwx------ 15 mailbox mailbox 4096 Dec 7 11:02 . drwx------ 3 mailbox mailbox 4096 Dec 7 11:02 .. drwx------ 2 mailbox mailbox 4096 Dec 7 11:02 cur -rw------- 1 mailbox mailbox 556 Dec 7 11:02 dovecot.index.log -rw------- 1 mailbox mailbox 96 Dec 7 11:02 dovecot.mailbox.log -rw------- 1 mailbox mailbox 51 Dec 7 11:02 dovecot-uidlist -rw------- 1 mailbox mailbox 8 Dec 7 11:02 dovecot-uidvalidity -r--r--r-- 1 mailbox mailbox 0 Dec 7 11:02 dovecot-uidvalidity.5847de3b drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .Drafts drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Drafts drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.FauxIndesirable drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Indesirable drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Sent drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Spam drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Trash drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .Junk -rw------- 1 mailbox mailbox 17 Dec 7 11:02 maildirsize drwx------ 2 mailbox mailbox 4096 Dec 7 11:02 new drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .Sent -rw------- 1 mailbox mailbox 23 Dec 7 11:02 subscriptions drwx------ 2 mailbox mailbox 4096 Dec 7 11:02 tmp drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .Trash But dovecot is condigured to have ".Trash", ".Junk" etc... folders, not ".INBOX.Trash" I've try multiple things : - use namespaces for compatibility and add "-n " in sync command, without success - modify the mail_location for the user, tried to add LAYOUT=fs, INBOX=, ... without success. Can anybody help me with that please ? Here's the #doveconf -n output : ------------------------------------------------------- # 2.2.devel (f7f4b65): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (53a3582) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 12345 imapc_features = rfc822.size fetch-headers imapc_host = oldserver.domain.tld imapc_master_user = masteruser imapc_password = # hidden, use -P to show it imapc_user = %u mail_plugins = " quota notify replication" mail_prefetch_count = 20 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl dotlock namespace compat { hidden = no list = no location = maildir:~/mail/ prefix = INBOX separator = / } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:192.168.159.9:12345 quota = maildir:User quota quota_grace = 10%% quota_rule = Trash:storage=+100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Boite de messagerie pleine. quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=85%% quota-warning 85 %u sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve/ sieve_before2 = /home/vmail/%d/%n/sieve/Vacation.sieve sieve_default = /var/lib/dovecot/sieve/dovecot.sieve sieve_default_name = default sieve_global = /var/lib/dovecot/sieve/ } protocols = " imap sieve pop3 sieve" service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = mailbox } unix_listener replication-notify { mode = 0666 user = mailbox } } service auth { inet_listener { port = 12346 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = mailbox user = mailbox } } service config { unix_listener config { user = mailbox } } service doveadm { inet_listener { port = 12345 } user = mailbox } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 1 vsz_limit = 64 M } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = mailbox } user = mailbox } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = mailbox mode = 0660 } } ssl = required ssl_cert = References: Message-ID: <1F5342F6-2B5F-4362-A7FF-1EB5EB9D053B@dovecot.fi> > On 7 Dec 2016, at 12.22, C?dric ML wrote: > > Hello, > > I'm trying to migrate mail accounts from an old dovecot 1.0.15 to a new dovecot 2.2.26. > I've set up a master-user on old dovecot, and I run dsync on new server, like this : > > # doveadm -D -o mail_fsync=never sync -R -u user at domain.tld imapc: > ? > But dovecot is condigured to have ".Trash", ".Junk" etc... folders, not ".INBOX.Trash" > I've try multiple things : > - use namespaces for compatibility and add "-n " in sync command, without success > - modify the mail_location for the user, tried to add LAYOUT=fs, INBOX=, ... without success. > > Can anybody help me with that please ? > you can try setting imapc_prefix=INBOX and imapc_list_prefix=INBOX or maybe ?INBOX.' Sami From cedric.bassaget.ml at gmail.com Wed Dec 7 12:02:21 2016 From: cedric.bassaget.ml at gmail.com (=?UTF-8?Q?C=c3=a9dric_ML?=) Date: Wed, 7 Dec 2016 13:02:21 +0100 Subject: Dovecot migration via dsync : mail_location problem (INBOX) ? In-Reply-To: <1F5342F6-2B5F-4362-A7FF-1EB5EB9D053B@dovecot.fi> References: <1F5342F6-2B5F-4362-A7FF-1EB5EB9D053B@dovecot.fi> Message-ID: <10090841-e0d3-cf53-b797-885fa45ff126@gmail.com> hi Sami, imapc_prefix is not a valid option. but imapc_prefix_list="INBOX" is great ! It does the trick ! Thanks a lot. Regards, C?dric Le 07/12/2016 ? 12:33, Sami Ketola a ?crit : >> On 7 Dec 2016, at 12.22, C?dric ML wrote: >> >> Hello, >> >> I'm trying to migrate mail accounts from an old dovecot 1.0.15 to a new dovecot 2.2.26. >> I've set up a master-user on old dovecot, and I run dsync on new server, like this : >> >> # doveadm -D -o mail_fsync=never sync -R -u user at domain.tld imapc: >> > ? > >> But dovecot is condigured to have ".Trash", ".Junk" etc... folders, not ".INBOX.Trash" >> I've try multiple things : >> - use namespaces for compatibility and add "-n " in sync command, without success >> - modify the mail_location for the user, tried to add LAYOUT=fs, INBOX=, ... without success. >> >> Can anybody help me with that please ? >> > you can try setting imapc_prefix=INBOX and imapc_list_prefix=INBOX or maybe ?INBOX.' > > Sami > From plataleas at gmail.com Wed Dec 7 12:37:49 2016 From: plataleas at gmail.com (plataleas) Date: Wed, 7 Dec 2016 13:37:49 +0100 Subject: Dovecot: Mails flagged as read get flagged as unread In-Reply-To: <3e7882c8-057f-cdfc-5b28-0a88955f2265@myzel.net> References: <2ac2906b-f53e-c088-eb32-7b0167c5e495@gmail.com> <3e7882c8-057f-cdfc-5b28-0a88955f2265@myzel.net> Message-ID: Hi all Thanks for your valuable Inputs! @Peter: we did enable the logs with flag_change. We will try to catch the logs when the issue appears. We try hard to reproduce, but it happens rarely. @Alex: in the logs we do not see any message "Missing middle file seq=..". But we will check this more in detail. Does the "mbox_lazy_writes" settings only affects the mbox backed? In our case we use mdbox, thus disabling this setting would not have any effect, right? regards plataleas On 12/06/2016 11:34 AM, Peter Chiochetti wrote: > Hi, There is a plugin "mail_log" that you can use to audit what > users/user agents are doing, probably mail_log_events flag_change is > helpful? > From ariep at xs4all.nl Thu Dec 8 12:29:03 2016 From: ariep at xs4all.nl (Arie Peterson) Date: Thu, 08 Dec 2016 13:29:03 +0100 Subject: Setting up replication - First steps... In-Reply-To: <3F31434B-F01A-4847-8F4A-F758528BBBEF@starionline.com> References: <3F31434B-F01A-4847-8F4A-F758528BBBEF@starionline.com> Message-ID: <1962830.vvCspnXYLl@pook> SH Development wrote: > [?] > So I believe my first step is to set up another server, on another IP, > different hostname, with Dovecot and Postfix, and simply use the files from > the /etc directories of the existing server to configure it (changing the > IP and hostname of course). > > Am I on the right track so far? > > Next steps involve setting up replication with dsync? > > If I have successfully setup replication between the two servers, does this > mean users can then actually log into either server and have their ?stuff? > intact? So I could set up DNS failover in case the primary server fails? > Would this make the setup acceptable for secondary MX as everything should > sync to the primary server when it comes back online? Yes, this is exactly what I've set up for my site a few weeks ago: the secondary server has almost exactly the same configuration as the primary one, and the secondary server is listed as MX20. Replication with dsync works pretty smoothly. I've myself noticed one case where a mass email deletion took somewhat longer than expected to propagate to the other server. As a user, most of the time it's like you're dealing with a single server. From cedric.malitte at gmail.com Thu Dec 8 13:47:03 2016 From: cedric.malitte at gmail.com (Cedric Malitte) Date: Thu, 8 Dec 2016 08:47:03 -0500 Subject: Setting up replication - First steps... In-Reply-To: <1962830.vvCspnXYLl@pook> References: <3F31434B-F01A-4847-8F4A-F758528BBBEF@starionline.com> <1962830.vvCspnXYLl@pook> Message-ID: I'm also about to deploy such a setup for a "small" mail server. I'll use mysql replication, but only one master server will be writable. I've used virtual machines to test, and so far so good. My plan is to use each server in separate datacenters from the same provider and route the users by dns. I use easydns and made some tests, seems to work fine for failover. 2016-12-08 7:29 GMT-05:00 Arie Peterson : > SH Development wrote: > > [?] > > So I believe my first step is to set up another server, on another IP, > > different hostname, with Dovecot and Postfix, and simply use the files > from > > the /etc directories of the existing server to configure it (changing the > > IP and hostname of course). > > > > Am I on the right track so far? > > > > Next steps involve setting up replication with dsync? > > > > If I have successfully setup replication between the two servers, does > this > > mean users can then actually log into either server and have their > ?stuff? > > intact? So I could set up DNS failover in case the primary server fails? > > Would this make the setup acceptable for secondary MX as everything > should > > sync to the primary server when it comes back online? > > Yes, this is exactly what I've set up for my site a few weeks ago: the > secondary server has almost exactly the same configuration as the primary > one, > and the secondary server is listed as MX20. > > Replication with dsync works pretty smoothly. I've myself noticed one case > where a mass email deletion took somewhat longer than expected to > propagate to > the other server. As a user, most of the time it's like you're dealing > with a > single server. > From dbetz at df.eu Thu Dec 8 10:23:18 2016 From: dbetz at df.eu (Daniel Betz) Date: Thu, 8 Dec 2016 10:23:18 +0000 Subject: Migrate from dovecot 1.1 to 2.2 Maildir to 2.2 mdbox Message-ID: Hello list, im am trying to migrate customer mails via dsync from an old dovecot 1.1 setup to an new installed dovecot 2.2.25 setup with mdbox. Upgrading the old dovecot 1.1 to 2.2 with Maildir isnt an problem and the replication to the new setup works well too. The only problem now is, that the POP3 UIDL are completely wrong on the target setup. Im using for Maildir pop3_uidl_format = %f With mdbox i cant use it anymore. But what do i need for mdbox ? Or is there an way to migrate the POP3 uidl list to the mdbox ? I could live with it, when i were able to mark the mails older 14 days as read. Is there an way to do this on many mailboxes ? I have read in Release News from 2.2.26 that there are some fixes with POP3 UIDL .. what is it in detail and could it help me ? Hop you can point me to the right direction. Regards, Daniel Freundliche Gr??e, Daniel Betz System Design Engineer / Senior Systemadministration ___________________________________ domainfactory GmbH Oskar-Messter-Str. 33 85737 Ismaning Germany Telefon: +49 (0)89 / 55266-364 Telefax: +49 (0)89 / 55266-222 E-Mail: dbetz at df.eu Internet: www.df.eu Registergericht: Amtsgericht M?nchen HRB-Nummer 150294, Gesch?ftsf?hrer: Tobias Mohr, Stephan Wolfram From ebroch at whitehorsetc.com Thu Dec 8 15:31:26 2016 From: ebroch at whitehorsetc.com (Eric Broch) Date: Thu, 8 Dec 2016 08:31:26 -0700 Subject: doveadm Message-ID: <6e5b1bd7-5181-87ac-574e-e134b7bab430@whitehorsetc.com> Hello list, I'm interested in setting up dovecot replication but when I run the command doveadm user '*', which is necessary as indicated here: http://wiki2.dovecot.org/Replication, I get the following output: Error: User listing returned failure Fatal: user listing failed It also indicates the following on the wiki2: "Make sure that user listing is configured for your userdb, this is required by replication to find the list of users that are periodically replicated" I use a vpopmail backup so the question is how do I "Make sure that user listing is configured for...userdb"? This is my userdb settings for vpopmail: userdb { args = cache_key=%u quota_template=quota_rule=*:backend=%q driver = vpopmail } Thank-you Eric From rs at sys4.de Thu Dec 8 16:35:09 2016 From: rs at sys4.de (Robert Schetterer) Date: Thu, 8 Dec 2016 17:35:09 +0100 Subject: Migrate from dovecot 1.1 to 2.2 Maildir to 2.2 mdbox In-Reply-To: References: Message-ID: Am 08.12.2016 um 11:23 schrieb Daniel Betz: > Hello list, > > im am trying to migrate customer mails via dsync from an old dovecot 1.1 setup to an new installed dovecot 2.2.25 setup with mdbox. > Upgrading the old dovecot 1.1 to 2.2 with Maildir isnt an problem and the replication to the new setup works well too. > > The only problem now is, that the POP3 UIDL are completely wrong on the target setup. > Im using for Maildir pop3_uidl_format = %f > With mdbox i cant use it anymore. > > But what do i need for mdbox ? > Or is there an way to migrate the POP3 uidl list to the mdbox ? > > I could live with it, when i were able to mark the mails older 14 days as read. Is there an way to do this on many mailboxes ? > > I have read in Release News from 2.2.26 that there are some fixes with POP3 UIDL .. what is it in detail and could it help me ? > > Hop you can point me to the right direction. > > > Regards, > Daniel For such an extrem version migration with format change you should better use imapsync, this will also give the chance for dry runs and testing before live migration and going production like https://sys4.de/de/blog/2013/04/26/mail-migration-mit-imapsync/ i "guess" you will fail migrate with POP3 uidl in that scenario in any case > > > > > > > Freundliche Gr??e, > > Daniel Betz > System Design Engineer / Senior Systemadministration > ___________________________________ > > domainfactory GmbH > Oskar-Messter-Str. 33 > 85737 Ismaning > Germany > > Telefon: +49 (0)89 / 55266-364 > Telefax: +49 (0)89 / 55266-222 > > E-Mail: dbetz at df.eu > Internet: www.df.eu > > Registergericht: Amtsgericht M?nchen > HRB-Nummer 150294, Gesch?ftsf?hrer: > Tobias Mohr, Stephan Wolfram > Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schlei?heimer Stra?e 26/MG, 80333 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From patrick at soverin.net Thu Dec 8 20:28:09 2016 From: patrick at soverin.net (Patrick van Zweden) Date: Thu, 8 Dec 2016 21:28:09 +0100 Subject: doveadm-server uses 100% cpu and never finishes, dsync backup also never finishes Message-ID: <84C5E0F9-1550-4639-A306-260D65762A3C@soverin.net> Hi Guys, I have a quite interesting problem. I have two servers that replicate to each-other. Suddenly one of the accounts is starting to eat a very large amount of disk space on, what basically is the replica for this account. doveadm-server seems to hang and keeps on filling the disk. I came across this message in the logs: Dec 8 07:36:40 dovecot: dsync-server(): Fatal: pool_system_malloc(6291528): Out of memory Dec 8 07:36:40 dovecot: dsync-server(): Fatal: master: service(doveadm): child 883 returned error 83 (Out of memory (service doveadm { vsz_limit=256 MB }, you may need to increase it) - set DEBUG_OUTOFMEM=1 environment to get core dump) I?ve increased the vsz_limit to 5G so it has stopped complaining. Only? the process never seems to finish. I?ve tried to export the mailbox using dsync: dsync -Dv backup -u 'xxxxx' sdbox:/tmp/patrick_export/ However this process never finishes either. It looks like it stays in one of the mailboxes and keeps on trying to copy messages. Format of the mailbox is sdbox Version of dovecot on all servers: 2.2.9 Any pointers for solving this problem? Kind regards, Patrick -- Patrick van Zweden -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: From toni at solu.fi Thu Dec 8 20:43:11 2016 From: toni at solu.fi (Toni Mattila) Date: Thu, 8 Dec 2016 22:43:11 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) In-Reply-To: <7c8e74c5-cb78-266b-283d-c23cc1add971@dovecot.fi> References: <0e96a9c5-07c4-663a-9ed3-db62cc7ce83d@dovecot.fi> <0376a44e-245b-65bf-a479-93727e06fae6@dovecot.fi> <7c8e74c5-cb78-266b-283d-c23cc1add971@dovecot.fi> Message-ID: Hi, On 06-Dec-16 12:11, Aki Tuomi wrote: > I was able to repeat this bug, thank you for your report. Noticed tss commited https://github.com/dovecot/core/commit/b7a0844fb8dffbf7f1dd0b5c6d30c22ff8cb6bec so testing that now. Cheers, Toni From john at voipsupport.it Thu Dec 8 21:32:40 2016 From: john at voipsupport.it (John Fawcett) Date: Thu, 8 Dec 2016 22:32:40 +0100 Subject: Correct user for replication Message-ID: Hi I've set up replication with the settings below. With these settings, aggregator runs as user dovecot and replicator as user root. Are those the recommended settings or should I change them, in particular for replicator which is running as a privileged user? service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service replicator { unix_listener replicator-doveadm { mode = 0660 group = mail } } service doveadm { inet_listener { port = 999 ssl = yes } } ssl_client_ca_file = /etc/pki/tls/cert.pem doveadm_password = secret plugin { mail_replica = tcps:hostname.domainname.tld:999 } thanks John From aki.tuomi at dovecot.fi Fri Dec 9 07:38:32 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Fri, 9 Dec 2016 09:38:32 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) In-Reply-To: References: <0e96a9c5-07c4-663a-9ed3-db62cc7ce83d@dovecot.fi> <0376a44e-245b-65bf-a479-93727e06fae6@dovecot.fi> <7c8e74c5-cb78-266b-283d-c23cc1add971@dovecot.fi> Message-ID: <6b73d011-0ea4-6b9c-852a-3ae5be89250f@dovecot.fi> On 08.12.2016 22:43, Toni Mattila wrote: > Hi, > > On 06-Dec-16 12:11, Aki Tuomi wrote: >> I was able to repeat this bug, thank you for your report. > > Noticed tss commited > https://github.com/dovecot/core/commit/b7a0844fb8dffbf7f1dd0b5c6d30c22ff8cb6bec > so testing that now. > > Cheers, > Toni Thank you. Please let us know how it went! Aki From ebroch at whitehorsetc.com Fri Dec 9 15:32:07 2016 From: ebroch at whitehorsetc.com (Eric Broch) Date: Fri, 9 Dec 2016 08:32:07 -0700 Subject: doveadm In-Reply-To: <6e5b1bd7-5181-87ac-574e-e134b7bab430@whitehorsetc.com> References: <6e5b1bd7-5181-87ac-574e-e134b7bab430@whitehorsetc.com> Message-ID: On 12/8/2016 8:31 AM, Eric Broch wrote: > Hello list, > > I'm interested in setting up dovecot replication but when I run the > command > doveadm user '*', which is necessary as indicated here: > http://wiki2.dovecot.org/Replication, I get the following output: > > Error: User listing returned failure > Fatal: user listing failed > > It also indicates the following on the wiki2: "Make sure that user > listing is configured for your userdb, this is required by replication > to find the list of users that are periodically replicated" > > I use a vpopmail backup so the question is how do I "Make sure that > user listing is configured for...userdb"? > > This is my userdb settings for vpopmail: > > userdb { > args = cache_key=%u quota_template=quota_rule=*:backend=%q > driver = vpopmail > } > > Thank-you > > Eric Can anyone help me with this? My settings (doveconf -n): auth_cache_size = 32 M auth_mechanisms = plain login digest-md5 cram-md5 first_valid_gid = 89 first_valid_uid = 89 log_path = /var/log/dovecot.log login_greeting = Dovecot toaster ready. mail_plugins = " quota replication notify" namespace { inbox = yes location = prefix = separator = . type = private } passdb { args = cache_key=%u webmail=127.0.0.1 driver = vpopmail } plugin { quota = maildir:ignore=Trash quota_rule = ?:storage=0 } protocols = imap pop3 ssl_cert = References: <84C5E0F9-1550-4639-A306-260D65762A3C@soverin.net> Message-ID: Hi All, Problem solved, turned out the index files were the problem in one mailbox. Deleting them solved the problem Patrick -- Patrick van Zweden > On 08 Dec 2016, at 21:28, Patrick van Zweden wrote: > > Hi Guys, > > I have a quite interesting problem. > > I have two servers that replicate to each-other. Suddenly one of the accounts is starting to eat a very large amount of disk space on, what basically is the replica for this account. doveadm-server seems to hang and keeps on filling the disk. > I came across this message in the logs: > > Dec 8 07:36:40 dovecot: dsync-server(): Fatal: pool_system_malloc(6291528): Out of memory > Dec 8 07:36:40 dovecot: dsync-server(): Fatal: master: service(doveadm): child 883 returned error 83 (Out of memory (service doveadm { vsz_limit=256 MB }, you may need to increase it) - set DEBUG_OUTOFMEM=1 environment to get core dump) > > I?ve increased the vsz_limit to 5G so it has stopped complaining. Only? the process never seems to finish. I?ve tried to export the mailbox using dsync: > dsync -Dv backup -u 'xxxxx' sdbox:/tmp/patrick_export/ > However this process never finishes either. It looks like it stays in one of the mailboxes and keeps on trying to copy messages. > > Format of the mailbox is sdbox > Version of dovecot on all servers: 2.2.9 > > Any pointers for solving this problem? > > Kind regards, > > Patrick > > -- > Patrick van Zweden > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: From toni at solu.fi Sat Dec 10 07:39:18 2016 From: toni at solu.fi (Toni Mattila) Date: Sat, 10 Dec 2016 09:39:18 +0200 Subject: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) In-Reply-To: <6b73d011-0ea4-6b9c-852a-3ae5be89250f@dovecot.fi> References: <0e96a9c5-07c4-663a-9ed3-db62cc7ce83d@dovecot.fi> <0376a44e-245b-65bf-a479-93727e06fae6@dovecot.fi> <7c8e74c5-cb78-266b-283d-c23cc1add971@dovecot.fi> <6b73d011-0ea4-6b9c-852a-3ae5be89250f@dovecot.fi> Message-ID: Hi, On 09-Dec-16 09:38, Aki Tuomi wrote: > Thank you. Please let us know how it went! Haven't seen panics since installing it so looks good. Cheers, Toni From laska at kam.mff.cuni.cz Sat Dec 10 18:11:33 2016 From: laska at kam.mff.cuni.cz (Ladislav Laska) Date: Sat, 10 Dec 2016 19:11:33 +0100 Subject: mail_location in userdb inconsistent with imap and pigeonhole Message-ID: Hi! I'm still fighting with lost mails and what I think is a locking problem. As I've lost some pretty important mails already, I decided to mitigate my troubles by moving to maildir format, which should not be susceptible to these problems. I read the docs and wanted to test on my account, before I mess with all the others and possibly break something. The way to do it seems to be to do an override via userdb. I already have a passwd-file authdb, so I uncommented those few lines in configuration, and added this to my passwd-file: krakonos:{SHA256}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=:1000:100::/home/krakonos:/bin/bash:userdb_mail=maildir:/home/krakonos/Mail Now, I'm not really sure why it has to be prefixed with userdb_, but the example in docs has it, and it seems to work. I've attached the relevant part of a logfile, with some debugging enabled, but in short: Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: Added userdb setting: mail=maildir:/home/krakonos/Mail [...] Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: maildir++: root=/home/krakonos/Mail, index=, indexpvt=, control=, inbox=/home/krakonos/Mail, alt= [...] Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: mbox: INBOX defaulted to /home/krakonos/.mbox/inbox I'm confused why the last line chooses my old mbox over the new location. I'm even more confused by the fact the IMAP works fine, and as I connect from mutt over imap, I can see empty mailboxes (the ~/Mail has only the basic cur/new/tmp structure). However, pigeonhole delivers into the .mbox, and not only if it's for INBOX, but also for spam and others. I read somewhere in the docs that the order is first try userdb, then mail_location and namespaces override the rest. This might be the problem, as I have: mail_location = mbox:~/.mbox namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } Due to inbox=yes this would explain why inbox is using the default path in mail_location. But why even the spam is delivered into the old mbox? And how do I solve the problem anyway, should I just remove the namespace? Anyway, it doesn't explain why the IMAP part and pigeonhole apply different rules and show me different inboxes, which is probably a bug. Thanks! ----------------------------------------------------------------------- Here is the rest of my configuration for reference, the log is attached: ----------------------------------------------------------------------- # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.26-gentoo x86_64 Gentoo Base System release 2.2 auth_username_format = %n hostname = ibex.krakonos.org login_greeting = Dovecot at krakonos.org ready. mail_debug = yes mail_location = mbox:~/.mbox mbox_read_locks = dotlock fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = * driver = pam } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute sieve_execute_socket_dir = sieve-execute sieve_extensions = +vnd.dovecot.filter +editheader sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter sieve_filter_socket_dir = sieve-filter sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_pipe_socket_dir = sieve-pipe sieve_plugins = sieve_extprograms } postmaster_address = postmaster at krakonos.org protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = References: Message-ID: And as always, I didn't attach the file. Here it is. -- S pozdravem Ladislav "Krakono?" L?ska http://www.krakonos.org/ -------------- next part -------------- Dec 10 18:39:15 ibex dovecot: master: Dovecot v2.2.26.0 (23d1de6) starting up for imap Dec 10 18:39:22 ibex dovecot: imap-login: Login: user=, method=PLAIN, rip=77.48.73.189, lip=78.108.107.19, mpid=906, TLS, session= Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: Added userdb setting: mail=maildir:/home/krakonos/Mail Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: Effective uid=1000, gid=100, home=/home/krakonos Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes lo cation=maildir:/home/krakonos/Mail Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: maildir++: root=/home/krakonos/Mail, index=, indexpvt=, control=, inbox=/home/krakonos/Mail, alt= Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: Loading modules from directory: /usr/lib64/dovecot Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: Effective uid=1000, gid=100, home=/home/krakonos Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes loc ation=mbox:~/.mbox Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: mbox: INBOX defaulted to /home/krakonos/.mbox/inbox Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: fs: root=/home/krakonos/.mbox, index=, indexpvt=, control=, inbox=/home/krakonos/.mbox/inbox, alt= Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: userdb lookup skipped, username taken from USER environment Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= From brad at koe.hn Sun Dec 11 15:49:18 2016 From: brad at koe.hn (Brad Koehn) Date: Sun, 11 Dec 2016 09:49:18 -0600 Subject: FTS solr info Message-ID: <514D2F22-EFAC-4C57-82E2-6649CA97C973@koe.hn> Are there updated instructions on setting up FTS with solr? I?m in the midst of upgrading my site and the links don?t appear to work or be applicable to current versions of solr. I grabbed 6.3.0 from apache and the instructions are no longer working, e.g., there?s no `solr/conf/schema.xml` file to replace; the `start.jar` has moved, etc. Just wondering if there?s somewhere else I should look, or if I should just hack it together on my own. Thanks! Brad Koehn From news at mefox.org Sun Dec 11 16:47:56 2016 From: news at mefox.org (Michael Fox) Date: Sun, 11 Dec 2016 08:47:56 -0800 Subject: postlogin script Message-ID: <007a01d253ce$53883710$fa98a530$@mefox.org> I'm using the postlogin service, following the examples in the wiki. But I can't find any documentation on the behavior (what's allowed/not allowed) of the script-login binary. So, some questions: Question 1: The examples show the following at the end of the post-login.sh script: exec "$@" My understanding is that this would exec each of the command line arguments to the post-login.sh script. But, there are no arguments sent to the post-login.sh script in the examples. So what is this line supposed to do? Question 2: One of the examples shows exporting some environmental variables, followed by the above exec line: export MAIL=maildir:/tmp/test export USERDB_KEYS="$USERDB_KEYS mail" exec "$@" Now, I'm really confused. Can someone explain step-by-step why this does anything at all? Question 3: I'd like to be able to pass some information to the post-login.sh script, such as the service (%s), as a positional parameter. For example: executable = script-login /path/post-login.sh %Ls Or even more explicitly: executable = script-login /path/post-login.sh imap But it appears that the script-login binary is expecting only script names to be passed to it so that it can handle more than one script. Is there a way to pass arguments to the different scripts? Thanks, Michael From larryrtx at gmail.com Sun Dec 11 16:52:08 2016 From: larryrtx at gmail.com (Larry Rosenman) Date: Sun, 11 Dec 2016 10:52:08 -0600 Subject: FTS solr info In-Reply-To: <514D2F22-EFAC-4C57-82E2-6649CA97C973@koe.hn> References: <514D2F22-EFAC-4C57-82E2-6649CA97C973@koe.hn> Message-ID: I wound up doing an "add core" via http://host:8983/solr, and then in the DB directory, there's a conf directory where you can put the schema.xml (it then gets renames/parsed to managed-schema. I called my instance dovecot, and it seems to be working fine. On Sun, Dec 11, 2016 at 9:49 AM, Brad Koehn wrote: > Are there updated instructions on setting up FTS with solr? I?m in the > midst of upgrading my site and the links don?t appear to work or be > applicable to current versions of solr. I grabbed 6.3.0 from apache and the > instructions are no longer working, e.g., there?s no `solr/conf/schema.xml` > file to replace; the `start.jar` has moved, etc. > > Just wondering if there?s somewhere else I should look, or if I should > just hack it together on my own. > > Thanks! > > Brad Koehn -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From sysadmin at e-positive.ee Mon Dec 12 11:00:34 2016 From: sysadmin at e-positive.ee (Mart Pirita) Date: Mon, 12 Dec 2016 13:00:34 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. Message-ID: Hello. Few days ago upgraded from v2.2.26.0 >v2.2.27 and now windows 10, with any outlook version (2007,2010,2013,2016) doesn't connect IMAP SSL: Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Warning: SSL failed: where=0x2002: SSLv3 read client certificate A [x.x.x.x] Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL error: Disconnected Dec 12 12:29:35 server dovecot: imap-login: Disconnected (no auth attempts in 0 secs): x.x.x.x, TLS handshaking: Disconnected Is this a bug or some new feature? How to fix it? -- Mart From aki.tuomi at dovecot.fi Mon Dec 12 11:02:01 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 12 Dec 2016 13:02:01 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. In-Reply-To: References: Message-ID: Can you On 12.12.2016 13:00, Mart Pirita wrote: > Hello. > > > Few days ago upgraded from v2.2.26.0 >v2.2.27 and now windows 10, with > any outlook version (2007,2010,2013,2016) doesn't connect IMAP SSL: > > > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: elliptic curve > secp384r1 will be used for ECDH and ECDHE key exchanges > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: elliptic curve > secp384r1 will be used for ECDH and ECDHE key exchanges > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x10, > ret=1: before/accept initialization [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, > ret=1: before/accept initialization [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, > ret=1: SSLv3 read client hello A [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, > ret=1: SSLv3 write server hello A [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, > ret=1: SSLv3 write certificate A [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, > ret=1: SSLv3 write key exchange A [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, > ret=1: SSLv3 write server done A [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2001, > ret=1: SSLv3 flush data [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2002, > ret=-1: SSLv3 read client certificate A [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: where=0x2002, > ret=-1: SSLv3 read client certificate A [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Warning: SSL failed: > where=0x2002: SSLv3 read client certificate A [x.x.x.x] > Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL error: Disconnected > Dec 12 12:29:35 server dovecot: imap-login: Disconnected (no auth > attempts in 0 secs): x.x.x.x, TLS handshaking: Disconnected > > Is this a bug or some new feature? How to fix it? > Can you do doveconf -a | grep auth_mech Aki From sysadmin at e-positive.ee Mon Dec 12 11:29:05 2016 From: sysadmin at e-positive.ee (Mart Pirita) Date: Mon, 12 Dec 2016 13:29:05 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. In-Reply-To: References: Message-ID: Aki Tuomi wrote: > > Can you do > > doveconf -a | grep auth_mech > auth_mechanisms = plain login P.S. Seems this 2.2.24 is the last win10 compatible version (as my testserver doesn't have win10 users and thunderbird works well), any never version gives an error. However I didn't find any hint from http://www.dovecot.org/list/dovecot-news/2016-July/000324.html etc. -- Mart From aki.tuomi at dovecot.fi Mon Dec 12 12:39:35 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 12 Dec 2016 14:39:35 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. In-Reply-To: References: Message-ID: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> On 12.12.2016 13:29, Mart Pirita wrote: > Aki Tuomi wrote: >> Can you do >> >> doveconf -a | grep auth_mech >> > auth_mechanisms = plain login > > P.S. Seems this 2.2.24 is the last win10 compatible version (as my > testserver doesn't have win10 users and thunderbird works well), any > never version gives an error. However I didn't find any hint from > http://www.dovecot.org/list/dovecot-news/2016-July/000324.html etc. > > > https://wiki2.dovecot.org/Debugging/Rawlog can you try this to get rawlogs to find out what happens? Aki From sysadmin at e-positive.ee Mon Dec 12 12:49:18 2016 From: sysadmin at e-positive.ee (Mart Pirita) Date: Mon, 12 Dec 2016 14:49:18 +0200 Subject: Dovecot 2.2.27 > 2.2.24 downgrade errors Message-ID: Hello. Due win10 issue I had to downgrade 2.2.27 > 2.2.24 and now some gettings errors for some users: Dec 12 14:42:17 server dovecot: imap(user): Panic: file mail-index-sync-keywords.c: line 227 (keywords_update_records): assertion failed: (data_offset >= sizeof(struct mail_index_record)) Dec 12 14:42:17 star dovecot: imap(senefelder): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x40185760] -> /usr/lib/dovecot/libdovecot.so.0 [0x401863a6] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x4018590c] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x400d80cf] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_keywords+0x182) [0x400d829a] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x400d9405] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0x2f) [0x400d98cb] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x31c) [0x400d9d24] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x9e) [0x400d17a2] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x400e5f3f] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x400e6241] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_open+0x86) [0x400e635e] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0xa4) [0x400c19e4] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x40076cce] -> /usr Dec 12 14:42:17 server dovecot: imap(user): Fatal: master: service(imap): child 1090 killed with signal 6 (core dumps disabled) I did stop dovecot, removed all dovecot-* and dovecot.* files from user Maildir, still sameerrors. Please advise? -- Mart From aki.tuomi at dovecot.fi Mon Dec 12 12:50:49 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 12 Dec 2016 14:50:49 +0200 Subject: Dovecot 2.2.27 > 2.2.24 downgrade errors In-Reply-To: References: Message-ID: <0082abcf-21e6-21f2-9ecd-1449bcf6300c@dovecot.fi> On 12.12.2016 14:49, Mart Pirita wrote: > Hello. > > Due win10 issue I had to downgrade 2.2.27 > 2.2.24 and now some gettings > errors for some users: > > Dec 12 14:42:17 server dovecot: imap(user): Panic: file > mail-index-sync-keywords.c: line 227 (keywords_update_records): > assertion failed: (data_offset >= sizeof(struct mail_index_record)) > Dec 12 14:42:17 star dovecot: imap(senefelder): Error: Raw backtrace: > /usr/lib/dovecot/libdovecot.so.0 [0x40185760] -> > /usr/lib/dovecot/libdovecot.so.0 [0x401863a6] -> > /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x4018590c] -> > /usr/lib/dovecot/libdovecot-storage.so.0 [0x400d80cf] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_keywords+0x182) > [0x400d829a] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x400d9405] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0x2f) > [0x400d98cb] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x31c) > [0x400d9d24] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x9e) > [0x400d17a2] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x400e5f3f] -> > /usr/lib/dovecot/libdovecot-storage.so.0 [0x400e6241] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_open+0x86) > [0x400e635e] -> > /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0xa4) > [0x400c19e4] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x40076cce] -> > /usr > Dec 12 14:42:17 server dovecot: imap(user): Fatal: master: > service(imap): child 1090 killed with signal 6 (core dumps disabled) > > > I did stop dovecot, removed all dovecot-* and dovecot.* files from user > Maildir, still sameerrors. > > > Please advise? > > Hi! Did you get a core file? Can you install debugging symbols and send gdb /path/to/bin /path/to/core bt full to us? Aki From sysadmin at e-positive.ee Mon Dec 12 13:10:19 2016 From: sysadmin at e-positive.ee (Mart Pirita) Date: Mon, 12 Dec 2016 15:10:19 +0200 Subject: Dovecot 2.2.27 > 2.2.24 downgrade errors In-Reply-To: <0082abcf-21e6-21f2-9ecd-1449bcf6300c@dovecot.fi> References: <0082abcf-21e6-21f2-9ecd-1449bcf6300c@dovecot.fi> Message-ID: Aki Tuomi wrote: > Hi! > > Did you get a core file? Can you install debugging symbols and send > > gdb /path/to/bin /path/to/core > bt full > > to us? > Seems no cores, atleast in /usr/sbin/ ( binary is in /usr/sbin/dovecot) is none. -- Mart From aki.tuomi at dovecot.fi Mon Dec 12 13:22:59 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 12 Dec 2016 15:22:59 +0200 Subject: Dovecot 2.2.27 > 2.2.24 downgrade errors In-Reply-To: References: <0082abcf-21e6-21f2-9ecd-1449bcf6300c@dovecot.fi> Message-ID: <8333ef41-5b3b-fedd-7a56-740f314478cb@dovecot.fi> 1 On 12.12.2016 15:10, Mart Pirita wrote: > Aki Tuomi wrote: >> Hi! >> >> Did you get a core file? Can you install debugging symbols and send >> >> gdb /path/to/bin /path/to/core >> bt full >> >> to us? >> > Seems no cores, atleast in /usr/sbin/ ( binary is in /usr/sbin/dovecot) > is none. > > > http://dovecot.org/bugreport.html Aki From sysadmin at e-positive.ee Mon Dec 12 13:43:26 2016 From: sysadmin at e-positive.ee (Mart Pirita) Date: Mon, 12 Dec 2016 15:43:26 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. In-Reply-To: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> References: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> Message-ID: <213c83f0-54cb-d7e4-f5b5-6c8156b784c8@e-positive.ee> Aki Tuomi wrote: > https://wiki2.dovecot.org/Debugging/Rawlog > > can you try this to get rawlogs to find out what happens? > > Aki I'm bit confused, how this rawlog works. I did: doveadm user -u kaka userdb: kaka user : kaka system_groups_user: kaka uid : 566 gid : 566 home : /home/kaka ls -al /home/kaka total 16 drwx------ 4 kaka kaka 4096 Dec 12 15:36 . drwxr-xr-x 12 root root 4096 Dec 12 12:41 .. drwx------ 2 kaka kaka 4096 Dec 12 12:41 dovecot.rawlog drwx------ 2 kaka kaka 4096 Dec 12 12:41 Maildir Added into dovecot.conf: protocol imap { rawlog_dir = /tmp/rawlog/%u } service imap { executable = imap postlogin } service postlogin { executable = script-login -d rawlog unix_listener postlogin { } } But /tmp/rawlog/kaka/ and /home/kaka/dovecot.rawlog/ are empty. What did I miss? The whole conf: listen = * plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_group_events = no mail_log_fields = uid box msgid size from subject vsize } login_log_format_elements = %u %r %m %c service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service lmtp { unix_listener lmtp { } } service imap { executable = imap postlogin } service pop3 { } service postlogin { executable = script-login -d rawlog unix_listener postlogin { } } service auth { unix_listener auth-userdb { } unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } } service auth-worker { } service dict { unix_listener dict { } } disable_plaintext_auth = no auth_cache_size = 1024 auth_cache_ttl = 1 hour auth_cache_negative_ttl = 1 hour auth_failure_delay = 60 secs auth_mechanisms = plain login passdb { driver = pam args = cache_key=%u%r%s * } userdb { driver = passwd } mail_location = maildir:~/Maildir mail_plugin_dir = /usr/lib/dovecot mail_plugins = $mail_plugins mail_log notify maildir_very_dirty_syncs = yes protocol imap { mail_max_userip_connections = 90 imap_logout_format = bytes=%i/%o imap_client_workarounds = tb-extra-mailbox-sep delay-newmail rawlog_dir = /tmp/rawlog/%u } protocol pop3 { pop3_logout_format = bytes=%i/%o, del=%d/%m, size=%s mail_max_userip_connections = 9 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ssl_cert = References: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> Message-ID: Edit: When using win8, then logs started appear in dovecot.rawlog. But as win10 gives error in ssl level, before user authentication, then no debug logs will be written into user dovecot.rawlog folder. So how to debug this ssl issue? Aki Tuomi wrote: > https://wiki2.dovecot.org/Debugging/Rawlog > > can you try this to get rawlogs to find out what happens? > > Aki I'm bit confused, how this rawlog works. I did: doveadm user -u kaka userdb: kaka user : kaka system_groups_user: kaka uid : 566 gid : 566 home : /home/kaka ls -al /home/kaka total 16 drwx------ 4 kaka kaka 4096 Dec 12 15:36 . drwxr-xr-x 12 root root 4096 Dec 12 12:41 .. drwx------ 2 kaka kaka 4096 Dec 12 12:41 dovecot.rawlog drwx------ 2 kaka kaka 4096 Dec 12 12:41 Maildir Added into dovecot.conf: protocol imap { rawlog_dir = /tmp/rawlog/%u } service imap { executable = imap postlogin } service postlogin { executable = script-login -d rawlog unix_listener postlogin { } } But /tmp/rawlog/kaka/ and /home/kaka/dovecot.rawlog/ are empty. What did I miss? The whole conf: listen = * plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_group_events = no mail_log_fields = uid box msgid size from subject vsize } login_log_format_elements = %u %r %m %c service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service lmtp { unix_listener lmtp { } } service imap { executable = imap postlogin } service pop3 { } service postlogin { executable = script-login -d rawlog unix_listener postlogin { } } service auth { unix_listener auth-userdb { } unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } } service auth-worker { } service dict { unix_listener dict { } } disable_plaintext_auth = no auth_cache_size = 1024 auth_cache_ttl = 1 hour auth_cache_negative_ttl = 1 hour auth_failure_delay = 60 secs auth_mechanisms = plain login passdb { driver = pam args = cache_key=%u%r%s * } userdb { driver = passwd } mail_location = maildir:~/Maildir mail_plugin_dir = /usr/lib/dovecot mail_plugins = $mail_plugins mail_log notify maildir_very_dirty_syncs = yes protocol imap { mail_max_userip_connections = 90 imap_logout_format = bytes=%i/%o imap_client_workarounds = tb-extra-mailbox-sep delay-newmail rawlog_dir = /tmp/rawlog/%u } protocol pop3 { pop3_logout_format = bytes=%i/%o, del=%d/%m, size=%s mail_max_userip_connections = 9 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ssl_cert = References: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> Message-ID: On 12.12.2016 16:21, Mart Pirita wrote: > Edit: When using win8, then logs started appear in dovecot.rawlog. But > as win10 gives error in ssl level, before user authentication, then no > debug logs will be written into user dovecot.rawlog folder. > > So how to debug this ssl issue? > > > Aki Tuomi wrote: >> https://wiki2.dovecot.org/Debugging/Rawlog >> >> can you try this to get rawlogs to find out what happens? >> >> Aki > I'm bit confused, how this rawlog works. I did: > > doveadm user -u kaka > userdb: kaka > user : kaka > system_groups_user: kaka > uid : 566 > gid : 566 > home : /home/kaka > > ls -al /home/kaka > total 16 > drwx------ 4 kaka kaka 4096 Dec 12 15:36 . > drwxr-xr-x 12 root root 4096 Dec 12 12:41 .. > drwx------ 2 kaka kaka 4096 Dec 12 12:41 dovecot.rawlog > drwx------ 2 kaka kaka 4096 Dec 12 12:41 Maildir > > Added into dovecot.conf: > > protocol imap { > rawlog_dir = /tmp/rawlog/%u > } > > service imap { > executable = imap postlogin > } > > service postlogin { > executable = script-login -d rawlog > unix_listener postlogin { > } > } > > But /tmp/rawlog/kaka/ and /home/kaka/dovecot.rawlog/ are empty. What did > I miss? > > > The whole conf: > > listen = * > plugin { > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename > mail_log_group_events = no > mail_log_fields = uid box msgid size from subject vsize > } > login_log_format_elements = %u %r %m %c > service imap-login { > inet_listener imap { > port = 0 > } > inet_listener imaps { > port = 993 > ssl = yes > } > } > service pop3-login { > inet_listener pop3 { > port = 110 > } > inet_listener pop3s { > port = 995 > ssl = yes > } > } > service lmtp { > unix_listener lmtp { > } > } > service imap { > executable = imap postlogin > } > service pop3 { > } > service postlogin { > executable = script-login -d rawlog > unix_listener postlogin { > } > } > service auth { > unix_listener auth-userdb { > } > unix_listener /var/spool/postfix/private/auth { > mode = 0666 > user = postfix > group = postfix > } > } > service auth-worker { > } > service dict { > unix_listener dict { > } > } > disable_plaintext_auth = no > auth_cache_size = 1024 > auth_cache_ttl = 1 hour > auth_cache_negative_ttl = 1 hour > auth_failure_delay = 60 secs > auth_mechanisms = plain login > passdb { > driver = pam > args = cache_key=%u%r%s * > } > userdb { > driver = passwd > } > mail_location = maildir:~/Maildir > mail_plugin_dir = /usr/lib/dovecot > mail_plugins = $mail_plugins mail_log notify > maildir_very_dirty_syncs = yes > protocol imap { > mail_max_userip_connections = 90 > imap_logout_format = bytes=%i/%o > imap_client_workarounds = tb-extra-mailbox-sep delay-newmail > rawlog_dir = /tmp/rawlog/%u > } > protocol pop3 { > pop3_logout_format = bytes=%i/%o, del=%d/%m, size=%s > mail_max_userip_connections = 9 > pop3_client_workarounds = outlook-no-nuls oe-ns-eoh > } > ssl_cert = ssl_key = ssl_parameters_regenerate = 0 > ssl_protocols = !SSLv2 !SSLv3 > plugin { > } > plugin { > } > plugin { > } > plugin { > } > plugin { > } > plugin { > } > plugin { > } > > This sounds like issue with SSL itself. Is your certificate self-signed or issued by some trusted CA? Aki From jerry at seibercom.net Mon Dec 12 17:54:20 2016 From: jerry at seibercom.net (Jerry) Date: Mon, 12 Dec 2016 12:54:20 -0500 Subject: Dovecot 2.2.27 > 2.2.24 downgrade errors In-Reply-To: References: Message-ID: <20161212125420.00006b44@seibercom.net> On Mon, 12 Dec 2016 14:49:18 +0200, Mart Pirita stated: >Hello. > >Due win10 issue I had to downgrade 2.2.27 > 2.2.24 and now some >gettings errors for some users: > >Dec 12 14:42:17 server dovecot: imap(user): Panic: file >mail-index-sync-keywords.c: line 227 (keywords_update_records): >assertion failed: (data_offset >= sizeof(struct mail_index_record)) >Dec 12 14:42:17 star dovecot: imap(senefelder): Error: Raw backtrace: >/usr/lib/dovecot/libdovecot.so.0 [0x40185760] -> >/usr/lib/dovecot/libdovecot.so.0 [0x401863a6] -> >/usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x4018590c] -> >/usr/lib/dovecot/libdovecot-storage.so.0 [0x400d80cf] -> >/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_keywords+0x182) >[0x400d829a] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x400d9405] >-> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0x2f) >[0x400d98cb] -> >/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x31c) >[0x400d9d24] -> >/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x9e) >[0x400d17a2] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x400e5f3f] >-> /usr/lib/dovecot/libdovecot-storage.so.0 [0x400e6241] -> >/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_open+0x86) >[0x400e635e] -> >/usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0xa4) >[0x400c19e4] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x40076cce] >-> /usr >Dec 12 14:42:17 server dovecot: imap(user): Fatal: master: >service(imap): child 1090 killed with signal 6 (core dumps disabled) > > >I did stop dovecot, removed all dovecot-* and dovecot.* files from user >Maildir, still sameerrors. > > >Please advise? I am not sure what your problem is. I have Dovecot 2.2.27 installed on a FreeBSD-11 machine. I also have Windows 10 PRO 64 bit, version 1607, and Outlook 2016. It is now and has been working just fine. Somehow you have something bonked on your system(s). -- Jerry From sysadmin at e-positive.ee Mon Dec 12 18:05:50 2016 From: sysadmin at e-positive.ee (Mart Pirita) Date: Mon, 12 Dec 2016 20:05:50 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. In-Reply-To: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> References: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> Message-ID: <1b209970-ab32-cc56-9a6c-85f1b9bedc02@e-positive.ee> Edit: Maybe it's the DH file issue (like https://i-mscp.net/index.php/Thread/10005-Notice-SSL-for-services-with-Courier-Windows-10-issue/), so added to the conf: ssl_dh_parameters_length = 2048 removed old file /usr/var/lib/dovecot/ssl-parameters.dat and dovecot generated new file. Still same error. Stared to look files timestaps and found the reason. I have a RH based custom disto and I'm using self compiled openssl, simple make, without any special options: ./config --prefix=/usr/local/ssl && make && make install And at some point, after building dovecot 2.2.24, I built new openssl, openssl-1.0.1t and with this and also with latest openssl-1.0.2j dovecot builds fine but doesn't work with windows 10. So finally I built latest openssl-0.9.8zh and dovecot 2.2.27 against it and windows 10 works like a charm. But I'm still curios, why latest openssl and latest dovecot doesn't work for windows 10. As new openssl should even provide more options, than older. /usr/local/ssl/bin/openssl version -a OpenSSL 0.9.8za 5 Jun 2014 built on: Wed Aug 6 15:45:46 EEST 2014 platform: linux-elf options: bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) idea(int) blowfish(idx) compiler: gcc -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -DL_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM OPENSSLDIR: "/usr/local/ssl/ssl" /usr/local/ssl/bin/openssl version -o options: bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) idea(int) blowfish(idx) ################## /usr/local/ssl/bin/openssl version -a OpenSSL 1.0.2j 26 Sep 2016 built on: reproducible build, date unspecified platform: linux-elf options: bn(64,32) rc4(1x,char) des(ptr,risc1,16,long) idea(int) blowfish(idx) compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -DL_ENDIAN -O3 -fomit-frame-pointer -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM OPENSSLDIR: "/usr/local/ssl/ssl" /usr/local/ssl/bin/openssl version -o options: bn(64,32) rc4(1x,char) des(ptr,risc1,16,long) idea(int) blowfish(idx) ############### Edit: When using win8, then logs started appear in dovecot.rawlog. But as win10 gives error in ssl level, before user authentication, then no debug logs will be written into user dovecot.rawlog folder. So how to debug this ssl issue? Aki Tuomi wrote: > https://wiki2.dovecot.org/Debugging/Rawlog > > can you try this to get rawlogs to find out what happens? > > Aki I'm bit confused, how this rawlog works. I did: doveadm user -u kaka userdb: kaka user : kaka system_groups_user: kaka uid : 566 gid : 566 home : /home/kaka ls -al /home/kaka total 16 drwx------ 4 kaka kaka 4096 Dec 12 15:36 . drwxr-xr-x 12 root root 4096 Dec 12 12:41 .. drwx------ 2 kaka kaka 4096 Dec 12 12:41 dovecot.rawlog drwx------ 2 kaka kaka 4096 Dec 12 12:41 Maildir Added into dovecot.conf: protocol imap { rawlog_dir = /tmp/rawlog/%u } service imap { executable = imap postlogin } service postlogin { executable = script-login -d rawlog unix_listener postlogin { } } But /tmp/rawlog/kaka/ and /home/kaka/dovecot.rawlog/ are empty. What did I miss? The whole conf: listen = * plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_group_events = no mail_log_fields = uid box msgid size from subject vsize } login_log_format_elements = %u %r %m %c service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service lmtp { unix_listener lmtp { } } service imap { executable = imap postlogin } service pop3 { } service postlogin { executable = script-login -d rawlog unix_listener postlogin { } } service auth { unix_listener auth-userdb { } unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } } service auth-worker { } service dict { unix_listener dict { } } disable_plaintext_auth = no auth_cache_size = 1024 auth_cache_ttl = 1 hour auth_cache_negative_ttl = 1 hour auth_failure_delay = 60 secs auth_mechanisms = plain login passdb { driver = pam args = cache_key=%u%r%s * } userdb { driver = passwd } mail_location = maildir:~/Maildir mail_plugin_dir = /usr/lib/dovecot mail_plugins = $mail_plugins mail_log notify maildir_very_dirty_syncs = yes protocol imap { mail_max_userip_connections = 90 imap_logout_format = bytes=%i/%o imap_client_workarounds = tb-extra-mailbox-sep delay-newmail rawlog_dir = /tmp/rawlog/%u } protocol pop3 { pop3_logout_format = bytes=%i/%o, del=%d/%m, size=%s mail_max_userip_connections = 9 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ssl_cert = References: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> Message-ID: On 12/12/2016 10:42 AM, Aki Tuomi wrote: > > > On 12.12.2016 16:21, Mart Pirita wrote: >> Edit: When using win8, then logs started appear in dovecot.rawlog. But >> as win10 gives error in ssl level, before user authentication, then no >> debug logs will be written into user dovecot.rawlog folder. >> >> So how to debug this ssl issue? >> >> >> Aki Tuomi wrote: >>> https://wiki2.dovecot.org/Debugging/Rawlog >>> >>> can you try this to get rawlogs to find out what happens? >>> >>> Aki >> I'm bit confused, how this rawlog works. I did: >> >> doveadm user -u kaka >> userdb: kaka >> user : kaka >> system_groups_user: kaka >> uid : 566 >> gid : 566 >> home : /home/kaka >> >> ls -al /home/kaka >> total 16 >> drwx------ 4 kaka kaka 4096 Dec 12 15:36 . >> drwxr-xr-x 12 root root 4096 Dec 12 12:41 .. >> drwx------ 2 kaka kaka 4096 Dec 12 12:41 dovecot.rawlog >> drwx------ 2 kaka kaka 4096 Dec 12 12:41 Maildir >> >> Added into dovecot.conf: >> >> protocol imap { >> rawlog_dir = /tmp/rawlog/%u >> } >> >> service imap { >> executable = imap postlogin >> } >> >> service postlogin { >> executable = script-login -d rawlog >> unix_listener postlogin { >> } >> } >> >> But /tmp/rawlog/kaka/ and /home/kaka/dovecot.rawlog/ are empty. What did >> I miss? >> >> >> The whole conf: >> >> listen = * >> plugin { >> mail_log_events = delete undelete expunge copy mailbox_delete >> mailbox_rename >> mail_log_group_events = no >> mail_log_fields = uid box msgid size from subject vsize >> } >> login_log_format_elements = %u %r %m %c >> service imap-login { >> inet_listener imap { >> port = 0 >> } >> inet_listener imaps { >> port = 993 >> ssl = yes >> } >> } >> service pop3-login { >> inet_listener pop3 { >> port = 110 >> } >> inet_listener pop3s { >> port = 995 >> ssl = yes >> } >> } >> service lmtp { >> unix_listener lmtp { >> } >> } >> service imap { >> executable = imap postlogin >> } >> service pop3 { >> } >> service postlogin { >> executable = script-login -d rawlog >> unix_listener postlogin { >> } >> } >> service auth { >> unix_listener auth-userdb { >> } >> unix_listener /var/spool/postfix/private/auth { >> mode = 0666 >> user = postfix >> group = postfix >> } >> } >> service auth-worker { >> } >> service dict { >> unix_listener dict { >> } >> } >> disable_plaintext_auth = no >> auth_cache_size = 1024 >> auth_cache_ttl = 1 hour >> auth_cache_negative_ttl = 1 hour >> auth_failure_delay = 60 secs >> auth_mechanisms = plain login >> passdb { >> driver = pam >> args = cache_key=%u%r%s * >> } >> userdb { >> driver = passwd >> } >> mail_location = maildir:~/Maildir >> mail_plugin_dir = /usr/lib/dovecot >> mail_plugins = $mail_plugins mail_log notify >> maildir_very_dirty_syncs = yes >> protocol imap { >> mail_max_userip_connections = 90 >> imap_logout_format = bytes=%i/%o >> imap_client_workarounds = tb-extra-mailbox-sep delay-newmail >> rawlog_dir = /tmp/rawlog/%u >> } >> protocol pop3 { >> pop3_logout_format = bytes=%i/%o, del=%d/%m, size=%s >> mail_max_userip_connections = 9 >> pop3_client_workarounds = outlook-no-nuls oe-ns-eoh >> } >> ssl_cert = > ssl_key = > ssl_parameters_regenerate = 0 >> ssl_protocols = !SSLv2 !SSLv3 >> plugin { >> } >> plugin { >> } >> plugin { >> } >> plugin { >> } >> plugin { >> } >> plugin { >> } >> plugin { >> } >> >> > > This sounds like issue with SSL itself. Is your certificate > self-signed or issued by some trusted CA? > > Aki I don't mean to but in but my dovecot-2.2.27 running on CentOS 6/CentOS 7 with Outlook 2007/2013 is working just fine. Also, Outlook doesn't allow storage of a certificate like Thunderbird but it does allow you to accept it (every time one opens Outlook) and open. From sysadmin at e-positive.ee Mon Dec 12 18:21:37 2016 From: sysadmin at e-positive.ee (Mart Pirita) Date: Mon, 12 Dec 2016 20:21:37 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. In-Reply-To: References: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> Message-ID: <51db5df1-6fbb-1c74-fa9c-0a1be3a0abaf@e-positive.ee> Aki Tuomi wrote: > This sounds like issue with SSL itself. Is your certificate self-signed > or issued by some trusted CA? > Self-signed. -- Mart From sysadmin at e-positive.ee Mon Dec 12 18:21:46 2016 From: sysadmin at e-positive.ee (Mart Pirita) Date: Mon, 12 Dec 2016 20:21:46 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. In-Reply-To: References: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> Message-ID: Eric Broch wrote: > > Also, Outlook doesn't allow storage of a certificate like Thunderbird > but it does allow you to accept it (every time one opens Outlook) and open. Install certificate to the trusted root and no pop-ups -s anymore:). -- Mart From aki.tuomi at dovecot.fi Mon Dec 12 18:53:25 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 12 Dec 2016 20:53:25 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. In-Reply-To: References: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> Message-ID: On 12.12.2016 20:21, Mart Pirita wrote: > Eric Broch wrote: >> Also, Outlook doesn't allow storage of a certificate like Thunderbird >> but it does allow you to accept it (every time one opens Outlook) and open. > Install certificate to the trusted root and no pop-ups -s anymore:). > > Or spend 10 minutes to get one from LetsEncrypt for free? =) Aki From sysadmin at e-positive.ee Mon Dec 12 19:25:07 2016 From: sysadmin at e-positive.ee (Mart Pirita) Date: Mon, 12 Dec 2016 21:25:07 +0200 Subject: Dovecot 2.2.27 & windows 10 outlook (no auth attempts in 0 secs) error. In-Reply-To: References: <5ee8c106-19da-26d6-de50-4153b49d308a@dovecot.fi> Message-ID: Aki Tuomi wrote: > > Or spend 10 minutes to get one from LetsEncrypt for free? =) > > Yes and no. It requires after every 3 months renewing and hasse with dns, certbot etc. Sometimes, in own company, long and self-signed is more usable:). -- Mart From doctor at doctor.nl2k.ab.ca Mon Dec 12 21:08:51 2016 From: doctor at doctor.nl2k.ab.ca (The Doctor) Date: Mon, 12 Dec 2016 14:08:51 -0700 Subject: Dovcot issues Message-ID: <20161212210851.GA35681@doctor.nl2k.ab.ca> I am seeing issues with Thunderbird IMAP and POP3 and Entourage issues of non-deleting / repeating e-mail. Any one else gettting that? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Merry Christmas 2016 and Happy New Year 2017 From ler at lerctr.org Mon Dec 12 21:16:35 2016 From: ler at lerctr.org (Larry Rosenman) Date: Mon, 12 Dec 2016 15:16:35 -0600 Subject: Dovcot issues In-Reply-To: <20161212210851.GA35681@doctor.nl2k.ab.ca> References: <20161212210851.GA35681@doctor.nl2k.ab.ca> Message-ID: On 2016-12-12 15:08, The Doctor wrote: > I am seeing issues with > Thunderbird > > IMAP and POP3 > > and > > Entourage issues > > of non-deleting / repeating e-mail. > > Any one else gettting that? Not I. Which Dovecot release? Pigeonhole? Mailbox format? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler at lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From doctor at doctor.nl2k.ab.ca Tue Dec 13 00:57:49 2016 From: doctor at doctor.nl2k.ab.ca (The Doctor) Date: Mon, 12 Dec 2016 17:57:49 -0700 Subject: Dovcot issues In-Reply-To: References: <20161212210851.GA35681@doctor.nl2k.ab.ca> Message-ID: <20161213005749.GB74126@doctor.nl2k.ab.ca> On Mon, Dec 12, 2016 at 03:16:35PM -0600, Larry Rosenman wrote: > On 2016-12-12 15:08, The Doctor wrote: > > I am seeing issues with > > Thunderbird > > > > IMAP and POP3 > > > > and > > > > Entourage issues > > > > of non-deleting / repeating e-mail. > > > > Any one else gettting that? > Not I. Which Dovecot release? Pigeonhole? Mailbox format? Dovcote 2.2.27 using mbox. > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: ler at lerctr.org > US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Merry Christmas 2016 and Happy New Year 2017 From ler at lerctr.org Tue Dec 13 01:11:13 2016 From: ler at lerctr.org (Larry Rosenman) Date: Mon, 12 Dec 2016 19:11:13 -0600 Subject: Dovcot issues In-Reply-To: <20161213005749.GB74126@doctor.nl2k.ab.ca> References: <20161212210851.GA35681@doctor.nl2k.ab.ca> <20161213005749.GB74126@doctor.nl2k.ab.ca> Message-ID: <856314736e6025b482f75493ae435fcd@lerctr.org> On 2016-12-12 18:57, The Doctor wrote: > On Mon, Dec 12, 2016 at 03:16:35PM -0600, Larry Rosenman wrote: >> On 2016-12-12 15:08, The Doctor wrote: >> > I am seeing issues with >> > Thunderbird >> > >> > IMAP and POP3 >> > >> > and >> > >> > Entourage issues >> > >> > of non-deleting / repeating e-mail. >> > >> > Any one else gettting that? >> Not I. Which Dovecot release? Pigeonhole? Mailbox format? > > Dovcote 2.2.27 using mbox. > Same Here, FreeBSD with no issues whatsoever. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler at lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From doctor at doctor.nl2k.ab.ca Tue Dec 13 01:55:46 2016 From: doctor at doctor.nl2k.ab.ca (The Doctor) Date: Mon, 12 Dec 2016 18:55:46 -0700 Subject: Dovcot issues In-Reply-To: <856314736e6025b482f75493ae435fcd@lerctr.org> References: <20161212210851.GA35681@doctor.nl2k.ab.ca> <20161213005749.GB74126@doctor.nl2k.ab.ca> <856314736e6025b482f75493ae435fcd@lerctr.org> Message-ID: <20161213015546.GA84504@doctor.nl2k.ab.ca> On Mon, Dec 12, 2016 at 07:11:13PM -0600, Larry Rosenman wrote: > On 2016-12-12 18:57, The Doctor wrote: > > On Mon, Dec 12, 2016 at 03:16:35PM -0600, Larry Rosenman wrote: > >> On 2016-12-12 15:08, The Doctor wrote: > >> > I am seeing issues with > >> > Thunderbird > >> > > >> > IMAP and POP3 > >> > > >> > and > >> > > >> > Entourage issues > >> > > >> > of non-deleting / repeating e-mail. > >> > > >> > Any one else gettting that? > >> Not I. Which Dovecot release? Pigeonhole? Mailbox format? > > > > Dovcote 2.2.27 using mbox. > > > > Same Here, FreeBSD with no issues whatsoever. > Looks like the problem is that /var/mail was switched back to chmod 0755 when it should be 1775 or 1777. > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: ler at lerctr.org > US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Merry Christmas 2016 and Happy New Year 2017 From thorsten.hater at gmail.com Tue Dec 13 09:48:42 2016 From: thorsten.hater at gmail.com (Thorsten Hater) Date: Tue, 13 Dec 2016 10:48:42 +0100 Subject: mailboxes and capitalisation Message-ID: Dear all, I have set up a series of special-use mailboxes in the default namespace differing by capitalisation of the names, mainly to capture multiple mailboxes with autoexpunge namespace inbox { ... mailbox Trash { auto = no autoexpunge = 30d special_use = \Trash } mailbox trash { auto = no autoexpunge = 30d special_use = \Trash } ... } However, doveconf -n reports only one mailbox, namely the second (lowercase t) and autoexpunge does not trigger for the first one (capital T). Removing the special use flag has no influence. namespace inbox { inbox = yes list = children location = ... mailbox trash { auto = subscribe special_use = \Trash } ... prefix = INBOX. separator = . subscriptions = yes type = private } Is this the intended behaviour? The example 15-mailboxes.conf seems to indicate otherwise and I would prefer the ability to set autoexpunge for both Trash and trash. (dovecot 2.2.26 built from source on Debian 8.0) Best regards, Thorsten From havrla at lhotkanet.cz Tue Dec 13 11:56:59 2016 From: havrla at lhotkanet.cz (Havrla) Date: Tue, 13 Dec 2016 12:56:59 +0100 Subject: replication and backend vpopmail Message-ID: Heloo, please I need "replicate" dovecot / dsync. Prerequisite: doveadm user '*' [Root @ joe ~] # doveadm user '' ' Error: User listing Returned failure Fatal: user listing failed It probably does not work because I have: userdb{ args = cache_key =% u quota_template quota_rule = = *: backend = q% driver = vpopmail } The manual is written: iterate_query = SELECT email as user FROM mail_user But does not specify how to connect to MySQL database if vpopmail How to do it ? To make it simple, vpopmail domain = DB table example domain example.com = table example_com [root at franta ~]# mysql vpopmail MariaDB [vpopmail]> desc lhotkanet_cz; +-----------------+-----------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-----------------+-----------+------+-----+---------+-------+ | pw_name | char(32) | NO | PRI | | | | pw_passwd | char(40) | YES | | NULL | | | pw_uid | int(11) | YES | | NULL | | | pw_gid | int(11) | YES | | NULL | | | pw_gecos | char(48) | YES | | NULL | | | pw_dir | char(160) | YES | | NULL | | | pw_shell | char(20) | YES | | NULL | | | pw_clear_passwd | char(16) | YES | | NULL | | +-----------------+-----------+------+-----+---------+-------+ 8 rows in set (0.00 sec) MariaDB [vpopmail]> Thank you. Havrla From mikefroehner at gmx.de Tue Dec 13 14:47:12 2016 From: mikefroehner at gmx.de (=?UTF-8?Q?Mike_Fr=c3=b6hner?=) Date: Tue, 13 Dec 2016 15:47:12 +0100 Subject: public folder subscriptions sync issue with ldap user/group in dovecot-acl Message-ID: <3ad12db0-c224-5652-e99b-6625fb236aca@gmx.de> Hello people, I am having an issue with 'doveadm sync'. I am currently trying to have two dovecots behind an haproxy (works fine). Therefore I configured these two dovecot server (imap-1/imap-2) to sync throught dsync. This works just partly. The sync of the maiboxes is fine, but the sync of the subscriptions file just works partly. It works for private folder subscription, but not completly for public folder subscription. I found two issues, if I am using LDAP (user/groups) in dovecot ACLs. 1. I would like to subscribe 2 public folder (public/test/test1 and public/test/test2). My user (ldaptestuser) is an ldap user and this user is member of the ldap group (ldaptestgroup) which does have all dovecot-acl rights on these folders. imap-1 # cat /opt/mail/_public/publictest/.test*/dovecot-acl group=ldaptestgroup akxeilprwts group=ldaptestgroup akxeilprwts I am now connecting with my mail client to imap-1 (throught haproxy) and the subscription to this folder works. The file which is written looks like: imap-1 # cat /opt/mail/ldaptestuser/Mails/subscriptions Sent publictest/test/test1 publictest/test/test2 Now I am awaiting the synch to imap-2, but the file which it written looks like: imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions Sent If I modify the dovecot-acl for .test1 to imap-1 # cat /opt/mail/_public/publictest/.test1/dovecot-acl group=ldaptestgroup akxeilprwts user=ldaptestuser akxeilprwts and execute the subscription again - the synced file looks like: imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions Sent publictest/test/test1 The subscription of public folder test2 will also been synced, if I add my ldaptestuser to the acl file for this folder. 2. Another issue is to unsubscribe a public folder. If I unsubscribe folder test1, it is written to subscriptions file on the imap where I am connected, but it is NOT synced even if my user and group are configured at the dovecot-acl file. If I then unsubscribe a not public folder (like Sent), the former unsubscribed folder test1 is (faulty) subscribed again. But both imap do have the same subscriptions for my ldaptestuser user. I do have the behavior with dovecot-2.2.26 and dovecot-2.2.27 on CentOS-7 (selinux disabled). If you need more information like the dovecot -n or some other stuff give me a short notice. Mike; From tanstaafl at libertytrek.org Tue Dec 13 15:08:29 2016 From: tanstaafl at libertytrek.org (Tanstaafl) Date: Tue, 13 Dec 2016 10:08:29 -0500 Subject: mailboxes and capitalisation In-Reply-To: References: Message-ID: On 12/13/2016 4:48 AM, Thorsten Hater wrote: > I have set up a series of special-use mailboxes in the default namespace > differing by capitalisation of the names, mainly to capture multiple > mailboxes > with autoexpunge > > namespace inbox { > ... > mailbox Trash { > auto = no > autoexpunge = 30d > special_use = \Trash > } > mailbox trash { > auto = no > autoexpunge = 30d > special_use = \Trash > } Ugh... why create such a huge pain point for yourself? I would never allow case sensitivity for usernames, or mail storage. Makes no sense. From skdovecot at smail.inf.fh-brs.de Tue Dec 13 15:16:16 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 13 Dec 2016 16:16:16 +0100 (CET) Subject: mailboxes and capitalisation In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 13 Dec 2016, Tanstaafl wrote: > On 12/13/2016 4:48 AM, Thorsten Hater wrote: >> I have set up a series of special-use mailboxes in the default namespace >> differing by capitalisation of the names, mainly to capture multiple >> mailboxes >> with autoexpunge >> >> namespace inbox { >> ... >> mailbox Trash { >> auto = no >> autoexpunge = 30d >> special_use = \Trash >> } >> mailbox trash { >> auto = no >> autoexpunge = 30d >> special_use = \Trash >> } > > Ugh... why create such a huge pain point for yourself? > > I would never allow case sensitivity for usernames, or mail storage. > Makes no sense. it starts with missing standards and device- or application-specific ways to do the same thing. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWFAQwHz1H7kL/d9rAQJkxwf/ea5WVv13qiPWhEUvNSKwIAXbgUDRbxru YJRYvqc9MpNDi+WibI0/2KojbjH2dxMk2xTRGfDodfkDd41Eue0npKaTR1/D49YZ CNT34yQMHGVpGyRQbRSsLncoMTrtGx9S8xYS/JwTWXgZ6B7FFYe00ypXVp8T6mxu O+/yre/DUfkTZW/0pqMj2i0kbL2NAeb6A1dSOxMuOCS2U4T5ZYNB6MuA6kIZsZ+S ZDvRx0uNJSRpS9hjdNdRFJ/ODyAdAE97LNqJTGUwSVlXHnTo3b4ibuLWHO9F4xs0 Cy/kRmpvxnyStcBaQqkARGefSRpp/hHI0E7X8AylDJpY4Ib38g5tmg== =ZiGg -----END PGP SIGNATURE----- From tanstaafl at libertytrek.org Tue Dec 13 15:33:50 2016 From: tanstaafl at libertytrek.org (Tanstaafl) Date: Tue, 13 Dec 2016 10:33:50 -0500 Subject: JMAP support in Dovecot In-Reply-To: <385273315.256.1480242517370@appsuite-dev.open-xchange.com> References: <5839DD54.2060705@carpenter.org> <20161126191625.2js5gzt5zuoq4sm6@nordisch.org> <385273315.256.1480242517370@appsuite-dev.open-xchange.com> Message-ID: <69ad3b1d-dbfd-9451-3e93-ccaad8f567b5@libertytrek.org> Hi Aki, Someone just asked in the bug for Thunderbird for this, so... Is there a git branch that they could use to start playing with what is there? If not, any idea when that might happen? It sounds like someone following the Thunderbird bug is interested in working on this, but they obviously need something to test against. Thanks, Charles On 11/27/2016 5:28 AM, Aki Tuomi wrote: > Hi! > > We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 > > Aki Tuomi > > Dovecot Oy > >> On November 26, 2016 at 11:17 PM Andrew Jones wrote: >> >> >> Hi Marcus >> >> Thanks for your helpful reply. >> >> Do you know what is going on with JMAP development into Dovecot 2.5? >> >> It's difficult to get any sort of information from the roadmap and there are no Dovecot forums. >> >> One of the main reasons I'm interested in JMAP is because of Roundcube Next and also the other clients it will power. Sadly, there has been little going on and having emailed Thomas, he is no longer involved in Roundcube Next - which is a shame. The Kolab guys are really taking liberties here, and trying their product, the thing is littered with bugs everywhere. >> >> Are you able to comment on what is going on with JMAP development into Dovecot? >> >> Thanks >> >> Andrew >> >> >> >> >> Sent from my iPhone >> >>> On 26 Nov 2016, at 19:16, Marcus Rueckert wrote: >>> >>>> On 2016-11-26 11:07:00 -0800, WJCarpenter wrote: >>>> I don't know the answer to that question, but I am curious about something. >>>> What client are you thinking about using with JMAP? I haven't found much. >>>> (And much of the demo stuff at jmap.io seems to be busted in various ways.) >>> >>> roundcube-next builds on top of it. >>> >>> darix >>> >>> -- >>> openSUSE - SUSE Linux is my linux >>> openSUSE is good for you >>> www.opensuse.org From thorsten.hater at gmail.com Tue Dec 13 15:44:54 2016 From: thorsten.hater at gmail.com (Thorsten Hater) Date: Tue, 13 Dec 2016 16:44:54 +0100 Subject: mailboxes and capitalisation In-Reply-To: References: Message-ID: As far as I understand IMAP folders are -- largely -- case-sensitive, so I need to plan for Trash and trash (and worse), as there is no standard. Further, I cannot really expect all MUAs to honor special-use flags. My intention is to cover the most likely cases with autoexpunge. I am still wondering if this behaviour is correct, given the case-sensitivity of IMAP. Thorsten On Tue, Dec 13, 2016 at 4:16 PM, Steffen Kaiser < skdovecot at smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Tue, 13 Dec 2016, Tanstaafl wrote: > >> On 12/13/2016 4:48 AM, Thorsten Hater wrote: >> >>> I have set up a series of special-use mailboxes in the default namespace >>> differing by capitalisation of the names, mainly to capture multiple >>> mailboxes >>> with autoexpunge >>> >>> namespace inbox { >>> ... >>> mailbox Trash { >>> auto = no >>> autoexpunge = 30d >>> special_use = \Trash >>> } >>> mailbox trash { >>> auto = no >>> autoexpunge = 30d >>> special_use = \Trash >>> } >>> >> >> Ugh... why create such a huge pain point for yourself? >> >> I would never allow case sensitivity for usernames, or mail storage. >> Makes no sense. >> > > it starts with missing standards and device- or application-specific ways > to do the same thing. > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEVAwUBWFAQwHz1H7kL/d9rAQJkxwf/ea5WVv13qiPWhEUvNSKwIAXbgUDRbxru > YJRYvqc9MpNDi+WibI0/2KojbjH2dxMk2xTRGfDodfkDd41Eue0npKaTR1/D49YZ > CNT34yQMHGVpGyRQbRSsLncoMTrtGx9S8xYS/JwTWXgZ6B7FFYe00ypXVp8T6mxu > O+/yre/DUfkTZW/0pqMj2i0kbL2NAeb6A1dSOxMuOCS2U4T5ZYNB6MuA6kIZsZ+S > ZDvRx0uNJSRpS9hjdNdRFJ/ODyAdAE97LNqJTGUwSVlXHnTo3b4ibuLWHO9F4xs0 > Cy/kRmpvxnyStcBaQqkARGefSRpp/hHI0E7X8AylDJpY4Ib38g5tmg== > =ZiGg > -----END PGP SIGNATURE----- > From vijay at ericavijay.net Tue Dec 13 16:25:48 2016 From: vijay at ericavijay.net (Vijay Sarvepalli) Date: Tue, 13 Dec 2016 11:25:48 -0500 Subject: Simple way to get mailbox size by folder. In-Reply-To: References: <2101756398.3143.1480802022598@appsuite-dev.open-xchange.com> Message-ID: Hello Mike and Aki, Thanks for the response. I had been using FETCH 1:* in my IMAP module, but found it slow with folders with lots of messages or even large-sized messages folder. The doveadm seems elegant and faster but I hate to fork a command line from web-UI, for obvious security and performance reasons. It will be great if dovecot team will consider IMAP extensions to release doveadm features when useful/relevant like this. Regards Vijay On Mon, Dec 5, 2016 at 6:27 PM, Michael Slusarz wrote: > On 12/3/2016 2:53 PM, Aki Tuomi wrote: > >> >> On December 3, 2016 at 11:16 PM Vijay Sarvepalli >>> wrote: >>> >>> >>> Is there a simple way to get each mailbox size using dovecot's IMAP >>> interface? The GETQUOTAROOT and GETQUOTA seems to work with the full >>> maildir size and not the individual folders. >>> >>> I am finding a simple way for the webmail client to show usage of each >>> folder. >>> >>> Thanks >>> Vijay >>> >> >> $ doveadm mailbox status -u cmouse all INBOX >> INBOX messages=9206 recent=0 uidnext=33115 uidvalidity=1451655531 >> unseen=7 highestmodseq=39954 vsize=538582181 guid=d595a62d65818656f72c00007 >> 4be03de >> >> $ doveadm -fjson mailbox status -u cmouse at cmouse.fi all INBOX >> [{"mailbox":"INBOX","messages":"9206","recent":"0","uidnext" >> :"33115","uidvalidity":"1451655531","unseen":"7","highestmod >> seq":"39954","vsize":"538582181","guid":"d595a62d658 >> 18656f72c000074be03de"}] >> > > If you want an IMAP specific method (rather than doveadm), you are stuck > with "FETCH 1:* (RFC822.SIZE)". With the nasty requirement - if you want > 100% full accuracy - that you need to track responses to ensure that each > size is only counted once. Practically speaking this shouldn't happen by > any reasonable server, but the warning needs to be made. > > michael > From sami.ketola at dovecot.fi Tue Dec 13 17:24:18 2016 From: sami.ketola at dovecot.fi (Sami Ketola) Date: Wed, 14 Dec 2016 02:24:18 +0900 Subject: Simple way to get mailbox size by folder. In-Reply-To: References: <2101756398.3143.1480802022598@appsuite-dev.open-xchange.com> Message-ID: <49386F54-285A-4528-9001-FB7EA04820A2@dovecot.fi> Hi, In that case you might be better of using the doveadm http api for accessing the information over http/json interface: http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP Sami > On 14 Dec 2016, at 1.25, Vijay Sarvepalli wrote: > > Hello Mike and Aki, > > Thanks for the response. I had been using FETCH 1:* in my IMAP module, > but found it slow with folders with lots of messages or even large-sized > messages folder. The doveadm seems elegant and faster but I hate to fork a > command line from web-UI, for obvious security and performance reasons. It > will be great if dovecot team will consider IMAP extensions to release > doveadm features when useful/relevant like this. > > Regards > Vijay > > On Mon, Dec 5, 2016 at 6:27 PM, Michael Slusarz > wrote: > >> On 12/3/2016 2:53 PM, Aki Tuomi wrote: >> >>> >>> On December 3, 2016 at 11:16 PM Vijay Sarvepalli >>>> wrote: >>>> >>>> >>>> Is there a simple way to get each mailbox size using dovecot's IMAP >>>> interface? The GETQUOTAROOT and GETQUOTA seems to work with the full >>>> maildir size and not the individual folders. >>>> >>>> I am finding a simple way for the webmail client to show usage of each >>>> folder. >>>> >>>> Thanks >>>> Vijay >>>> >>> >>> $ doveadm mailbox status -u cmouse all INBOX >>> INBOX messages=9206 recent=0 uidnext=33115 uidvalidity=1451655531 >>> unseen=7 highestmodseq=39954 vsize=538582181 guid=d595a62d65818656f72c00007 >>> 4be03de >>> >>> $ doveadm -fjson mailbox status -u cmouse at cmouse.fi all INBOX >>> [{"mailbox":"INBOX","messages":"9206","recent":"0","uidnext" >>> :"33115","uidvalidity":"1451655531","unseen":"7","highestmod >>> seq":"39954","vsize":"538582181","guid":"d595a62d658 >>> 18656f72c000074be03de"}] >>> >> >> If you want an IMAP specific method (rather than doveadm), you are stuck >> with "FETCH 1:* (RFC822.SIZE)". With the nasty requirement - if you want >> 100% full accuracy - that you need to track responses to ensure that each >> size is only counted once. Practically speaking this shouldn't happen by >> any reasonable server, but the warning needs to be made. >> >> michael >> From aki.tuomi at dovecot.fi Tue Dec 13 17:29:56 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Tue, 13 Dec 2016 19:29:56 +0200 (EET) Subject: Simple way to get mailbox size by folder. In-Reply-To: References: <2101756398.3143.1480802022598@appsuite-dev.open-xchange.com> Message-ID: <1976235538.307.1481650198131@appsuite-dev.open-xchange.com> Hi! You could use doveadm http api instead. See http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP It takes same parameters as command line. Aki > On December 13, 2016 at 6:25 PM Vijay Sarvepalli wrote: > > > Hello Mike and Aki, > > Thanks for the response. I had been using FETCH 1:* in my IMAP module, > but found it slow with folders with lots of messages or even large-sized > messages folder. The doveadm seems elegant and faster but I hate to fork a > command line from web-UI, for obvious security and performance reasons. It > will be great if dovecot team will consider IMAP extensions to release > doveadm features when useful/relevant like this. > > Regards > Vijay > > On Mon, Dec 5, 2016 at 6:27 PM, Michael Slusarz > wrote: > > > On 12/3/2016 2:53 PM, Aki Tuomi wrote: > > > >> > >> On December 3, 2016 at 11:16 PM Vijay Sarvepalli > >>> wrote: > >>> > >>> > >>> Is there a simple way to get each mailbox size using dovecot's IMAP > >>> interface? The GETQUOTAROOT and GETQUOTA seems to work with the full > >>> maildir size and not the individual folders. > >>> > >>> I am finding a simple way for the webmail client to show usage of each > >>> folder. > >>> > >>> Thanks > >>> Vijay > >>> > >> > >> $ doveadm mailbox status -u cmouse all INBOX > >> INBOX messages=9206 recent=0 uidnext=33115 uidvalidity=1451655531 > >> unseen=7 highestmodseq=39954 vsize=538582181 guid=d595a62d65818656f72c00007 > >> 4be03de > >> > >> $ doveadm -fjson mailbox status -u cmouse at cmouse.fi all INBOX > >> [{"mailbox":"INBOX","messages":"9206","recent":"0","uidnext" > >> :"33115","uidvalidity":"1451655531","unseen":"7","highestmod > >> seq":"39954","vsize":"538582181","guid":"d595a62d658 > >> 18656f72c000074be03de"}] > >> > > > > If you want an IMAP specific method (rather than doveadm), you are stuck > > with "FETCH 1:* (RFC822.SIZE)". With the nasty requirement - if you want > > 100% full accuracy - that you need to track responses to ensure that each > > size is only counted once. Practically speaking this shouldn't happen by > > any reasonable server, but the warning needs to be made. > > > > michael > > From aki.tuomi at dovecot.fi Tue Dec 13 17:30:01 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Tue, 13 Dec 2016 19:30:01 +0200 (EET) Subject: Simple way to get mailbox size by folder. In-Reply-To: References: <2101756398.3143.1480802022598@appsuite-dev.open-xchange.com> Message-ID: <1210952513.308.1481650202292@appsuite-dev.open-xchange.com> Hi! You could use doveadm http api instead. See http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP It takes same parameters as command line. Aki > On December 13, 2016 at 6:25 PM Vijay Sarvepalli wrote: > > > Hello Mike and Aki, > > Thanks for the response. I had been using FETCH 1:* in my IMAP module, > but found it slow with folders with lots of messages or even large-sized > messages folder. The doveadm seems elegant and faster but I hate to fork a > command line from web-UI, for obvious security and performance reasons. It > will be great if dovecot team will consider IMAP extensions to release > doveadm features when useful/relevant like this. > > Regards > Vijay > > On Mon, Dec 5, 2016 at 6:27 PM, Michael Slusarz > wrote: > > > On 12/3/2016 2:53 PM, Aki Tuomi wrote: > > > >> > >> On December 3, 2016 at 11:16 PM Vijay Sarvepalli > >>> wrote: > >>> > >>> > >>> Is there a simple way to get each mailbox size using dovecot's IMAP > >>> interface? The GETQUOTAROOT and GETQUOTA seems to work with the full > >>> maildir size and not the individual folders. > >>> > >>> I am finding a simple way for the webmail client to show usage of each > >>> folder. > >>> > >>> Thanks > >>> Vijay > >>> > >> > >> $ doveadm mailbox status -u cmouse all INBOX > >> INBOX messages=9206 recent=0 uidnext=33115 uidvalidity=1451655531 > >> unseen=7 highestmodseq=39954 vsize=538582181 guid=d595a62d65818656f72c00007 > >> 4be03de > >> > >> $ doveadm -fjson mailbox status -u cmouse at cmouse.fi all INBOX > >> [{"mailbox":"INBOX","messages":"9206","recent":"0","uidnext" > >> :"33115","uidvalidity":"1451655531","unseen":"7","highestmod > >> seq":"39954","vsize":"538582181","guid":"d595a62d658 > >> 18656f72c000074be03de"}] > >> > > > > If you want an IMAP specific method (rather than doveadm), you are stuck > > with "FETCH 1:* (RFC822.SIZE)". With the nasty requirement - if you want > > 100% full accuracy - that you need to track responses to ensure that each > > size is only counted once. Practically speaking this shouldn't happen by > > any reasonable server, but the warning needs to be made. > > > > michael > > From gjn at gjn.priv.at Tue Dec 13 20:42:17 2016 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Tue, 13 Dec 2016 21:42:17 +0100 Subject: LDAP cache clear ?? Message-ID: <2869161.zUUYrma5dK@techz> Hello, I have a big problem to clear the ldap cache ? Can any tell me a way to clear the passwords in dovecot when I have to change a password in LDAP? auth_cache_ttl: is not working thanks for a answer, -- mit freundlichen Gr??en / best regards, G?nther J. Niederwimmer From ricardo at wenn.com Tue Dec 13 22:44:28 2016 From: ricardo at wenn.com (Ricardo Branco) Date: Tue, 13 Dec 2016 22:44:28 +0000 Subject: Reprocessing MDBOX account to reduce m.* file count Message-ID: <4e6734f1-ce78-094d-19ab-1a2b025d8d82@wenn.com> Is there a way to force dovecot to reprocess a user account to refile the m.* files based on new config for max file size. Ive got one account at 22k files due to a 2M split. From tss at iki.fi Tue Dec 13 23:37:57 2016 From: tss at iki.fi (Timo Sirainen) Date: Wed, 14 Dec 2016 01:37:57 +0200 Subject: mailboxes and capitalisation In-Reply-To: References: Message-ID: <8170CB13-2F30-4595-97CA-CC042A79B6B2@iki.fi> On 13 Dec 2016, at 11.48, Thorsten Hater wrote: > > Dear all, > > I have set up a series of special-use mailboxes in the default namespace > differing by capitalisation of the names, mainly to capture multiple > mailboxes > with autoexpunge > > namespace inbox { > ... > mailbox Trash { > auto = no > autoexpunge = 30d > special_use = \Trash > } > mailbox trash { > auto = no > autoexpunge = 30d > special_use = \Trash > } > ... > } > > However, doveconf -n reports only one mailbox, namely the second (lowercase > t) > and autoexpunge does not trigger for the first one (capital T). Removing > the special > use flag has no influence. I think you could do it for example: mailbox Trash { ... } mailbox trash2 { name = trash ... } By default name is the same as the section name, but while name setting itself is case-sensitive, the section name is not. This is because the setting keys may end up being environment variables, which are always uppercased. From tss at iki.fi Tue Dec 13 23:38:58 2016 From: tss at iki.fi (Timo Sirainen) Date: Wed, 14 Dec 2016 01:38:58 +0200 Subject: Reprocessing MDBOX account to reduce m.* file count In-Reply-To: <4e6734f1-ce78-094d-19ab-1a2b025d8d82@wenn.com> References: <4e6734f1-ce78-094d-19ab-1a2b025d8d82@wenn.com> Message-ID: <5FF1E75F-EE34-4D2D-8A04-62CF5C2FC703@iki.fi> On 14 Dec 2016, at 0.44, Ricardo Branco wrote: > > Is there a way to force dovecot to reprocess a user account to refile the m.* files based on new config for max file size. > > Ive got one account at 22k files due to a 2M split. dsync elsewhere and mv them back? From ricardo at wenn.com Wed Dec 14 00:11:09 2016 From: ricardo at wenn.com (Ricardo Branco) Date: Wed, 14 Dec 2016 00:11:09 +0000 Subject: Reprocessing MDBOX account to reduce m.* file count In-Reply-To: <5FF1E75F-EE34-4D2D-8A04-62CF5C2FC703@iki.fi> References: <4e6734f1-ce78-094d-19ab-1a2b025d8d82@wenn.com> <5FF1E75F-EE34-4D2D-8A04-62CF5C2FC703@iki.fi> Message-ID: Hmm, thanks, ile give that a try. Would be nice (if possible, I have no idea of internals) to have some in-place method for certain things like this that does not affect any connected clients, ie they can stay connected and the indexes are updated while moving all data to new storage files. On 13 Dec 2016 23:38, Timo Sirainen wrote: > On 14 Dec 2016, at 0.44, Ricardo Branco wrote: >> >> Is there a way to force dovecot to reprocess a user account to refile the m.* files based on new config for max file size. >> >> Ive got one account at 22k files due to a 2M split. > > dsync elsewhere and mv them back? > From ricardo at wenn.com Wed Dec 14 00:53:30 2016 From: ricardo at wenn.com (Ricardo Branco) Date: Wed, 14 Dec 2016 00:53:30 +0000 Subject: random mmap_anon Cannot allocate memory in log Message-ID: I am getting lots of these error messages in the log file, any idea why? vsz_limit = 512M Dec 14 00:50:12 lmtp(it at wenn.com)(it at wenn.com): Error: mmap_anon(211079168) failed: Cannot allocate memory -- The information contained in or attached to this email is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorised to and must not disclose, copy, distribute, or retain any message or any part of it. If you have received an email in error, please contact the sender and delete the material from any computer. The contents of this email are not for publication unless specifically stated. Furthermore, the information contained in this message, and any attachment(s) thereto, is for information purposes only and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of WENN or its subsidiaries and associated companies. We make every effort to keep our network free from viruses. However, you do need to check this e-mail and any attachments to it for viruses as we can take no responsibility for any computer virus which may be transferred by way of this e-mail. WENN Ltd: Registered Office: 4a Tileyard Studios, Tileyard Road, London, N7 9AH, England. Registered No: 4375163. Place of Registration: United Kingdom. USA Entertainment News Inc (d/b/a WENN): Registered Office: 352 7th Avenue, Suite 1105, New York, NY 10001-5657, USA The WENN name, design and related marks are trademarks of the WENN group of companies. (c) 2014 All Rights Reserved. From news at mefox.org Wed Dec 14 03:58:04 2016 From: news at mefox.org (Michael Fox) Date: Tue, 13 Dec 2016 19:58:04 -0800 Subject: FW: postlogin script In-Reply-To: <007a01d253ce$53883710$fa98a530$@mefox.org> References: <007a01d253ce$53883710$fa98a530$@mefox.org> Message-ID: <023901d255be$45da7e60$d18f7b20$@mefox.org> No response seen yet. Trying again. Surely someone knows how the postlogin scripts work and can answer these questions easily... Anyone? Thanks, Michael -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Michael Fox Sent: Sunday, December 11, 2016 8:48 AM To: Dovecot Mailing List Subject: postlogin script I'm using the postlogin service, following the examples in the wiki. But I can't find any documentation on the behavior (what's allowed/not allowed) of the script-login binary. So, some questions: Question 1: The examples show the following at the end of the post-login.sh script: exec "$@" My understanding is that this would exec each of the command line arguments to the post-login.sh script. But, there are no arguments sent to the post-login.sh script in the examples. So what is this line supposed to do? Question 2: One of the examples shows exporting some environmental variables, followed by the above exec line: export MAIL=maildir:/tmp/test export USERDB_KEYS="$USERDB_KEYS mail" exec "$@" Now, I'm really confused. Can someone explain step-by-step why this does anything at all? Question 3: I'd like to be able to pass some information to the post-login.sh script, such as the service (%s), as a positional parameter. For example: executable = script-login /path/post-login.sh %Ls Or even more explicitly: executable = script-login /path/post-login.sh imap But it appears that the script-login binary is expecting only script names to be passed to it so that it can handle more than one script. Is there a way to pass arguments to the different scripts? Thanks, Michael From skdovecot at smail.inf.fh-brs.de Wed Dec 14 06:19:19 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Wed, 14 Dec 2016 07:19:19 +0100 (CET) Subject: LDAP cache clear ?? In-Reply-To: <2869161.zUUYrma5dK@techz> References: <2869161.zUUYrma5dK@techz> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 13 Dec 2016, G?nther J. Niederwimmer wrote: > Can any tell me a way to clear the passwords in dovecot when I have to change > a password in LDAP? > > auth_cache_ttl: is not working what do you mean with "is not working", does the passwords time out never? Manually you can use: doveadm auth cache flush http://wiki2.dovecot.org/Tools/Doveadm/Auth - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWFDkZ3z1H7kL/d9rAQIWDwgArKPAMsQORchT9Rb2+RM1Ae3Rc7/Ad+un KgfSf6eRG3JZ1VHISWddOUmw1u4ohlLakhZJDh8HKEiZifB6je2G1CThzXSR49ju e5E6HJkjBBmg3SSL2fhdxPhlfnWGsbFyQHp7o2rHiWKULEre5+LpdfK54BKJk6O5 QEaIYr8AO+EiauMMQS40BUo3uI5ZDbFJ9D3EtR/vgcIsYUnIDuz1Nb1COhrlE0iQ BxMMdJLhyqzA4Pd96hLMWjrEfA3L4Tf2Zd/B6U1JBr2eckqQAx+GBS9U7s783/Je y2GF+JxkdkoMfzA95aVGJM+qC8QV0lQfqqi1AOs4WfPcANtXOO7IOQ== =ZS2d -----END PGP SIGNATURE----- From aki.tuomi at dovecot.fi Wed Dec 14 07:49:23 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Wed, 14 Dec 2016 09:49:23 +0200 Subject: random mmap_anon Cannot allocate memory in log In-Reply-To: References: Message-ID: <30a7ae65-e6b1-6ab4-04b6-fb7964e0f262@dovecot.fi> On 14.12.2016 02:53, Ricardo Branco wrote: > I am getting lots of these error messages in the log file, any idea why? > > vsz_limit = 512M > > Dec 14 00:50:12 lmtp(it at wenn.com)(it at wenn.com): Error: > mmap_anon(211079168) failed: Cannot allocate memory > You are probably running out of memory on the process. mmap_anon only shows how much it was trying to allocate (201 megs), not total VSZ size. Aki From aki.tuomi at dovecot.fi Wed Dec 14 08:27:47 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Wed, 14 Dec 2016 10:27:47 +0200 Subject: JMAP support in Dovecot In-Reply-To: <69ad3b1d-dbfd-9451-3e93-ccaad8f567b5@libertytrek.org> References: <5839DD54.2060705@carpenter.org> <20161126191625.2js5gzt5zuoq4sm6@nordisch.org> <385273315.256.1480242517370@appsuite-dev.open-xchange.com> <69ad3b1d-dbfd-9451-3e93-ccaad8f567b5@libertytrek.org> Message-ID: <41a4bb93-5d3c-9a38-8b8b-03c5af3ad481@dovecot.fi> Unfortunately we don't have any beta version yet for testing. Hopefully sometime next year. Aki On 13.12.2016 17:33, Tanstaafl wrote: > Hi Aki, > > Someone just asked in the bug for Thunderbird for this, so... > > Is there a git branch that they could use to start playing with what is > there? If not, any idea when that might happen? > > It sounds like someone following the Thunderbird bug is interested in > working on this, but they obviously need something to test against. > > Thanks, > > Charles > > > On 11/27/2016 5:28 AM, Aki Tuomi wrote: >> Hi! >> >> We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 >> >> Aki Tuomi >> >> Dovecot Oy >> >>> On November 26, 2016 at 11:17 PM Andrew Jones wrote: >>> >>> >>> Hi Marcus >>> >>> Thanks for your helpful reply. >>> >>> Do you know what is going on with JMAP development into Dovecot 2.5? >>> >>> It's difficult to get any sort of information from the roadmap and there are no Dovecot forums. >>> >>> One of the main reasons I'm interested in JMAP is because of Roundcube Next and also the other clients it will power. Sadly, there has been little going on and having emailed Thomas, he is no longer involved in Roundcube Next - which is a shame. The Kolab guys are really taking liberties here, and trying their product, the thing is littered with bugs everywhere. >>> >>> Are you able to comment on what is going on with JMAP development into Dovecot? >>> >>> Thanks >>> >>> Andrew >>> >>> >>> >>> >>> Sent from my iPhone >>> >>>> On 26 Nov 2016, at 19:16, Marcus Rueckert wrote: >>>> >>>>> On 2016-11-26 11:07:00 -0800, WJCarpenter wrote: >>>>> I don't know the answer to that question, but I am curious about something. >>>>> What client are you thinking about using with JMAP? I haven't found much. >>>>> (And much of the demo stuff at jmap.io seems to be busted in various ways.) >>>> roundcube-next builds on top of it. >>>> >>>> darix >>>> >>>> -- >>>> openSUSE - SUSE Linux is my linux >>>> openSUSE is good for you >>>> www.opensuse.org From mikefroehner at gmx.de Wed Dec 14 09:16:02 2016 From: mikefroehner at gmx.de (=?UTF-8?Q?Mike_Fr=c3=b6hner?=) Date: Wed, 14 Dec 2016 10:16:02 +0100 Subject: public folder subscriptions sync issue with ldap user/group in dovecot-acl In-Reply-To: <3ad12db0-c224-5652-e99b-6625fb236aca@gmx.de> References: <3ad12db0-c224-5652-e99b-6625fb236aca@gmx.de> Message-ID: <93219fbe-50fd-e50c-aa62-5639bc190b12@gmx.de> I made some additional tests and found that also local unix groups are not working in replacement for my ldap groups as discribed below. Do groups in dovecot-acl intendedly not work? On 12/13/2016 03:47 PM, Mike Fr?hner wrote: > Hello people, > > I am having an issue with 'doveadm sync'. I am currently trying to have > two dovecots behind an haproxy (works fine). Therefore I configured > these two dovecot server (imap-1/imap-2) to sync throught dsync. This > works just partly. The sync of the maiboxes is fine, but the sync of the > subscriptions file just works partly. It works for private folder > subscription, but not completly for public folder subscription. I found > two issues, if I am using LDAP (user/groups) in dovecot ACLs. > > 1. I would like to subscribe 2 public folder (public/test/test1 and > public/test/test2). > > My user (ldaptestuser) is an ldap user and this user is member of the > ldap group (ldaptestgroup) which does have all dovecot-acl rights on > these folders. > > imap-1 # cat /opt/mail/_public/publictest/.test*/dovecot-acl > group=ldaptestgroup akxeilprwts > group=ldaptestgroup akxeilprwts > > I am now connecting with my mail client to imap-1 (throught haproxy) and > the subscription to this folder works. The file which is written looks > like: > > imap-1 # cat /opt/mail/ldaptestuser/Mails/subscriptions > Sent > publictest/test/test1 > publictest/test/test2 > > Now I am awaiting the synch to imap-2, but the file which it written > looks like: > > imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions > Sent > > If I modify the dovecot-acl for .test1 to > > imap-1 # cat /opt/mail/_public/publictest/.test1/dovecot-acl > group=ldaptestgroup akxeilprwts > user=ldaptestuser akxeilprwts > > and execute the subscription again - the synced file looks like: > > imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions > Sent > publictest/test/test1 > > The subscription of public folder test2 will also been synced, if I add > my ldaptestuser to the acl file for this folder. > > 2. Another issue is to unsubscribe a public folder. If I unsubscribe > folder test1, it is written to subscriptions file on the imap where I am > connected, but it is NOT synced even if my user and group are configured > at the dovecot-acl file. If I then unsubscribe a not public folder (like > Sent), the former unsubscribed folder test1 is (faulty) subscribed > again. But both imap do have the same subscriptions for my ldaptestuser > user. > > I do have the behavior with dovecot-2.2.26 and dovecot-2.2.27 on > CentOS-7 (selinux disabled). > > If you need more information like the dovecot -n or some other stuff > give me a short notice. > > Mike; > From j.raschke at mittwald.de Wed Dec 14 10:18:57 2016 From: j.raschke at mittwald.de (Juergen Raschke) Date: Wed, 14 Dec 2016 11:18:57 +0100 Subject: unexpected behaviour of search queries with mixed AND and OR Message-ID: <98fe2fa0-be07-92af-63b6-44590c7ab0ac@mittwald.de> Hello, I found out an unexpected behaviour of search queries with mixed "AND" and "OR". With search query "\( condA OR condB condC \)" I get an error: Fatal: Use parenthesis when mixing ANDs and ORs if I switch left and right OR-part and use the query "\( condB condC OR condA \)" I get a result, but it is not the expected result of the query "\( \( condB condC \) OR condA \)" I get the result of the query "\( condB OR condC OR condA \)" which is more then suprising. The query "\( condB condC OR condA \)" should either throw an error like "\( condA OR condB condC \)" or deliever the result of "\( \( condB condC \) OR condA \)" Example: doveadm -f flow fetch -u USER guid \( savedbefore 21d OR seen savedbefore 5d \) | wc -l Fatal: Use parenthesis when mixing ANDs and ORs 0 doveadm -f flow fetch -u USER guid \( seen savedbefore 5d OR savedbefore 21d \) | wc -l 63690 doveadm -f flow fetch -u USER guid \( seen OR savedbefore 5d OR savedbefore 21d \) | wc -l 63690 doveadm -f flow fetch -u USER guid \( \( seen savedbefore 5d \) OR savedbefore 21d \) |wc -l 63247 doveadm -f flow fetch -u USER guid \( savedbefore 21d OR \( seen savedbefore 5d \) \) |wc -l 63247 doveconf -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 Mit freundlichen Gruessen, Juergen Raschke -- Mittwald CM Service GmbH & Co. KG Koenigsberger Strasse 6 Tel: +49-5772-293-100 32339 Espelkamp Fax: +49-5772-293-333 Geschaeftsfuehrer: Robert Meyer, HRA 6640, AG Bad Oeynhausen Komplementaerin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From aki.tuomi at dovecot.fi Wed Dec 14 10:50:26 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Wed, 14 Dec 2016 12:50:26 +0200 Subject: unexpected behaviour of search queries with mixed AND and OR In-Reply-To: <98fe2fa0-be07-92af-63b6-44590c7ab0ac@mittwald.de> References: <98fe2fa0-be07-92af-63b6-44590c7ab0ac@mittwald.de> Message-ID: <8f20b938-ac85-d84b-f45d-d9073be69347@dovecot.fi> On 14.12.2016 12:18, Juergen Raschke wrote: > Hello, > > > I found out an unexpected behaviour of search queries with mixed > "AND" and "OR". > > > With search query "\( condA OR condB condC \)" I get an error: > Fatal: Use parenthesis when mixing ANDs and ORs > > if I switch left and right OR-part and use the query > "\( condB condC OR condA \)" > > I get a result, but it is not the expected result of the query > "\( \( condB condC \) OR condA \)" > > I get the result of the query > "\( condB OR condC OR condA \)" > which is more then suprising. > > > The query "\( condB condC OR condA \)" should either throw an > error like "\( condA OR condB condC \)" or deliever the result > of "\( \( condB condC \) OR condA \)" > > > > > Example: > > doveadm -f flow fetch -u USER guid \( savedbefore 21d OR seen savedbefore 5d \) | wc -l > Fatal: Use parenthesis when mixing ANDs and ORs > 0 > > doveadm -f flow fetch -u USER guid \( seen savedbefore 5d OR savedbefore 21d \) | wc -l > 63690 > > doveadm -f flow fetch -u USER guid \( seen OR savedbefore 5d OR savedbefore 21d \) | wc -l > 63690 > > doveadm -f flow fetch -u USER guid \( \( seen savedbefore 5d \) OR savedbefore 21d \) |wc -l > 63247 > > doveadm -f flow fetch -u USER guid \( savedbefore 21d OR \( seen savedbefore 5d \) \) |wc -l > 63247 > > > > doveconf -n > # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.9 (357ac0a0e68b+) > # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 > > > > > > Mit freundlichen Gruessen, > > Juergen Raschke > Hi! We believe this has been fixed in https://github.com/dovecot/core/commit/df8046c9a4f6bc2a478ad1e74504d50f3110c906 Aki Tuomi Dovecot oy From gjn at gjn.priv.at Wed Dec 14 11:08:18 2016 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Wed, 14 Dec 2016 12:08:18 +0100 Subject: LDAP cache clear ?? In-Reply-To: References: <2869161.zUUYrma5dK@techz> Message-ID: <3975700.AFmXof5Q2M@techz> Hello, Am Mittwoch, 14. Dezember 2016, 07:19:19 CET schrieb Steffen Kaiser: > On Tue, 13 Dec 2016, G?nther J. Niederwimmer wrote: > > Can any tell me a way to clear the passwords in dovecot when I have to > > change a password in LDAP? > > > > auth_cache_ttl: is not working > > what do you mean with "is not working", does the passwords time out never? dovecot 2.2.25 the old password is working and also the new ? I have set auth_cache_ttl: 7200 but this is not working :-( the default I mean is "1 hour" but this is also not working a restart from dovecot don't work .. In witch file store dovecot this information ? > Manually you can use: > > doveadm auth cache flush > http://wiki2.dovecot.org/Tools/Doveadm/Auth I have read this and do a doveadm auth cache flush 0 cache entries flushed but the old passwords exists ? -- mit freundlichen Gr??en / best regards, G?nther J. Niederwimmer From aki.tuomi at dovecot.fi Wed Dec 14 11:09:21 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Wed, 14 Dec 2016 13:09:21 +0200 Subject: LDAP cache clear ?? In-Reply-To: <3975700.AFmXof5Q2M@techz> References: <2869161.zUUYrma5dK@techz> <3975700.AFmXof5Q2M@techz> Message-ID: On 14.12.2016 13:08, G?nther J. Niederwimmer wrote: > Hello, > > > Am Mittwoch, 14. Dezember 2016, 07:19:19 CET schrieb Steffen Kaiser: >> On Tue, 13 Dec 2016, G?nther J. Niederwimmer wrote: >>> Can any tell me a way to clear the passwords in dovecot when I have to >>> change a password in LDAP? >>> >>> auth_cache_ttl: is not working >> what do you mean with "is not working", does the passwords time out never? > dovecot 2.2.25 > > the old password is working and also the new ? > > I have set auth_cache_ttl: 7200 > > but this is not working :-( > > the default I mean is "1 hour" but this is also not working > > a restart from dovecot don't work .. > > In witch file store dovecot this information ? > >> Manually you can use: >> >> doveadm auth cache flush > >> http://wiki2.dovecot.org/Tools/Doveadm/Auth > I have read this and do a > > doveadm auth cache flush > 0 cache entries flushed > > but the old passwords exists ? > Did you check it's really changed in LDAP with, say, ldapsearch? Aki From aki.tuomi at dovecot.fi Wed Dec 14 11:35:48 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Wed, 14 Dec 2016 13:35:48 +0200 Subject: FW: postlogin script In-Reply-To: <023901d255be$45da7e60$d18f7b20$@mefox.org> References: <007a01d253ce$53883710$fa98a530$@mefox.org> <023901d255be$45da7e60$d18f7b20$@mefox.org> Message-ID: On 14.12.2016 05:58, Michael Fox wrote: > No response seen yet. Trying again. > > Surely someone knows how the postlogin scripts work and can answer these > questions easily... Anyone? > > Thanks, > Michael > > > -----Original Message----- > From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Michael Fox > Sent: Sunday, December 11, 2016 8:48 AM > To: Dovecot Mailing List > Subject: postlogin script > > I'm using the postlogin service, following the examples in the wiki. But I > can't find any documentation on the behavior (what's allowed/not allowed) of > the script-login binary. So, some questions: > > > > Question 1: > > The examples show the following at the end of the post-login.sh script: > exec "$@" > > My understanding is that this would exec each of the command line arguments > to the post-login.sh script. But, there are no arguments sent to the > post-login.sh script in the examples. So what is this line supposed to do? > > > > Question 2: > > One of the examples shows exporting some environmental variables, followed > by the above exec line: > > export MAIL=maildir:/tmp/test > > export USERDB_KEYS="$USERDB_KEYS mail" > > exec "$@" > > Now, I'm really confused. Can someone explain step-by-step why this does > anything at all? > > > > Question 3: > > I'd like to be able to pass some information to the post-login.sh script, > such as the service (%s), as a positional parameter. > > For example: executable = script-login /path/post-login.sh %Ls > > Or even more explicitly: executable = script-login /path/post-login.sh imap > > But it appears that the script-login binary is expecting only script names > to be passed to it so that it can handle more than one script. Is there a > way to pass arguments to the different scripts? > > > > Thanks, > > Michael > > > > > > > > > > Hi! You need to use executable = script-login -- /path/post-login.sh -a -r -g -s note the double-dash. it tells getopt to stop processing arguments. Aki From abj at online.fr Wed Dec 14 11:42:04 2016 From: abj at online.fr (=?iso-8859-1?Q?Aur=E9lien?= Beaujean) Date: Wed, 14 Dec 2016 12:42:04 +0100 Subject: Virtual POP3 namespaces and quota-status Message-ID: <20161214114204.GP1717@dagobah.eu.org> Hi, I've tried to do configure Virtual POP3 INBOX (dovecot version 2.2.18) as explained here http://wiki.dovecot.org/Plugins/Virtual with a static userdb and nopassword=y so I dont have any database on the dovecot server without the possibility to distinguish POP3 or IMAP in the userdb extra field to change the namespace on the fly. So I've put the namespace virtual informations inside the protocol pop3 { ... }, I did the same for the protocol imap { }: protocol pop3 { mail_plugins = $mail_plugins last_login virtual namespace inbox { prefix = separator = / list = yes } namespace virtual { inbox = yes prefix = virtual/ separator = / location = virtual:/etc/dovecot/virtual:INDEX=MEMORY list = no hidden = yes } namespace real { prefix = RealMails/ separator = / list = no hidden = yes } } protocol imap { mail_plugins = $mail_plugins imap_quota last_login namespace inbox { inbox = yes } } protocol lda { mail_plugins = " quota sieve" namespace inbox { inbox = yes } } passdb { args = nopassword=y uid=vmail gid=vmail home=/var/mail/%2Mn/%2.2Mn/%n driver = static } userdb { args = nopassword=y uid=vmail gid=vmail home=/var/mail/%2Mn/%2.2Mn/%n driver = static } service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } process_min_avail = 8 } But the service quota-status getting lost with a message: namespace configuration error: inbox=yes namespace missing I didn't find a way to tell quota-status which namespace to use as you can't setup a default one. If I declare a "global" namespace inbox pop3 deamon fails because of duplicated namespace inbox in the configuration files: pop3(xxx): Error: User initialization failed: namespace configuration error: There can be only one namespace with inbox=yes Any idea before I will patch some piece of code to disable the unique restriction of inbox namespace ? Thanks, -- Aur? From gjn at gjn.priv.at Wed Dec 14 12:34:23 2016 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Wed, 14 Dec 2016 13:34:23 +0100 Subject: LDAP cache clear ?? In-Reply-To: References: <2869161.zUUYrma5dK@techz> <3975700.AFmXof5Q2M@techz> Message-ID: <6831475.CJ1nStY3Wa@techz> Hello, Am Mittwoch, 14. Dezember 2016, 13:09:21 CET schrieb Aki Tuomi: > On 14.12.2016 13:08, G?nther J. Niederwimmer wrote: > > Am Mittwoch, 14. Dezember 2016, 07:19:19 CET schrieb Steffen Kaiser: > >> On Tue, 13 Dec 2016, G?nther J. Niederwimmer wrote: > >>> Can any tell me a way to clear the passwords in dovecot when I have to > >>> change a password in LDAP? > >>> > >>> auth_cache_ttl: is not working > >> > >> what do you mean with "is not working", does the passwords time out > >> never? > > > > dovecot 2.2.25 > > > > the old password is working and also the new ? > > > > I have set auth_cache_ttl: 7200 > > > > but this is not working :-( > > > > the default I mean is "1 hour" but this is also not working > > > > a restart from dovecot don't work .. > > > > In witch file store dovecot this information ? > > > >> Manually you can use: > >> > >> doveadm auth cache flush > >> > >> http://wiki2.dovecot.org/Tools/Doveadm/Auth > > > > I have read this and do a > > > > doveadm auth cache flush > > 0 cache entries flushed > > > > but the old passwords exists ? > > Did you check it's really changed in LDAP with, say, ldapsearch? Yes the Problem is, the old Password and the new is working, I test it with "doveadm auth test info at example.com" old and new is working, a wrong password is not working ? But now, after xx reboot and restart from dovecot the old password is deleted!! Hurrrrrrra ;-) -- mit freundlichen Gr??en / best regards, G?nther J. Niederwimmer From andrew at mykolab.com Wed Dec 14 15:08:33 2016 From: andrew at mykolab.com (Andrew Jones) Date: Wed, 14 Dec 2016 15:08:33 +0000 Subject: JMAP support in Dovecot In-Reply-To: <69ad3b1d-dbfd-9451-3e93-ccaad8f567b5@libertytrek.org> References: <5839DD54.2060705@carpenter.org> <20161126191625.2js5gzt5zuoq4sm6@nordisch.org> <385273315.256.1480242517370@appsuite-dev.open-xchange.com> <69ad3b1d-dbfd-9451-3e93-ccaad8f567b5@libertytrek.org> Message-ID: <3D383D9F-24C7-42DD-98AA-E2A7C77CC01D@mykolab.com> Dear Charles In order to gain more info on JMAP implementations and progress being made on server-side implementations, I'd say the JMAP Google groups would contain the most information with all discussions. Currently the most current implementation is the JMAP proxy, which connects to an IMAP/CalDAV/CardDAV server, and Fastmail are hard at work at trying to get JMAP support into Cyrus. Clientside implementations include a mobile app being developed by Atmail, as well as Roundcube Next - it may be worth reaching out to them to see what they are using for development. Good luck Sent from my iPhone > On 13 Dec 2016, at 15:34, Tanstaafl wrote: > > Hi Aki, > > Someone just asked in the bug for Thunderbird for this, so... > > Is there a git branch that they could use to start playing with what is > there? If not, any idea when that might happen? > > It sounds like someone following the Thunderbird bug is interested in > working on this, but they obviously need something to test against. > > Thanks, > > Charles > > >> On 11/27/2016 5:28 AM, Aki Tuomi wrote: >> Hi! >> >> We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 >> >> Aki Tuomi >> >> Dovecot Oy >> >>> On November 26, 2016 at 11:17 PM Andrew Jones wrote: >>> >>> >>> Hi Marcus >>> >>> Thanks for your helpful reply. >>> >>> Do you know what is going on with JMAP development into Dovecot 2.5? >>> >>> It's difficult to get any sort of information from the roadmap and there are no Dovecot forums. >>> >>> One of the main reasons I'm interested in JMAP is because of Roundcube Next and also the other clients it will power. Sadly, there has been little going on and having emailed Thomas, he is no longer involved in Roundcube Next - which is a shame. The Kolab guys are really taking liberties here, and trying their product, the thing is littered with bugs everywhere. >>> >>> Are you able to comment on what is going on with JMAP development into Dovecot? >>> >>> Thanks >>> >>> Andrew >>> >>> >>> >>> >>> Sent from my iPhone >>> >>>>> On 26 Nov 2016, at 19:16, Marcus Rueckert wrote: >>>>> >>>>> On 2016-11-26 11:07:00 -0800, WJCarpenter wrote: >>>>> I don't know the answer to that question, but I am curious about something. >>>>> What client are you thinking about using with JMAP? I haven't found much. >>>>> (And much of the demo stuff at jmap.io seems to be busted in various ways.) >>>> >>>> roundcube-next builds on top of it. >>>> >>>> darix >>>> >>>> -- >>>> openSUSE - SUSE Linux is my linux >>>> openSUSE is good for you >>>> www.opensuse.org From tss at iki.fi Wed Dec 14 17:40:27 2016 From: tss at iki.fi (Timo Sirainen) Date: Wed, 14 Dec 2016 19:40:27 +0200 Subject: public folder subscriptions sync issue with ldap user/group in dovecot-acl In-Reply-To: <93219fbe-50fd-e50c-aa62-5639bc190b12@gmx.de> References: <3ad12db0-c224-5652-e99b-6625fb236aca@gmx.de> <93219fbe-50fd-e50c-aa62-5639bc190b12@gmx.de> Message-ID: <833927C3-931F-4E0E-9425-A6389B3C2188@iki.fi> On 14 Dec 2016, at 11.16, Mike Fr?hner wrote: > > I made some additional tests and found that also local unix groups are not working in replacement for my ldap groups as discribed below. > > Do groups in dovecot-acl intendedly not work? http://wiki2.dovecot.org/ACL -> ACL groups support works by returning a comma-separated acl_groups extra field from userdb, which contains all the groups the user belongs to. User's UNIX groups have no effect on ACLs (you can "enable" them by using a special post-login script). > > On 12/13/2016 03:47 PM, Mike Fr?hner wrote: >> Hello people, >> >> I am having an issue with 'doveadm sync'. I am currently trying to have >> two dovecots behind an haproxy (works fine). Therefore I configured >> these two dovecot server (imap-1/imap-2) to sync throught dsync. This >> works just partly. The sync of the maiboxes is fine, but the sync of the >> subscriptions file just works partly. It works for private folder >> subscription, but not completly for public folder subscription. I found >> two issues, if I am using LDAP (user/groups) in dovecot ACLs. >> >> 1. I would like to subscribe 2 public folder (public/test/test1 and >> public/test/test2). >> >> My user (ldaptestuser) is an ldap user and this user is member of the >> ldap group (ldaptestgroup) which does have all dovecot-acl rights on >> these folders. >> >> imap-1 # cat /opt/mail/_public/publictest/.test*/dovecot-acl >> group=ldaptestgroup akxeilprwts >> group=ldaptestgroup akxeilprwts >> >> I am now connecting with my mail client to imap-1 (throught haproxy) and >> the subscription to this folder works. The file which is written looks >> like: >> >> imap-1 # cat /opt/mail/ldaptestuser/Mails/subscriptions >> Sent >> publictest/test/test1 >> publictest/test/test2 >> >> Now I am awaiting the synch to imap-2, but the file which it written >> looks like: >> >> imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions >> Sent >> >> If I modify the dovecot-acl for .test1 to >> >> imap-1 # cat /opt/mail/_public/publictest/.test1/dovecot-acl >> group=ldaptestgroup akxeilprwts >> user=ldaptestuser akxeilprwts >> >> and execute the subscription again - the synced file looks like: >> >> imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions >> Sent >> publictest/test/test1 >> >> The subscription of public folder test2 will also been synced, if I add >> my ldaptestuser to the acl file for this folder. >> >> 2. Another issue is to unsubscribe a public folder. If I unsubscribe >> folder test1, it is written to subscriptions file on the imap where I am >> connected, but it is NOT synced even if my user and group are configured >> at the dovecot-acl file. If I then unsubscribe a not public folder (like >> Sent), the former unsubscribed folder test1 is (faulty) subscribed >> again. But both imap do have the same subscriptions for my ldaptestuser >> user. >> >> I do have the behavior with dovecot-2.2.26 and dovecot-2.2.27 on >> CentOS-7 (selinux disabled). >> >> If you need more information like the dovecot -n or some other stuff >> give me a short notice. >> >> Mike; >> From ruga at protonmail.com Wed Dec 14 23:18:08 2016 From: ruga at protonmail.com (Ruga) Date: Wed, 14 Dec 2016 18:18:08 -0500 Subject: Existing shared mailbox ... does not exist In-Reply-To: References: Message-ID: bump On Tue, Nov 8, 2016 at 5:49 PM, Ruga <'ruga at protonmail.com'> wrote: Hello, Dovecot 2.2.26.0 Thunderbird 45.4.0 ESR Scenario: We have a shared mailbox with e-mails in its subdirectories. There are no e-mails in the shared mailbox itself. Example: /Shared <----------------------------------- empty /Shared/call_for_papers <-------------- empty /Shared/call_for_papers/AAMAS <-- populated ...more of the same... Problem: When selecting /Shared, Thunderbird chirps this message: "The current operation on 'Shared' did not succeed. The mail server for account @example.com responded: Mailbox doesn't exist: Shared/Shared (0.000 + 0.000 secs)." From aki.tuomi at dovecot.fi Thu Dec 15 06:49:54 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Thu, 15 Dec 2016 08:49:54 +0200 Subject: FW: postlogin script In-Reply-To: <04d401d25686$f485edf0$dd91c9d0$@mefox.org> References: <007a01d253ce$53883710$fa98a530$@mefox.org> <023901d255be$45da7e60$d18f7b20$@mefox.org> <04d401d25686$f485edf0$dd91c9d0$@mefox.org> Message-ID: On 15.12.2016 05:54, Michael Fox wrote: >> Hi! >> >> You need to use executable = script-login -- /path/post-login.sh -a -r -g > -s >> note the double-dash. it tells getopt to stop processing arguments. >> >> Aki > Thanks Aki. So that let's me call a single script with arguments. Great. > What if there is more than one script? I'm unable to guess what the > complete syntax would be for calling more than one script, some of which may > have their own arguments. Please keep responses in the list. Maybe you could, I don't know, call multiple scripts in your script? > Also, can you help with my other two questions (below): > >> Question 1: >> >> The examples show the following at the end of the post-login.sh script: >> exec "$@" >> >> My understanding is that this would exec each of the command line arguments >> to the post-login.sh script. But, there are no arguments sent to the >> post-login.sh script in the examples. So what is this line supposed to do? It will execute something dovecot wants in order to import the env variables set in your question 2. >> >> >> Question 2: >> >> One of the examples shows exporting some environmental variables, followed >> by the above exec line: >> >> export MAIL=maildir:/tmp/test >> >> export USERDB_KEYS="$USERDB_KEYS mail" >> >> exec "$@" >> >> Now, I'm really confused. Can someone explain step-by-step why this does >> anything at all? > Michael Aki From aki.tuomi at dovecot.fi Thu Dec 15 06:52:15 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Thu, 15 Dec 2016 08:52:15 +0200 Subject: FW: postlogin script In-Reply-To: References: <007a01d253ce$53883710$fa98a530$@mefox.org> <023901d255be$45da7e60$d18f7b20$@mefox.org> <04d401d25686$f485edf0$dd91c9d0$@mefox.org> Message-ID: <3c24e883-03c8-45b1-b41e-f30cdf6ad761@dovecot.fi> Also, if you look at the examples at http://wiki.dovecot.org/PostLoginScripting you can see how it's used and how to call multiple scripts as well. Aki On 15.12.2016 08:49, Aki Tuomi wrote: > > On 15.12.2016 05:54, Michael Fox wrote: >>> Hi! >>> >>> You need to use executable = script-login -- /path/post-login.sh -a -r -g >> -s >>> note the double-dash. it tells getopt to stop processing arguments. >>> >>> Aki >> Thanks Aki. So that let's me call a single script with arguments. Great. >> What if there is more than one script? I'm unable to guess what the >> complete syntax would be for calling more than one script, some of which may >> have their own arguments. > Please keep responses in the list. Maybe you could, I don't know, call > multiple scripts in your script? > >> Also, can you help with my other two questions (below): >> >>> Question 1: >>> >>> The examples show the following at the end of the post-login.sh script: >>> exec "$@" >>> >>> My understanding is that this would exec each of the command line arguments >>> to the post-login.sh script. But, there are no arguments sent to the >>> post-login.sh script in the examples. So what is this line supposed to do? > It will execute something dovecot wants in order to import the env > variables set in your question 2. > >>> >>> Question 2: >>> >>> One of the examples shows exporting some environmental variables, followed >>> by the above exec line: >>> >>> export MAIL=maildir:/tmp/test >>> >>> export USERDB_KEYS="$USERDB_KEYS mail" >>> >>> exec "$@" >>> >>> Now, I'm really confused. Can someone explain step-by-step why this does >>> anything at all? >> Michael > Aki From gerben.wierda at rna.nl Thu Dec 15 12:16:22 2016 From: gerben.wierda at rna.nl (Gerben Wierda) Date: Thu, 15 Dec 2016 13:16:22 +0100 Subject: Maildir: do message files need to have a unique name across all directories? Message-ID: <5A63861E-259B-4124-A330-351E80C3DEB1@rna.nl> While testing a new mail server I created a temporary account and filled its mailbox (Milder, dovecot) with the contents of another account. That means the actual message files in each account have identical names. Is that a problem? (I?m asking because I see some weird behaviour of visible/invisible messages and I wonder if this could have been the reason). G From skdovecot at smail.inf.fh-brs.de Thu Dec 15 13:54:01 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 15 Dec 2016 14:54:01 +0100 (CET) Subject: Maildir: do message files need to have a unique name across all directories? In-Reply-To: <5A63861E-259B-4124-A330-351E80C3DEB1@rna.nl> References: <5A63861E-259B-4124-A330-351E80C3DEB1@rna.nl> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 15 Dec 2016, Gerben Wierda wrote: > While testing a new mail server I created a temporary account and filled > its mailbox (Milder, dovecot) with the contents of another account. That > means the actual message files in each account have identical names. Is > that a problem? (I?m asking because I see some weird behaviour of > visible/invisible messages and I wonder if this could have been the > reason). I have no problems using the same filenames in different Maildir directories (not in new and cur of the same Maildir). - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWFKgeXz1H7kL/d9rAQLxtQgApZ294wK4y+8Tc5f40AAy53UFxVEaZLLZ wnFxwpWUhPLh02Y7cNxND8jTcNLBTC4hnuzRVkqpJNFbEUwWYkcc7zdmOm3Kra3z yguiZ0p7phFsBMG85aAfQLyPeLBSGzDJsdDe+wojUdCBmbvMTdF5KICbVcEM8LyT M1V+Ecm6nhdgmCkGzFe1yrWzXWbfwTMPaK4DPOJi0FWLZ0YWYhppZ5XFI+pOaPnE d60Lbry+/B9FSgfbkgnQ7s92FdjpkRR9oAANLZVzx3J+X5aXSap5TMn/Rx/1zNKj MVoa3Xy3gNdsXQlwe2VeP8hik+DbXdvsSNHXMSODHbI9XGhgrbaWWw== =bslK -----END PGP SIGNATURE----- From rkudyba at fordham.edu Thu Dec 15 15:56:08 2016 From: rkudyba at fordham.edu (Robert Kudyba) Date: Thu, 15 Dec 2016 10:56:08 -0500 Subject: imap Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 on Fedora 24 References: <3B63C035-856D-48A6-AE3A-4FB18FEE2EDC@fordham.edu> Message-ID: <5F078179-8B86-43D5-B49D-A959EB5262DB@fordham.edu> Seems to be related to https://bugzilla.redhat.com/show_bug.cgi?id=1189198 . Separate note the link to Overview of all dovecot.org mailing lists http://dovecot.org/mailman/listinfo is broken as are the images on the page. Here?s the backtrace. dovecot[12438]: imap(username): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x91ab2) [0x7ff01e98cab2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x91bad) [0x7ff01e98cbad] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff01e925f41] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xaa1ed) [0x7ff01ecc01ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0xd2) [0x7ff01ecc0652] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x3d) [0x7ff01ec4c88d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xbe717) [0x7ff01ecd4717] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xbe952) [0x7ff01ecd4952] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7ff01e997653] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7ff01e99807d] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7ff01e9748e2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x73d91) [0x7ff01e96ed91] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7ff01e997653] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7ff01e99807d] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7ff01e9748e2] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header+0x4f) [0x7ff01e97527f] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xb0d4b) [0x7ff01ecc6d4b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xb2e63) [0x7ff01ecc8e63] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x114) [0x7ff01ecc9574] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22) [0x7ff01ec56d52] -> dovecot/imap(+0x221ff) [0x559b559541ff] -> dovecot/imap(imap_search_start+0xd1) [0x559b559545c1] -> dovecot/imap(cmd_search+0xd3) [0x559b55946063] -> dovecot/imap(command_exec+0xa5) [0x559b5594d5d5] -> dovecot/imap(+0x19852) [0x559b5594b852] -> dovecot/imap(+0x198de) [0x559b5594b8de] -> dovecot/imap(client_handle_input+0x1b5) [0x559b5594bce5] -> dovecot/imap(client_input+0x82) [0x559b5594c262] dovecot[12438]: imap(username): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x91ab2) [0x7f77a0cd7ab2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x91bad) [0x7f77a0cd7bad] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f77a0c70f41] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xaa1ed) [0x7f77a100b1ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0xd2) [0x7f77a100b652] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x3d) [0x7f77a0f9788d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xbe717) [0x7f77a101f717] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xbe952) [0x7f77a101f952] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7f77a0ce2653] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f77a0ce307d] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7f77a0cbf8e2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x73d91) [0x7f77a0cb9d91] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7f77a0ce2653] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f77a0ce307d] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7f77a0cbf8e2] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header+0x4f) [0x7f77a0cc027f] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xb0d4b) [0x7f77a1011d4b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xb2e63) [0x7f77a1013e63] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x114) [0x7f77a1014574] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22) [0x7f77a0fa1d52] -> dovecot/imap(+0x221ff) [0x563492d1d1ff] -> dovecot/imap(imap_search_start+0xd1) [0x563492d1d5c1] -> dovecot/imap(cmd_search+0xd3) [0x563492d0f063] -> dovecot/imap(command_exec+0xa5) [0x563492d165d5] -> dovecot/imap(+0x19852) [0x563492d14852] -> dovecot/imap(+0x198de) [0x563492d148de] -> dovecot/imap(client_handle_input+0x1b5) [0x563492d14ce5] -> dovecot/imap(client_input+0x82) [0x563492d15262] dovecot --version 2.2.26.0 (23d1de6) dovecot -n # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # OS: Linux 4.8.4-200.fc24.x86_64 x86_64 Fedora release 24 (Twenty Four) mail_fsync = always mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_nfs_index = yes mail_nfs_storage = yes mbox_write_locks = fcntl mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } ssl = required ssl_cert = Hello, i want to configure a virtual mailsystem on an debian server with exim and dovecot. Because it is running on a V-Server, i want to store everythink in a LUKS encrypted contrainer. So i created a group crypt with the members Debian-exim (107), dovecot, (other users with encrypted content) All mails should be stored in /mail in the mounted container. Dovecot has this configuration: ======================================= passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } userdb { driver = static args = uid=Debian-exim gid=mail home=/mountpoint/mail/%d/%n } mail_uid = Debian-exim first_valid_uid = 107 last_valid_uid = 107 first_valid_gid = 8 last_valid_gid = 9 mail_location = maildir:/mountpoint/mail/%d/%n ======================================= The /mountpoint has the following rights: drwxrwx--- 5 root crypt 4,0K Dez 13 19:05 mountpoint The subdirectories are all owned by Debian-exim: drwxrwx--- 4 Debian-exim mail 4,0K Okt 23 17:05 mail The group mail has id 8 and the group crypt has id 9 The Problem is that dovecot will not go into the directory with group crypt! I always get the following error message: Dec 15 18:03:25 pop3(karsten at server): Error: user karsten at server: Initialization failed: Initializing mail storage from mail_location setting failed: stat(/mountpoint/mail/server/karsten) failed: Permission denied (euid=107(Debian-exim) egid=8(mail) missing +x perm: /mnt, we're not in group 9(crypt), dir owned by 0:9 mode=0770) Dec 15 18:03:25 pop3(karsten at server): Error: Invalid user settings. Refer to server log for more information. But dovecot is definitely in the group crypt! What i am doing wrong? Regards Karsten From eduardo at kalinowski.com.br Thu Dec 15 17:22:56 2016 From: eduardo at kalinowski.com.br (Eduardo M KALINOWSKI) Date: Thu, 15 Dec 2016 17:22:56 +0000 Subject: Configuration problem for secure virtual server In-Reply-To: Message-ID: <20161215172256.Horde.aN68ycLVIloSTgCs6Dob21w@mail.kalinowski.com.br> On Qui, 15 Dez 2016, Karsten Malcher wrote: > Hello, > > mail_uid = Debian-exim This will be important later > > Dec 15 18:03:25 pop3(karsten at server): Error: user karsten at server: > Initialization failed: Initializing mail storage from > mail_location setting failed: stat(/mountpoint/mail/server/karsten) > failed: Permission denied (euid=107(Debian-exim) > egid=8(mail) missing +x perm: /mnt, we're not in group 9(crypt), dir > owned by 0:9 mode=0770) > Dec 15 18:03:25 pop3(karsten at server): Error: Invalid user settings. > Refer to server log for more information. > > But dovecot is definitely in the group crypt! dovecot may be, but the process is not trying to access as user dovecot, but as Debian-exim (as shown in the log). And this happens because of the mail_uid line in your config. -- Eduardo M KALINOWSKI eduardo at kalinowski.com.br From debian at home.decotrain.de Thu Dec 15 17:29:28 2016 From: debian at home.decotrain.de (Karsten Malcher) Date: Thu, 15 Dec 2016 18:29:28 +0100 Subject: Configuration problem for secure virtual server In-Reply-To: <20161215172256.Horde.aN68ycLVIloSTgCs6Dob21w@mail.kalinowski.com.br> References: <20161215172256.Horde.aN68ycLVIloSTgCs6Dob21w@mail.kalinowski.com.br> Message-ID: <2e1c205f-6143-ba07-0a4b-448f5d0b7f5c@home.decotrain.de> Am 15.12.2016 um 18:22 schrieb Eduardo M KALINOWSKI: > On Qui, 15 Dez 2016, Karsten Malcher wrote: >> Hello, >> >> mail_uid = Debian-exim > This will be important later It does not run when i comment this out. Dovecot was running before i moved the mail-path from a non encrypted one to the encrypted path. >> >> Dec 15 18:03:25 pop3(karsten at server): Error: user karsten at server: Initialization failed: Initializing mail storage from >> mail_location setting failed: stat(/mountpoint/mail/server/karsten) failed: Permission denied (euid=107(Debian-exim) >> egid=8(mail) missing +x perm: /mnt, we're not in group 9(crypt), dir owned by 0:9 mode=0770) >> Dec 15 18:03:25 pop3(karsten at server): Error: Invalid user settings. Refer to server log for more information. >> >> But dovecot is definitely in the group crypt! > > dovecot may be, but the process is not trying to access as user dovecot, but as Debian-exim (as shown in the log). And > this happens because of the mail_uid line in your config. > Yes - the error message say it - but Debian-exim is in the group crypt too. Dovecot is rejecting the path of the mountpoint! Why? From debian at home.decotrain.de Thu Dec 15 17:43:31 2016 From: debian at home.decotrain.de (Karsten Malcher) Date: Thu, 15 Dec 2016 18:43:31 +0100 Subject: Configuration problem for secure virtual server In-Reply-To: <20161215172256.Horde.aN68ycLVIloSTgCs6Dob21w@mail.kalinowski.com.br> References: <20161215172256.Horde.aN68ycLVIloSTgCs6Dob21w@mail.kalinowski.com.br> Message-ID: <5c82c697-6993-1fe3-114e-91b4e9bddd22@home.decotrain.de> I can only login when i alter the group to crypt. But then dovecot has the problem that it is not in group mail: Dec 15 18:33:39 imap(karsten at server): Error: fchown(/mountpoint/mail/server/karsten/dovecot-uidlist.tmp, group=8(mail)) failed: Operation not permitted (egid=9(crypt), group based on /mountpoint/mail/server/karsten - see http://wiki2.dovecot.org/Errors/ChgrpNoPerm) So dovecot will not handle different groups in the path !? From support at netfront.net Fri Dec 16 05:53:20 2016 From: support at netfront.net (Netfront Customer Service) Date: Fri, 16 Dec 2016 13:53:20 +0800 Subject: Possible solr and indexing bug Message-ID: Bug Report: We had one of our solr server down for a while, then observed a lot of "Warning: fscking index file " actions. Version 2.2.27 with auto fsck. A follow up investigation shows direct one to one relationship between solr error and subsequent fscking. The fscking lasts for quite a long time (for at least an hour) when the mailbox is concurrently accessed. Thank you. Netfront Hong Kong Dec 16 07:48:14 dovecot: pop3(glhk44): Disconnected: Logged out top=0/0, retr=0/0, del=0/221, size=143216382 Dec 16 08:13:20 dovecot: pop3-login: Login: user=, method=PLAIN, rip=4.5.6.7, lip=1.2.3.4, mpid=99633, TLS, session= Dec 16 08:13:23 dovecot: pop3(glhk44): Disconnected: Logged out top=0/0, retr=0/0, del=0/221, size=143216382 Dec 16 08:39:10 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 08:46:01 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 08:53:33 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 08:57:53 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 09:00:39 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 09:05:00 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 09:09:32 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 09:21:44 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 09:24:59 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 09:29:52 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 09:31:08 dovecot: indexer-worker(glhk44): Indexed 1 messages in INBOX Dec 16 09:44:18 dovecot: imap-login: Login: user=, method=PLAIN, rip=6.7.8.9, lip=1.2.3.4, mpid=22866, session=<0yNKtbxDwuTaZxfh> Dec 16 09:44:18 dovecot: imap-login: Login: user=, method=PLAIN, rip=6.7.8.9, lip=1.2.3.4, mpid=22867, session= Dec 16 09:44:18 dovecot: imap-login: Login: user=, method=PLAIN, rip=6.7.8.9, lip=1.2.3.4, mpid=22868, session= Dec 16 09:44:18 dovecot: imap-login: Login: user=, method=PLAIN, rip=6.7.8.9, lip=1.2.3.4, mpid=22869, session= Dec 16 09:44:29 dovecot: pop3-login: Login: user=, method=PLAIN, rip=6.7.8.9, lip=1.2.3.4, mpid=23090, TLS, session= Dec 16 09:44:30 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=23093, secured, session= Dec 16 09:44:31 dovecot: imap(glhk44): Connection closed in=0 out=404 Dec 16 09:45:34 dovecot: pop3(glhk44): Disconnected: Logged out top=0/0, retr=11/3587310, del=0/232, size=146803474 Dec 16 09:45:38 dovecot: imap(glhk44): Logged out in=202 out=4336 Dec 16 09:46:17 dovecot: imap-login: Login: user=, method=PLAIN, rip=6.7.8.9, lip=1.2.3.4, mpid=27449, session= Dec 16 09:46:19 dovecot: imap-login: Login: user=, method=PLAIN, rip=6.7.8.9, lip=1.2.3.4, mpid=27550, session= Dec 16 09:46:20 dovecot: imap(glhk44): copy from INBOX: box=Deleted Messages, uid=1690, msgid=, size=6759 Dec 16 09:46:20 dovecot: imap(glhk44): delete: box=INBOX, uid=124159, msgid=<20161215164627444789108 at sensioinc.cn>, size=127611 Dec 16 09:46:20 dovecot: imap(glhk44): expunge: box=INBOX, uid=124159, msgid=<20161215164627444789108 at sensioinc.cn>, size=127611 Dec 16 09:46:28 dovecot: imap(glhk44): Error: fts_solr: Indexing failed: 503 Service Unavailable < ----------------------- solr error Dec 16 09:46:28 dovecot: indexer-worker(glhk44): Error: fts_solr: Indexing failed: 503 Service Unavailable Dec 16 09:46:28 dovecot: indexer-worker(glhk44): Error: Mailbox Deleted Messages: Transaction commit failed: FTS transaction commit failed: backend deinit Dec 16 09:46:28 dovecot: imap(glhk44): copy from INBOX: box=Deleted Messages, uid=1691, msgid=<20161215003910.C4439ABB653 at smtp3.mthai.in.th>, size=17896 Dec 16 09:46:29 dovecot: indexer-worker(glhk44): Indexed 1 messages in Deleted Messages Dec 16 09:46:30 dovecot: imap(glhk44): delete: box=INBOX, uid=124164, msgid=<00c701d256b1$3bbbcfd0$b3336f70$@com>, size=107064 Dec 16 09:46:30 dovecot: imap(glhk44): expunge: box=INBOX, uid=124164, msgid=<00c701d256b1$3bbbcfd0$b3336f70$@com>, size=107064 Dec 16 09:46:31 dovecot: imap(glhk44): delete: box=INBOX, uid=124175, msgid=<00f201d256c2$a4db5f10$ee921d30$@com>, size=3518208 Dec 16 09:46:31 dovecot: imap(glhk44): expunge: box=INBOX, uid=124175, msgid=<00f201d256c2$a4db5f10$ee921d30$@com>, size=3518208 Dec 16 09:46:31 dovecot: imap(glhk44): copy from INBOX: box=Deleted Messages, uid=1692, msgid=<1616393.344200011xAAAAA at enterprisecommunicationnetwork.com>, size=47100 Dec 16 09:46:31 dovecot: imap(glhk44): Error: Corrupted transaction log file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log seq 1268: file size shrank (28960 < 29056) (sync_offset=29056) <-------- fscking starts Dec 16 09:46:31 dovecot: imap(glhk44): Error: Index /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index: Lost log for seq=1268 offset=24900: Failed to map file seq=1268 offset=24900..18446744073709551615 (ret=0) (initial_mapped=1, reason=Index mapped) Dec 16 09:46:31 dovecot: imap(glhk44): Warning: fscking index file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index Dec 16 09:46:31 dovecot: imap(glhk44): Error: Index /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index: Lost log for seq=1268 offset=24900: Failed to map file seq=1268 offset=24900..18446744073709551615 (ret=0) (initial_mapped=1, reason=Index mapped) Dec 16 09:46:31 dovecot: imap(glhk44): Warning: fscking index file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index Dec 16 09:46:31 dovecot: imap(glhk44): Error: Index /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index: Lost log for seq=1268 offset=24900: Failed to map file seq=1268 offset=24900..18446744073709551615 (ret=0) (initial_mapped=1, reason=Index mapped) Dec 16 09:46:31 dovecot: imap(glhk44): Warning: fscking index file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index Dec 16 09:46:31 dovecot: imap(glhk44): Error: Index /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index: Lost log for seq=1268 offset=24900: Failed to map file seq=1268 offset=24900..18446744073709551615 (ret=0) (initial_mapped=1, reason=Index mapped) Dec 16 09:46:31 dovecot: imap(glhk44): Warning: fscking index file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index Dec 16 09:46:31 dovecot: imap(glhk44): Error: Index /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index: Lost log for seq=1268 offset=24900: Failed to map file seq=1268 offset=24900..18446744073709551615 (ret=0) (initial_mapped=1, reason=Index mapped) Dec 16 09:46:31 dovecot: imap(glhk44): Warning: fscking index file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index Dec 16 09:46:31 dovecot: imap(glhk44): Error: Index /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index: Lost log for seq=1268 offset=24900: Failed to map file seq=1268 offset=24900..18446744073709551615 (ret=0) (initial_mapped=1, reason=Index mapped) Dec 16 09:46:31 dovecot: imap(glhk44): Warning: fscking index file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index Dec 16 09:46:31 dovecot: indexer-worker(glhk44): Indexed 1 messages in Deleted Messages Dec 16 09:46:31 dovecot: imap(glhk44): Error: Index /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index: Lost log for seq=1268 offset=24900: Failed to map file seq=1268 offset=24900..18446744073709551615 (ret=0) (initial_mapped=1, reason=Index mapped) Dec 16 09:46:31 dovecot: imap(glhk44): Warning: fscking index file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index Dec 16 09:46:31 dovecot: imap(glhk44): Error: Index /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index: Lost log for seq=1268 offset=24900: Failed to map file seq=1268 offset=24900..18446744073709551615 (ret=0) (initial_mapped=1, reason=Index mapped) Dec 16 09:46:31 dovecot: imap(glhk44): Warning: fscking index file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index Dec 16 09:46:31 dovecot: imap(glhk44): Logged out in=833 out=13350 Dec 16 09:46:31 dovecot: imap(glhk44): copy from INBOX: box=Deleted Messages, uid=1693, msgid=<1616408.344200011xAAAAA at enterprisecommunicationnetwork.com>, size=44739 Dec 16 09:46:31 dovecot: indexer-worker(glhk44): Error: Transaction log file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log: marked corrupted Dec 16 09:46:32 dovecot: indexer-worker(glhk44): Indexed 1 messages in Deleted Messages Dec 16 09:46:32 dovecot: imap(glhk44): Error: Corrupted transaction log file /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log seq 1268: Invalid transaction log size (28960 vs 24900): /home/glhk44/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log (sync_offset=289 60) From dovecot at list-post.mks-mail.de Fri Dec 16 09:30:26 2016 From: dovecot at list-post.mks-mail.de (=?UTF-8?Q?Markus_Sch=c3=b6nhaber?=) Date: Fri, 16 Dec 2016 10:30:26 +0100 Subject: v2.2.27 Debian packages on xi.dovecot.fi Message-ID: <8823685d-154c-1ffa-0833-5b39a66193b7@list-post.mks-mail.de> Hi, at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can we expect packages for v2.2.27 to appear there? -- Regards mks From petehodur at gmail.com Fri Dec 16 10:42:16 2016 From: petehodur at gmail.com (Peter Hodur) Date: Fri, 16 Dec 2016 11:42:16 +0100 Subject: autoexpunge=30d does not works :( Message-ID: Hello, just upgraded to Dovecot 2.2.27 and altered dovecot.conf to contain autoexpunge directive for Spam mailbox (yes it's migrated from Courier 3 years ago): namespace inbox { prefix = INBOX. separator = . inbox = yes mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Spam { auto = subscribe special_use = \Junk autoexpunge = 30d } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } } As I hope, when user logout (POP3 or IMAP) or after Postfix delivers mail via LMTP, Dovecot should check Spam folder for emails, which have ctime older than 30 days and deletes this emails. Recently I have tried this. I have tried login / logout and nothing happend. I have tried turning log verbosity to debug but I can not find any note in debug.log according to this. I would like to kindly ask someone for which this directive works to help me, what is wrong with my config or how can I debug it and find error. Thanks Pete From stephan at rename-it.nl Fri Dec 16 12:37:35 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Fri, 16 Dec 2016 13:37:35 +0100 Subject: v2.2.27 Debian packages on xi.dovecot.fi In-Reply-To: <8823685d-154c-1ffa-0833-5b39a66193b7@list-post.mks-mail.de> References: <8823685d-154c-1ffa-0833-5b39a66193b7@list-post.mks-mail.de> Message-ID: <57f67595-5e6d-7864-ccbb-d36c7d3caa67@rename-it.nl> Op 16-12-2016 om 10:30 schreef Markus Sch?nhaber: > Hi, > > at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can > we expect packages for v2.2.27 to appear there? Actually, there are packages there that have the 2.2.27 release in there, but they are not marked as such. Ever since the git move I haven't finished fixing the automatic version updates. It is still a manual effort that I need to do after a release. Did that now. However, I have a much more advanced version of the builder running in a test environment for a while now. It is available here (only for Jessie atm): http://xi.rename-it.nl/debian.new/pool/ This repository is structured quite differently. There are now two separate package streams: - The familiar alpha package stream "stable-auto" that follows the Dovecot master(-2.2) and Pigeonhole master(-0.4) branches. This releases "alpha" development packages for the upcoming release, which means that the version numbers are always equal to the last official release +1 (this is obviously different from before). Use this package stream if you want to follow bleeding edge development. The last version in this package stream is "2.2.28~alpha0-1~auto+10". - The new rc package stream "stable-rc-auto" that follows the last Dovecot and Pigeonhole release branches. This releases "rc" release (candidate) packages. So, once development forks from the master branch to a new release-2.x.y branch, this package stream will output new packages. The initial packages will have an rc0 tag. Once a real rc1 release is performed, the package version will be updated accordingly and so forth... Once the final release is made, the rc tag is dropped from the package version as well. Use this package stream if you want to get more stable packages. Still, it's use is not recommended for production systems (yes, even RC versions are sometimes horribly broken, especially before they're finished). The last version in this package stream is "2.2.27-1~auto+1". I will make this the main repository soon. Regards, Stephan. From matteo.biagini88 at gmail.com Fri Dec 16 12:56:59 2016 From: matteo.biagini88 at gmail.com (Matteo Biagini) Date: Fri, 16 Dec 2016 13:56:59 +0100 Subject: service(indexer-worker): child 18977 killed with signal 11 (core dumped) Message-ID: Hello to everybody, first of all: thanks a lot for your hard work and for this nice piece of software! After many search about the following SIGSEGV, I decide to post the backtrace and I hope to have avoided duplicated thread. The problem arise after I enable clucene fts. I tryed the clucene ports version (I am using OpenBSD) and a fixed version from github (Blue-Rocket/clucene::feature/pod) which contains FreeBSD fixes and others memory leak patches, but the problem persists. I built either dovecot-* and clucene-core with -g and the following logs are taken from that version. Maybe, I can do more debugging but I don't know how; some ideas? thanks a lot == LOG == Dec 16 12:30:34 mail02 dovecot: indexer-worker(user at hostname): Indexed 1 messages in Trash Dec 16 12:31:16 mail02 dovecot: imap-login: Login: user=, method=PLAIN, rip=10.244.3.101, lip=10.244.3.200, mpid=90234, TLS, session=<68Ny6MRDml8K9ANl> Dec 16 12:31:16 mail02 dovecot: imap-login: Login: user=, method=PLAIN, rip=10.244.3.101, lip=10.244.3.200, mpid=59810, TLS, session= Dec 16 12:31:16 mail02 dovecot: imap-login: Login: user=, method=PLAIN, rip=10.244.3.101, lip=10.244.3.200, mpid=66756, TLS, session= Dec 16 12:31:16 mail02 dovecot: imap-login: Login: user=, method=PLAIN, rip=10.244.3.101, lip=10.244.3.200, mpid=81959, TLS, session= Dec 16 12:31:16 mail02 dovecot: imap-login: Login: user=, method=PLAIN, rip=10.244.3.101, lip=10.244.3.200, mpid=14099, TLS, session= Dec 16 12:31:16 mail02 dovecot: indexer-worker(user at hostname): Indexed 1 messages in INBOX Dec 16 12:32:18 mail02 dovecot: indexer-worker: Fatal: master: service(indexer-worker): child 18977 killed with signal 11 (core dumped) == GDB == (gdb) bt #0 strlen () at /usr/src/lib/libc/arch/amd64/string/strlen.S:152 #1 0x0000093434d7c120 in __vfprintf (fp=0x7f7fffff96c0, fmt0=0x9343cef79ae "Timeout leak: %p (%s:%u)", ap=Variable "ap" is not available. ) at /usr/src/lib/libc/stdio/vfprintf.c:885 #2 0x0000093434d9b068 in *_libc_vsnprintf (str=0x933ab0940b8 "Timeout leak: 0x9342f652300", n=120, fmt=0x9343cef79ae "Timeout leak: %p (%s:%u)", ap=0x7f7fffff9870) at /usr/src/lib/libc/stdio/vsnprintf.c:61 #3 0x000009343cdd4aa5 in str_vprintfa (str=0x933ab094078, fmt=0x9343cef79ae "Timeout leak: %p (%s:%u)", args=0x7f7fffff9870) at str.c:129 #4 0x000009343cdaacd1 in internal_handler (ctx=0x9343d22fab0, format=0x9343cef79ae "Timeout leak: %p (%s:%u)", args=0x7f7fffff9870) at failures.c:602 #5 0x000009343cdab839 in i_internal_error_handler (ctx=Variable "ctx" is not available. ) at failures.c:677 #6 0x000009343cdab3f4 in i_warning (format=0x9343cef79ae "Timeout leak: %p (%s:%u)") at failures.c:325 #7 0x000009343cdc107b in io_loop_destroy (_ioloop=Variable "_ioloop" is not available. ) at ioloop.c:741 #8 0x000009343cd485bd in master_service_deinit (_service=Variable "_service" is not available. ) at master-service.c:876 #9 0x0000093193802642 in main (argc=1, argv=0x7f7fffff9b28) at indexer-worker.c:83 (gdb) bt full #0 strlen () at /usr/src/lib/libc/arch/amd64/string/strlen.S:152 No locals. #1 0x0000093434d7c120 in __vfprintf (fp=0x7f7fffff96c0, fmt0=0x9343cef79ae "Timeout leak: %p (%s:%u)", ap=Variable "ap" is not available. ) at /usr/src/lib/libc/stdio/vfprintf.c:885 mbs = { __mbstate8 = "{\t\000\000\000\000\000\000\000\000\000\000r3\t\000\000\000\000\000\000\000\000\000\0004\t\000\000\001\000\000\000\000\000\000\000223\177\177\000\000\001\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000\t216U\035\rP", '\0' , __mbstateL = 10118011532464} mbseqlen = Variable "mbseqlen" is not available. == DOVECONF == # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: OpenBSD 6.0 amd64 auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN base_dir = /var/run/dovecot dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } first_valid_uid = 2000 last_valid_uid = 2000 listen = * [::] login_greeting = Welcome mail_gid = 2000 mail_location = mdbox:%Lh/Maildir/:INDEX=%Lh/Maildir/ mail_plugins = quota mailbox_alias acl zlib fts fts_lucene trash mail_uid = 2000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mdbox_rotate_size = 60 M namespace { inbox = yes location = mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox "Junk E-mail" { auto = no special_use = \Junk } mailbox SPAM { auto = no special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = separator = / type = private } namespace { list = children location = mdbox:%%Lh/Maildir/:INDEX=%%Lh/Maildir/Shared/%%Ld/%%Ln prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-master-users driver = passwd-file master = yes } plugin { acl = vfile acl_shared_dict = proxy::acl antispam_backend = MAILTRAIN antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/local/bin/sa-learn-pipe.sh antispam_mail_spam = --spam antispam_signature = X-Spam-Flag antispam_signature_missing = move antispam_spam = Spam;Junk antispam_spam_pattern = spam;Spam;junk;Junk antispam_spam_pattern_ignorecase = SPAM;JUNK antispam_trash = trash;Trash;Deleted Items;Deleted Messages antispam_trash_pattern = trash;Trash;Deleted * antispam_trash_pattern_ignorecase = TRASH auth_socket_path = /var/run/dovecot/auth-master fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_new3 = SPAM mailbox_alias_new4 = Spam mailbox_alias_old = Sent mailbox_alias_old2 = Sent mailbox_alias_old3 = Junk mailbox_alias_old4 = Junk quota = dict:user::proxy::quotadict quota_grace = 10%% quota_rule = *:storage=1G quota_warning = storage=100%% quota-warning 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u sieve = %Lh/sieve/dovecot.sieve sieve_before = /var/vmail/sieve/dovecot.sieve sieve_dir = %Lh/sieve sieve_global_dir = /var/vmail/sieve sieve_max_redirects = 30 trash = /etc/dovecot/dovecot-trash.conf.ext zlib_save = lz4 zlib_save_level = 6 } protocols = pop3 imap sieve lmtp service auth { inet_listener { address = 127.0.0.1 port = 12345 } unix_listener /var/spool/postfix/private/dovecot-auth { group = _postfix mode = 0666 user = _postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { process_limit = 500 service_count = 1 } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = _postfix mode = 0600 user = _postfix } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { service_count = 1 } service quota-status { client_limit = 2 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = References: Message-ID: <20161216133611.GA1227@nihlus.leuxner.net> * Peter Hodur 2016.12.16 11:42: > mailbox Spam { > auto = subscribe > special_use = \Junk > autoexpunge = 30d Hi Peter, may be easier to use per-user settings for testing. Something along the line: userdb_namespace/inbox/mailbox/Spam/autoexpunge=6h > As I hope, when user logout (POP3 or IMAP) or after Postfix delivers mail > via LMTP, Dovecot should check Spam folder for emails, which have ctime > older than 30 days and deletes this emails. AFAIK it uses indexes rather than FS attributes, let's see if this query yields some candidates (adjust time): $ doveadm search -u peter mailbox Spam savedsince 6h Regards Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: From mikefroehner at gmx.de Fri Dec 16 14:25:53 2016 From: mikefroehner at gmx.de (=?UTF-8?Q?Mike_Fr=c3=b6hner?=) Date: Fri, 16 Dec 2016 15:25:53 +0100 Subject: public folder subscriptions sync issue with ldap user/group in dovecot-acl In-Reply-To: <833927C3-931F-4E0E-9425-A6389B3C2188@iki.fi> References: <3ad12db0-c224-5652-e99b-6625fb236aca@gmx.de> <93219fbe-50fd-e50c-aa62-5639bc190b12@gmx.de> <833927C3-931F-4E0E-9425-A6389B3C2188@iki.fi> Message-ID: Thanks for your reply Timo. On 12/14/2016 06:40 PM, Timo Sirainen wrote: > On 14 Dec 2016, at 11.16, Mike Fr?hner > wrote: >> >> I made some additional tests and found that also local unix groups are >> not working in replacement for my ldap groups as discribed below. >> >> Do groups in dovecot-acl intendedly not work? > > http://wiki2.dovecot.org/ACL -> ACL groups support works by returning a > comma-separated acl_groups extra field from userdb, which contains all > the groups the user belongs to. User's UNIX groups have no effect on > ACLs (you can "enable" them by using a special post-login script). I think I have configured the userdb right, because the debug log tells me this: imap-1 dovecot: imap(ldaptestuser): Debug: acl: acl username = ldaptestuser imap-1 dovecot: imap(ldaptestuser): Debug: acl: owner = 1 imap-1 dovecot: imap(ldaptestuser): Debug: acl: group added: mailusers imap-1 dovecot: imap(ldaptestuser): Debug: acl: group added: ldaptestgroup > >> >> On 12/13/2016 03:47 PM, Mike Fr?hner wrote: >>> Hello people, >>> >>> I am having an issue with 'doveadm sync'. I am currently trying to have >>> two dovecots behind an haproxy (works fine). Therefore I configured >>> these two dovecot server (imap-1/imap-2) to sync throught dsync. This >>> works just partly. The sync of the maiboxes is fine, but the sync of the >>> subscriptions file just works partly. It works for private folder >>> subscription, but not completly for public folder subscription. I found >>> two issues, if I am using LDAP (user/groups) in dovecot ACLs. >>> >>> 1. I would like to subscribe 2 public folder (public/test/test1 and >>> public/test/test2). >>> >>> My user (ldaptestuser) is an ldap user and this user is member of the >>> ldap group (ldaptestgroup) which does have all dovecot-acl rights on >>> these folders. >>> >>> imap-1 # cat /opt/mail/_public/publictest/.test*/dovecot-acl >>> group=ldaptestgroup akxeilprwts >>> group=ldaptestgroup akxeilprwts >>> >>> I am now connecting with my mail client to imap-1 (throught haproxy) and >>> the subscription to this folder works. The file which is written looks >>> like: >>> >>> imap-1 # cat /opt/mail/ldaptestuser/Mails/subscriptions >>> Sent >>> publictest/test/test1 >>> publictest/test/test2 >>> >>> Now I am awaiting the synch to imap-2, but the file which it written >>> looks like: >>> >>> imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions >>> Sent >>> >>> If I modify the dovecot-acl for .test1 to >>> >>> imap-1 # cat /opt/mail/_public/publictest/.test1/dovecot-acl >>> group=ldaptestgroup akxeilprwts >>> user=ldaptestuser akxeilprwts >>> >>> and execute the subscription again - the synced file looks like: >>> >>> imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions >>> Sent >>> publictest/test/test1 >>> >>> The subscription of public folder test2 will also been synced, if I add >>> my ldaptestuser to the acl file for this folder. >>> >>> 2. Another issue is to unsubscribe a public folder. If I unsubscribe >>> folder test1, it is written to subscriptions file on the imap where I am >>> connected, but it is NOT synced even if my user and group are configured >>> at the dovecot-acl file. If I then unsubscribe a not public folder (like >>> Sent), the former unsubscribed folder test1 is (faulty) subscribed >>> again. But both imap do have the same subscriptions for my ldaptestuser >>> user. >>> >>> I do have the behavior with dovecot-2.2.26 and dovecot-2.2.27 on >>> CentOS-7 (selinux disabled). >>> >>> If you need more information like the dovecot -n or some other stuff >>> give me a short notice. >>> >>> Mike; >>> > From mikefroehner at gmx.de Fri Dec 16 15:41:40 2016 From: mikefroehner at gmx.de (=?UTF-8?Q?Mike_Fr=c3=b6hner?=) Date: Fri, 16 Dec 2016 16:41:40 +0100 Subject: public folder subscriptions sync issue with ldap user/group in dovecot-acl In-Reply-To: References: <3ad12db0-c224-5652-e99b-6625fb236aca@gmx.de> <93219fbe-50fd-e50c-aa62-5639bc190b12@gmx.de> <833927C3-931F-4E0E-9425-A6389B3C2188@iki.fi> Message-ID: Hi again, here some more debugs: On 12/16/2016 03:25 PM, Mike Fr?hner wrote: > Thanks for your reply Timo. > > On 12/14/2016 06:40 PM, Timo Sirainen wrote: >> On 14 Dec 2016, at 11.16, Mike Fr?hner > > wrote: >>> >>> I made some additional tests and found that also local unix groups are >>> not working in replacement for my ldap groups as discribed below. >>> >>> Do groups in dovecot-acl intendedly not work? >> >> http://wiki2.dovecot.org/ACL -> ACL groups support works by returning a >> comma-separated acl_groups extra field from userdb, which contains all >> the groups the user belongs to. User's UNIX groups have no effect on >> ACLs (you can "enable" them by using a special post-login script). > > I think I have configured the userdb right, because the debug log tells > me this: > > imap-1 dovecot: imap(ldaptestuser): Debug: acl: acl username = ldaptestuser > imap-1 dovecot: imap(ldaptestuser): Debug: acl: owner = 1 > imap-1 dovecot: imap(ldaptestuser): Debug: acl: group added: mailusers > imap-1 dovecot: imap(ldaptestuser): Debug: acl: group added: ldaptestgroup Well, the IMAP debug lists/adds the groups, but not the doveadm: Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: auth PASS input: user=ldaptestuser Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: auth USER input: ldaptestuser home=/opt/mail/ldaptestuser mail=maildir:/opt/mail/ldaptestuser/Mails gid=991 uid=834603987 Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: Added userdb setting: mail=maildir:/opt/mail/ldaptestuser/Mails Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: Effective uid=834603987, gid=991, home=/opt/mail/ldaptestuser Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: Namespace public-test: type=public, prefix=public/test/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=no location=maildir:/opt/mail/_public/test Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: maildir++: root=/opt/mail/_public/test, index=, indexpvt=, control=, inbox=, alt= Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: acl: initializing backend with data: vfile Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: acl: acl username = ldaptestuser Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: acl: owner = 0 Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: acl vfile: Global ACLs disabled The debug output equals on server imap-1 and imap-2. > >> >>> >>> On 12/13/2016 03:47 PM, Mike Fr?hner wrote: >>>> Hello people, >>>> >>>> I am having an issue with 'doveadm sync'. I am currently trying to have >>>> two dovecots behind an haproxy (works fine). Therefore I configured >>>> these two dovecot server (imap-1/imap-2) to sync throught dsync. This >>>> works just partly. The sync of the maiboxes is fine, but the sync of >>>> the >>>> subscriptions file just works partly. It works for private folder >>>> subscription, but not completly for public folder subscription. I found >>>> two issues, if I am using LDAP (user/groups) in dovecot ACLs. >>>> >>>> 1. I would like to subscribe 2 public folder (public/test/test1 and >>>> public/test/test2). >>>> >>>> My user (ldaptestuser) is an ldap user and this user is member of the >>>> ldap group (ldaptestgroup) which does have all dovecot-acl rights on >>>> these folders. >>>> >>>> imap-1 # cat /opt/mail/_public/publictest/.test*/dovecot-acl >>>> group=ldaptestgroup akxeilprwts >>>> group=ldaptestgroup akxeilprwts >>>> >>>> I am now connecting with my mail client to imap-1 (throught haproxy) >>>> and >>>> the subscription to this folder works. The file which is written looks >>>> like: >>>> >>>> imap-1 # cat /opt/mail/ldaptestuser/Mails/subscriptions >>>> Sent >>>> publictest/test/test1 >>>> publictest/test/test2 >>>> >>>> Now I am awaiting the synch to imap-2, but the file which it written >>>> looks like: >>>> >>>> imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions >>>> Sent >>>> >>>> If I modify the dovecot-acl for .test1 to >>>> >>>> imap-1 # cat /opt/mail/_public/publictest/.test1/dovecot-acl >>>> group=ldaptestgroup akxeilprwts >>>> user=ldaptestuser akxeilprwts >>>> >>>> and execute the subscription again - the synced file looks like: >>>> >>>> imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions >>>> Sent >>>> publictest/test/test1 >>>> >>>> The subscription of public folder test2 will also been synced, if I add >>>> my ldaptestuser to the acl file for this folder. >>>> >>>> 2. Another issue is to unsubscribe a public folder. If I unsubscribe >>>> folder test1, it is written to subscriptions file on the imap where >>>> I am >>>> connected, but it is NOT synced even if my user and group are >>>> configured >>>> at the dovecot-acl file. If I then unsubscribe a not public folder >>>> (like >>>> Sent), the former unsubscribed folder test1 is (faulty) subscribed >>>> again. But both imap do have the same subscriptions for my ldaptestuser >>>> user. >>>> >>>> I do have the behavior with dovecot-2.2.26 and dovecot-2.2.27 on >>>> CentOS-7 (selinux disabled). >>>> >>>> If you need more information like the dovecot -n or some other stuff >>>> give me a short notice. >>>> >>>> Mike; >>>> >> > From micah at riseup.net Fri Dec 16 16:48:30 2016 From: micah at riseup.net (micah anderson) Date: Fri, 16 Dec 2016 11:48:30 -0500 Subject: making a plugin encrypt index data Message-ID: <8760mjrfa9.fsf@riseup.net> Hello, I'm encrypting mail on disk using a plugin[0], but the index files are not encrypted (specifically the dovecot.index.cache can be read). I want to do is encrypt index on disk, so I'm looking for how a plugin can achieve that by hooking into the right locations. Is that easily possible in a plugin? I can turn off those indexes by passing INDEX=MEMORY, but that isn't possible if I use sdbox/mdbox. thanks for any suggestions! micah 0. https://0xacab.org/riseuplabs/tofu-scrambler From pbopbo at freemail.hu Fri Dec 16 17:29:31 2016 From: pbopbo at freemail.hu (Peter Benko) Date: Fri, 16 Dec 2016 18:29:31 +0100 (CET) Subject: doveadm acl set negative rights not supported? Message-ID: Hi all, I'm trying to set an ACL with negative rights. I have no problems setting it with standard IMAP commands, but I'm unable to do it with the doveadm acl command. I tried: sudo -u vmail doveadm acl set -u "user at domain" Spam user="-user at domain" lookup (notice the "-" before the username) Unfortunately, this adds a (positive) ACL for the user named "-user at domain" instead of adding a negative one for the user "user at domain". Am I messing up something or is negative ACL support missing from doveadm? I have not seen anything in the docs about this... Regards, Peter From mrforsythexeter at googlemail.com Fri Dec 16 13:53:59 2016 From: mrforsythexeter at googlemail.com (Shaun Forsyth) Date: Fri, 16 Dec 2016 13:53:59 +0000 Subject: Vacation Sending To Root Message-ID: Dovecot Version 2.0.9 I am having an issue where all vacation messages are being sent to root. Is any one able to advise. Dovecot Log Shows :- Sieve: msgid=< CAMD5TViw0sSigGm8JY5WOv0ROs1UdCJFnvb9vo-RzcNN74E92Q at mail.xxxxxx.com>: sent vacation response to The emails are handed off to dovecot from sendmail using procmail :0 w | $DELIVER The variable $DELIVER is set as DELIVER="/usr/libexec/dovecot/deliver" I do have DROPPRIVS=YES in procmail, however I don't think deliver works without this. Any advice would greatly help. Shaun From dovecot at list-post.mks-mail.de Fri Dec 16 19:10:40 2016 From: dovecot at list-post.mks-mail.de (=?UTF-8?Q?Markus_Sch=c3=b6nhaber?=) Date: Fri, 16 Dec 2016 20:10:40 +0100 Subject: v2.2.27 Debian packages on xi.dovecot.fi In-Reply-To: <57f67595-5e6d-7864-ccbb-d36c7d3caa67@rename-it.nl> References: <8823685d-154c-1ffa-0833-5b39a66193b7@list-post.mks-mail.de> <57f67595-5e6d-7864-ccbb-d36c7d3caa67@rename-it.nl> Message-ID: <74a7a73c-0e9d-6f7e-1167-807bea005d3f@list-post.mks-mail.de> Stephan Bosch, Fri, 16 Dec 2016 13:37:35 +0100: > > Op 16-12-2016 om 10:30 schreef Markus Sch?nhaber: >> at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can >> we expect packages for v2.2.27 to appear there? > > Actually, there are packages there that have the 2.2.27 release in > there, but they are not marked as such. Ever since the git move I > haven't finished fixing the automatic version updates. It is still a > manual effort that I need to do after a release. Did that now. > > However, I have a much more advanced version of the builder running in a > test environment for a while now. It is available here (only for Jessie > atm): > > http://xi.rename-it.nl/debian.new/pool/ Good to know. Thanks a lot for your packaging efforts! -- Regards mks From aki.tuomi at dovecot.fi Fri Dec 16 19:25:52 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Fri, 16 Dec 2016 21:25:52 +0200 (EET) Subject: making a plugin encrypt index data In-Reply-To: <8760mjrfa9.fsf@riseup.net> References: <8760mjrfa9.fsf@riseup.net> Message-ID: <1389288924.4260.1481916353769@appsuite-dev.open-xchange.com> > On December 16, 2016 at 6:48 PM micah anderson wrote: > > > > Hello, > > I'm encrypting mail on disk using a plugin[0], but the index files are > not encrypted (specifically the dovecot.index.cache can be read). > > I want to do is encrypt index on disk, so I'm looking for how a plugin > can achieve that by hooking into the right locations. Is that easily > possible in a plugin? > > I can turn off those indexes by passing INDEX=MEMORY, but that isn't > possible if I use sdbox/mdbox. > > thanks for any suggestions! > micah > > 0. https://0xacab.org/riseuplabs/tofu-scrambler Hi! At the moment it's not possible without making new storage class. We are planning to add support for fs drivers for indexes at some point. Aki Tuomi Dovecot Oy From aki.tuomi at dovecot.fi Fri Dec 16 19:27:46 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Fri, 16 Dec 2016 21:27:46 +0200 (EET) Subject: service(indexer-worker): child 18977 killed with signal 11 (core dumped) In-Reply-To: References: Message-ID: <1694174708.4262.1481916467112@appsuite-dev.open-xchange.com> > On December 16, 2016 at 2:56 PM Matteo Biagini wrote: > > > Hello to everybody, > first of all: thanks a lot for your hard work and for this nice piece > of software! > > After many search about the following SIGSEGV, I decide to post the backtrace > and I hope to have avoided duplicated thread. > The problem arise after I enable clucene fts. I tryed the clucene ports version > (I am using OpenBSD) and a fixed version from github > (Blue-Rocket/clucene::feature/pod) which contains FreeBSD fixes and > others memory leak patches, but the problem persists. > I built either dovecot-* and clucene-core with -g and the following > logs are taken > from that version. > Maybe, I can do more debugging but I don't know how; some ideas? > > thanks a lot > > > Hi! This is known issue at the moment and we are looking into it. Currently our only advice is to use something else, such as solr, for indexing, until we get this fixed. Aki From aki.tuomi at dovecot.fi Fri Dec 16 21:27:58 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Fri, 16 Dec 2016 23:27:58 +0200 (EET) Subject: Fwd: Re: making a plugin encrypt index data In-Reply-To: <1120691088.4450.1481923509025@appsuite-dev.open-xchange.com> References: <8760mjrfa9.fsf@riseup.net> <1389288924.4260.1481916353769@appsuite-dev.open-xchange.com> <8737hnr6p7.fsf@riseup.net> <1120691088.4450.1481923509025@appsuite-dev.open-xchange.com> Message-ID: <1887005123.4458.1481923679201@appsuite-dev.open-xchange.com> > ---------- Original Message ---------- > From: Aki Tuomi > To: micah anderson > Date: December 16, 2016 at 11:25 PM > Subject: Re: making a plugin encrypt index data > > When we released our encryption plugin, mail-crypt, it's capabilities include fs-crypt. This can be used to encrypt things like FTS indexes and attachments, and with suitable mail storage, such as obox, you can also encrypt indexes. > > To extend this support to dbox or maildir, does require rather involved changes in dovecot core, which currently has no support for fs-api in index handling. This might happen on v2.3 or v2.4, depending. > > I somehow suspect that the work estimate would exceed your budget. But it is going to happen, it's just matter of time. Can't give you any timeline though, since we have not decided on one yet. > > Aki > > > On December 16, 2016 at 9:53 PM micah anderson wrote: > > > > > > > > Hi Aki, > > > > Do you have any idea approximately when this would be planned for? > > > > We are also interested potentially paying for the ability to encrypt our > > indexes, as this is a major concern for us. We don't have a lot of money > > as a non-profit, but if there is a possibility of contract work, we > > would be interested to know what it would cost to do it. > > > > thanks, > > micah > > > > Aki Tuomi writes: > > > > >> On December 16, 2016 at 6:48 PM micah anderson wrote: > > >> > > >> > > >> > > >> Hello, > > >> > > >> I'm encrypting mail on disk using a plugin[0], but the index files are > > >> not encrypted (specifically the dovecot.index.cache can be read). > > >> > > >> I want to do is encrypt index on disk, so I'm looking for how a plugin > > >> can achieve that by hooking into the right locations. Is that easily > > >> possible in a plugin? > > >> > > >> I can turn off those indexes by passing INDEX=MEMORY, but that isn't > > >> possible if I use sdbox/mdbox. > > >> > > >> thanks for any suggestions! > > >> micah > > >> > > >> 0. https://0xacab.org/riseuplabs/tofu-scrambler > > > > > > Hi! > > > > > > At the moment it's not possible without making new storage class. We are planning to add support for fs drivers for indexes at some point. > > > > > > Aki Tuomi > > > Dovecot Oy From ruga at protonmail.com Sat Dec 17 10:57:12 2016 From: ruga at protonmail.com (Ruga) Date: Sat, 17 Dec 2016 05:57:12 -0500 Subject: Existing shared mailbox ... does not exist In-Reply-To: References: Message-ID: # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf auth_default_realm = example.com auth_mechanisms = cram-md5 auth_realms = example.com auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_winbind_helper_path = default_client_limit = 256 default_internal_user = _dovecot default_login_user = _dovenull first_valid_uid = 458 mail_access_groups = vmail mail_cache_min_mail_count = 25 mail_gid = vmail mail_location = maildir:/var/vmail/%d/%n mail_plugins = " acl quota" mail_privileged_group = vmail mail_uid = vmail mailbox_list_index = yes namespace { hidden = no inbox = no list = yes location = maildir:/var/vmail/%d/shared:INDEXPVT=/var/vmail/%d/%n/shared mailbox Junk { auto = create comment = Shared junk folder special_use = \Junk } mailbox info { auto = subscribe special_use = } mailbox jobs { auto = create special_use = } mailbox news { auto = create special_use = } prefix = Shared/ separator = / subscriptions = no type = public } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Archive { special_use = \Archive } mailbox Drafts { special_use = \Drafts } mailbox Junk { comment = SPAM special_use = \Junk } mailbox Notes { special_use = } mailbox Sent { special_use = \Sent } mailbox Trash { special_use = \Trash } mailbox virtual/Flagged { comment = All my flagged messages special_use = \Flagged } prefix = separator = / subscriptions = yes type = private } passdb { args = scheme=CRAM-MD5 username_format=%n@%d /domains/%d/etc/mail/passdb driver = passwd-file } plugin { acl = vfile:/etc/dovecot/dovecot-acl.conf:cache_secs=300 acl_shared_dict = file:/var/vmail/%d/shared-mailboxes.db quota = maildir:User quota:ns= quota2 = maildir:Shared quota:ns=Shared/ quota_exceeded_message = Quota exceeded. quota_rule = *:storage=0 quota_rule2 = Junk:storage=+100M quota_rule3 = Trash:storage=+100M } protocols = imap quota_full_tempfail = yes service auth-worker { user = $default_internal_user } service auth { client_limit = 300 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } service_count = 1 } userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = static override_fields = home=/var/vmail/%d/%n mail=maildir:/var/vmail/%d/%n } protocol imap { mail_plugins = " acl quota imap_acl imap_quota" } From ruga at protonmail.com Sat Dec 17 11:04:55 2016 From: ruga at protonmail.com (Ruga) Date: Sat, 17 Dec 2016 06:04:55 -0500 Subject: Existing shared mailbox ... does not exist In-Reply-To: References: Message-ID: From dovecot's own log, a long stream of errors: [...] Error: /var/vmail/[example.com/username/shared/.foldername](http://example.com/isername/shared/.foldername) com/dovecot.index.pvt reset, view is now inconsistent From markc at renta.net Sat Dec 17 11:35:25 2016 From: markc at renta.net (Mark Constable) Date: Sat, 17 Dec 2016 21:35:25 +1000 Subject: Domains on different IPs Message-ID: I want to supply separate Letsencrypt certificates for each virtual domain and seeing that SNI does not work I need to allocate separate IPs. Could anyone give some pointers, or keywords to search for, on... a) how to make dovecot listen for different domains on different IPs? b) how to configure separate SSL certs for each of these IPs? From aki.tuomi at dovecot.fi Sat Dec 17 12:44:04 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Sat, 17 Dec 2016 14:44:04 +0200 (EET) Subject: Domains on different IPs In-Reply-To: References: Message-ID: <301519685.11.1481978646343@appsuite-dev.open-xchange.com> > On December 17, 2016 at 1:35 PM Mark Constable wrote: > > > I want to supply separate Letsencrypt certificates for each virtual domain > and seeing that SNI does not work I need to allocate separate IPs. Could > anyone give some pointers, or keywords to search for, on... > > a) how to make dovecot listen for different domains on different IPs? > > b) how to configure separate SSL certs for each of these IPs? Au contraire, dovecot does support SNI. On earlier versions, it works by specifying local_name server.name { ssl_cert= I don?t know if this is considered OT, but dovecot has support for sieve. I had a rule set running under Mac OS X 10.8.5 Server 2.2.5 which I did maintain by hand on the server because a while before Mac OS X Server had dropped support for Squirrelmail. Now I wonder if there is a decent way to get sieve running again on macOS 10.12 Sierra with Server 5.2 G From tom at talpey.com Sat Dec 17 22:57:54 2016 From: tom at talpey.com (Tom Talpey) Date: Sat, 17 Dec 2016 17:57:54 -0500 Subject: Antispam plugin: insufficent error messages In-Reply-To: <4985521.DvuYhMxLoT@desktop> References: <4985521.DvuYhMxLoT@desktop> Message-ID: <9cfb6d5b-4335-23e5-2798-b709edf86c53@talpey.com> On 11/28/2016 3:28 PM, Volker Wysk wrote: > Hi! > > "Dovecot always logs a detailed error message if something goes wrong. > If it doesn't, it's considered a bug and will be fixed." (http:// > wiki2.dovecot.org/Logging) > > I'm trying to set up a spam filter with dovecot-antispam and dspam as backend. > > When I move a spam message from INBOX to Spam, I get this in syslog: > > Nov 28 21:15:58 desktop imap: antispam: mailbox_is_unsure(Spam): 0 > Nov 28 21:15:58 desktop imap: antispam: mailbox_is_trash(INBOX): 0 > Nov 28 21:15:58 desktop imap: antispam: mailbox_is_trash(Spam): 0 > Nov 28 21:15:58 desktop imap: antispam: mail copy: from trash: 0, to trash: 0 > Nov 28 21:15:58 desktop imap: antispam: mailbox_is_spam(INBOX): 0 > Nov 28 21:15:58 desktop imap: antispam: mailbox_is_spam(Spam): 1 > Nov 28 21:15:58 desktop imap: antispam: mailbox_is_unsure(INBOX): 0 > Nov 28 21:15:58 desktop imap: antispam: mail copy: src spam: 0, dst spam: 1, > src unsure: 0 > > There are no log entries about how dspam is called, or what goes on. Indeed, > dspam doesn't get called at all. I know, because I've examined the antispam- > plugin source code. There would be a log message if dspam was called. > > It's hard to study the source code, because there are hardly any comments. > > I have been able to trace the problem to function signature_extract_to_list() > in signature.c. There, -1 is returned: > > int signature_extract_to_list(const struct signature_config *cfg, > struct mailbox_transaction_context *t, > struct mail *mail, struct siglist **list, > enum classification wanted) > { > const char *const *signatures; > struct siglist *item; > > signatures = get_mail_headers(mail, cfg->signature_hdr); > if (!signatures || !signatures[0]) { > if (!cfg->signature_nosig_ignore) { > > mail_storage_set_error(t->box->storage, > ME(NOTPOSSIBLE) > "antispam signature not found"); > return -1; /* <-- HERE */ > } else { > return 0; > } > } > > while (signatures[1]) > signatures++; > > item = i_new(struct siglist, 1); > item->next = *list; > item->wanted = wanted; > item->sig = i_strdup(signatures[0]); > > *list = item; > > return 0; > } > > So, what's happening is "antispam signature not found". My question: What > does this mean? What's going on? > I too encountered this same issue after upgrading to 2.2.27. I traced it to an apparent change in Dovecot's mail_get_headers() function, which now returns a non-zero value even when the header is found. This wasn't the behavior in 2.2.24, though I'm not sure if it was in .25 or .26. I haven't tracked down the details further. Anyway, the antispam plugin uses this API to find the X-DSPAM-Signature header, and the change causes the plugin to abort. This happens in the plugin's antispam-plugin.h wrapper, which I modified as follows. I'm confused why the dovecot API behavior changed, but I hope this helps! Tom. *** antispam-plugin.h 2016-12-17 17:25:48.571704442 -0500 --- antispam-plugin.h.orig 2016-12-17 17:24:55.010093416 -0500 *************** *** 268,275 **** static inline const char *const * get_mail_headers(struct mail *mail, const char *hdr) { ! const char *const *ret = NULL; ! mail_get_headers(mail, hdr, &ret); return ret; } --- 268,276 ---- static inline const char *const * get_mail_headers(struct mail *mail, const char *hdr) { ! const char *const *ret; ! if (mail_get_headers(mail, hdr, &ret)) ! return NULL; return ret; } From petros.fraser at gmail.com Sun Dec 18 03:50:46 2016 From: petros.fraser at gmail.com (Peter Fraser) Date: Sat, 17 Dec 2016 22:50:46 -0500 Subject: Upgrade from version 1 to 2 Message-ID: Hi All I am upgrading from dovecot-1.2.17 to dovecot2-2.2.27_4. I configured version 2 from scratch. I have email in the maildir format. Would it be ok in theory if I simply copy over the email files from the version 1 server to the version 2 server or are there any hidden dangers here? Any problems with indexing? Thanks for any advice From post at volker-wysk.de Sun Dec 18 07:48:42 2016 From: post at volker-wysk.de (Volker Wysk) Date: Sun, 18 Dec 2016 08:48:42 +0100 Subject: Antispam plugin: insufficent error messages In-Reply-To: <9cfb6d5b-4335-23e5-2798-b709edf86c53@talpey.com> References: <4985521.DvuYhMxLoT@desktop> <9cfb6d5b-4335-23e5-2798-b709edf86c53@talpey.com> Message-ID: <1887665.uqtIZhKeUU@desktop> Am Samstag, 17. Dezember 2016, 17:57:54 CET schrieb Tom Talpey: > I too encountered this same issue after upgrading to 2.2.27. I traced it > to an apparent change in Dovecot's mail_get_headers() function, which > now returns a non-zero value even when the header is found. This wasn't > the behavior in 2.2.24, though I'm not sure if it was in .25 or .26. > I haven't tracked down the details further. > > Anyway, the antispam plugin uses this API to find the X-DSPAM-Signature > header, and the change causes the plugin to abort. This happens in the > plugin's antispam-plugin.h wrapper, which I modified as follows. > > I'm confused why the dovecot API behavior changed, but I hope this > helps! Thank you for your help, but I've already done it differently now. I'm using the spam filter capabilities of my mail reader (KMail). This uses an external spam filter (I've chosen CRM114). That's not optimal, because I have two spam filters now (on my desktop and my laptop), and no spam filter for my smartphone, but it works. Bye Volker From tss at iki.fi Sun Dec 18 10:00:46 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 18 Dec 2016 12:00:46 +0200 Subject: Antispam plugin: insufficent error messages In-Reply-To: <9cfb6d5b-4335-23e5-2798-b709edf86c53@talpey.com> References: <4985521.DvuYhMxLoT@desktop> <9cfb6d5b-4335-23e5-2798-b709edf86c53@talpey.com> Message-ID: On 18 Dec 2016, at 0.57, Tom Talpey wrote: > > > I too encountered this same issue after upgrading to 2.2.27. I traced it > to an apparent change in Dovecot's mail_get_headers() function, which > now returns a non-zero value even when the header is found. This wasn't > the behavior in 2.2.24, though I'm not sure if it was in .25 or .26. > I haven't tracked down the details further. > > Anyway, the antispam plugin uses this API to find the X-DSPAM-Signature > header, and the change causes the plugin to abort. This happens in the > plugin's antispam-plugin.h wrapper, which I modified as follows. > > I'm confused why the dovecot API behavior changed, but I hope this > helps! It was mostly an accident. There was a mismatch between mail_get_headers() and mail_get_headers_utf8() return values, which was fixed the wrong way. Also I think there might have been some code that assumed that mail_get_headers() would return > 0 on success. Anyway, too late to change back now... > ! const char *const *ret = NULL; > ! mail_get_headers(mail, hdr, &ret); > return ret; That works, but maybe a nicer way that works for both old and new API and checks also the return value: if (mail_get_headers(mail, hdr, &ret) < 0) return NULL; > } > > --- 268,276 ---- > static inline const char *const * > get_mail_headers(struct mail *mail, const char *hdr) > { > ! const char *const *ret; > ! if (mail_get_headers(mail, hdr, &ret)) > ! return NULL; > return ret; > } From zhb at iredmail.org Sun Dec 18 12:26:24 2016 From: zhb at iredmail.org (Zhang Huangbin) Date: Sun, 18 Dec 2016 20:26:24 +0800 Subject: Error while migrating mailbox with 'doveadm sync' Message-ID: <751ED64D-7B96-40DE-887B-B0E138EEA8F3@iredmail.org> Dear all, I successfully migrated hundreds of mailboxes with Dovecot 2.2.24 on OpenBSD 6.0 (amd64. Old server is OpenBSD 5.1, i386, Dovecot-2.0.17), but got error while migrating 3 mailboxes: # doveadm -o mail_fsync=never sync -1 -R -s '' -u user at domain.com imapc: dsync(user at domain.com): Panic: file mailbox-alias-plugin.c: line 77 (mailbox_symlink_exists): assertion failed: (ret > 0) Abort trap Same error while running ?doveadm ? backup ?'. What does this error actually mean? How can i fix it? - Here?s full log running doveadm with ?-D? option: http://pastebin.com/Um5fbuNM - ?dovecot -n? on old server: http://pastebin.com/4E6xzFKU - ?dovecot -n? on new server: http://pastebin.com/4uHwQnMN I checked release notes of Dovecot 2.2.25/26/27, there?re 3 fixes related to 'doveadm sync?, but not sure whether it helps fix this issue. 2.2.26: + doveadm sync/backup: Added -I parameter to skip too large mails. + doveadm sync/backup: Fixed -t parameter and added -e for "end date?. 2.2.27: - doveadm sync -1: Fixed handling mailbox GUID conflicts. From zhb at iredmail.org Sun Dec 18 12:42:18 2016 From: zhb at iredmail.org (Zhang Huangbin) Date: Sun, 18 Dec 2016 20:42:18 +0800 Subject: Error while migrating mailbox with 'doveadm sync' In-Reply-To: <751ED64D-7B96-40DE-887B-B0E138EEA8F3@iredmail.org> References: <751ED64D-7B96-40DE-887B-B0E138EEA8F3@iredmail.org> Message-ID: > On Dec 18, 2016, at 8:26 PM, Zhang Huangbin wrote: > > # doveadm -o mail_fsync=never sync -1 -R -s '' -u user at domain.com imapc: > dsync(user at domain.com): Panic: file mailbox-alias-plugin.c: line 77 (mailbox_symlink_exists): assertion failed: (ret > 0) > Abort trap Checked IMAP folders on old server, this user has ?.Sent? and ?.Sent Messages? on old server, but ?.Sent Message? is configured to be a alias mailbox on new server. After merge 2 folders, then sync works fine. Sorry about the noise. From stephan at rename-it.nl Sun Dec 18 14:16:20 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Sun, 18 Dec 2016 15:16:20 +0100 Subject: RFC 3501 violation in FETCH BODY responses In-Reply-To: <20160822122932.t5d5iuzwdulfdfbv@localhost.localdomain> References: <20160822122932.t5d5iuzwdulfdfbv@localhost.localdomain> Message-ID: <6508fa59-a663-3644-8702-7943914f4c06@rename-it.nl> Op 8/22/2016 om 2:29 PM schreef Guilhem Moulin: > Hi there, > > Quoting RFC 3501 sec. 7.4.2 ?FETCH Response? (data item BODYSTRUCTURE): > > ?A body type of type MESSAGE and subtype RFC822 contains, > immediately after the basic fields, the envelope structure, body > structure, and size in text lines of the encapsulated message.? > > According the ABNF (RFC 3501 sec. 9) the envelope structure is that of > the ENVELOPE FETCH data item, and the env-{from,sender,reply-to,to,cc, > bcc} fields are non-space-separated address lists: > > body-type-msg = media-message SP body-fields SP envelope SP body SP body-fld-lines > envelope = "(" env-from SP ? SP env-to SP ? ")" > env-from = "(" 1*address ")" / nil > env-to = "(" 1*address ")" / nil > > While this is indeed the case for ?FETCH ? (ENVELOPE)?, for ?FETCH ? > (BODY)? dovecot 2.2.25 adds a space between addresses of an address list > of the envelope structure of an encapsulated MESSAGE/RFC822 message. > > See the attached patch to ?src/lib-imap/test-imap-bodystructure.c?, > which currently (2.2.25) fails as follows > > test-imap-bodystructure.c:122: Assert failed: strcmp(str_c(str), testmsg_body) == 0 > test-imap-bodystructure.c:129: Assert failed: strcmp(str_c(str), testmsg_bodystructure) == 0 > imap bodystructure parser ............................................ : FAILED > > because the ?env-to? field of the envelope structure of the encapsulated > MESSAGE/RFC822 message is printed as > > ((NIL NIL "sub-to1" "domain.org") (NIL NIL "sub-to2" "domain.org")) > > while it should be > > ((NIL NIL "sub-to1" "domain.org")(NIL NIL "sub-to2" "domain.org")) > > After a quick look at the source, this seems to be due to > src/lib-imap/imap-bodystructure.c:imap_write_list, which always > separates list items with spaces. In the case of an envelope, only the > top-level list should be space-separated. Indeed, not adding a space > between items of type IMAP_ARG_LIST in the recursive call makes the test > pass again. Fixed: https://github.com/dovecot/core/commit/f549b400d50935754cbeb6ceabd922ab777b4d77 Regards, Stephan. From ricardo at wenn.com Sun Dec 18 21:50:09 2016 From: ricardo at wenn.com (Ricardo Branco) Date: Sun, 18 Dec 2016 21:50:09 +0000 Subject: Renumbering UID on messages Message-ID: I am having a problem with Horde due to large variations in email UID for a few users. At one time they were receiving thousands of emails a day, they have deleted all these messages but because they still have early emails in the mailbox the UID range from start to now is massive. We use Horde webmail and it creates an internal array based on range of messages but due to large UID range it eats though the ram. If I use dsync on a mailbox will the UIDs be renumbered? -- The information contained in or attached to this email is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorised to and must not disclose, copy, distribute, or retain any message or any part of it. If you have received an email in error, please contact the sender and delete the material from any computer. The contents of this email are not for publication unless specifically stated. Furthermore, the information contained in this message, and any attachment(s) thereto, is for information purposes only and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of WENN or its subsidiaries and associated companies. We make every effort to keep our network free from viruses. However, you do need to check this e-mail and any attachments to it for viruses as we can take no responsibility for any computer virus which may be transferred by way of this e-mail. WENN Ltd: Registered Office: 4a Tileyard Studios, Tileyard Road, London, N7 9AH, England. Registered No: 4375163. Place of Registration: United Kingdom. USA Entertainment News Inc (d/b/a WENN): Registered Office: 352 7th Avenue, Suite 1105, New York, NY 10001-5657, USA The WENN name, design and related marks are trademarks of the WENN group of companies. (c) 2014 All Rights Reserved. From pch at myzel.net Sun Dec 18 23:05:33 2016 From: pch at myzel.net (Peter Chiochetti) Date: Mon, 19 Dec 2016 00:05:33 +0100 Subject: Renumbering UID on messages In-Reply-To: References: Message-ID: Am 2016-12-18 um 22:50 schrieb Ricardo Branco: > I am having a problem with Horde due to large variations in email UID > for a few users. > At one time they were receiving thousands of emails a day, they have > deleted all these messages but because they still have early emails in > the mailbox the UID range from start to now is massive. > We use Horde webmail and it creates an internal array based on range of > messages but due to large UID range it eats though the ram. Not an answer, just curious: PHP arrays are sparse by design. Must be something peculiar to the way Horde does IDs. > If I use dsync on a mailbox will the UIDs be renumbered? ? -- peter From ricardo at wenn.com Mon Dec 19 00:00:46 2016 From: ricardo at wenn.com (Ricardo Branco) Date: Mon, 19 Dec 2016 00:00:46 +0000 Subject: Renumbering UID on messages In-Reply-To: References: Message-ID: this was the ticket I posted re the horde issue. https://bugs.horde.org/ticket/13761 On 18 Dec 2016 23:05, Peter Chiochetti wrote: > Am 2016-12-18 um 22:50 schrieb Ricardo Branco: >> I am having a problem with Horde due to large variations in email UID >> for a few users. >> At one time they were receiving thousands of emails a day, they have >> deleted all these messages but because they still have early emails in >> the mailbox the UID range from start to now is massive. >> We use Horde webmail and it creates an internal array based on range of >> messages but due to large UID range it eats though the ram. > > Not an answer, just curious: PHP arrays are sparse by design. Must be > something peculiar to the way Horde does IDs. > >> If I use dsync on a mailbox will the UIDs be renumbered? > > ? > From mwd at md5i.com Mon Dec 19 00:57:12 2016 From: mwd at md5i.com (Michael Welsh Duggan) Date: Sun, 18 Dec 2016 19:57:12 -0500 Subject: fts-solr: Returning 400 on searches; unescaped braces Message-ID: <87d1gorb13.fsf@md5i.com> Using Debian, dovecot-solr 1:2.2.26.0-4, and solr-tomcat 3.6.2+dfsg-9, I am getting 400 errors when doing searches. Here is an example search query from dovecot that failed (captured with wireshark): Frame 23: 338 bytes on wire (2704 bits), 338 bytes captured (2704 bits) on interface 0 Linux cooked capture Internet Protocol Version 6, Src: ::1, Dst: ::1 Transmission Control Protocol, Src Port: 56860, Dst Port: 8080, Seq: 1, Ack: 1, Len: 250 Hypertext Transfer Protocol GET /solr/select?fl=uid,score&rows=2664&sort=uid+asc&q={!lucene+q.op%3dAND}(hdr:test+OR+body:test)&fq=%2Bbox:6d5de009f991854df726000012cf7b9c+%2Buser:md5i HTTP/1.1\r\n Host: localhost:8080\r\n Date: Mon, 19 Dec 2016 00:25:56 GMT\r\n Connection: Keep-Alive\r\n \r\n [Full request URI: http://localhost:8080/solr/select?fl=uid,score&rows=2664&sort=uid+asc&q={!lucene+q.op%3dAND}(hdr:test+OR+body:test)&fq=%2Bbox:6d5de009f991854df726000012cf7b9c+%2Buser:md5i] [HTTP request 1/1] [Response in frame: 25] Here is the same query from firefox, which succeeds: Frame 66: 646 bytes on wire (5168 bits), 646 bytes captured (5168 bits) on interface 0 Linux cooked capture Internet Protocol Version 6, Src: ::1, Dst: ::1 Transmission Control Protocol, Src Port: 56862, Dst Port: 8080, Seq: 1, Ack: 1, Len: 558 Hypertext Transfer Protocol GET /solr/select?fl=uid,score&rows=2664&sort=uid+asc&q=%7B!lucene+q.op%3DAND%7D(hdr:test+OR+body:test)&fq=%2Bbox:6d5de009f991854df726000012cf7b9c+%2Buser:md5i HTTP/1.1\r\n Host: localhost:8080\r\n Connection: keep-alive\r\n Cache-Control: max-age=0\r\n Upgrade-Insecure-Requests: 1\r\n User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36\r\n Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8\r\n DNT: 1\r\n Accept-Encoding: gzip, deflate, sdch, br\r\n Accept-Language: en-US,en;q=0.8\r\n \r\n [Full request URI: http://localhost:8080/solr/select?fl=uid,score&rows=2664&sort=uid+asc&q=%7B!lucene+q.op%3DAND%7D(hdr:test+OR+body:test)&fq=%2Bbox:6d5de009f991854df726000012cf7b9c+%2Buser:md5i] [HTTP request 1/1] [Response in frame: 86] The salient difference seems to be the encoding of the braces. Indeed in the tomcat 8 logs, I find the following which seems to corroborate my hypothesis: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986 at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:467) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:667) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:789) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1437) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Indeed the braces are listed in fts-backend-solr.c as part of solr_escape_chars, so don't know how the braces are making it through unencoded. -- Michael Welsh Duggan (md5i at md5i.com) From jean-francois.senechal at ac.marche.be Mon Dec 19 09:30:14 2016 From: jean-francois.senechal at ac.marche.be (=?UTF-8?B?SmVhbi1GcmFuw6dvaXMgU8OpbsOpY2hhbA==?=) Date: Mon, 19 Dec 2016 10:30:14 +0100 Subject: Problem with default_process_limit max 200 Message-ID: Hello, The default_process_limit parameter is limited to 200 On my server there is a lot of connection imap and this figure is quickly reached And users can no longer connect If I try to increase it I get this error message Warning: service auth { client_limit=1000 } is lower than required under max. load (1100) [....] Restarting IMAP/POP3 mail server: dovecotdoveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (1100) Warning: service auth { client_limit=1000 } is lower than required under max. load (1100) How do I solve this problem? My full config # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.11 auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes debug_log_path = /var/log/dovecot.debug default_process_limit = 200 dict { expire = mysql:/etc/dovecot/dovecot-dict-expire.conf.ext } disable_plaintext_auth = no first_valid_gid = 5000 first_valid_uid = 3000 imapc_features = rfc822.size fetch-headers imapc_host = mail.marche.be imapc_list_prefix = INBOX imapc_master_user = cyrus imapc_password = homer imapc_user = dherman info_log_path = /var/log/dovecot.log last_valid_gid = 5000 log_path = /var/log/dovecot.log mail_gid = 5000 mail_location = maildir:~/Maildir:LAYOUT=fs mail_plugins = " expire quota" mail_prefetch_count = 20 maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-master-users driver = passwd-file master = yes } passdb { driver = shadow } plugin { expire = Trash expire2 = Trash/* expire3 = Spam expire_cache = yes expire_dict = proxy::expire quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=150M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=90%% quota-warning 90 %u sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.sieve sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/ stats_refresh = 30 secs stats_track_cmds = yes } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh postmaster_address = jf at marche.be protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 } } service dict { unix_listener dict { group = vmail mode = 0666 } } service imap-login { process_limit = 200 process_min_avail = 2 } service imap { process_limit = 1024 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot } ssl_ca = Hi, with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run ?doveadm expunge -A mailbox Spam savedbefore 30d? dovecot an error: doveadm: Error: dict-client: Commit failed: Dict server timeout: No input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs ago: C1) (reply took 0.000 secs) doveadm: Error: expire: Dictionary commit failed Probably also "doveadm quota recalc -A" fail. Everything worked fine up to version 2.2.24 I hope can be fixed. Thanks -- Alessio Cecchi Postmaster AT http://www.qboxmail.it http://www.linkedin.com/in/alessice From aki.tuomi at dovecot.fi Mon Dec 19 13:28:44 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Mon, 19 Dec 2016 15:28:44 +0200 Subject: doveadm expunge -A Error: Dictionary commit failed In-Reply-To: References: Message-ID: <95519d70-0193-3025-05fb-1260c34a7225@dovecot.fi> On 19.12.2016 15:25, Alessio Cecchi wrote: > Hi, > > with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run > ?doveadm expunge -A mailbox Spam savedbefore 30d? dovecot an error: > > doveadm: Error: dict-client: Commit failed: Dict server timeout: No > input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs > ago: C1) (reply took 0.000 secs) > doveadm: Error: expire: Dictionary commit failed > > Probably also "doveadm quota recalc -A" fail. > > Everything worked fine up to version 2.2.24 > > I hope can be fixed. > Thanks Hi! Can you check your server's logs? Aki From skdovecot at smail.inf.fh-brs.de Mon Dec 19 13:38:35 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 19 Dec 2016 14:38:35 +0100 (CET) Subject: Upgrade from version 1 to 2 In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 17 Dec 2016, Peter Fraser wrote: > I am upgrading from dovecot-1.2.17 to dovecot2-2.2.27_4. I configured > version 2 from scratch. I have email in the maildir format. Would it be ok > in theory if I simply copy over the email files from the version 1 server > to the version 2 server or are there any hidden dangers here? Any problems > with indexing? I upgrades from Dovecot v1 to v2.0 with Maildir without any problem. The indexes got upgraded onb the fly on the first use if the mailbox. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWFfi23z1H7kL/d9rAQLLDgf+J/hcIzVA4EsCKcW8KXo6jkylZREEb3EP Elq6Fl/Z+KPgB8Fk9pnlJY1c9gy9pRlr25c+MKn8Hu1ABPyI9j8eEKvYGrqoz0dn G0MOkypOVnGRgiMY2MKUmGUa/jsnL9WMBybQkl5DEFm1mbovIF4O/02PSiILXDgq FoZbL/J+XLSd2PmzlehLhP0G1npf90dEW7RTU6t6mHREa6FvZmmzkCf8rEwJ7ryJ Dr4FRXiBW4AK2TjYeiuJ5Ihk8rrUT8tjdGxRKH1eQ8GirE9mA5jsJ/apwQgDWJrr 0zh3U/wMCfCcjo1kNHIa0lvf3gCkPfbE4eLfzOuTpDATEBsirnybOQ== =ohAY -----END PGP SIGNATURE----- From gerben.wierda at rna.nl Mon Dec 19 20:33:15 2016 From: gerben.wierda at rna.nl (Gerben Wierda) Date: Mon, 19 Dec 2016 21:33:15 +0100 Subject: Checking sieve Message-ID: <060BF90F-E70C-45C3-88FA-A91B013B37C3@rna.nl> A simple question: I?ve installed roundcube on macOS Sierra with Server 5.2 and created a set of sieve rules in my dovecot setup. How can I check their functioning (other than send test mails) e.g. is there some logging I can set / look at? G From rob.mcaninch at gmail.com Mon Dec 19 21:12:23 2016 From: rob.mcaninch at gmail.com (Rob McAninch) Date: Mon, 19 Dec 2016 16:12:23 -0500 Subject: Checking sieve In-Reply-To: <060BF90F-E70C-45C3-88FA-A91B013B37C3@rna.nl> References: <060BF90F-E70C-45C3-88FA-A91B013B37C3@rna.nl> Message-ID: > On Dec 19, 2016, at 15:33, Gerben Wierda wrote: > > A simple question: I?ve installed roundcube on macOS Sierra with Server 5.2 and created a set of sieve rules in my dovecot setup. How can I check their functioning (other than send test mails) e.g. is there some logging I can set / look at? > I think you will see some sieve activity in the system logs. If that's not enough: https://wiki2.dovecot.org/Logging mail_debug=yes From tlx at leuxner.net Tue Dec 20 08:21:55 2016 From: tlx at leuxner.net (Thomas Leuxner) Date: Tue, 20 Dec 2016 09:21:55 +0100 Subject: Latest Dovecot v2.2.devel (9bc8d9b) crashes on login and lmtp Message-ID: <20161220082129.GA10980@nihlus.leuxner.net> I was unable to produce an IMAP core but have been successful with LMTP. Basically it crashes right upon login or delivery: Dec 20 08:55:23 nihlus dovecot: master: Dovecot v2.2.devel (9bc8d9b) starting up for imap, lmtp Dec 20 08:56:15 nihlus dovecot: imap(tlx at leuxner.net): Fatal: master: service(imap): child 5710 killed with signal 11 (core not dumped) Dec 20 08:57:23 nihlus dovecot: lmtp(5967): Connect from local Dec 20 08:57:23 nihlus dovecot: lmtp(5967): Fatal: master: service(lmtp): child 5967 killed with signal 11 (core dumped) $ gdb /usr/lib/dovecot/lmtp core_lmtp.5967.nihlus.leuxner.net GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/dovecot/lmtp...Reading symbols from /usr/lib/debug/.build-id/ec/199069dd786feb54e5af43f983ce9c3bb4c29c.debug...done. done. [New LWP 5967] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/lmtp'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 33 ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory. #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 No locals. #1 0x00007f9177db4779 in memcpy (__len=, __src=0x0, __dest=0x7f917a5c5bf8) at /usr/include/x86_64-linux-gnu/bits/string3.h:51 No locals. #2 p_strconcat (pool=, str1=) at strfuncs.c:218 args = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7ffdcadea060, reg_save_area = 0x7ffdcade9f90}} temp = 0x0 ret = len = 49 #3 0x00007f91780744fd in mdbox_storage_create (_storage=0x7f917a5c5930, ns=0x7f917a5b79d0, error_r=0x7ffdcadea1a0) at mdbox-storage.c:57 storage = 0x7f917a5c5930 dir = #4 0x00007f917805952b in mail_storage_create_full (ns=ns at entry=0x7f917a5b79d0, driver=, driver at entry=0x0, data=, flags=flags at entry=(unknown: 0), storage_r=storage_r at entry=0x7ffdcadea170, error_r=error_r at entry=0x7ffdcadea1a0) at mail-storage.c:395 storage = 0x7f917a5c5930 list = 0x7f917a5c3ca0 list_set = {layout = 0x7f91781083c6 "fs", root_dir = 0x7f917a52e100 "/var/vmail/domains/leuxner.net/tlx/mdbox", index_dir = 0x0, index_pvt_dir = 0x0, control_dir = 0x0, alt_dir = 0x0, inbox_path = 0x0, subscription_fname = 0x7f917810f234 "subscriptions", list_index_fname = 0x7f917810925e "dovecot.list.index", maildir_name = 0x7f917810bc17 "dbox-Mails", mailbox_dir_name = 0x7f917810c301 "mailboxes", escape_char = 0 '\000', broken_char = 0 '\000', utf8 = false, alt_dir_nocheck = false, index_control_use_maildir_name = false} list_flags = p = __FUNCTION__ = "mail_storage_create_full" #5 0x00007f91780598cc in mail_storage_create (ns=ns at entry=0x7f917a5b79d0, driver=driver at entry=0x0, flags=flags at entry=(unknown: 0), error_r=error_r at entry=0x7ffdcadea1a0) at mail-storage.c:416 storage = 0x7f917a5bfc90 #6 0x00007f9178051b89 in mail_namespaces_init_add (user=user at entry=0x7f917a5bfc90, ns_set=, unexpanded_ns_set=0x7f917a5c0178, ns_p=ns_p at entry=0x7ffdcadea200, error_r=error_r at entry=0x7ffdcadea290) at mail-namespace.c:195 mail_set = ns = 0x7f917a5b79d0 driver = 0x0 error = 0x0 ret = #7 0x00007f9178052cd9 in mail_namespaces_init (user=0x7f917a5bfc90, error_r=error_r at entry=0x7ffdcadea290) at mail-namespace.c:414 mail_set = 0x7f917a5c0c58 ns_set = 0x7f917a5c0f70 unexpanded_ns_set = 0x7f917a5c0150 namespaces = 0x0 ns_p = 0x7ffdcadea200 i = count = count2 = __FUNCTION__ = "mail_namespaces_init" #8 0x00007f9178060b65 in mail_storage_service_init_post (ctx=, error_r=0x7ffdcadea290, mail_user_r=, priv=0x7ffdcadea2a0, user=0x7f917a573910) at mail-storage-service.c:728 mail_set = 0x7f917a5c0c58 home = 0x7f917a59e761 "/var/vmail/domains/leuxner.net/tlx" mail_user = 0x7f917a5bfc90 #9 mail_storage_service_next_real (mail_user_r=, user=0x7f917a573910, ctx=) at mail-storage-service.c:1427 len = temp_priv_drop = priv = {uid = 5000, gid = 5000, uid_source = 0x7f9178107684 "userdb lookup", gid_source = 0x7f9178107684 "userdb lookup", home = 0x7f917a59e761 "/var/vmail/domains/leuxner.net/tlx", chroot = 0x7f917a52d458 ""} error = 0x7f917a5b3830 "" disallow_root = use_chroot = #10 mail_storage_service_next (ctx=, user=0x7f917a573910, mail_user_r=mail_user_r at entry=0x7f917a560b48) at mail-storage-service.c:1445 old_log_prefix = 0x7f917a5ba530 "lmtp(5967, tlx at leuxner.net): " #11 0x00007f9178789f55 in client_deliver (session=0x7f917a5bf880, src_mail=0x7f917a5bb060, rcpt=0x7f917a5621d0, client=0x7f917a560a10) at commands.c:837 set_parser = line = str = mail_error = 2052462064 ret = input = ns = delivery_time_started = {tv_sec = 1482220643, tv_usec = 129544} sets = storage = 0x7f917a5b3870 mail_set = username = 0x7f917a52d070 "tlx at leuxner.net" dctx = {pool = 0x0, set = 0x7f917a560a10, session = 0x0, timeout_secs = 0, session_time_msecs = 0, delivery_time_started = {tv_sec = 140262799447056, tv_usec = 140262799447168}, dup_ctx = 0x2, session_id = 0x7f9177d980d8 "H\211\305H\211\350H\301\350?\204\300D\017\266\350\017\205\030\001", src_mail = 0xf72, src_envelope_sender = 0xf65305b35804d500 , dest_user = 0x0, dest_addr = 0x7f917a561410 "\001", final_dest_addr = 0x7f917a561480 "q ", dest_mailbox_name = 0x2 , dest_mail = 0x0, var_expand_table = 0x7f9177d93c33 , tempfail_error = 0x7f917a560a10 "", tried_default_save = 64, saved_mail = 71, save_dest_mail = 83, mailbox_full = 122, dsn = 145} lda_set = error = #12 client_deliver_next (session=0x7f917a5bf880, src_mail=0x7f917a5bb060, client=0x7f917a560a10) at commands.c:930 count = #13 client_input_data_write_local (input=, client=0x7f917a560a10) at commands.c:1026 src_mail = 0x7f917a5bb060 first_uid = 4294967295 session = 0x7f917a5bf880 old_uid = 0 #14 client_input_data_write (client=0x7f917a560a10) at commands.c:1161 input = 0x7f917a57d1f0 #15 client_input_data_handle (client=0x7f917a560a10) at commands.c:1256 data = size = 110 ret = #16 0x00007f9177d9d962 in io_loop_call_io (io=0x7f917a5615f0) at ioloop.c:599 ioloop = 0x7f917a534740 t_id = 2 __FUNCTION__ = "io_loop_call_io" #17 0x00007f9177d9efba in io_loop_handler_run_internal (ioloop=ioloop at entry=0x7f917a534740) at ioloop-epoll.c:222 ctx = 0x7f917a53a370 io = tv = {tv_sec = 299, tv_usec = 984106} events_count = msecs = ret = 1 i = 0 j = call = __FUNCTION__ = "io_loop_handler_run_internal" #18 0x00007f9177d9d9fc in io_loop_handler_run (ioloop=ioloop at entry=0x7f917a534740) at ioloop.c:648 No locals. #19 0x00007f9177d9dba8 in io_loop_run (ioloop=0x7f917a534740) at ioloop.c:623 __FUNCTION__ = "io_loop_run" #20 0x00007f9177d25a83 in master_service_run (service=0x7f917a5345e0, callback=) at master-service.c:641 No locals. #21 0x00007f9178788262 in main (argc=1, argv=0x7f917a534390) at main.c:125 set_roots = {0x7f917855e400 , 0x7f917898f580 , 0x0} service_flags = storage_service_flags = c = -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: From aki.tuomi at dovecot.fi Tue Dec 20 08:25:50 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Tue, 20 Dec 2016 10:25:50 +0200 (EET) Subject: Latest Dovecot v2.2.devel (9bc8d9b) crashes on login and lmtp In-Reply-To: <20161220082129.GA10980@nihlus.leuxner.net> References: <20161220082129.GA10980@nihlus.leuxner.net> Message-ID: <1923034671.537.1482222351739@appsuite-dev.open-xchange.com> > On December 20, 2016 at 10:21 AM Thomas Leuxner wrote: > > > I was unable to produce an IMAP core but have been successful with LMTP. Basically it crashes right upon login or delivery: > > Dec 20 08:55:23 nihlus dovecot: master: Dovecot v2.2.devel (9bc8d9b) starting up for imap, lmtp > Dec 20 08:56:15 nihlus dovecot: imap(tlx at leuxner.net): Fatal: master: service(imap): child 5710 killed with signal 11 (core not dumped) > Dec 20 08:57:23 nihlus dovecot: lmtp(5967): Connect from local > Dec 20 08:57:23 nihlus dovecot: lmtp(5967): Fatal: master: service(lmtp): child 5967 killed with signal 11 (core dumped) > > $ gdb /usr/lib/dovecot/lmtp core_lmtp.5967.nihlus.leuxner.net > GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 > Copyright (C) 2014 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > . > Find the GDB manual and other documentation resources online at: > . > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from /usr/lib/dovecot/lmtp...Reading symbols from /usr/lib/debug/.build-id/ec/199069dd786feb54e5af43f983ce9c3bb4c29c.debug...done. > done. > [New LWP 5967] > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > Core was generated by `dovecot/lmtp'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 > 33 ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory. > #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 > No locals. > #1 0x00007f9177db4779 in memcpy (__len=, __src=0x0, __dest=0x7f917a5c5bf8) at /usr/include/x86_64-linux-gnu/bits/string3.h:51 > No locals. > #2 p_strconcat (pool=, str1=) at strfuncs.c:218 > args = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7ffdcadea060, reg_save_area = 0x7ffdcade9f90}} > temp = 0x0 > ret = > len = 49 > #3 0x00007f91780744fd in mdbox_storage_create (_storage=0x7f917a5c5930, ns=0x7f917a5b79d0, error_r=0x7ffdcadea1a0) at mdbox-storage.c:57 > storage = 0x7f917a5c5930 > dir = > #4 0x00007f917805952b in mail_storage_create_full (ns=ns at entry=0x7f917a5b79d0, driver=, driver at entry=0x0, data=, flags=flags at entry=(unknown: 0), > storage_r=storage_r at entry=0x7ffdcadea170, error_r=error_r at entry=0x7ffdcadea1a0) at mail-storage.c:395 > storage = 0x7f917a5c5930 > list = 0x7f917a5c3ca0 > list_set = {layout = 0x7f91781083c6 "fs", root_dir = 0x7f917a52e100 "/var/vmail/domains/leuxner.net/tlx/mdbox", index_dir = 0x0, index_pvt_dir = 0x0, control_dir = 0x0, alt_dir = 0x0, > inbox_path = 0x0, subscription_fname = 0x7f917810f234 "subscriptions", list_index_fname = 0x7f917810925e "dovecot.list.index", maildir_name = 0x7f917810bc17 "dbox-Mails", > mailbox_dir_name = 0x7f917810c301 "mailboxes", escape_char = 0 '\000', broken_char = 0 '\000', utf8 = false, alt_dir_nocheck = false, index_control_use_maildir_name = false} > list_flags = > p = > __FUNCTION__ = "mail_storage_create_full" > #5 0x00007f91780598cc in mail_storage_create (ns=ns at entry=0x7f917a5b79d0, driver=driver at entry=0x0, flags=flags at entry=(unknown: 0), error_r=error_r at entry=0x7ffdcadea1a0) at mail-storage.c:416 > storage = 0x7f917a5bfc90 > #6 0x00007f9178051b89 in mail_namespaces_init_add (user=user at entry=0x7f917a5bfc90, ns_set=, unexpanded_ns_set=0x7f917a5c0178, ns_p=ns_p at entry=0x7ffdcadea200, > error_r=error_r at entry=0x7ffdcadea290) at mail-namespace.c:195 > mail_set = > ns = 0x7f917a5b79d0 > driver = 0x0 > error = 0x0 > ret = > #7 0x00007f9178052cd9 in mail_namespaces_init (user=0x7f917a5bfc90, error_r=error_r at entry=0x7ffdcadea290) at mail-namespace.c:414 > mail_set = 0x7f917a5c0c58 > ns_set = 0x7f917a5c0f70 > unexpanded_ns_set = 0x7f917a5c0150 > namespaces = 0x0 > ns_p = 0x7ffdcadea200 > i = > count = > count2 = > __FUNCTION__ = "mail_namespaces_init" > #8 0x00007f9178060b65 in mail_storage_service_init_post (ctx=, error_r=0x7ffdcadea290, mail_user_r=, priv=0x7ffdcadea2a0, user=0x7f917a573910) at mail-storage-service.c:728 > mail_set = 0x7f917a5c0c58 > home = 0x7f917a59e761 "/var/vmail/domains/leuxner.net/tlx" > mail_user = 0x7f917a5bfc90 > #9 mail_storage_service_next_real (mail_user_r=, user=0x7f917a573910, ctx=) at mail-storage-service.c:1427 > len = > temp_priv_drop = > priv = {uid = 5000, gid = 5000, uid_source = 0x7f9178107684 "userdb lookup", gid_source = 0x7f9178107684 "userdb lookup", home = 0x7f917a59e761 "/var/vmail/domains/leuxner.net/tlx", > chroot = 0x7f917a52d458 ""} > error = 0x7f917a5b3830 "" > disallow_root = > use_chroot = > #10 mail_storage_service_next (ctx=, user=0x7f917a573910, mail_user_r=mail_user_r at entry=0x7f917a560b48) at mail-storage-service.c:1445 > old_log_prefix = 0x7f917a5ba530 "lmtp(5967, tlx at leuxner.net): " > #11 0x00007f9178789f55 in client_deliver (session=0x7f917a5bf880, src_mail=0x7f917a5bb060, rcpt=0x7f917a5621d0, client=0x7f917a560a10) at commands.c:837 > set_parser = > line = > str = > mail_error = 2052462064 > ret = > input = > ns = > delivery_time_started = {tv_sec = 1482220643, tv_usec = 129544} > sets = > storage = 0x7f917a5b3870 > mail_set = > username = 0x7f917a52d070 "tlx at leuxner.net" > dctx = {pool = 0x0, set = 0x7f917a560a10, session = 0x0, timeout_secs = 0, session_time_msecs = 0, delivery_time_started = {tv_sec = 140262799447056, tv_usec = 140262799447168}, dup_ctx = 0x2, > session_id = 0x7f9177d980d8 "H\211\305H\211\350H\301\350?\204\300D\017\266\350\017\205\030\001", src_mail = 0xf72, > src_envelope_sender = 0xf65305b35804d500 , dest_user = 0x0, dest_addr = 0x7f917a561410 "\001", final_dest_addr = 0x7f917a561480 "q ", > dest_mailbox_name = 0x2 , dest_mail = 0x0, var_expand_table = 0x7f9177d93c33 , tempfail_error = 0x7f917a560a10 "", > tried_default_save = 64, saved_mail = 71, save_dest_mail = 83, mailbox_full = 122, dsn = 145} > lda_set = > error = > #12 client_deliver_next (session=0x7f917a5bf880, src_mail=0x7f917a5bb060, client=0x7f917a560a10) at commands.c:930 > count = > #13 client_input_data_write_local (input=, client=0x7f917a560a10) at commands.c:1026 > src_mail = 0x7f917a5bb060 > first_uid = 4294967295 > session = 0x7f917a5bf880 > old_uid = 0 > #14 client_input_data_write (client=0x7f917a560a10) at commands.c:1161 > input = 0x7f917a57d1f0 > #15 client_input_data_handle (client=0x7f917a560a10) at commands.c:1256 > data = > size = 110 > ret = > #16 0x00007f9177d9d962 in io_loop_call_io (io=0x7f917a5615f0) at ioloop.c:599 > ioloop = 0x7f917a534740 > t_id = 2 > __FUNCTION__ = "io_loop_call_io" > #17 0x00007f9177d9efba in io_loop_handler_run_internal (ioloop=ioloop at entry=0x7f917a534740) at ioloop-epoll.c:222 > ctx = 0x7f917a53a370 > io = > tv = {tv_sec = 299, tv_usec = 984106} > events_count = > msecs = > ret = 1 > i = 0 > j = > call = > __FUNCTION__ = "io_loop_handler_run_internal" > #18 0x00007f9177d9d9fc in io_loop_handler_run (ioloop=ioloop at entry=0x7f917a534740) at ioloop.c:648 > No locals. > #19 0x00007f9177d9dba8 in io_loop_run (ioloop=0x7f917a534740) at ioloop.c:623 > __FUNCTION__ = "io_loop_run" > #20 0x00007f9177d25a83 in master_service_run (service=0x7f917a5345e0, callback=) at master-service.c:641 > No locals. > #21 0x00007f9178788262 in main (argc=1, argv=0x7f917a534390) at main.c:125 > set_roots = {0x7f917855e400 , 0x7f917898f580 , 0x0} > service_flags = > storage_service_flags = > c = > Hi! Thank you for your report, we will look into it. Aki From j.raschke at mittwald.de Tue Dec 20 12:45:36 2016 From: j.raschke at mittwald.de (Juergen Raschke) Date: Tue, 20 Dec 2016 13:45:36 +0100 Subject: unexpected behaviour of search queries with mixed AND and OR In-Reply-To: <8f20b938-ac85-d84b-f45d-d9073be69347@dovecot.fi> References: <98fe2fa0-be07-92af-63b6-44590c7ab0ac@mittwald.de> <8f20b938-ac85-d84b-f45d-d9073be69347@dovecot.fi> Message-ID: <2590772a-ade4-b0b5-c296-8423e36f1906@mittwald.de> Hello, On 14.12.2016 11:50, Aki Tuomi wrote: > > > On 14.12.2016 12:18, Juergen Raschke wrote: >> Hello, >> >> >> I found out an unexpected behaviour of search queries with mixed >> "AND" and "OR". >> >> >> >> doveconf -n >> # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf >> # Pigeonhole version 0.4.9 (357ac0a0e68b+) >> # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 > We believe this has been fixed in > > https://github.com/dovecot/core/commit/df8046c9a4f6bc2a478ad1e74504d50f3110c906 > Same behaviour with dovecot 2.2.27 # 2.2.27 () [XI:2:2.2.27-1~auto+1]: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 () # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.11 root at maildev:~ > doveadm -f flow fetch -u USER "date.saved flags" \( seen savedbefore 3d OR savedbefore 21d \) date.saved=2016-09-27 15:39:25 flags=\Seen date.saved=2016-09-27 15:39:25 flags=\Seen date.saved=2016-09-27 15:39:26 flags=\Seen date.saved=2016-09-27 15:39:26 flags= date.saved=2016-09-27 15:39:26 flags= date.saved=2016-09-27 15:39:27 flags= date.saved=2016-09-27 15:39:27 flags= date.saved=2016-09-27 15:39:38 flags= date.saved=2016-09-27 15:39:51 flags= date.saved=2016-12-16 15:36:00 flags=\Recent root at maildev4:~ > date Tue Dec 20 11:54:41 CET 2016 The last email "date.saved=2016-12-16 15:36:00 flags=\Recent" should not be found. Let me know if you need further information. Mit freundlichen Gruessen, Juergen Raschke -- Mittwald CM Service GmbH & Co. KG Koenigsberger Strasse 6 Tel: +49-5772-293-100 32339 Espelkamp Fax: +49-5772-293-333 Geschaeftsfuehrer: Robert Meyer, HRA 6640, AG Bad Oeynhausen Komplementaerin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From alessio at skye.it Tue Dec 20 13:37:37 2016 From: alessio at skye.it (Alessio Cecchi) Date: Tue, 20 Dec 2016 14:37:37 +0100 Subject: doveadm expunge -A Error: Dictionary commit failed In-Reply-To: <95519d70-0193-3025-05fb-1260c34a7225@dovecot.fi> References: <95519d70-0193-3025-05fb-1260c34a7225@dovecot.fi> Message-ID: Il 19/12/2016 14:28, Aki Tuomi ha scritto: > > > On 19.12.2016 15:25, Alessio Cecchi wrote: >> Hi, >> >> with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run >> ?doveadm expunge -A mailbox Spam savedbefore 30d? dovecot an error: >> >> doveadm: Error: dict-client: Commit failed: Dict server timeout: No >> input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs >> ago: C1) (reply took 0.000 secs) >> doveadm: Error: expire: Dictionary commit failed >> >> Probably also "doveadm quota recalc -A" fail. >> >> Everything worked fine up to version 2.2.24 >> >> I hope can be fixed. >> Thanks > > Hi! > > Can you check your server's logs? > > Aki > Hi Aki, no errors in the log, the only log in dovecot.log is: Dec 8 09:56:54 mx01eeh dovecot: master: Dovecot v2.2.26.1 (8feb0e1) starting up for sieve (core dumps disabled) and also "doveadm error log" is empty, only in the shell where i run "doveadm expunge -A" I see the error. Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice From aki.tuomi at dovecot.fi Tue Dec 20 14:06:15 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Tue, 20 Dec 2016 16:06:15 +0200 Subject: doveadm expunge -A Error: Dictionary commit failed In-Reply-To: References: <95519d70-0193-3025-05fb-1260c34a7225@dovecot.fi> Message-ID: <14b94c8a-1f55-603c-cb64-932bee172a3b@dovecot.fi> On 20.12.2016 15:37, Alessio Cecchi wrote: > Il 19/12/2016 14:28, Aki Tuomi ha scritto: >> >> >> On 19.12.2016 15:25, Alessio Cecchi wrote: >>> Hi, >>> >>> with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run >>> ?doveadm expunge -A mailbox Spam savedbefore 30d? dovecot an error: >>> >>> doveadm: Error: dict-client: Commit failed: Dict server timeout: No >>> input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs >>> ago: C1) (reply took 0.000 secs) >>> doveadm: Error: expire: Dictionary commit failed >>> >>> Probably also "doveadm quota recalc -A" fail. >>> >>> Everything worked fine up to version 2.2.24 >>> >>> I hope can be fixed. >>> Thanks >> >> Hi! >> >> Can you check your server's logs? >> >> Aki >> > > Hi Aki, > > no errors in the log, the only log in dovecot.log is: > > Dec 8 09:56:54 mx01eeh dovecot: master: Dovecot v2.2.26.1 (8feb0e1) > starting up for sieve (core dumps disabled) > > and also "doveadm error log" is empty, only in the shell where i run > "doveadm expunge -A" I see the error. > > Thanks For some reason dict-client in quota recalc cannot reach dict-server. Can you provide doveconf -n? Aki From pbopbo at freemail.hu Tue Dec 20 14:20:13 2016 From: pbopbo at freemail.hu (Peter Benko) Date: Tue, 20 Dec 2016 15:20:13 +0100 (CET) Subject: doveadm acl set negative rights not supported? In-Reply-To: Message-ID: Hi all, Although noone answered, I figured out how to set negative rights via doveadm. You should not prefix the username with '-' (as you should do in a normal IMAP setacl command). Instead you should specify the *rights* starting with a '-'. There are two problems with this: 1. The '-username' version runs smoothly and does not throw any errors. However, it does *not* set negative rights. It adds a useless entry for a user named '-username' 2. If you try to specify the rights with a '-', such as '-writeseen', doveadm throws an error like this: set: invalid option -- 'w' So the solution is to add '--' to the command line signaling the end of the options: sudo -u vmail doveadm acl set -u user at domain -- "Spam" user=user at domain -write-seen Regards, Peter Peter Benko ?rta: >Hi all, > >I'm trying to set an ACL with negative rights. I have no problems setting it with standard IMAP commands, but I'm unable to do it with the doveadm acl command. > >I tried: > >sudo -u vmail doveadm acl set -u "user at domain" Spam user="-user at domain" lookup >(notice the "-" before the username) > >Unfortunately, this adds a (positive) ACL for the user named "-user at domain" instead of adding a negative one for the user "user at domain". > >Am I messing up something or is negative ACL support missing from doveadm? I have not seen anything in the docs about this... > >Regards, > >Peter > From alessio at skye.it Tue Dec 20 17:09:03 2016 From: alessio at skye.it (Alessio Cecchi) Date: Tue, 20 Dec 2016 18:09:03 +0100 Subject: doveadm expunge -A Error: Dictionary commit failed In-Reply-To: <14b94c8a-1f55-603c-cb64-932bee172a3b@dovecot.fi> References: <95519d70-0193-3025-05fb-1260c34a7225@dovecot.fi> <14b94c8a-1f55-603c-cb64-932bee172a3b@dovecot.fi> Message-ID: <01f38cba-0ab4-6fb1-06d9-686cfe5c0beb@skye.it> Il 20/12/2016 15:06, Aki Tuomi ha scritto: > > > On 20.12.2016 15:37, Alessio Cecchi wrote: >> Il 19/12/2016 14:28, Aki Tuomi ha scritto: >>> >>> >>> On 19.12.2016 15:25, Alessio Cecchi wrote: >>>> Hi, >>>> >>>> with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run >>>> ?doveadm expunge -A mailbox Spam savedbefore 30d? dovecot an error: >>>> >>>> doveadm: Error: dict-client: Commit failed: Dict server timeout: No >>>> input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs >>>> ago: C1) (reply took 0.000 secs) >>>> doveadm: Error: expire: Dictionary commit failed >>>> >>>> Probably also "doveadm quota recalc -A" fail. >>>> >>>> Everything worked fine up to version 2.2.24 >>>> >>>> I hope can be fixed. >>>> Thanks >>> >>> Hi! >>> >>> Can you check your server's logs? >>> >>> Aki >>> >> >> Hi Aki, >> >> no errors in the log, the only log in dovecot.log is: >> >> Dec 8 09:56:54 mx01eeh dovecot: master: Dovecot v2.2.26.1 (8feb0e1) >> starting up for sieve (core dumps disabled) >> >> and also "doveadm error log" is empty, only in the shell where i run >> "doveadm expunge -A" I see the error. >> >> Thanks > > For some reason dict-client in quota recalc cannot reach dict-server. > Can you provide doveconf -n? > > Aki Yes! Note: on this server dovecot act only as LDA, before the upgrade, with version 2.2.24 and the same configuration works fine. Thanks # 2.2.26.1 (8feb0e1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (1dc4c73) # OS: Linux 2.6.32-642.11.1.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_cache_negative_ttl = 5 mins auth_cache_size = 10 M auth_cache_ttl = 20 mins auth_mechanisms = plain login auth_worker_max_count = 50 deliver_log_format = msgid=%m, from=%f, subject="%s": %$ dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sieve = mysql:/etc/dovecot/dovecot-dict-sieve-sql.conf.ext sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_gid = 89 first_valid_uid = 89 imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_idle_notify_interval = 29 mins last_valid_gid = 89 last_valid_uid = 89 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_fsync = always mail_location = maildir:~/Maildir mail_plugins = quota acl expire zlib maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mmap_disable = yes namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%n/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl antispam_backend = mailtrain antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/bin/sa-learn antispam_mail_spam = --spam antispam_spam = Spam antispam_trash = Trash expire = Trash expire2 = Spam expire_dict = proxy::expire quota = maildir:UserQuota quota2 = dict:Quota Usage::noenforcing:proxy::sqlquota quota_grace = 10M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = dict:proxy::sieve;name=activesql sieve_before2 = /etc/dovecot/sieve/before.sieve sieve_duplicate_default_period = 1h sieve_duplicate_max_period = 1d zlib_save = gz zlib_save_level = 6 } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_fast_size_lookups = yes protocols = sieve sendmail_path = /var/qmail/bin/sendmail service auth { client_limit = 6524 unix_listener auth-userdb { group = vchkpw mode = 0660 user = vpopmail } } service dict { process_limit = 500 unix_listener dict { group = vchkpw mode = 0660 user = vpopmail } } service imap-login { process_min_avail = 4 service_count = 0 } service imap-postlogin { executable = script-login /etc/dovecot/scripts/imap-postlogin.sh unix_listener imap-postlogin { group = vchkpw mode = 0660 user = vpopmail } user = vpopmail } service imap { executable = imap imap-postlogin process_limit = 5000 service_count = 100 vsz_limit = 384 M } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { process_min_avail = 4 service_count = 0 } service pop3-postlogin { executable = script-login /etc/dovecot/scripts/pop3-postlogin.sh unix_listener pop3-postlogin { group = vchkpw mode = 0660 user = vpopmail } user = vpopmail } service pop3 { executable = pop3 pop3-postlogin process_limit = 1024 service_count = 100 } service quota-warning { executable = script /etc/dovecot/scripts/quota-warning.sh unix_listener quota-warning { user = vpopmail } user = vpopmail } ssl = no submission_host = 127.0.0.1 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lda { mail_fsync = optimized mail_location = maildir:~/Maildir:INDEX=MEMORY mail_plugins = quota acl expire zlib sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota acl expire zlib imap_quota imap_acl imap_zlib } protocol sieve { mail_max_userip_connections = 2 } protocol pop3 { mail_max_userip_connections = 15 } -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice From fedoraproject at cyberpear.com Wed Dec 21 15:46:27 2016 From: fedoraproject at cyberpear.com (James Cassell) Date: Wed, 21 Dec 2016 10:46:27 -0500 Subject: doveadm acl set negative rights not supported? In-Reply-To: References: Message-ID: <1482335187.1622553.826039769.389B041F@webmail.messagingengine.com> On Tue, Dec 20, 2016, at 09:20 AM, Peter Benko wrote: > Hi all, > > Although noone answered, I figured out how to set negative rights via doveadm. You should not prefix the username with '-' (as you should do in a normal IMAP setacl command). Instead you should specify the *rights* starting with a '-'. There are two problems with this: > > 1. The '-username' version runs smoothly and does not throw any errors. However, it does *not* set negative rights. It adds a useless entry for a user named '-username' > > 2. If you try to specify the rights with a '-', such as '-writeseen', doveadm throws an error like this: > set: invalid option -- 'w' > > So the solution is to add '--' to the command line signaling the end of the options: > > sudo -u vmail doveadm acl set -u user at domain -- "Spam" user=user at domain -write-seen > Thanks for sharing the solution you found. V/r, James Cassell From tss at iki.fi Wed Dec 21 23:35:38 2016 From: tss at iki.fi (Timo Sirainen) Date: Wed, 21 Dec 2016 18:35:38 -0500 Subject: doveadm expunge -A Error: Dictionary commit failed In-Reply-To: References: Message-ID: <4C97D0EC-5455-497F-A624-C4994922C543@iki.fi> On 19 Dec 2016, at 8.25, Alessio Cecchi wrote: > > Hi, > > with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run ?doveadm expunge -A mailbox Spam savedbefore 30d? dovecot an error: > > doveadm: Error: dict-client: Commit failed: Dict server timeout: No input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs ago: C1) (reply took 0.000 secs) > doveadm: Error: expire: Dictionary commit failed > > Probably also "doveadm quota recalc -A" fail. > > Everything worked fine up to version 2.2.24 Try if 2.2.27.1 works better. It has fixes related to this. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3665 bytes Desc: not available URL: From ilya at ilya.pp.ua Thu Dec 22 04:30:57 2016 From: ilya at ilya.pp.ua (=?UTF-8?B?0JjQu9GM0Y8=?=) Date: Thu, 22 Dec 2016 06:30:57 +0200 Subject: The left angle bracket at the beginning of the certificate path Message-ID: dovecot 2.2.27 (c0f36b0) openSUSE Tumbleweed x86_64 https://forums.opensuse.org/showthread.php/521796-Dovecot-doveconf-Fatal-execvp(-usr-lib-dovecot-managesieve)-failed-Argument-list-too-long Faced with an unpleasant situation, when ssl_client_ca_file options are specified path to the left angle bracket, as in options ssl_key ssl_cert ssl_ca path is so. This doveconf shows no syntax error, and the arrow moves to managesieve which there generally is not involved in any side. dovecot: doveconf: Fatal: execvp(/usr/lib/dovecot/managesieve) failed: Argument list too long dovecot: config: Error: managesieve-login: dump-capability process returned 89 I consider this a bug, and that it should not be. And explain why you need left angle brackets in the options ssl_key ssl_cert ssl_ca? From mikefroehner at gmx.de Thu Dec 22 10:31:15 2016 From: mikefroehner at gmx.de (=?UTF-8?Q?Mike_Fr=c3=b6hner?=) Date: Thu, 22 Dec 2016 11:31:15 +0100 Subject: dsync for subscription on public/shared folder Message-ID: Hello, I already wrote regarding that, but maybe it sounded too complex. I will write it a bit softer now. The replication through dsnyc works perfectly with one exception. I am having an issue with the replication of the subscriptions file on shared folder. We have a public mailbox defined: namespace public-test { location = maildir:/opt/mail/_public/test prefix = public/test/ separator = / subscriptions = no type = public } There 2 subfolder .Test1 and .Test2 which I would like to subscribe on my user "ldaptestuser" which is part of the group "ldaptestgroup" The dovecot-acl file on /opt/mail/_public/test and /opt/mail/_public/test/.Test{1,2} are the same and are containing: group=ldaptestgroup lrwstipekxa Now if I login through my client (Thunderbird or Roundcubemail) I can see the following debug log: dovecot: imap(ldaptestuser): Debug: acl: acl username = ldaptestuser dovecot: imap(ldaptestuser): Debug: acl: owner = 0 dovecot: imap(ldaptestuser): Debug: acl: group added: domain users dovecot: imap(ldaptestuser): Debug: acl: group added: ldaptestgroup dovecot: imap(ldaptestuser): Debug: acl: group added: all_mailuser I created one new private folder on the mailbox of my test user and also subscribed it. This subscription is successfully replicated. After that I am trying to subscribe the public folder. I can see the folder in my client after I subscribed them. But on the 2nd dovecot server the subscription file is not updated. imap-1 # cat subscription Private1 public/test/Test1 imap-2 # cat subscription Private1 The debug log on both dovecot server tells me: dovecot: doveadm(,ldaptestuser): Debug: Effective uid=834603987, gid=991, home=/opt/mail/ldaptestuser dovecot: doveadm(,ldaptestuser): Debug: acl: No acl_shared_dict setting - shared mailbox listing is disabled dovecot: doveadm(,ldaptestuser): Debug: maildir++: root=/opt/mail/_public/test, index=, indexpvt=, control=, inbox=, alt= dovecot: doveadm(,ldaptestuser): Debug: acl: initializing backend with data: vfile dovecot: doveadm(,ldaptestuser): Debug: acl: acl username = ldaptestuser dovecot: doveadm(,ldaptestuser): Debug: acl: owner = 0 dovecot: doveadm(,ldaptestuser): Debug: acl vfile: Global ACLs disabled It looks like the doveadm() cannot find the group or is not checking/initalizing the groups. Anybody any idea if I missconfigured something or is this just a bug? I really would appreciate some help. kind regards, Mike; From dovecot at vosslamber.nl Thu Dec 22 19:46:34 2016 From: dovecot at vosslamber.nl (dovecot) Date: Thu, 22 Dec 2016 20:46:34 +0100 Subject: permissions and doveadm Message-ID: I did an upgrade from OpenSUSE 13.1 to 13.2 (finally), and now doveadm fails. I went from an self-compiled source, to 'repsitory'-version (from version 2.1.6, to 2.2.13) luuk at opensuse:~/bin> id uid=1000(luuk) gid=100(users) groups=100(users),7(lp),33(video),118(vboxusers) luuk at opensuse:~/bin> doveadm quota recalc luuk at opensuse:~/bin> doveadm quota recalc -u luuk doveadm(luuk): Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-userdb) failed: Connection refused doveadm(luuk): Fatal: User lookup failed: Internal error occurred. Refer to server log for more information. Why is it that with the '-u' option, doveadm is getting a connection refused? -- Luuk From ml+dovecot at valo.at Thu Dec 22 20:55:52 2016 From: ml+dovecot at valo.at (Christian Kivalo) Date: Thu, 22 Dec 2016 21:55:52 +0100 Subject: permissions and doveadm In-Reply-To: References: Message-ID: <2565231df20b86cef1fffc154a78840a@valo.at> On 2016-12-22 20:46, dovecot wrote: > I did an upgrade from OpenSUSE 13.1 to 13.2 (finally), and now doveadm > fails. dovecot is running? No errors? Other doveadm commands work? > > I went from an self-compiled source, to 'repsitory'-version > > (from version 2.1.6, to 2.2.13) > > luuk at opensuse:~/bin> id > uid=1000(luuk) gid=100(users) > groups=100(users),7(lp),33(video),118(vboxusers) > luuk at opensuse:~/bin> doveadm quota recalc > luuk at opensuse:~/bin> doveadm quota recalc -u luuk > doveadm(luuk): Error: userdb lookup: > connect(/usr/local/var/run/dovecot/auth-userdb) failed: Connection > refused Does the socket /usr/local/var/run/dovecot/auth-userdb exist? This looks like a leftover from your self-compiled version. The distro packaged version probably has all the sockets in /var/run/dovecot/. Please show your dovecot -n > doveadm(luuk): Fatal: User lookup failed: Internal error occurred. > Refer to server log for more information. Whats in the logs? You have a problem with your configuration that needs to be fixed, dovecot/doveadm isn't able to lookup you users. > > > Why is it that with the '-u' option, doveadm is getting a connection > refused? -- Christian Kivalo From brong at fastmail.fm Thu Dec 22 23:03:13 2016 From: brong at fastmail.fm (Bron Gondwana) Date: Fri, 23 Dec 2016 10:03:13 +1100 Subject: JMAP support in Dovecot In-Reply-To: <69ad3b1d-dbfd-9451-3e93-ccaad8f567b5@libertytrek.org> References: <5839DD54.2060705@carpenter.org> <20161126191625.2js5gzt5zuoq4sm6@nordisch.org> <385273315.256.1480242517370@appsuite-dev.open-xchange.com> <69ad3b1d-dbfd-9451-3e93-ccaad8f567b5@libertytrek.org> Message-ID: <1482447793.1110360.827500657.72C3C5F6@webmail.messagingengine.com> Hi Charles, We are actually pretty close to a complete implementation in Cyrus now, and there's the proxy of course. We'll be doing a release candidate of Cyrus 3.0 with JMAP support on January 13th. There's also the hosted copy of the JMAP proxy, which I'm afraid I haven't been giving much love recently. It's very close to feature complete though. What number is the Thunderbird bug? I appear to not be CCd, or missing the emails from it. I should probably sign up! Feel free to ask me anything directly as well. Bron. On Wed, 14 Dec 2016, at 02:33, Tanstaafl wrote: > Hi Aki, > > Someone just asked in the bug for Thunderbird for this, so... > > Is there a git branch that they could use to start playing with what is > there? If not, any idea when that might happen? > > It sounds like someone following the Thunderbird bug is interested in > working on this, but they obviously need something to test against. > > Thanks, > > Charles > > > On 11/27/2016 5:28 AM, Aki Tuomi wrote: > > Hi! > > > > We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 > > > > Aki Tuomi > > > > Dovecot Oy > > > >> On November 26, 2016 at 11:17 PM Andrew Jones wrote: > >> > >> > >> Hi Marcus > >> > >> Thanks for your helpful reply. > >> > >> Do you know what is going on with JMAP development into Dovecot 2.5? > >> > >> It's difficult to get any sort of information from the roadmap and there are no Dovecot forums. > >> > >> One of the main reasons I'm interested in JMAP is because of Roundcube Next and also the other clients it will power. Sadly, there has been little going on and having emailed Thomas, he is no longer involved in Roundcube Next - which is a shame. The Kolab guys are really taking liberties here, and trying their product, the thing is littered with bugs everywhere. > >> > >> Are you able to comment on what is going on with JMAP development into Dovecot? > >> > >> Thanks > >> > >> Andrew > >> > >> > >> > >> > >> Sent from my iPhone > >> > >>> On 26 Nov 2016, at 19:16, Marcus Rueckert wrote: > >>> > >>>> On 2016-11-26 11:07:00 -0800, WJCarpenter wrote: > >>>> I don't know the answer to that question, but I am curious about something. > >>>> What client are you thinking about using with JMAP? I haven't found much. > >>>> (And much of the demo stuff at jmap.io seems to be busted in various ways.) > >>> > >>> roundcube-next builds on top of it. > >>> > >>> darix > >>> > >>> -- > >>> openSUSE - SUSE Linux is my linux > >>> openSUSE is good for you > >>> www.opensuse.org -- Bron Gondwana brong at fastmail.fm From gkontos.mail at gmail.com Fri Dec 23 12:10:37 2016 From: gkontos.mail at gmail.com (George Kontostanos) Date: Fri, 23 Dec 2016 14:10:37 +0200 Subject: Domains on different IPs In-Reply-To: References: Message-ID: On Sat, Dec 17, 2016 at 1:35 PM, Mark Constable wrote: > I want to supply separate Letsencrypt certificates for each virtual domain > and seeing that SNI does not work I need to allocate separate IPs. Could > anyone give some pointers, or keywords to search for, on... > > a) how to make dovecot listen for different domains on different IPs? > > b) how to configure separate SSL certs for each of these IPs? > The way we do it is by specifying each IP address and certificate in 10-ssl.conf ssl = yes local xxx.xxx.xxx.xxx { # instead of IP you can also use hostname, which will be resolved protocol imap { ssl_cert = References: <20161214114204.GP1717@dagobah.eu.org> Message-ID: <20161223135354.GA6575@dagobah.eu.org> Hi again, Le Wednesday 14 December 2016 ? 12:42, Aur?lien Beaujean ?crivait: > Any idea before I will patch some piece of code to disable the unique > restriction of inbox namespace ? I've found a way to address my problem, using the %s (protocol) in the configuration file, as this: namespace virtual { hidden = yes inbox = yes list = no location = virtual:/etc/dovecot/virtual/%s:INDEX=MEMORY prefix = virtual/ separator = / } With 2 different pop3 / imap dovecot-virtual files: # cat /etc/dovecot/virtual/imap/INBOX/dovecot-virtual !RealMails/INBOX all # cat /etc/dovecot/virtual/pop3/INBOX/dovecot-virtual !RealMails/INBOX RealMails/BOX1 RealMails/BOX2 all Consequence that dovecot-lda getting lost, so I had to patch the code to allow to override the namespace inbox configuration in the LDA protocol: protocol lda { mail_plugins = " virtual quota sieve" namespace inbox { inbox = yes location = prefix = } } That works but still brakes quota-status, which seems trying to get the size of /etc/dovecot/virtual/ instead of the size of the user mailbox. For information, such configuration created me those subdirs: /etc/dovecot/virtual/ /etc/dovecot/virtual/pop3 /etc/dovecot/virtual/pop3/INBOX /etc/dovecot/virtual/pop3/INBOX/dovecot-virtual /etc/dovecot/virtual/lda /etc/dovecot/virtual/imap /etc/dovecot/virtual/imap/.virtual-subscriptions /etc/dovecot/virtual/imap/INBOX /etc/dovecot/virtual/imap/INBOX/dovecot-virtual /etc/dovecot/virtual/quota-status /etc/dovecot/virtual/managesieve /etc/dovecot/virtual/doveadm If nobody has a last idea, it seems I will need to manually hardcode BOX1 & BOX2 in the POP3 daemon code to not break the rest of the dovecot processes. Thanks, -- Aur? From dovecot at vosslamber.nl Sat Dec 24 13:26:43 2016 From: dovecot at vosslamber.nl (Luuk) Date: Sat, 24 Dec 2016 14:26:43 +0100 Subject: permissions and doveadm In-Reply-To: References: Message-ID: <79f79e94-3fb4-1ca4-64e5-4bb3570bebad@vosslamber.nl> @Christian: thanks! OK, config problem, i need to look into that problem first, so i can receveive answers send to the list too ... :-[:-[:-\ this time i found the answer here: http://dovecot.org/list/dovecot/2016-December/106552.html On 22-12-16 20:46, dovecot wrote: > I did an upgrade from OpenSUSE 13.1 to 13.2 (finally), and now doveadm > fails. > > I went from an self-compiled source, to 'repsitory'-version > > (from version 2.1.6, to 2.2.13) > > luuk at opensuse:~/bin> id > uid=1000(luuk) gid=100(users) > groups=100(users),7(lp),33(video),118(vboxusers) > luuk at opensuse:~/bin> doveadm quota recalc > luuk at opensuse:~/bin> doveadm quota recalc -u luuk > doveadm(luuk): Error: userdb lookup: > connect(/usr/local/var/run/dovecot/auth-userdb) failed: Connection > refused > doveadm(luuk): Fatal: User lookup failed: Internal error occurred. > Refer to server log for more information. > > > Why is it that with the '-u' option, doveadm is getting a connection > refused? > > From aki.tuomi at dovecot.fi Sun Dec 25 07:54:51 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Sun, 25 Dec 2016 09:54:51 +0200 (EET) Subject: permissions and doveadm In-Reply-To: <79f79e94-3fb4-1ca4-64e5-4bb3570bebad@vosslamber.nl> References: <79f79e94-3fb4-1ca4-64e5-4bb3570bebad@vosslamber.nl> Message-ID: <1129869683.700.1482652492168@appsuite-dev.open-xchange.com> > On 22-12-16 20:46, dovecot wrote: > > I did an upgrade from OpenSUSE 13.1 to 13.2 (finally), and now doveadm > > fails. > > > > I went from an self-compiled source, to 'repsitory'-version > > > > (from version 2.1.6, to 2.2.13) > > > > luuk at opensuse:~/bin> id > > uid=1000(luuk) gid=100(users) > > groups=100(users),7(lp),33(video),118(vboxusers) > > luuk at opensuse:~/bin> doveadm quota recalc > > luuk at opensuse:~/bin> doveadm quota recalc -u luuk > > doveadm(luuk): Error: userdb lookup: > > connect(/usr/local/var/run/dovecot/auth-userdb) failed: Connection > > refused > > doveadm(luuk): Fatal: User lookup failed: Internal error occurred. > > Refer to server log for more information. > > > > > > Why is it that with the '-u' option, doveadm is getting a connection > > refused? > > > > Connection refused either means that your dovecot is not running (it needs to be), or you have somehow prevented it from connecting to that socket, or no one is listening there. Also remember to *remove* the old binaries, or at least ensure you are calling the repository ones, as they default to different paths. Aki From news at mefox.org Sun Dec 25 22:57:21 2016 From: news at mefox.org (Michael Fox) Date: Sun, 25 Dec 2016 14:57:21 -0800 Subject: postlogin script - still confused Message-ID: <008d01d25f02$402d9c70$c088d550$@mefox.org> > You need to use executable = script-login -- /path/post-login.sh -a -r -g > note the double-dash. it tells getopt to stop processing arguments. > > Aki OK. Thanks. So let me make sure I have this right, since there is no syntax defined on the wiki - just an example which doesn't show the above syntax. The valid possibilities are: executable = script-login [-d] /path/script1 /path/script2 ... -or- executable = script-login [-d] -- /path/script1 -a -r -g -s In other words, I can either call multiple scripts, each with no arguments, or I can call one script with arguments. But I cannot call multiple scripts, some with arguments, some without arguments. Is that correct? If not, please show all valid syntax options. Also, regarding the exec "$@" line shown at the end of the wiki examples. If I pass arguments "-a -r -g -s" to my script, as in: executable = script-login -- /path/script1 -a -r -g -s then doesn't the exec "$@" line at the end become: exec -a -r -g -s And surely that's not right. So, could you please explain in words the purpose of the exec line at the end - what it does, why it's needed, and what to do if I'm sending arguments to my postlogin script? Thanks, Michael From dovecot at vosslamber.nl Mon Dec 26 10:09:41 2016 From: dovecot at vosslamber.nl (Luuk) Date: Mon, 26 Dec 2016 11:09:41 +0100 Subject: permissions and doveadm In-Reply-To: <1129869683.700.1482652492168@appsuite-dev.open-xchange.com> References: <79f79e94-3fb4-1ca4-64e5-4bb3570bebad@vosslamber.nl> <1129869683.700.1482652492168@appsuite-dev.open-xchange.com> Message-ID: On 25-12-16 08:54, Aki Tuomi wrote: >> On 22-12-16 20:46, dovecot wrote: >>> I did an upgrade from OpenSUSE 13.1 to 13.2 (finally), and now doveadm >>> fails. >>> >>> I went from an self-compiled source, to 'repsitory'-version >>> >>> (from version 2.1.6, to 2.2.13) >>> >>> luuk at opensuse:~/bin> id >>> uid=1000(luuk) gid=100(users) >>> groups=100(users),7(lp),33(video),118(vboxusers) >>> luuk at opensuse:~/bin> doveadm quota recalc >>> luuk at opensuse:~/bin> doveadm quota recalc -u luuk >>> doveadm(luuk): Error: userdb lookup: >>> connect(/usr/local/var/run/dovecot/auth-userdb) failed: Connection >>> refused >>> doveadm(luuk): Fatal: User lookup failed: Internal error occurred. >>> Refer to server log for more information. >>> >>> >>> Why is it that with the '-u' option, doveadm is getting a connection >>> refused? >>> >>> > > Connection refused either means that your dovecot is not running (it needs to be), or you have somehow prevented it from connecting to that socket, or no one is listening there. > > Also remember to *remove* the old binaries, or at least ensure you are calling the repository ones, as they default to different paths. > > Aki > Thanks, it seems i'm finally getting messages from the list again ... Indeed i was still using the old binaries (in /usr/local/bin), But i was also blocking a backup MX from sending mail to /me ;( I started reading this list somewhere in 2007, and did not fillow it god enough for the last two years, but time has come to investigate how i can upgrade my stuff (linux/postfix/dovecot) and all the other stuff that's doing something on that pieve of hardware, without breaking more that i did with my mail from this list. From saikiran.gummaraj at gmail.com Tue Dec 27 11:22:56 2016 From: saikiran.gummaraj at gmail.com (Sai Kiran Gummaraj) Date: Tue, 27 Dec 2016 16:52:56 +0530 Subject: Identify if a message_part is an attachment ? Message-ID: Hello, This is my first post to this group. I have read through the instructions before posting. I hope am doing the right thing. If not my sincere apologies. I am in the process of developing a dovecot IMAP plugin (over v2.2.25). The plugin works with mdbox/sdbox which has ability to keep attachments as external references (via SiS POSIX). The plugin must enable fetching attachment from REDIS instead of local-store. To accomplish this I was following dovecot via my debugger. I wanted to understand if there was a way to determine a message_part to be of an attachment type ? Thanks. -- Regards, Sai Kiran cmd_fetch() |_ imap_fetch_more() |_ imap_fetch_more_int() |_ imap_fetch_state *state = &ctx->state; state->cur_mail is NULL. search mailbox |_ mailbox_search_next(state->search_ctx, &state->cur_mail) |_ mailbox_search_next_nonblock (via vfunc) |_ index_storage_search_next_nonblock |_ search_more_with_prefetching(ctx, mail_r) |_ mail = index_search_get_mail(ctx) |_ allocates mail (vfunc mail_alloc) and calls hook. |_ also allocates index_mails ret = search_more_with_mail(ctx, mail); |_ call handler (*h) => fetch_body_msgpart |_ imap_msgpart_open |_ imap_msgpart_find_part(mail, msgpart, &part); /* only mail comes here */ mail (uid=1739, seq=5) msgpart (section_number = 2, fetch_type = FETCH_MIME_BODY, partial_offset = 0, partial_size = 512, decode_cte_to_binary = 0) |_ mail_get_parts(mail, &parts) /* atmail send msgpart */ |_ call to p->v.get_parts(mail, parts_r) (index_mail_get_parts) /* atmail over-ride this function */ |_ get_cached_parts(mail) /* sets data->part */ |_ get_unserialized_parts(index_mail) |_ get_serialized_parts(mail, &part_buf) |_ index_mail_cache_lookup_field |_ mail_cache_lookup_field |_ imap_msgpart_open_normal() |_ .. see call stack below .. From aki.tuomi at dovecot.fi Tue Dec 27 12:25:14 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Tue, 27 Dec 2016 14:25:14 +0200 (EET) Subject: Identify if a message_part is an attachment ? In-Reply-To: References: Message-ID: <1430687789.585.1482841516269@appsuite-dev.open-xchange.com> > On December 27, 2016 at 1:22 PM Sai Kiran Gummaraj wrote: > > > Hello, > > This is my first post to this group. I have read through the instructions > before posting. I hope am doing the right thing. If not my sincere > apologies. > > I am in the process of developing a dovecot IMAP plugin (over v2.2.25). The > plugin works with mdbox/sdbox which has ability to keep attachments as > external references (via SiS POSIX). The plugin must enable fetching > attachment from REDIS instead of local-store. > > To accomplish this I was following dovecot via my debugger. I wanted to > understand if there was a way to determine a message_part to be of an > attachment type ? > > Thanks. > > -- > Regards, > Sai Kiran Hi! Why not, instead, implement fs-redis driver and use that with SIS and let SIS worry about the deduplication? Aki From news at mefox.org Wed Dec 28 01:31:42 2016 From: news at mefox.org (Michael Fox) Date: Tue, 27 Dec 2016 17:31:42 -0800 Subject: expunging all mailboxes Message-ID: <013801d260aa$259e8be0$70dba3a0$@mefox.org> Evidently, the 'doveadm expunge' command requires a "mailbox" to be defined in the search string. But is there a way tell it all mailboxes for a user? For example, something like: doveadm expunge -u user at domain mailbox ALL savedbefore 30d Thanks, Michael From gjn at gjn.priv.at Wed Dec 28 16:10:59 2016 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Wed, 28 Dec 2016 17:10:59 +0100 Subject: Versioning Problem Message-ID: <74158231.K7Qo848Tqv@techz> Hello List, I have installed dovecot 2.2.25 on three Systems with two I have a problem with doveadm / dsync ? first: # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.10.0-514.2.2.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) second: # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.10.0-514.2.2.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) But I have this Error in the Logs ? Dec 27 12:00:12 mx dovecot: doveadm(2a02:xxxx:xxxx:xxxx::218): Error: doveadm client not compatible with this server (mixed old and new binaries?) Dec 27 12:01:08 mx dovecot: doveadm(2a02:xxxx:xxxx:xxxx::218): Error: doveadm client not compatible with this server (mixed old and new binaries?) can any tell me why ? -- mit freundlichen Gr?ssen / best regards G?nther J. Niederwimmer From trashcan at ellael.org Wed Dec 28 16:18:37 2016 From: trashcan at ellael.org (Michael Grimm) Date: Wed, 28 Dec 2016 17:18:37 +0100 Subject: IPv4/IPv6 mismatches of doveadm: Fatal: connect(fd00:b::1:12345) failed: Connection refused Message-ID: Hi ? I recently extendend my IPsec tunnel between two mail servers to deal with IPv4 addresses in addition to IPv6 ones. (No specific reason for that.) I ran into an issue worth reporting. This is Dovecot v2.2.27 (c0f36b0) at FreeBSD STABLE-11. Previously: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = [::] } } | local> host remote.test: remote.test has IPv6 address fd00:b::1 working well. Currently: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = * } } | local> host remote.test: remote.test has address 10.2.0.1 remote.test has IPv6 address fd00:b::1 Now, Replication stops and throws an error like: | local.test dovecot: doveadm(user): Fatal: connect(fd00:b::1:12345) failed: Connection refused If I either #) remove IPv6 from my lokal DNS, #) use "mail_replica = tcp:10.2.0.1", or #) define the appropriate IPv4 address of remote.test in /etc/hosts, then replication works as usual. Hmm, shouldn't doveadm be more persistent in using every IP address of that entry of mail_replica *before* throwing a "Fatal:" error? Or do I miss something, and it's a feature, instead? Regards, Michael From yamakasi.014 at gmail.com Thu Dec 29 02:47:33 2016 From: yamakasi.014 at gmail.com (Matt .) Date: Thu, 29 Dec 2016 03:47:33 +0100 Subject: dovecot-ldap.conf.ext for FreeIPA usage Message-ID: Hello, I'm figuring out how to auth users against FreeIPA and I wonder if someone did this without GSAPI. My users are stored in a mysql DB where I wonder what I shall use as authname, the username or the mailaddress. As the mailaddress is always unique it could be best but if a user has multiple mailaddresses under seperate domains username might be better. Any clue here and maybe an example for dovecot-ldap.conf.ext when using FreeIPA ? Thanks! Matt From aki.tuomi at dovecot.fi Thu Dec 29 08:27:17 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Thu, 29 Dec 2016 10:27:17 +0200 Subject: dovecot-ldap.conf.ext for FreeIPA usage In-Reply-To: References: Message-ID: <92fcbac6-b030-0f52-331c-23d2713182f5@dovecot.fi> On 29.12.2016 04:47, Matt . wrote: > Hello, > > I'm figuring out how to auth users against FreeIPA and I wonder if > someone did this without GSAPI. > > My users are stored in a mysql DB where I wonder what I shall use as > authname, the username or the mailaddress. As the mailaddress is > always unique it could be best but if a user has multiple > mailaddresses under seperate domains username might be better. > > Any clue here and maybe an example for dovecot-ldap.conf.ext when > using FreeIPA ? > > Thanks! > > Matt The best idea is to use same username as you use in FreeIPA. This way you can use passdb with ldap to authenticate your users, and mysql userdb to get the settings from MySQL. Aki From alessio at skye.it Thu Dec 29 08:44:30 2016 From: alessio at skye.it (Alessio Cecchi) Date: Thu, 29 Dec 2016 09:44:30 +0100 Subject: doveadm expunge -A Error: Dictionary commit failed In-Reply-To: <4C97D0EC-5455-497F-A624-C4994922C543@iki.fi> References: <4C97D0EC-5455-497F-A624-C4994922C543@iki.fi> Message-ID: <095d273e-3b29-c076-882b-5660735b62de@skye.it> Il 22/12/2016 00:35, Timo Sirainen ha scritto: > On 19 Dec 2016, at 8.25, Alessio Cecchi wrote: >> >> Hi, >> >> with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run ?doveadm expunge -A mailbox Spam savedbefore 30d? dovecot an error: >> >> doveadm: Error: dict-client: Commit failed: Dict server timeout: No input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs ago: C1) (reply took 0.000 secs) >> doveadm: Error: expire: Dictionary commit failed >> >> Probably also "doveadm quota recalc -A" fail. >> >> Everything worked fine up to version 2.2.24 > > Try if 2.2.27.1 works better. It has fixes related to this. > Thanks Timo, with 2.2.27.1 works fine. -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice From dovecot at vosslamber.nl Thu Dec 29 20:22:51 2016 From: dovecot at vosslamber.nl (Luuk) Date: Thu, 29 Dec 2016 21:22:51 +0100 Subject: expunging all mailboxes In-Reply-To: <013801d260aa$259e8be0$70dba3a0$@mefox.org> References: <013801d260aa$259e8be0$70dba3a0$@mefox.org> Message-ID: <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> On 28-12-16 02:31, Michael Fox wrote: > Evidently, the 'doveadm expunge' command requires a "mailbox" to be defined > in the search string. > > > > But is there a way tell it all mailboxes for a user? For example, something > like: > > > > doveadm expunge -u user at domain mailbox ALL savedbefore 30d try: doveadm expunge -u user at domain ALL savedbefore 30d just like the example thats here: http://wiki2.dovecot.org/Tools/Doveadm/SearchQuery From lists at merit.unu.edu Thu Dec 29 20:23:21 2016 From: lists at merit.unu.edu (mj) Date: Thu, 29 Dec 2016 21:23:21 +0100 Subject: two listeners with different "driver = " configs Message-ID: <9355de41-083c-5e1a-0292-bf09957b07c2@merit.unu.edu> Hi, I would like to have two seperate imap listeners, with different authentication settings, but the mailstore and userbase etc will be identical. I know I can do this: > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imap2 { > port = 144 > } > } But I'm unsure how to configure imap/143 with "driver = ldap" and imap2/144 with "driver = pam" Just to explain why i would like this: I am using pam-script-saml (https://github.com/ck-ws/pam-script-saml) to enable saml-based access to dovecot. I would like to have one listener 144 to only serve this saml authentication listener, and the regular 143 listener with driver = ldap. Is that config possible? Best regards, MJ From dovecot at paz.bz Fri Dec 30 01:21:14 2016 From: dovecot at paz.bz (Jim Pazarena) Date: Thu, 29 Dec 2016 17:21:14 -0800 Subject: FreeBSD / dovecot 2.2.27 / libwrap Message-ID: I have compiled dovecot2 for FreeBSD with the tcpwrap option. A tcpwrap binary gets built and resides in the FreeBSD directory /usr/local/libexec/dovecot an examination of the compiled options (using the FreeBSD pkg install dovecot2) confirms: LIBWRAP : on yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap I get the following logged error message: 20161229 17:02:49 imap-login: Error: connect(tcpwrap) failed: No such file or directory Is there any way to turn up some super logging so that I can find just what dovecot feels is the failure ? Or, does anyone have an idea how to figure this out? What little hair I have is rapidly getting pulled out in frustration! Thank you. -- Jim Pazarena dovecot at paz.bz From larryrtx at gmail.com Fri Dec 30 01:27:02 2016 From: larryrtx at gmail.com (Larry Rosenman) Date: Thu, 29 Dec 2016 19:27:02 -0600 Subject: FreeBSD / dovecot 2.2.27 / libwrap In-Reply-To: References: Message-ID: login_access_sockets = tcpwrap service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } On Thu, Dec 29, 2016 at 7:21 PM, Jim Pazarena wrote: > I have compiled dovecot2 for FreeBSD with the tcpwrap option. > > A tcpwrap binary gets built and resides in the FreeBSD directory > /usr/local/libexec/dovecot > > an examination of the compiled options (using the FreeBSD pkg install > dovecot2) confirms: LIBWRAP : on > > yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap > > I get the following logged error message: > > 20161229 17:02:49 imap-login: Error: connect(tcpwrap) failed: No such file > or directory > > Is there any way to turn up some super logging so that I can find just > what dovecot feels is the failure ? > > Or, does anyone have an idea how to figure this out? What little hair I > have is rapidly getting pulled out in frustration! > > Thank you. > > > > -- > Jim Pazarena dovecot at paz.bz > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From dovecot at paz.bz Fri Dec 30 01:39:24 2016 From: dovecot at paz.bz (Jim Pazarena) Date: Thu, 29 Dec 2016 17:39:24 -0800 Subject: FreeBSD / dovecot 2.2.27 / libwrap Message-ID: <881d6fd3-89d0-290a-1a8e-5f34207ad5de@paz.bz> It works ! It was THAT easy ! Can you suggest how to replace the hair I pulled out ? :-) On 2016-12-29 5:27 PM, Larry Rosenman wrote: > login_access_sockets = tcpwrap > > service tcpwrap { > unix_listener login/tcpwrap { > group = $default_login_user > mode = 0600 > user = $default_login_user > } > } > > > > On Thu, Dec 29, 2016 at 7:21 PM, Jim Pazarena wrote: > >> I have compiled dovecot2 for FreeBSD with the tcpwrap option. >> >> A tcpwrap binary gets built and resides in the FreeBSD directory >> /usr/local/libexec/dovecot >> >> an examination of the compiled options (using the FreeBSD pkg install >> dovecot2) confirms: LIBWRAP : on >> >> yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap >> >> I get the following logged error message: >> >> 20161229 17:02:49 imap-login: Error: connect(tcpwrap) failed: No such file >> or directory >> >> Is there any way to turn up some super logging so that I can find just >> what dovecot feels is the failure ? >> >> Or, does anyone have an idea how to figure this out? What little hair I >> have is rapidly getting pulled out in frustration! >> >> Thank you. >> >> >> >> -- >> Jim Pazarena dovecot at paz.bz >> > > -- Jim Pazarena dovecot at paz.bz From larryrtx at gmail.com Fri Dec 30 01:41:08 2016 From: larryrtx at gmail.com (Larry Rosenman) Date: Thu, 29 Dec 2016 19:41:08 -0600 Subject: FreeBSD / dovecot 2.2.27 / libwrap In-Reply-To: <881d6fd3-89d0-290a-1a8e-5f34207ad5de@paz.bz> References: <881d6fd3-89d0-290a-1a8e-5f34207ad5de@paz.bz> Message-ID: that I can't help with :) Glad I could save some of it (the hair that is). On Thu, Dec 29, 2016 at 7:39 PM, Jim Pazarena wrote: > It works ! > > It was THAT easy ! > > Can you suggest how to replace the hair I pulled out ? :-) > > > > On 2016-12-29 5:27 PM, Larry Rosenman wrote: > >> login_access_sockets = tcpwrap >> >> service tcpwrap { >> unix_listener login/tcpwrap { >> group = $default_login_user >> mode = 0600 >> user = $default_login_user >> } >> } >> >> >> >> On Thu, Dec 29, 2016 at 7:21 PM, Jim Pazarena wrote: >> >> I have compiled dovecot2 for FreeBSD with the tcpwrap option. >>> >>> A tcpwrap binary gets built and resides in the FreeBSD directory >>> /usr/local/libexec/dovecot >>> >>> an examination of the compiled options (using the FreeBSD pkg install >>> dovecot2) confirms: LIBWRAP : on >>> >>> yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap >>> >>> I get the following logged error message: >>> >>> 20161229 17:02:49 imap-login: Error: connect(tcpwrap) failed: No such >>> file >>> or directory >>> >>> Is there any way to turn up some super logging so that I can find just >>> what dovecot feels is the failure ? >>> >>> Or, does anyone have an idea how to figure this out? What little hair I >>> have is rapidly getting pulled out in frustration! >>> >>> Thank you. >>> >>> >>> >>> -- >>> Jim Pazarena dovecot at paz.bz >>> >>> >> >> > -- > Jim Pazarena dovecot at paz.bz > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From news at mefox.org Fri Dec 30 03:23:49 2016 From: news at mefox.org (Michael Fox) Date: Thu, 29 Dec 2016 19:23:49 -0800 Subject: expunging all mailboxes In-Reply-To: <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> References: <013801d260aa$259e8be0$70dba3a0$@mefox.org> <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> Message-ID: <028301d2624c$23bd70e0$6b3852a0$@mefox.org> > > But is there a way tell it all mailboxes for a user? For example, > something > > like: > > > > doveadm expunge -u user at domain mailbox ALL savedbefore 30d > > try: > doveadm expunge -u user at domain ALL savedbefore 30d > > just like the example thats here: > http://wiki2.dovecot.org/Tools/Doveadm/SearchQuery I already tried that. Did you? For me, expunge returns an error that says the mailbox must be listed. Also, that example is for search, not expunge. So, the original question remains: is there a way to specify all mailboxes for a user? Michael From lists at merit.unu.edu Fri Dec 30 10:30:12 2016 From: lists at merit.unu.edu (mj) Date: Fri, 30 Dec 2016 11:30:12 +0100 Subject: two listeners with different "driver = " configs In-Reply-To: <9355de41-083c-5e1a-0292-bf09957b07c2@merit.unu.edu> References: <9355de41-083c-5e1a-0292-bf09957b07c2@merit.unu.edu> Message-ID: <63e793e5-177e-15cd-b2e8-abad41b226de@merit.unu.edu> On 12/29/2016 09:23 PM, mj wrote: > Hi, > > I would like to have two seperate imap listeners, with different > authentication settings, but the mailstore and userbase etc will be > identical. > > I know I can do this: > >> service imap-login { >> inet_listener imap { >> port = 143 >> } >> inet_listener imap2 { >> port = 144 >> } >> } For the record, I'm using dovecot 2.2.26 on debian. MJ From tom at talpey.com Fri Dec 30 14:32:37 2016 From: tom at talpey.com (Tom Talpey) Date: Fri, 30 Dec 2016 09:32:37 -0500 Subject: expunging all mailboxes In-Reply-To: <028301d2624c$23bd70e0$6b3852a0$@mefox.org> References: <013801d260aa$259e8be0$70dba3a0$@mefox.org> <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> <028301d2624c$23bd70e0$6b3852a0$@mefox.org> Message-ID: <60797fcb-7d32-f8e2-1de8-3d6b5e7ff51f@talpey.com> On 12/29/2016 10:23 PM, Michael Fox wrote: >>> But is there a way tell it all mailboxes for a user? For example, >> something >>> like: >>> >>> doveadm expunge -u user at domain mailbox ALL savedbefore 30d >> >> try: >> doveadm expunge -u user at domain ALL savedbefore 30d >> >> just like the example thats here: >> http://wiki2.dovecot.org/Tools/Doveadm/SearchQuery > > I already tried that. Did you? > For me, expunge returns an error that says the mailbox must be listed. > Also, that example is for search, not expunge. > > So, the original question remains: is there a way to specify all mailboxes > for a user? doveadm expunge -u mailbox '*' savedbefore 30d Are you sure you really want to do this? My server expunges Trash and Junk on a cycle, but reaching into other mailboxes seems iffy. From news at mefox.org Fri Dec 30 16:03:04 2016 From: news at mefox.org (Michael Fox) Date: Fri, 30 Dec 2016 08:03:04 -0800 Subject: expunging all mailboxes In-Reply-To: <60797fcb-7d32-f8e2-1de8-3d6b5e7ff51f@talpey.com> References: <013801d260aa$259e8be0$70dba3a0$@mefox.org> <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> <028301d2624c$23bd70e0$6b3852a0$@mefox.org> <60797fcb-7d32-f8e2-1de8-3d6b5e7ff51f@talpey.com> Message-ID: <009b01d262b6$34aba600$9e02f200$@mefox.org> > doveadm expunge -u mailbox '*' savedbefore 30d That doesn't work for me either. The command is accepted, but the messages are not expunged. I guess my search/fetch will just have to return the mailbox name, in addition to other fields, and then I'll need to loop through the mailbox names and perform multiple expunges for each user. I understand the desire to avoid accidents by requiring that the mailbox be specified. But if "mailbox ALL" or "mailbox '*' were allowed, that would still avoid the accident and yet also avoid the inefficiency of having to perform multiple expunges for one user. *** Enhancement request: provide a "mailbox all" or "mailbox '*'" option for doveadm search_query so that expunge can be used to remove mail without regard to which mailbox it's in. > Are you sure you really want to do this? My server expunges Trash and > Junk on a cycle, but reaching into other mailboxes seems iffy. Yes. I understand it's unusual. This is an RF (radio) application for emergency services. We have to be efficient about channel utilization. Users know they need to keep their mailboxes clean so that, at the start of an emergency (or other incident), the channel is not clogged with downloading lots of old, irrelevant mail. If they haven't logged in for a while, we'll keep it clear for them. Michael From dovecot at vosslamber.nl Fri Dec 30 18:28:47 2016 From: dovecot at vosslamber.nl (Luuk) Date: Fri, 30 Dec 2016 19:28:47 +0100 Subject: expunging all mailboxes In-Reply-To: <009b01d262b6$34aba600$9e02f200$@mefox.org> References: <013801d260aa$259e8be0$70dba3a0$@mefox.org> <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> <028301d2624c$23bd70e0$6b3852a0$@mefox.org> <60797fcb-7d32-f8e2-1de8-3d6b5e7ff51f@talpey.com> <009b01d262b6$34aba600$9e02f200$@mefox.org> Message-ID: On 30-12-16 17:03, Michael Fox wrote: >> doveadm expunge -u mailbox '*' savedbefore 30d > > That doesn't work for me either. The command is accepted, but the messages > are not expunged. > > I guess my search/fetch will just have to return the mailbox name, in > addition to other fields, and then I'll need to loop through the mailbox > names and perform multiple expunges for each user. I understand the desire > to avoid accidents by requiring that the mailbox be specified. But if > "mailbox ALL" or "mailbox '*' were allowed, that would still avoid the > accident and yet also avoid the inefficiency of having to perform multiple > expunges for one user. > > > *** Enhancement request: provide a "mailbox all" or "mailbox '*'" option > for doveadm search_query so that expunge can be used to remove mail without > regard to which mailbox it's in. > How i read the docs here: http://wiki2.dovecot.org/Tools/Doveadm/SearchQuery and here: http://wiki2.dovecot.org/Tools/Doveadm/Expunge Is what i can test, but i will/can not test 'expunge' ... luuk at opensuse:~> doveadm search ALL savedbefore 1800d 0d41613267fb0e4f28190000bbf0c0ec 1 0d41613267fb0e4f28190000bbf0c0ec 2 0d41613267fb0e4f28190000bbf0c0ec 3 luuk at opensuse:~> doveadm fetch date.received ALL before 1800d | sed 's/^L//g' date.received: 2012-01-12 16:11:09 date.received: 2012-01-12 16:25:27 date.received: 2012-01-12 17:26:23 date.received: 2012-01-12 17:27:15 luuk at opensuse:~> After this, i think this should work: daveadm expunge ALL before 1800d or, in you case: doveadm expunge -u ALL savedbefore 30d if this is not working, that this might be a bug? From tom at talpey.com Fri Dec 30 19:26:57 2016 From: tom at talpey.com (Tom Talpey) Date: Fri, 30 Dec 2016 14:26:57 -0500 Subject: expunging all mailboxes In-Reply-To: <009b01d262b6$34aba600$9e02f200$@mefox.org> References: <013801d260aa$259e8be0$70dba3a0$@mefox.org> <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> <028301d2624c$23bd70e0$6b3852a0$@mefox.org> <60797fcb-7d32-f8e2-1de8-3d6b5e7ff51f@talpey.com> <009b01d262b6$34aba600$9e02f200$@mefox.org> Message-ID: <06bd1a47-fde0-6691-686c-fea3195ed1e5@talpey.com> On 12/30/2016 11:03 AM, Michael Fox wrote: >> doveadm expunge -u mailbox '*' savedbefore 30d > > That doesn't work for me either. The command is accepted, but the messages > are not expunged. Huh, it certainly did for me, although I used "all" instead of "savedbefore 30d" since I just wanted to empty the trash. What version of Dovecot? Mine is 2.2.27. >> Are you sure you really want to do this? My server expunges Trash and >> Junk on a cycle, but reaching into other mailboxes seems iffy. > > Yes. I understand it's unusual. This is an RF (radio) application for > emergency services. We have to be efficient about channel utilization. > Users know they need to keep their mailboxes clean so that, at the start of > an emergency (or other incident), the channel is not clogged with > downloading lots of old, irrelevant mail. If they haven't logged in for a > while, we'll keep it clear for them. I guess that's reasonable for a critical application, but normally I would expect an IMAP client to request headers-only, or just recent messages. My phone's K9 client defaults to something like 2 weeks. Tom. From news at mefox.org Sat Dec 31 06:53:08 2016 From: news at mefox.org (Michael Fox) Date: Fri, 30 Dec 2016 22:53:08 -0800 Subject: expunging all mailboxes In-Reply-To: <06bd1a47-fde0-6691-686c-fea3195ed1e5@talpey.com> References: <013801d260aa$259e8be0$70dba3a0$@mefox.org> <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> <028301d2624c$23bd70e0$6b3852a0$@mefox.org> <60797fcb-7d32-f8e2-1de8-3d6b5e7ff51f@talpey.com> <009b01d262b6$34aba600$9e02f200$@mefox.org> <06bd1a47-fde0-6691-686c-fea3195ed1e5@talpey.com> Message-ID: <015401d26332$8b9de0a0$a2d9a1e0$@mefox.org> > Huh, it certainly did for me, although I used "all" instead of > "savedbefore 30d" since I just wanted to empty the trash. What > version of Dovecot? Mine is 2.2.27. Well, not for me. doveadm search -u user at domain ALL savedbefore 2d -- returns some messages doveadm expunge -u user at domain mailbox '*' savedbefore 2d -- nothing shown, but no error doveadm search -u user at domain ALL savedbefore 2d -- returns the same messages as before I've got 2.2.9 (Ubuntu package for 14.04) > I guess that's reasonable for a critical application, but normally I > would expect an IMAP client to request headers-only, or just recent > messages. My phone's K9 client defaults to something like 2 weeks. Right. But your phone has 100s of kbps or even Mbps of bandwidth, full duplex. But when multiple users are sharing a simplex 56kbps radio channel, even just the headers of old/irrelevant mail are to be avoided. Michael From lists at merit.unu.edu Sat Dec 31 09:38:53 2016 From: lists at merit.unu.edu (mj) Date: Sat, 31 Dec 2016 10:38:53 +0100 Subject: two listeners with different "driver = " configs In-Reply-To: <9355de41-083c-5e1a-0292-bf09957b07c2@merit.unu.edu> References: <9355de41-083c-5e1a-0292-bf09957b07c2@merit.unu.edu> Message-ID: Hi, Does the lack of replies mean that what I'm asking is not possible? (or am I missing something SO obvious that nobody bothers to point it out..?) MJ On 12/29/2016 09:23 PM, mj wrote: > Hi, > > I would like to have two seperate imap listeners, with different > authentication settings, but the mailstore and userbase etc will be > identical. > > I know I can do this: > >> service imap-login { >> inet_listener imap { >> port = 143 >> } >> inet_listener imap2 { >> port = 144 >> } >> } > > But I'm unsure how to configure imap/143 with "driver = ldap" and > imap2/144 with "driver = pam" > > Just to explain why i would like this: > > I am using pam-script-saml (https://github.com/ck-ws/pam-script-saml) to > enable saml-based access to dovecot. I would like to have one listener > 144 to only serve this saml authentication listener, and the regular 143 > listener with driver = ldap. > > Is that config possible? > > Best regards, > MJ From aki.tuomi at dovecot.fi Sat Dec 31 09:56:03 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Sat, 31 Dec 2016 11:56:03 +0200 (EET) Subject: two listeners with different "driver = " configs In-Reply-To: References: <9355de41-083c-5e1a-0292-bf09957b07c2@merit.unu.edu> Message-ID: <214513579.450.1483178164543@appsuite-dev.open-xchange.com> It's very difficult at least. I can't instantly think any sensible way forward, but you might be able to get somewhere using %a variable. Aki > On December 31, 2016 at 11:38 AM mj wrote: > > > Hi, > > Does the lack of replies mean that what I'm asking is not possible? > > (or am I missing something SO obvious that nobody bothers to point it > out..?) > > MJ > > On 12/29/2016 09:23 PM, mj wrote: > > Hi, > > > > I would like to have two seperate imap listeners, with different > > authentication settings, but the mailstore and userbase etc will be > > identical. > > > > I know I can do this: > > > >> service imap-login { > >> inet_listener imap { > >> port = 143 > >> } > >> inet_listener imap2 { > >> port = 144 > >> } > >> } > > > > But I'm unsure how to configure imap/143 with "driver = ldap" and > > imap2/144 with "driver = pam" > > > > Just to explain why i would like this: > > > > I am using pam-script-saml (https://github.com/ck-ws/pam-script-saml) to > > enable saml-based access to dovecot. I would like to have one listener > > 144 to only serve this saml authentication listener, and the regular 143 > > listener with driver = ldap. > > > > Is that config possible? > > > > Best regards, > > MJ From pch at myzel.net Sat Dec 31 10:23:42 2016 From: pch at myzel.net (Peter Chiochetti) Date: Sat, 31 Dec 2016 11:23:42 +0100 Subject: expunging all mailboxes In-Reply-To: <015401d26332$8b9de0a0$a2d9a1e0$@mefox.org> References: <013801d260aa$259e8be0$70dba3a0$@mefox.org> <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> <028301d2624c$23bd70e0$6b3852a0$@mefox.org> <60797fcb-7d32-f8e2-1de8-3d6b5e7ff51f@talpey.com> <009b01d262b6$34aba600$9e02f200$@mefox.org> <06bd1a47-fde0-6691-686c-fea3195ed1e5@talpey.com> <015401d26332$8b9de0a0$a2d9a1e0$@mefox.org> Message-ID: <305489c7-56de-36c4-bc20-b0677cb132b7@myzel.net> Am 2016-12-31 um 07:53 schrieb Michael Fox: >> Huh, it certainly did for me, although I used "all" instead of >> "savedbefore 30d" since I just wanted to empty the trash. > > Well, not for me. > doveadm search -u user at domain ALL savedbefore 2d > -- returns some messages > doveadm expunge -u user at domain mailbox '*' savedbefore 2d > -- nothing shown, but no error > doveadm search -u user at domain ALL savedbefore 2d > -- returns the same messages as before The inefficiency of compiling a list of folders and expunging from each single one seems quite minor to me. That is, as it seems, when "expunge" search-query requires a real mailbox/folder name. Maybe you can "doveadm move" selected messages to a /fresh/ folder and then expunge that one completely? Slightly less efficient, easier to script though all the time. -- peter From aki.tuomi at dovecot.fi Sat Dec 31 10:50:19 2016 From: aki.tuomi at dovecot.fi (Aki Tuomi) Date: Sat, 31 Dec 2016 12:50:19 +0200 (EET) Subject: two listeners with different "driver = " configs In-Reply-To: <214513579.450.1483178164543@appsuite-dev.open-xchange.com> References: <9355de41-083c-5e1a-0292-bf09957b07c2@merit.unu.edu> <214513579.450.1483178164543@appsuite-dev.open-xchange.com> Message-ID: <1037720096.789.1483181420926@appsuite-dev.open-xchange.com> or maybe you can try local 0.0.0.0/0:144 { passdb { } } > On December 31, 2016 at 11:56 AM Aki Tuomi wrote: > > > It's very difficult at least. I can't instantly think any sensible way forward, but you might be able to get somewhere using %a variable. > > Aki > > > On December 31, 2016 at 11:38 AM mj wrote: > > > > > > Hi, > > > > Does the lack of replies mean that what I'm asking is not possible? > > > > (or am I missing something SO obvious that nobody bothers to point it > > out..?) > > > > MJ > > > > On 12/29/2016 09:23 PM, mj wrote: > > > Hi, > > > > > > I would like to have two seperate imap listeners, with different > > > authentication settings, but the mailstore and userbase etc will be > > > identical. > > > > > > I know I can do this: > > > > > >> service imap-login { > > >> inet_listener imap { > > >> port = 143 > > >> } > > >> inet_listener imap2 { > > >> port = 144 > > >> } > > >> } > > > > > > But I'm unsure how to configure imap/143 with "driver = ldap" and > > > imap2/144 with "driver = pam" > > > > > > Just to explain why i would like this: > > > > > > I am using pam-script-saml (https://github.com/ck-ws/pam-script-saml) to > > > enable saml-based access to dovecot. I would like to have one listener > > > 144 to only serve this saml authentication listener, and the regular 143 > > > listener with driver = ldap. > > > > > > Is that config possible? > > > > > > Best regards, > > > MJ From dovecot at vosslamber.nl Sat Dec 31 14:51:39 2016 From: dovecot at vosslamber.nl (Luuk) Date: Sat, 31 Dec 2016 15:51:39 +0100 Subject: expunging all mailboxes In-Reply-To: <015401d26332$8b9de0a0$a2d9a1e0$@mefox.org> References: <013801d260aa$259e8be0$70dba3a0$@mefox.org> <0fe6e2e6-37da-f08a-a475-e8a68ce87913@vosslamber.nl> <028301d2624c$23bd70e0$6b3852a0$@mefox.org> <60797fcb-7d32-f8e2-1de8-3d6b5e7ff51f@talpey.com> <009b01d262b6$34aba600$9e02f200$@mefox.org> <06bd1a47-fde0-6691-686c-fea3195ed1e5@talpey.com> <015401d26332$8b9de0a0$a2d9a1e0$@mefox.org> Message-ID: On 31-12-16 07:53, Michael Fox wrote: >> Huh, it certainly did for me, although I used "all" instead of >> "savedbefore 30d" since I just wanted to empty the trash. What >> version of Dovecot? Mine is 2.2.27. > > Well, not for me. > doveadm search -u user at domain ALL savedbefore 2d > -- returns some messages > doveadm expunge -u user at domain mailbox '*' savedbefore 2d > -- nothing shown, but no error > doveadm search -u user at domain ALL savedbefore 2d > -- returns the same messages as before > > I've got 2.2.9 (Ubuntu package for 14.04) > > >> I guess that's reasonable for a critical application, but normally I >> would expect an IMAP client to request headers-only, or just recent >> messages. My phone's K9 client defaults to something like 2 weeks. > > Right. But your phone has 100s of kbps or even Mbps of bandwidth, full > duplex. But when multiple users are sharing a simplex 56kbps radio channel, > even just the headers of old/irrelevant mail are to be avoided. > > Michael > ok, i did setup a test, and these are the results ;) sh-4.3# doveadm search -u luuk savedbefore 2d 6e076801a027c655aa700000e4766c2b 1 a11f76379f27c655a4700000e4766c2b 1 sh-4.3# doveadm expunge -u luuk mailbox INBOX savedbefore 2d sh-4.3# doveadm search -u luuk savedbefore 2d 6e076801a027c655aa700000e4766c2b 1 sh-4.3# doveadm fetch -u luuk mailbox savedbefore 2d | sed 's/^L//g' mailbox: Sent sh-4.3# doveadm expunge -u luuk mailbox '*' savedbefore 2d sh-4.3# doveadm fetch -u luuk mailbox savedbefore 2d | sed 's/^L//g' sh-4.3# doveadm search -u luuk savedbefore 2d sh-4.3# maybe the debug option '-D' gives a clue why it failes on your site? doveadm -D expunge -u user at domain mailbox '*' savedbefore 2d From daniele.barresi at gmail.com Tue Dec 27 16:35:24 2016 From: daniele.barresi at gmail.com (Daniele Barresi) Date: Tue, 27 Dec 2016 17:35:24 +0100 Subject: Fatal error with IMAP MOVE from a shared mailbox to Trash folder Message-ID: Hello everyone. I have a problem using Dovecot 2.2.26 with ACL plugin and deleting e-mails from a shared mailbox. My user doesn't have the "expunge" permission on the shared mailbox, but it has the "write-deleted" permission. So, when I delete a message from the shared mailbox using a client that implements the IMAP MOVE command, it tries to move the message to my Trash folder. Then the server closes the connection to the client (process aborted) and I get three lines in the log file with a backtrace and "Fatal" error. In this case the message doesn't get copied or moved from the shared folder and the client complaints. I found the same thing happens whenever I try to move anything between folders of the shared mailbox itself, while logged in with my user. I can move messages inside my own mailbox just fine. If I try the same operation from a client that uses the IMAP COPY + DELETE commands, no errors are logged and the outcome is as expected: the message gets copied from the shared folder to my Trash and gets the flag "\Deleted" set on the shared folder. My setup is as follows: Dovecot: 2.2.26.0 OS: Ubuntu 16.04.1 LTS CPU architecture: x86_64 Filesystem: ext4 The relevant lines from mail.err log: Dec 27 15:21:18 dovecot dovecot: imap(danielebarresi): Panic: file mail-storage.c: line 2143 (mailbox_save_context_reset): assertion failed: (ctx->copying_via_save) Dec 27 15:21:18 dovecot dovecot: imap(danielebarresi): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9438e) [0x7fbcd478538e] -> /usr/lib/dovecot/libdovecot.so.0(+0x9447c) [0x7fbcd478547c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbcd471ea4e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x41b78) [0x7fbcd4a50b78] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_cancel+0x73) [0x7fbcd4a53d73] -> /usr/lib/dovecot/modules/lib01_acl_plugin.so(+0xe142) [0x7fbcd3f1d142] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x4516d) [0x7fbcd4a5416d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x23) [0x7fbcd4a54333] -> dovecot/imap(+0xf9c5) [0x557cf98629c5] -> dovecot/imap(command_exec+0xa6) [0x557cf986f196] -> dovecot/imap(+0x1a4c2) [0x557cf986d4c2] -> dovecot/imap(+0x1a550) [0x557cf986d550] -> dovecot/imap(client_handle_input+0x195) [0x557cf986d915] -> dovecot/imap(client_input+0x85) [0x557cf986de25] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7fbcd4799bdc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) [0x7fbcd479b09a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fbcd4799c65] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fbcd4799e08] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fbcd4724f53] -> dovecot/imap(main+0x322) [0x557cf9860ca2] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fbcd4348830] -> dovecot/imap(+0xde1f) [0x557cf9860e1f] Dec 27 15:21:18 dovecot dovecot: imap(danielebarresi): Fatal: master: service(imap): child 6907 killed with signal 6 (core dumped) Dovecot configuration (doveadm -n): # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.0-57-generic x86_64 Ubuntu 16.04.1 LTS auth_cache_negative_ttl = 10 mins auth_cache_size = 2 M auth_master_user_separator = * auth_mechanisms = plain login first_valid_uid = 12 last_valid_uid = 12 mail_location = maildir:~/Maildir mail_plugins = acl quota notify mail_log stats lazy_expunge managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace casellecondivise { list = children location = maildir:%%h/Maildir:INDEXPVT=~/Maildir/shared/%%u prefix = Caselle condivise/%%u/ separator = / subscriptions = no type = shared } namespace expunged { hidden = yes list = no location = maildir:/var/expunged/%n/Expunged prefix = EXPUNGED/ separator = / } namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/etc/dovecot/shared/shared-mailboxes lazy_expunge = EXPUNGED/ lazy_expunge_only_last_instance = yes mail_log_events = delete copy flag_change save undelete expunge mail_log_fields = uid box msgid size quota = maildir:user quota quota_exceeded_message = (Quota exceeded) La casella di posta elettronica del destinatario ? piena. quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=100%% quota-warning 100 %u sieve = file:~/sieve;active=~/.dovecot.sieve stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 32 M stats_refresh = 30 secs stats_session_min_time = 15 mins stats_track_cmds = yes stats_user_min_time = 1 hours } protocols = " imap sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = mail mode = 0666 user = postfix } unix_listener auth-userdb { group = mail user = mail } } service dict { unix_listener dict { group = mail mode = 0600 user = mail } } service imap-login { process_limit = 300 process_min_avail = 2 } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /etc/dovecot/scripts/quota-warning.sh unix_listener quota-warning { group = mail user = mail } } service stats { fifo_listener stats-mail { mode = 0600 user = mail } } ssl = required ssl_cert =