Re: Expunge (?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Mar 2015, Muzaffer Tolga Ozses wrote: I don't know if this is the correct term. Let me elaborate. From time to time, I want to expunge (?) the mail folder so that users' Trash'd mails don't occupy space. So, here are my questions: 1. Is this the correct term? Well, perhaps. Why you clinge on the term? 2. Is it a Good Idea™ to do it? That depends on your users. Some users of mine use Trash as some sort I do not need the message, but wait, in some days it might become sort of interessting. Therefore check out the expire plugin to remove messages that idle for an amount of days in Trash. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEVAwUBVQFLoHz1H7kL/d9rAQIExgf/eBdQVeJfpDNtRwXO/CeihybV+C09nRq4 jasutSbZU2yDQi/8XhqRdob76frvhhj3kPRX6z8epkIMNHiD7NGKbaXsfe+ACibq Sn81WRBhcUDrPPB3CJmkS0IqVdEuMLs9O0YAeK1WyT+Dh48Xcn+o0uYCjLkYM2By n6+vX1AD0k5BHqlWz157zZuUAlgZJRtlzJnWSIAbCBpKP5nKLmDZ9uZAEqc1Goj9 DBpGs24HL4kGddENk4bhfy/NFFqaVINOiEM/Q/bqZAEb9nA9dQSEWQQFjyGnAuq9 UOI0/Ijo/Hj/8H2fqTm+oC3EK2+C90E0QFCidjrp3b4B2pRQNjPBtQ== =XErt -END PGP SIGNATURE-
Re: Expunge (?)
On 12 March 2015 at 10:17, Steffen Kaiser skdove...@smail.inf.fh-brs.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Mar 2015, Muzaffer Tolga Ozses wrote: I don't know if this is the correct term. Let me elaborate. From time to time, I want to expunge (?) the mail folder so that users' Trash'd mails don't occupy space. So, here are my questions: 1. Is this the correct term? Well, perhaps. Why you clinge on the term? Because if it is, I'm going to search on that keyword. 2. Is it a Good Idea™ to do it? That depends on your users. Some users of mine use Trash as some sort I do not need the message, but wait, in some days it might become sort of interessting. Therefore check out the expire plugin to remove messages that idle for an amount of days in Trash. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEVAwUBVQFLoHz1H7kL/d9rAQIExgf/eBdQVeJfpDNtRwXO/CeihybV+C09nRq4 jasutSbZU2yDQi/8XhqRdob76frvhhj3kPRX6z8epkIMNHiD7NGKbaXsfe+ACibq Sn81WRBhcUDrPPB3CJmkS0IqVdEuMLs9O0YAeK1WyT+Dh48Xcn+o0uYCjLkYM2By n6+vX1AD0k5BHqlWz157zZuUAlgZJRtlzJnWSIAbCBpKP5nKLmDZ9uZAEqc1Goj9 DBpGs24HL4kGddENk4bhfy/NFFqaVINOiEM/Q/bqZAEb9nA9dQSEWQQFjyGnAuq9 UOI0/Ijo/Hj/8H2fqTm+oC3EK2+C90E0QFCidjrp3b4B2pRQNjPBtQ== =XErt -END PGP SIGNATURE- Thanks, -- mto
Re: Released Pigeonhole v0.4.7.rc1 for Dovecot v2.2.16.rc1
On 3/12/2015 4:23 AM, E.B. wrote: I'll check on 0.4.6 and report if I see anything interesting, but I will assume for the moment that since personal scripts work in 0.4.6 that this log info won't be there. It is correct that there is no sieve file or directory in the user's home dir. This wasn't a problem in 0.4.6. Is it a requirement? Well, since your config says the following: sieve = file:~/sieve;active=~/.dovecot.sieve It expects a sieve storage directory at ~/sieve (created when ManageSieve is used to upload a script). Also, a symbolic link pointing to the active script will be located at ~/.dovecot.sieve once a script is activated (i.e. through ManageSieve or doveadm sieve). I wonder how this would have worked before with 0.4.6. Is the ~/.dovecot.sieve a normal script file perhaps (rather than a symlink)? This would mean that the following config would work (e.g. if you don't use ManageSieve): sieve = file:~/.dovecot.sieve The configuration for that was not of my doing (doesn't that mean it shouldn't have shown up in doveconf -n?). Yes, the .sieve scripts in user home are regular files. Strange 0.4.6 didn't mind this situation, but seems easy to put the configuration right and move on. Well, even though your config is a bit strange, Pigeonhole should recognize this rather than fail. I will fix this. Regards, Stephan.
Re: Different realm for different listeners?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10-03-15 18:20, Chris Adams wrote: I see this has been asked a few times over the years (but not in several years), and the response was along the lines of maybe someday, so I figured I'd see if someday was here yet... I have a need to have a different default realm for different listeners. Basically, I've a bunch of different domains, and a few of them insist their users not be required to authenticate with user@domain and just use user, and I'm trying to make this work without separate daemons and/or VMs. I'll be using Dovecot 2.2 (most likely 2.2.10 as provided by RHEL/CentOS 7). Thanks. If there's not a way to do this directly in Dovecot, does anybody have any suggestion that doesn't require several different VMs? You could drop the default realm completely, and create a second passdb lookup which uses only the username part to lookup credentials. This means that, as long as you have no conflicts as usernames 'j...@foo.com' vs 'j...@bar.com', you'd be able to support username 'john'. When you're able to use the password in your sql WHERE statement [1] too, you could even work around that, because you'd only have mismatches when 'j...@foo.com' and 'j...@bar.com' have the same passphrase. [1] http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_server Tom -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJU/ywgAAoJEJPfMZ19VO/1mzQP/Anz44a5c7J6ir8mUgTVZEOn bFOrkXHkntLSruOZ9FHrMJX4RYXTSbZTe9fUUx1zDXiU7Aj2VQ6LqueXt7LFUW2Z jmPsxaHXBL8fSR8suwpzZ06/blz563Qi06HEZb2ixjITyvd3iVJCSPzVu3NLdsSH oxAE50I2vzuFHqfN9JbXD98HuEdGedhOldjlw9MsXmUFthfAYN8N4AhCgzm7G1C8 wk0909pvUAjfDuY7mJU6Q9smDBRdvP4i/aZtKrs/G1ZGq8SPbClbjwLedQy88q76 F/5DcY0M+Z2hYHEZrBQimfUByANY0YvMlQubqQ/s/lsUSD2IdDX6K3lvYKIuKNSe SHgnt9p6/yTAmX3gbsnB7fbbYQQNRrTHM8Uk8KWJhkxhWZpKt3BOoPMphMa5TCKR 9sBRZqIdN1vSd31Gu/QylKv0+zDeIXay7T+HVCf82KPHq/+zFzSZ1iR14V4TdOyz SXNprdxRik49tiAHRTSMQwRmOHDel9+guhozSJVj0ISnTCeRAC5vSvGActA3Gl8l 8aMBLDf/VyS7B+Ss0aWOs8MwIrre9oAxMa937lLc3sNh48A7uw38wJmIB6L20q2n QPlsYCm39wMgWvWi84rEhi663jBdRsZKBq+/Ou7oFHXkQmVmt1ToXw0mC5Bst9Ew y832vTrhtp1Sl2Siv1RV =KWRg -END PGP SIGNATURE-
Re: Different realm for different listeners?
On Tuesday 10 March 2015 18:38:40 Tom Hendrikx wrote: On 10-03-15 18:20, Chris Adams wrote: I see this has been asked a few times over the years (but not in several years), and the response was along the lines of maybe someday, so I figured I'd see if someday was here yet... I have a need to have a different default realm for different listeners. Basically, I've a bunch of different domains, and a few of them insist their users not be required to authenticate with user@domain and just use user, and I'm trying to make this work without separate daemons and/or VMs. I'll be using Dovecot 2.2 (most likely 2.2.10 as provided by RHEL/CentOS 7). Thanks. If there's not a way to do this directly in Dovecot, does anybody have any suggestion that doesn't require several different VMs? You could drop the default realm completely, and create a second passdb lookup which uses only the username part to lookup credentials. This means that, as long as you have no conflicts as usernames 'j...@foo.com' vs 'j...@bar.com', you'd be able to support username 'john'. Well, I think conflict is the keyword here. Everybody want an e-mail address called contact or office :) When you're able to use the password in your sql WHERE statement [1] too, you could even work around that, because you'd only have mismatches when 'j...@foo.com' and 'j...@bar.com' have the same passphrase. [1] http://wiki2.dovecot.org/AuthDatabase/SQL#Password_verification_by_SQL_serve r Tom -- Mihai Bădici http://mihai.badici.ro
Re: Different realm for different listeners?
Once upon a time, Tom Hendrikx t...@whyscream.net said: You could drop the default realm completely, and create a second passdb lookup which uses only the username part to lookup credentials. This means that, as long as you have no conflicts as usernames 'j...@foo.com' vs 'j...@bar.com', you'd be able to support username 'john'. The domains I need to handle are separate telephone company ISPs, so they all want common things like sales, so that won't work. All my users are in MySQL. Reading the docs, I see that %l expands to the local IP address almost everywhere. If that's available in the userdb SQL expansion, I could write a (somewhat convoluted) SQL statement that adds a domain based on the local IP. Does that sound like it'll work? Not quite as elegant as just setting auth_default_realm in separate listeners, but should work I guess. -- Chris Adams c...@cmadams.net
Expunge (?)
Hi, I don't know if this is the correct term. Let me elaborate. From time to time, I want to expunge (?) the mail folder so that users' Trash'd mails don't occupy space. So, here are my questions: 1. Is this the correct term? 2. Is it a Good Idea™ to do it? Thanks, -- mto
libdriver_msql.so
Hello, i installed dovecot 2.11.1 on ubuntu Linux dadd3041 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:07:11 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux To make it clear, architecture is PowerPC 64bit Then i installed dovecot via apt-get. But the file /usr/lib/dovecot/modules/auth/libdriver_mysql.so is missing. So i compiled dovecot myself on this system and got a file /usr/lib/dovecot/modules/auth/libdriver_mysql.so Then i restartetd the server and try to do a login via a webmailer (roundcube), but i get no connection to the database server. This is found in /var/log/mail.log Mar 11 15:19:04 dadd3041 dovecot: master: Dovecot v2.2.9 starting up (core dumps disabled) Mar 11 15:19:04 dadd3041 postfix/master[3367]: reload -- version 2.11.1, configuration /etc/postfix Mar 11 15:19:04 dadd3041 postfix/master[3367]: terminating on signal 15 Mar 11 15:19:04 dadd3041 postfix/master[3597]: daemon started -- version 2.11.1, configuration /etc/postfix Mar 11 15:19:25 dadd3041 dovecot: auth: Error: dlopen(/usr/lib/dovecot/modules/auth/libdriver_mysql.so) failed: /usr/lib/dovecot/modules/auth/libdriver_mysql.so: wrong ELF class: ELFCLASS32 Mar 11 15:19:25 dadd3041 dovecot: auth: Fatal: Unknown database driver 'mysql' Mar 11 15:19:25 dadd3041 dovecot: master: Error: service(auth): command startup failed, throttling for 2 secs Mar 11 15:19:25 dadd3041 dovecot: imap-login: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=, rip=::1, lip=::1, TLS handshaking, session=rJpS9AMR9wAB I know this means it is not a 64bit object but how could i achieve to get right one? best regards, kaniggl
Re: location of dovecot.rawlog-directory
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Mar 2015, Hardy Flor wrote: How is it possible to have the dovecot.rawlog-directory outside the mail_location? A link to another directory is not because it is checked in rawlog.c S_ISDIR to directory. Patch rawlog.c and recompile. :) - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEVAwUBVQFzYnz1H7kL/d9rAQJM5gf/YKr5UP1Z1UlfjCzxgX0sYNUgo4Syd6wD 2lDrlxjkjtWaNgIOY5Kiv2NBJwU579rL+VMqwd1CpkUSmBGbJZGY/YNgDxLfsJkM +EgpmPbFB1+TeZjKygu5F1i9B51MECVRUvWWKI3BA/WQjFMGH7PiK+vSkuUzAi+g XhqvoaKx5doInX5nJibgeZv9W9kF2dLXPFYu79DI6go5laE4VFVSIaeiyVzo+Myl 6DHT1kRV7AHFhTe2wYc2YiIJcJUoiL9x8s5c5nCUKpzjdw5F95Mh5nMcyc1pu8Wz Gg9Po8tr2nNxpimlP/F7krJQKJFPltjZMOi7qJL03C0ILLTKqha35Q== =l/zF -END PGP SIGNATURE-
Re: Why is Sieve trying to re-compile global scripts?
On 03/12/2015 12:02 AM, Stephan Bosch wrote: On 3/11/2015 11:10 AM, Olaf Hopp wrote: Please see the thread with subject Sieve permissions issue following update I tested sucessfully a developper issue last month on the hint of Stephan. Yesterday I started to test the currenr RCs. First I was disappointed, because the error seems to persist. So I double checked everything, recreated / recompiled everything an the error went away. So I thought it was mistake on my side. I gave Spephan postive feedback. And I'm waiting for the final release for my production server. But when I read your mails, I'm not feeling happy. I think it's a kink of luck/voodoo/whatever. What you must do, I think, is to compile the sieve script with the exact version running afterwards. And I think you should the remove the compiled .svbin files before recreating them again. Don't overwrite them with the compiler. I think I'll also dig into this any further today. Please do. I cannot reproduce this so far. Since E.B. still got an obscure debug message about metadata not being up to date, I added debug lines to the remaining places where this could emerge (currently only available from hg). Regards, Stephan. Hi, I'm still trying but currently I can not reproduce the bug. But I will keep on hammering on it. Olaf -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: olaf.h...@kit.edu atis.informatik.kit.edu www.kit.edu KIT - Universität des Landes Baden-Württemberg und nationales Forschungszentrum in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert. smime.p7s Description: S/MIME Cryptographic Signature
Re: Released Pigeonhole v0.4.7.rc1 for Dovecot v2.2.16.rc1
On 12 Mar 2015, at 05:48, E.B. emailbuilde...@yahoo.com wrote: However, I do see that Sieve was accessing the user home directory because for some reason now it just created a .pki directory therein, which inside of it has an empty nssdb directory. That never happened before...? Not a big problem, but I'd prefer not to have that there. Sieve doesn't do that. I don't think Dovecot does that either, but I am not sure. Odd. Some lib Sieve uses? These directories do not appear in user home directories unless I install the newest Sieve (and not until a delivery via LMTP happens). No other changes. No other software is currently accessing user home locations at all. Using today's hg version, these .pki directories aren't created. I wonder if Timo could shine a light on this. Probably some PAM plugin or some other strange automation. Dovecot definitely doesn't create those itself.
Re: Dovecot fails to compile --with-cdb (and attempted fix)
On Thu, Mar 12, 2015 at 9:43 PM, Timo Sirainen t...@iki.fi wrote:
On 10 Mar 2015, at 16:24, Jeffrey 'jf' Lim jfs.wo...@gmail.com wrote:
On Tue, Mar 10, 2015 at 2:22 AM, Jeffrey 'jf' Lim jfs.wo...@gmail.com
wrote:
On Tue, Mar 10, 2015 at 2:15 AM, Jeffrey 'jf' Lim jfs.wo...@gmail.com
wrote:
Dovecot version: 2.2.15
Tinycdb: 0.78
I'm attempting to compile dovecot --with-cdb, but keep getting into a
problem with cdb:
libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes
-Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2
-Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2
-Wl,--as-needed -o .libs/anvil main.o anvil-connection.o
anvil-settings.o
connect-limit.o penalty.o -Wl,--export-dynamic
../../src/lib-dovecot/.libs/libdovecot.so -ldl -lrt -Wl,-rpath
-Wl,/usr/local/lib/dovecot
../../src/lib-dovecot/.libs/libdovecot.so: undefined reference to
`cdb_read'
../../src/lib-dovecot/.libs/libdovecot.so: undefined reference to
`cdb_find'
../../src/lib-dovecot/.libs/libdovecot.so: undefined reference to
`cdb_free'
../../src/lib-dovecot/.libs/libdovecot.so: undefined reference to
`cdb_init'
collect2: ld returned 1 exit status
make[3]: *** [anvil] Error 1
make[3]: Leaving directory `/home/jf/dovecot-2.2.15/src/anvil'
==
After some troubleshooting, I've finally managed to get dovecot to
compile, albeit with a hack:
--- src/lib-dovecot/Makefile.old2015-03-09 17:36:15.690179802 +
+++ src/lib-dovecot/Makefile2015-03-09 18:01:43.075719700 +
@@ -230,7 +230,7 @@
LIBDOVECOT_STORAGE_DEPS = $(top_builddir)/src/lib-storage/
libdovecot-storage.la $(top_builddir)/src/lib-imap-storage/
libimap-storage.la
LIBICONV =
LIBOBJS =
-LIBS = -lrt
+LIBS = -lrt -lcdb
LIBTOOL = $(SHELL) $(top_builddir)/libtool
LIBWRAP_LIBS =
LINKED_STORAGE_LDADD =
This isn't the best fix, admittedly (I wish I were more familiar with
autotools), but I'll say that the configure process isn't right yet for
cdb. Can anybody produce a better fix? Would love to learn more.
ok, well I guess that fixed the compilation, but as I've just found
out,
it does *not* link in libcdb (I've got libcdb in /usr/local/lib)
properly!
Has anybody tried to compile dovecot with cdb support?
For anybody following: sorry, my bad. It turns out I hadn't set CPPFLAGS
and LDFLAGS during the configure to use /usr/local/{include,lib}. When
that's done, this works (in the sense that libdovecot.so is now linked
with
libcdb!).
I'm not so sure that this is the best place to link libcdb in, though,
but
for an expedient fix, it works Would appreciate somebody more
familiar
with the code weighing in on this one.
Well, it was never supposed to be linked to anything except the dict
binary, allowing it to be used via the dict proxy. Changed:
http://hg.dovecot.org/dovecot-2.2/rev/16ff063e3588
Thanks, Timo. Is this the only patch that needs to go in for the current
version (2.2.15)? I've applied this to 2.2.15, and configured and compiled
as before:
CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib ./configure
--with-cdb
make
and I still get the same errors.
-jf
Re: v2.2.16 release candidate released
On 09 Mar 2015, at 13:07, Hardy Flor hf...@gmx.de wrote: This easy to correct errors is unfortunately still exists. I once hung my solution, but I can only test on a system. # dovecot --version 2.2.16.rc1 # doveadm -f table mailbox status messages guid -u flor_hardy * mailbox messages guid Trash 060a619171f66fd5403584b126f5b Entwürfe 062a619171f66fd5403584b126f5b INBOX 061a619171f66fd5403584b126f5b dovecot-2.2.16rc1-table.diffNachricht als Anhang.eml Thanks, committed with some coding style changes: http://hg.dovecot.org/dovecot-2.2/rev/8780ca0fbf22 http://hg.dovecot.org/dovecot-2.2/rev/8780ca0fbf22
Re: doveconf -a Segmentation Fault
Am 12.03.2015 um 15:07 schrieb Dan LaSota: Getting Segmentation Fault When I run doveconf -a i don't in other words: bad for you but what's the purpose of the information without any debugging like strace? signature.asc Description: OpenPGP digital signature
Re: location of dovecot.rawlog-directory
I want running servers, not with each new version have to compile. Am 12.03.2015 um 12:07 schrieb Steffen Kaiser: Patch rawlog.c and recompile. :)
Re: location of dovecot.rawlog-directory
Am 12.03.2015 um 15:18 schrieb Hardy Flor: I want running servers, not with each new version have to compile. well, rpm-SPECs allow including of patches if you rely on distribution packages you won't see a update even if upstream would introduce a config option for years Am 12.03.2015 um 12:07 schrieb Steffen Kaiser: Patch rawlog.c and recompile. :) signature.asc Description: OpenPGP digital signature
Re: rawlog with -i not worked
On 11 Mar 2015, at 12:50, Hardy Flor hf...@gmx.de wrote: When I change the option 'i' to the letter 'a' is everything as designed. Why is 'i' at this location the problem? Fix explanation: http://hg.dovecot.org/dovecot-2.2/rev/cd5fc6ff8027 Oops, also http://hg.dovecot.org/dovecot-2.2/rev/aed1e8340ea7
Re: Fixing broken UTF-8 handling with MySQL driver
On 11 Mar 2015, at 21:31, Felix Zandanel fe...@zandanel.me wrote: Although my MySQL installation is set up to use UTF-8 as the default charset on every level (config, database, table and field), and the character_set_* runtime variables all yield the value utf8, it still seems that the mysql client library must be instructed to actually use UTF-8 explicitly. Adding the following statement to driver_mysql_connect() fixes the issue for me: mysql_options(db-mysql, MYSQL_SET_CHARSET_NAME, utf8); I think you can also add to /etc/my.cnf : [client] default-character-set = utf8
doveconf -a Segmentation Fault
Getting Segmentation Fault When I run doveconf -a Dan LaSota Instructional Designer, UAF eLearning (907) 451-4067 dan.las...@alaska.edu http://elearning.uaf.edu
Re: location of dovecot.rawlog-directory
When I set in the home-variable in the userdb-section on my request directory and not used the home-dirctory in the configuration, have what can be expected for other effects?
Re: Dovecot fails to compile --with-cdb (and attempted fix)
On 10 Mar 2015, at 16:24, Jeffrey 'jf' Lim jfs.wo...@gmail.com wrote:
On Tue, Mar 10, 2015 at 2:22 AM, Jeffrey 'jf' Lim jfs.wo...@gmail.com
wrote:
On Tue, Mar 10, 2015 at 2:15 AM, Jeffrey 'jf' Lim jfs.wo...@gmail.com
wrote:
Dovecot version: 2.2.15
Tinycdb: 0.78
I'm attempting to compile dovecot --with-cdb, but keep getting into a
problem with cdb:
libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes
-Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2
-Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2
-Wl,--as-needed -o .libs/anvil main.o anvil-connection.o anvil-settings.o
connect-limit.o penalty.o -Wl,--export-dynamic
../../src/lib-dovecot/.libs/libdovecot.so -ldl -lrt -Wl,-rpath
-Wl,/usr/local/lib/dovecot
../../src/lib-dovecot/.libs/libdovecot.so: undefined reference to
`cdb_read'
../../src/lib-dovecot/.libs/libdovecot.so: undefined reference to
`cdb_find'
../../src/lib-dovecot/.libs/libdovecot.so: undefined reference to
`cdb_free'
../../src/lib-dovecot/.libs/libdovecot.so: undefined reference to
`cdb_init'
collect2: ld returned 1 exit status
make[3]: *** [anvil] Error 1
make[3]: Leaving directory `/home/jf/dovecot-2.2.15/src/anvil'
==
After some troubleshooting, I've finally managed to get dovecot to
compile, albeit with a hack:
--- src/lib-dovecot/Makefile.old2015-03-09 17:36:15.690179802 +
+++ src/lib-dovecot/Makefile2015-03-09 18:01:43.075719700 +
@@ -230,7 +230,7 @@
LIBDOVECOT_STORAGE_DEPS = $(top_builddir)/src/lib-storage/
libdovecot-storage.la $(top_builddir)/src/lib-imap-storage/
libimap-storage.la
LIBICONV =
LIBOBJS =
-LIBS = -lrt
+LIBS = -lrt -lcdb
LIBTOOL = $(SHELL) $(top_builddir)/libtool
LIBWRAP_LIBS =
LINKED_STORAGE_LDADD =
This isn't the best fix, admittedly (I wish I were more familiar with
autotools), but I'll say that the configure process isn't right yet for
cdb. Can anybody produce a better fix? Would love to learn more.
ok, well I guess that fixed the compilation, but as I've just found out,
it does *not* link in libcdb (I've got libcdb in /usr/local/lib) properly!
Has anybody tried to compile dovecot with cdb support?
For anybody following: sorry, my bad. It turns out I hadn't set CPPFLAGS
and LDFLAGS during the configure to use /usr/local/{include,lib}. When
that's done, this works (in the sense that libdovecot.so is now linked with
libcdb!).
I'm not so sure that this is the best place to link libcdb in, though, but
for an expedient fix, it works Would appreciate somebody more familiar
with the code weighing in on this one.
Well, it was never supposed to be linked to anything except the dict binary,
allowing it to be used via the dict proxy. Changed:
http://hg.dovecot.org/dovecot-2.2/rev/16ff063e3588
Re: How to detect out-of-sync condition
Thanks. I use dovecot's lda and dovecot's sieve filter. So it looks like I need to compare the index/mailbox mtimes as you suggest. What am I looking for? I see that the indexes are updated when I run the resync. I checked my mailbox (that was not resynced) and noticed that dovecot.index last update was 16 days ago. So am I resyncing if the gap is over x days? If so, is there a way to resync just those mailboxes with a doveadm command or do I have to write a program look for that condition and run doveadm when matched? Cliff Hayes cha...@afo.net writes: I recently had a user whose mailbox had gone out of sync. Webmail and client inbox totals had become vastly different and response times had become unacceptable. A doveadm force-resync fixed the problem nicely. This will no doubt happen again as we grow the service and I would like to have some type of indication at the server level so I can run a resync on a per-user basis as required. Perhaps what you ought to look for is how are they getting out of sync in the first place. Assuming your webmail is a IMAP/POP client, I would look at ways that your user's INBOX can be modified out of Dovecot's sight. For example, does your LDA use dovecot's lda/lmtp, or do your users run mail clients that directly manipulate mailbox files, or do you use procmail/mail filters? By closing off other avenues other than dovecot imap/pop/lda/etc., the indices will stay sync'd. If you really have to do manual resyncing, comparing index/mailbox mtimes might be one way to do it. Joseph Tam jtam.h...@gmail.com
Re: Dovecot fails to compile --with-cdb (and attempted fix)
On 12 Mar 2015, at 16:49, Jeffrey 'jf' Lim jfs.wo...@gmail.com wrote: On Thu, Mar 12, 2015 at 9:43 PM, Timo Sirainen t...@iki.fi wrote: Well, it was never supposed to be linked to anything except the dict binary, allowing it to be used via the dict proxy. Changed: http://hg.dovecot.org/dovecot-2.2/rev/16ff063e3588 Thanks, Timo. Is this the only patch that needs to go in for the current version (2.2.15)? I've applied this to 2.2.15, and configured and compiled as before: CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib ./configure --with-cdb make and I still get the same errors. Did you run autogen.sh again before configure?
v2.2.16 released
http://dovecot.org/releases/2.2/dovecot-2.2.16.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.16.tar.gz.sig A few fixes and some imapc improvements since the release candidate. * dbox: Resyncing (e.g. doveadm force-resync) no longer deletes dovecot.index.cache file. The cache file was rarely the problem so this just caused unnecessary slowness. * Mailbox name limits changed during mailbox creation: Each part of a hierarchical name (e.g. x or y in x/y) can now be up to 255 chars long (instead of 200). This also reduces the max number of hierarchical levels to 16 (instead of 20) to keep the maximum name length 4096 (a common PATH_MAX limit). The 255 char limit is hopefully large enough for migrations from all existing systems. It's also the limit on many filesystems. + director: Added director_consistent_hashing setting to enable consistent hashing (instead of the mostly-random MD5 hashing). This causes fewer user moves between backends when backend counts are changed, which may improve performance (mainly due to caching). + director: Added support for tags, which allows one director ring to serve multiple backend clusters with different sets of users. + LMTP server: Added lmtp_user_concurrency_limit setting to limit how many LMTP deliveries can be done concurrently for a single user. + LMTP server: Added support for STARTTLS command. + If logging data is generated faster than it can be written, log a warning about it and show information about it in log process's process title in ps output. Also don't allow a single service to flood too long at the cost of delaying other services' logging. + stats: Added support for getting global statistics. + stats: Use the same session IDs as the rest of Dovecot. + stats: Plugins can now create their own statistics fields + doveadm server: Non-mail related commands can now also be used via doveadm server (TCP socket). + doveadm proxying: passdb lookup can now override doveadm_port and change the username. + doveadm: Search query supports now oldestonly parameter to stop immediately on the first non-match. This can be used to optimize: doveadm expunge mailbox Trash savedbefore 30d oldestonly + doveadm: Added save command to directly save mails to specified mailbox (bypassing Sieve). + doveadm fetch: Added body.snippet field, which returns the first 100 chars of a message without whitespace or HTML tags. The result is stored into dovecot.index.cache, so it can be fetched efficiently. + dsync: Added -t timestamp parameter to sync only mails newer than the given received-timestamp. + dsync: Added -F [-]flag parameter to sync only mails with[out] the given flag/keyword. + dsync: Added -a mailbox parameter to specify the virtual mailbox containing user's all mails. If this mailbox is already found to contain the wanted mail (by its GUID), the message is copied from there instead of being re-saved. (This isn't efficient enough yet for incremental replication.) + dsync: -m parameter can now specify \Special-use names for mailboxes. + imapc: Added imapc_features=gmail-migration to help migrations from GMail. See http://wiki2.dovecot.org/Migration/Gmail + imapc: Added imapc_features=search to support IMAP SEARCH command. (Currently requires ESEARCH support from remote server.) + expire plugin: Added expire_cache=yes setting to cache most of the database lookups in dovecot index files. + quota: If overquota-flag in userdb doesn't match the current quota usage, execute a configured script. + redis dict: Added support for expiring keys (:expire_secs=n) and specifying the database number (:db=n) - auth: Don't crash if master user login is attempted without any configured master=yes passdbs - Parsing UTF-8 text for mails could have caused broken results sometimes if buffering was split in the middle of a UTF-8 character. This affected at least searching messages. - String sanitization for some logged output wasn't done properly: UTF-8 text could have been truncated wrongly or the truncation may not have happened at all. - fts-lucene: Lookups from virtual mailbox consisting of over 32 physical mailboxes could have caused crashes.
Re: v2.2.16 released
For this no man-page available. Am 12.03.2015 um 18:30 schrieb Timo Sirainen: + doveadm: Added save command to directly save mails to specified mailbox (bypassing Sieve).
looks like a repeat of this problem
http://permalink.gmane.org/gmane.mail.imap.dovecot/80062
How to detect out-of-sync condition
Hello list, I recently had a user whose mailbox had gone out of sync. Webmail and client inbox totals had become vastly different and response times had become unacceptable. A doveadm force-resync fixed the problem nicely. This will no doubt happen again as we grow the service and I would like to have some type of indication at the server level so I can run a resync on a per-user basis as required. However, I don't know what to look for. I did not see any signs of the problem on the server - but perhaps I did not know what to look for. The only other alternative is for me to do a global resync in the cron.daily but my fear is that this won't scale well for thousands of users. Please advise. Thanks in advance.
indexer-worker panics with latest mercurial
Hi. I am seeing the following in my logs. Happy to downgrade to an earlier version if you think this might be the problem, but dovecot.org is extremely slow (and has been for months) so I found it easier just to pull the latest from mercurial. Thanks. Laeeth Mar 12 20:48:39 indexer: Error: Indexer worker disconnected, discarding 1 reques ts for lae...@laeeth.com Mar 12 20:48:39 indexer-worker(lae...@laeeth.com): Fatal: master: service(indexe r-worker): child 24003 killed with signal 6 (core dumps disabled) Mar 12 20:49:01 dsync-local(lae...@laeeth.com): Error: Couldn't lock /home/mail/ laeeth_laeeth_com/.dovecot-sync.lock: Timed out after 30 seconds Mar 12 20:49:16 indexer-worker(lae...@laeeth.com): Error: fts_tika: PUT http://l ocalhost:9997/tika/ failed: 500 Server Error Mar 12 20:49:17 indexer-worker(ro...@kaleidicassociates.com): Warning: I/O leak: 0x7fc47d60fcf0 (line 127, fd 25) Mar 12 20:49:17 indexer-worker(ro...@kaleidicassociates.com): Panic: file ioloop .c: line 39 (io_add_file): assertion failed: (callback != NULL) Mar 12 20:49:17 indexer-worker(ro...@kaleidicassociates.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x76c40) [0x7fc47d63fc40] - /usr/lib64/dovecot/libdovecot.so.0(+0x76d1e) [0x7fc47d63fd1e] - /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fc47d5f02e5] - /usr/lib64/dovecot/libdovecot.so.0(+0x87bd0) [0x7fc47d650bd0] - /usr/lib64/dovecot/libdovecot.so.0(io_loop_move_io+0x3e) [0x7fc47d65183e] - /usr/lib64/dovecot/libdovecot.so.0(connection_switch_ioloop+0x14) [0x7fc47d63db14] - /usr/lib64/dovecot/libdovecot.so.0(http_client_switch_ioloop+0x28) [0x7fc47d614448] - /usr/lib64/dovecot/libdovecot.so.0(+0x43876) [0x7fc47d60c876] - /usr/lib64/dovecot/lib21_fts_solr_plugin.so(solr_connection_post_more+0x29) [0x7fc47c733159] - /usr/lib64/dovecot/lib21_fts_solr_plugin.so(+0x3637) [0x7fc47c72f637] - /usr/lib64/dovecot/lib20_fts_plugin.so(+0x6d83) [0x7fc47cf5dd83] - /usr/lib64/dovecot/lib20_fts_plugin.so(fts_build_mail+0x614) [0x7fc47cf5e3c4] - /usr/lib64/dovecot/lib20_fts_plugin.so(+0xc14e) [0x7fc47cf6314e] - /usr/lib64/dovecot/libdovecot-storage.so.0(mail_precache+0x19) [0x7fc47d8ef429] - dovecot/indexer-worker() [0x40237c] - /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7fc47d65155c] - /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbb) [0x7fc47d65249b] - /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7fc47d6515c9] - /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fc47d651648] - /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fc47d5f5703] - dovecot/indexer-worker(main+0xcb) [0x401e7b] - /lib64/libc.so.6(__libc_start_main+0xf5) [0x32c6021d65] - dovecot/indexer-worker() [0x401f25] Mar 12 20:49:17 indexer: Error: Indexer worker disconnected, discarding 15 reque sts for ro...@kaleidicassociates.com Mar 12 20:49:17 indexer-worker(ro...@kaleidicassociates.com): Fatal: master: service(indexer-worker): child 24022 killed with signal 6 (core dumps disabled) Mar 12 20:49:17 indexer-worker(lae...@kaleidicassociates.com): Warning: I/O leak: 0x7f22c4d4dcf0 (line 127, fd 23) Mar 12 20:49:17 indexer-worker(lae...@kaleidicassociates.com): Panic: file ioloop.c: line 829 (io_loop_move_io): assertion failed: ((old_io-condition IO_NOTIFY) == 0) Mar 12 20:49:17 indexer-worker(lae...@kaleidicassociates.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x76c40) [0x7f22c4d7dc40] - /usr/lib64/dovecot/libdovecot.so.0(+0x76d1e) [0x7f22c4d7dd1e] - /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f22c4d2e2e5] - /usr/lib64/dovecot/libdovecot.so.0(+0x888ba) [0x7f22c4d8f8ba] - /usr/lib64/dovecot/libdovecot.so.0(connection_switch_ioloop+0x14) [0x7f22c4d7bb14] - /usr/lib64/dovecot/libdovecot.so.0(http_client_switch_ioloop+0x28) [0x7f22c4d52448] - /usr/lib64/dovecot/libdovecot.so.0(+0x43876) [0x7f22c4d4a876] - /usr/lib64/dovecot/lib21_fts_solr_plugin.so(solr_connection_post_more+0x29) [0x7f22c3e71159] - /usr/lib64/dovecot/lib21_fts_solr_plugin.so(+0x3637) [0x7f22c3e6d637] - /usr/lib64/dovecot/lib20_fts_plugin.so(+0x6d83) [0x7f22c469bd83] - /usr/lib64/dovecot/lib20_fts_plugin.so(fts_build_mail+0x123) [0x7f22c469bed3] - /usr/lib64/dovecot/lib20_fts_plugin.so(+0xc14e) [0x7f22c46a114e] - /usr/lib64/dovecot/libdovecot-storage.so.0(mail_precache+0x19) [0x7f22c502d429] - dovecot/indexer-worker() [0x40237c] - /usr/lib64/dovecot/libdovecot.so.0(io _loop_call_io+0x4c) [0x7f22c4d8f55c] - /usr/lib64/dovecot/libdovecot.s o.0(io_loop_handler_run_internal+0xbb) [0x7f22c4d9049b] - /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7f22c4d8f5c9] - /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f22c4d8f648] - /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f22c4d33703] - dovecot/indexer-worker(main+0xcb) [0x401e7b] - /lib64/libc.so.6(__libc_start_main+0xf5) [0x32c6021d65] - dovecot/indexer-worker() [0x401f25]
Re: v2.2.16 released
/usr/lib64/dovecot/stats/libstats_mail.so why in the world a new sub-directory containing just one so-file enforcing pakcage buildsers to change SPEC files? Am 12.03.2015 um 18:30 schrieb Timo Sirainen: http://dovecot.org/releases/2.2/dovecot-2.2.16.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.16.tar.gz.sig A few fixes and some imapc improvements since the release candidate. * dbox: Resyncing (e.g. doveadm force-resync) no longer deletes dovecot.index.cache file. The cache file was rarely the problem so this just caused unnecessary slowness. * Mailbox name limits changed during mailbox creation: Each part of a hierarchical name (e.g. x or y in x/y) can now be up to 255 chars long (instead of 200). This also reduces the max number of hierarchical levels to 16 (instead of 20) to keep the maximum name length 4096 (a common PATH_MAX limit). The 255 char limit is hopefully large enough for migrations from all existing systems. It's also the limit on many filesystems. + director: Added director_consistent_hashing setting to enable consistent hashing (instead of the mostly-random MD5 hashing). This causes fewer user moves between backends when backend counts are changed, which may improve performance (mainly due to caching). + director: Added support for tags, which allows one director ring to serve multiple backend clusters with different sets of users. + LMTP server: Added lmtp_user_concurrency_limit setting to limit how many LMTP deliveries can be done concurrently for a single user. + LMTP server: Added support for STARTTLS command. + If logging data is generated faster than it can be written, log a warning about it and show information about it in log process's process title in ps output. Also don't allow a single service to flood too long at the cost of delaying other services' logging. + stats: Added support for getting global statistics. + stats: Use the same session IDs as the rest of Dovecot. + stats: Plugins can now create their own statistics fields + doveadm server: Non-mail related commands can now also be used via doveadm server (TCP socket). + doveadm proxying: passdb lookup can now override doveadm_port and change the username. + doveadm: Search query supports now oldestonly parameter to stop immediately on the first non-match. This can be used to optimize: doveadm expunge mailbox Trash savedbefore 30d oldestonly + doveadm: Added save command to directly save mails to specified mailbox (bypassing Sieve). + doveadm fetch: Added body.snippet field, which returns the first 100 chars of a message without whitespace or HTML tags. The result is stored into dovecot.index.cache, so it can be fetched efficiently. + dsync: Added -t timestamp parameter to sync only mails newer than the given received-timestamp. + dsync: Added -F [-]flag parameter to sync only mails with[out] the given flag/keyword. + dsync: Added -a mailbox parameter to specify the virtual mailbox containing user's all mails. If this mailbox is already found to contain the wanted mail (by its GUID), the message is copied from there instead of being re-saved. (This isn't efficient enough yet for incremental replication.) + dsync: -m parameter can now specify \Special-use names for mailboxes. + imapc: Added imapc_features=gmail-migration to help migrations from GMail. See http://wiki2.dovecot.org/Migration/Gmail + imapc: Added imapc_features=search to support IMAP SEARCH command. (Currently requires ESEARCH support from remote server.) + expire plugin: Added expire_cache=yes setting to cache most of the database lookups in dovecot index files. + quota: If overquota-flag in userdb doesn't match the current quota usage, execute a configured script. + redis dict: Added support for expiring keys (:expire_secs=n) and specifying the database number (:db=n) - auth: Don't crash if master user login is attempted without any configured master=yes passdbs - Parsing UTF-8 text for mails could have caused broken results sometimes if buffering was split in the middle of a UTF-8 character. This affected at least searching messages. - String sanitization for some logged output wasn't done properly: UTF-8 text could have been truncated wrongly or the truncation may not have happened at all. - fts-lucene: Lookups from virtual mailbox consisting of over 32 physical mailboxes could have caused crashes. signature.asc Description:
Re: doveconf -a Segmentation Fault
On 03/12/2015 02:07 PM, Dan LaSota wrote: Getting Segmentation Fault When I run doveconf -a Have a look at http://dovecot.org/bugreport.html and try again. Regards, Pascal -- The trapper recommends today: f007ba11.1507...@localdomain.org
Re: Why is Sieve trying to re-compile global scripts?
On 3/12/2015 11:56 AM, Olaf Hopp wrote: On 03/12/2015 12:02 AM, Stephan Bosch wrote: On 3/11/2015 11:10 AM, Olaf Hopp wrote: Please see the thread with subject Sieve permissions issue following update I tested sucessfully a developper issue last month on the hint of Stephan. Yesterday I started to test the currenr RCs. First I was disappointed, because the error seems to persist. So I double checked everything, recreated / recompiled everything an the error went away. So I thought it was mistake on my side. I gave Spephan postive feedback. And I'm waiting for the final release for my production server. But when I read your mails, I'm not feeling happy. I think it's a kink of luck/voodoo/whatever. What you must do, I think, is to compile the sieve script with the exact version running afterwards. And I think you should the remove the compiled .svbin files before recreating them again. Don't overwrite them with the compiler. I think I'll also dig into this any further today. Please do. I cannot reproduce this so far. Since E.B. still got an obscure debug message about metadata not being up to date, I added debug lines to the remaining places where this could emerge (currently only available from hg). Regards, Stephan. Hi, I'm still trying but currently I can not reproduce the bug. But I will keep on hammering on it. Looks like I found the bug. Will need some time to fix this properly. Regards, Stephan.
location of dovecot.rawlog-directory
How is it possible to have the dovecot.rawlog-directory outside the mail_location? A link to another directory is not because it is checked in rawlog.c S_ISDIR to directory.
Re: How to detect out-of-sync condition
Cliff Hayes cha...@afo.net writes: I recently had a user whose mailbox had gone out of sync. Webmail and client inbox totals had become vastly different and response times had become unacceptable. A doveadm force-resync fixed the problem nicely. This will no doubt happen again as we grow the service and I would like to have some type of indication at the server level so I can run a resync on a per-user basis as required. Perhaps what you ought to look for is how are they getting out of sync in the first place. Assuming your webmail is a IMAP/POP client, I would look at ways that your user's INBOX can be modified out of Dovecot's sight. For example, does your LDA use dovecot's lda/lmtp, or do your users run mail clients that directly manipulate mailbox files, or do you use procmail/mail filters? By closing off other avenues other than dovecot imap/pop/lda/etc., the indices will stay sync'd. If you really have to do manual resyncing, comparing index/mailbox mtimes might be one way to do it. Joseph Tam jtam.h...@gmail.com
Re: doveconf -a Segmentation Fault
I will try. thanks. Dan LaSota Instructional Designer, UAF eLearning (907) 451-4067 dan.las...@alaska.edu http://elearning.uaf.edu On Mar 12, 2015, at 5:34 PM, Pascal Volk user+dove...@localhost.localdomain.org wrote: On 03/12/2015 02:07 PM, Dan LaSota wrote: Getting Segmentation Fault When I run doveconf -a Have a look at http://dovecot.org/bugreport.html and try again. Regards, Pascal -- The trapper recommends today: f007ba11.1507...@localdomain.org
Re: Released Pigeonhole v0.4.7.rc1 for Dovecot v2.2.16.rc1
On 10/03/15 11:40, Timo Sirainen wrote: I think it's pure chance that it happens to crash that way. I don't see how the duplicate checking could have affected this crash. Oh! Do you mean Timo, that Computer Science is non-deterministic! Is there chance, therefore luck, to it? Just kidding! Thanks for all the the good work you and your associates are doing. For us in the education sector and with dwindling money supplies you are a life saver. Thanks. Andreas -- Andreas Kasenides Senior IT Officer Dept. of Computer Science, University of Cyprus Tel: 22892714, Fax: 22892701 (5B4ANK)
Re: Why is Sieve trying to re-compile global scripts?
On 03/11/2015 07:17 AM, E.B. wrote: Might be unpredictable caching. Might be the error didn't go away last time I recreated due to different methods of creating the files. Who knows, I think I should give up and stop spamming the list with uneducated guesswork. No - no spam at least for me. Please see the thread with subject Sieve permissions issue following update I tested sucessfully a developper issue last month on the hint of Stephan. Yesterday I started to test the currenr RCs. First I was disappointed, because the error seems to persist. So I double checked everything, recreated / recompiled everything an the error went away. So I thought it was mistake on my side. I gave Spephan postive feedback. And I'm waiting for the final release for my production server. But when I read your mails, I'm not feeling happy. I think it's a kink of luck/voodoo/whatever. What you must do, I think, is to compile the sieve script with the exact version running afterwards. And I think you should the remove the compiled .svbin files before recreating them again. Don't overwrite them with the compiler. I think I'll also dig into this any further today. Olaf -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: olaf.h...@kit.edu atis.informatik.kit.edu www.kit.edu KIT - Universität des Landes Baden-Württemberg und nationales Forschungszentrum in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert. smime.p7s Description: S/MIME Cryptographic Signature
