Sieve duplicate detection
Good day, Gents. We are running: dovecot 1.2.17 dovecot-1.2-sieve-0.1.19 dovecot-1.2-managesieve-0.11.13 postfix 2.4.3 on OS X 10.5.8 server. Only about 15 users access the server. No problems. My question is... what would I have to upgrade, and to what version, in order to take advantage of pigeonhole sieve's duplicate detection (vnd.dovecot.duplicate) functionality? Thank you very much. Bruce
Re: [Dovecot] v1.2.16 released
On Nov 15, 2010, at 1:41 AM, Stephan Bosch wrote: On 11/15/2010 2:17 AM, Bruce Bodger wrote: On Nov 11, 2010, at 2:11 PM, Stephan Bosch wrote: Refreshed the ManageSieve patch: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.16-managesieve-0.11.12.diff.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.16-managesieve-0.11.12.diff.gz.sig Hello, Stephan, Perhaps some of us need a new sieve version for compatibility w/ Dovecot 1.2.16 ? :-) What do you mean? I get this when I compile and run Dovecot 1.2.16 while still using dovecot-1.2-sieve-0.1.18: Nov 14 15:44:42 server dovecot[37024]: deliver(jjohnson): Module is for different version 1.2.15: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Nov 14 15:44:42 server dovecot[37024]: deliver(jjohnson): Fatal: Couldn't load required plugins I presume I would need a version of sieve specifically for Dovecot 1.2.16. Didn't you add some version checking a few months ago? Thank you, B. Bodger
Re: [Dovecot] v1.2.16 released
On Nov 15, 2010, at 6:53 AM, Timo Sirainen wrote: Nov 14 15:44:42 server dovecot[37024]: deliver(jjohnson): Module is for different version 1.2.15: /usr/local/lib/dovecot/lda/ lib90_sieve_plugin.so Nov 14 15:44:42 server dovecot[37024]: deliver(jjohnson): Fatal: Couldn't load required plugins I presume I would need a version of sieve specifically for Dovecot 1.2.16. Didn't you add some version checking a few months ago? You just need to recompile. I did that however I did not do a 'make clean' first. Once I did, and then recompiled, all is well. Thanks to you and Stephan. B. Bodger
Re: [Dovecot] v1.2.16 released
On Nov 11, 2010, at 2:11 PM, Stephan Bosch wrote: Refreshed the ManageSieve patch: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.16-managesieve-0.11.12.diff.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.16-managesieve-0.11.12.diff.gz.sig Hello, Stephan, Perhaps some of us need a new sieve version for compatibility w/ Dovecot 1.2.16 ? :-) Thank you, B. Bodger
Re: [Dovecot] Released Pigeonhole Sieve v0.1.15 and ManageSieve v0.11.11 for Dovecot v1.2.10
On Jan 25, 2010, at 5:03 AM, Stephan Bosch wrote: The releases are available as follows: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.15.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2- sieve-0.1.15.tar.gz.sig First time I ever received an error when compiling dovecot sieve from you... ld: duplicate symbol _act_notify_old in .libs/lib90_sieve_plugin.lax/ libsieve.a/ext-notify-common.o and .libs/lib90_sieve_plugin.lax/ libsieve.a/cmd-denotify.o collect2: ld returned 1 exit status make[4]: *** [lib90_sieve_plugin.la] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Let me know if you need to see anything else, Stephan. B. Bodger Oklahoma City, OK
Re: [Dovecot] Released Pigeonhole Sieve v0.1.15 and ManageSieve v0.11.11 for Dovecot v1.2.10
On Jan 25, 2010, at 2:16 PM, Stephan Bosch wrote: Sigh.. not again. I forgot extern at various occasions (and possibly even more): http://hg.rename-it.nl/dovecot-1.2-sieve/rev/fe0b2ff50326 Why doesn't GCC warn about this? I usually only find out when people like you report compile failures. What compiler are you using? Can apply the above change and try again.. Much better! Thank you. Compiling with gcc version 4.0.1 (Apple Inc. build 5493) Thank you very much. B. Bodger Oklahoma City, OK
Re: [Dovecot] Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8
On Nov 25, 2009, at 4:51 PM, Stephan Bosch wrote: Hello Dovecot users, I am getting closer to new releases for Sieve and ManageSieve for Dovecot v1.2.8. However, the release for Sieve includes a large restructuring of the sources to improve extension handling and to remove global state. That is why I first provide a few pre-releases for you to check first: Sieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz.sig Feel free to test these release candidates and please notify me when you incur any problems. The real releases will follow this weekend. Stephen, How are you doing regarding the real releases, specifically dovecot-1.2-sieve-0.1.14 ? The pre release is/was a bit confusing as it contains a dovecot-1.2-sieve-0.1.13 folder within the dovecot-1.2- sieve-0.1.14pre.tar.gz archive. Thank you, Bruce
Re: [Dovecot] Index file (date timestamp) issue on OS X 10.6.2 Server
On Nov 13, 2009, at 2:15 PM, Darren Latter wrote: Volumes of emails arriving - hits either server, some will be correctly received with date/time, others time stamped with 8 July 2037, 23:53 Same server could give either the correct or the 2037 timestamp. It's a long shot, but are the emails that contain the errant date/time stamp being created by any php mail routine? We ask because we've seen similar issues with dates from a PEAR/Date library that's not php v5.3 compliant. B. Bodger
Re: [Dovecot] compiling issue 1.2.6 - Solaris
On Oct 6, 2009, at 3:55 AM, Jernej Porenta wrote: I am expiriencing compiling issues on Solaris 8 and Solaris 10 boxes with dovecot 1.2.6. On Solaris 8 the compiler is gcc 64bit 3.2.2, on Solaris 10 gcc 3.4.3. Same type of problem here on OS X 10.5.8 Server. Command line to configure: ./configure --with-ssldir=/System/Library/ OpenSSL --with-ssl=openssl .. Undefined symbols: _SSL_get_current_compression, referenced from: _ssl_proxy_get_security_string in liblogin-common.a(ssl-proxy- openssl.o) _SSL_COMP_get_name, referenced from: _ssl_proxy_get_security_string in liblogin-common.a(ssl-proxy- openssl.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[3]: *** [imap-login] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Please let me know if you need any more information. Thank you, B. Bodger
Re: [Dovecot] compiling issue 1.2.6 - Solaris
On Oct 6, 2009, at 8:26 AM, Bruce Bodger wrote: Same type of problem here on OS X 10.5.8 Server. Command line to configure: ./configure --with-ssldir=/System/ Library/OpenSSL --with-ssl=openssl .. Undefined symbols: _SSL_get_current_compression, referenced from: _ssl_proxy_get_security_string in liblogin-common.a(ssl-proxy- openssl.o) _SSL_COMP_get_name, referenced from: _ssl_proxy_get_security_string in liblogin-common.a(ssl-proxy- openssl.o) What OpenSSL version do you have? I thought those compression functions were new enough that everyone would have them by now.. bash-3.2# /usr/bin/OpenSSL version OpenSSL 0.9.7l 28 Sep 2006 A bit of oddity I just discovered by viewing source code at http://www.opensource.apple.com/ OS X 10.5.8 - OpenSSL 0.9.7l 28 Sep 2006 OS X 10.6.0 - OpenSSL 0.9.6l 04 Nov 2003 OS X 10.6.1 - OpenSSL 0.9.6l 04 Nov 2003 Looks like they moved back to 0.96l in later versions. B. Bodger
Re: [Dovecot] connect to IMAP
On Aug 7, 2009, at 2:38 AM, jolan D wrote: Dovecot IMAP/POP3 Server Version 1.0.7 Jolan, You're running a version many months behind current release. The 1 series is at 1.1.18 and the 2 series is at 1.2.2. It would be quite irrelevant for us to try to troubleshoot problems that you're having with antiquated code. Strongly suggest that you upgrade as your first step in self-troubleshooting. Respectfully, B. Bodger
Re: [Dovecot] v1.2.1 released
Timo, On Jul 9, 2009, at 10:00 PM, Timo Sirainen wrote: http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz.sig I was a bit surprised to see these in the log this morning after upgrading from 1.2.0 to 1.2.1 7/10/09 7:21:17 AM dovecot[67884] deliver(llyles): Rebuilding index file /Users/llyles/Maildir/dovecot.index: CPU architecture changed [..] 7/10/09 7:30:15 AM dovecot[67951] deliver(gzinkus): Rebuilding index file /Users/gzinkus/Maildir/dovecot.index: CPU architecture changed [..] 7/10/09 7:52:36 AM dovecot[67038] IMAP(gzinkus): Rebuilding index file /Users/gzinkus/Maildir/.Sent Messages/dovecot.index: CPU architecture changed I also saw them when I recently upgraded from 1.1.16 to 1.2.0 and simultaneously switched to a new server (FROM PowerPC to Intel Mac Pro) but didn't expect to see them when simply upgrading to 1.2.1. Do they have any relevance? Thanks, B. Bodger
Re: [Dovecot] v1.2.1 released
On Jul 10, 2009, at 10:47 AM, Timo Sirainen wrote: I also saw them when I recently upgraded from 1.1.16 to 1.2.0 and simultaneously switched to a new server (FROM PowerPC to Intel Mac Pro) but didn't expect to see them when simply upgrading to 1.2.1. Maybe those mailboxes just hadn't been opened since the PPC - Intel change? That's not the case. They had been opened. No big deal: everything is working famously. Just a curiosity. Thank you. B. Bodger
Re: [Dovecot] Login processes in Dovecot
On Jun 8, 2009, at 2:47 PM, Scott Haneda wrote: I will be deploying Dovecot on OS X shortly. I am looking for clarification on the limits imposed by OS X and sysctl [kern.maxproc]. I understand that it is defaulting to 532, but can be raised to 2500. I believe the OS uses around 100 or so, plus I will have other processes and shells at times. Which version of OS X? 10.4 or 10.5 ? Server or client ? It matters. B. Bodger
Re: [Dovecot] Login processes in Dovecot
On Jun 8, 2009, at 3:35 PM, Scott Haneda wrote: I will be deploying Dovecot on OS X shortly. I am looking for clarification on the limits imposed by OS X and sysctl [kern.maxproc]. I understand that it is defaulting to 532, but can be raised to 2500. I believe the OS uses around 100 or so, plus I will have other processes and shells at times. Which version of OS X? 10.4 or 10.5 ? Server or client ? It matters. My current target for deployment is a Dual 2.0 PPC G5, running OS X 10.5 client. Thank you. From http://www.postfix.org/TUNING_README.html#proc_limit I would presume relevant to Dovecot as well: === Tuning the number of processes on the system MacOS X will run out of process slots when you increase Postfix process limits. The following works with OSX 10.4 and OSX 10.5. MacOS X kernel parameters can be specified in /etc/sysctl.conf. /etc/sysctl.conf: kern.maxproc=2048 kern.maxprocperuid=2048 Unfortunately these can't simply be set on the fly with sysctl -w. You also have to set the following in /etc/launchd.conf so that the root user after boot will have the right process limit (2048). Otherwise you have to always run ulimit -u 2048 as root, then start a user shell, and then start processes for things to take effect. /etc/launchd.conf: limit maxproc 2048 Once these are in place, reboot the system. After that, the limits will stay in place. Hope it helps, B. Bodger
Re: [Dovecot] Login processes in Dovecot
On Jun 8, 2009, at 4:17 PM, Scott Haneda wrote: Thanks, I have been looking at those adjustments. My concern, is that if Dovecot uses a process per imap or pop connection, 2048 is not nearly enough for any significant email system. There are several parameters in dovecot.conf that can be adjusted to prevent the problem that you're concerned about... # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. login_process_per_connection = no # Maximum number of login processes to create. The listening process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until the limit set by # this setting is reached. login_max_processes_count = 128 [..] Search dovecot-example.conf for 'process' B. Bodger
[Dovecot] v 1.1.16 imminent?
Timo, I sense a v 1.1.16 is getting ready to hatch? True story? :-) B. Bodger
Re: [Dovecot] v 1.1.15 imminent?
On May 17, 2009, at 7:31 PM, Brad wrote: On Sunday 17 May 2009 20:27:20 Bruce Bodger wrote: Timo, I sense a v 1.1.15 is getting ready to hatch? True story? :-) B. Bodger Someone needs to learn how to count. :P Don't know what you mean? wink :-) B. Bodger
[Dovecot] Compiling dovecot-sieve-1.1.6 against dovecot-1.1.14
When attempting to compile dovecot-sieve-1.1.6 against dovecot-1.1.14 using the following command line to config... G520X2:~/Temp/dovecot-sieve-1.1.6 root# ./configure --with-dovecot=../ dovecot-1.1.14 make fails with the following... G520X2:~/Temp/dovecot-sieve-1.1.6 root# make make all-recursive Making all in src Making all in libsieve /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 - Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith - Wchar-subscripts -Wformat=2 -Wbad-function-cast -DENABLE_REGEX -o sievec sievec.o map.o imparse.o libsieve.la /Users/BB/Temp/ dovecot-1.1.14/src/lib/liblib.a gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing- declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad- function-cast -DENABLE_REGEX -o sievec sievec.o map.o imparse.o ./.libs/libsieve.a /Users/BB/Temp/dovecot-1.1.14/src/lib/ liblib.a ld: Undefined symbols: _printf$LDBLStub _snprintf$LDBLStub _sprintf$LDBLStub _fprintf$LDBLStub make[3]: *** [sievec] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 This is the top of config.log. Please let me know if you'd like to see any additional information. hostname = G520X2.xx.COM uname -m = Power Macintosh uname -r = 8.11.0 uname -s = Darwin uname -v = Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC /usr/bin/uname -p = powerpc /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = Mach kernel version: Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC Kernel configured for up to 2 processors. 2 processors are physically available. Processor type: ppc970 (PowerPC 970) Processors active: 0 1 Primary memory available: 5.00 gigabytes Thank you, B. Bodger
Re: [Dovecot] v1.1.11 released - killall crash
On Feb 3, 2009, at 5:53 PM, Timo Sirainen wrote: http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz.sig Just FYI, ONLY SINCE UPGRADING TO 1.1.11 from 1.1.10, a 'killall dovecot' yields this... Feb 5 07:59:23 G520X2 dovecot: Killed with signal 15 Feb 5 07:59:23 G520X2 dovecot: child 23439 (^?) returned error 82 (Internal logging error) Feb 5 07:59:24 G520X2 crashdump[23503]: dovecot crashed Feb 5 07:59:24 G520X2 crashdump[23503]: crash report written to: / Library/Logs/CrashReporter/dovecot.crash.log Contents of crash log... Host Name: G520X2 Date/Time: 2009-02-05 07:59:24.054 -0600 OS Version: 10.4.11 (Build 8S165) Report Version: 4 Command: dovecot Path:/usr/local/sbin/dovecot Parent: launchd [1] Version: ??? (???) PID:22087 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0018 Thread 0 Crashed: 0 0x0018 0 + 24 1 dovecot 0x4284 child_processes_deinit + 36 (child-process.c: 226) 2 dovecot 0xaaa8 main + 2504 (main.c:333) 3 dovecot 0x1d4c _start + 760 4 dovecot 0x1a50 start + 48 Thread 0 crashed with PPC Thread State 64: srr0: 0x0018 srr1: 0x10004000f030vrsave: 0x cr: 0x84004434 xer: 0x2000 lr: 0x40fc ctr: 0x0018 r0: 0x0018 r1: 0xb8d0 r2: 0x00029fbc r3: 0x00301fa0 r4: 0x5b8f r5: 0x0001 r6: 0x r7: 0x r8: 0x r9: 0x r10: 0x0002 r11: 0xa00061ec r12: 0x0018 r13: 0x0002a0f4 r14: 0x0002a0f4 r15: 0x0002a0f4 r16: 0x r17: 0x0002a0f4 r18: 0x r19: 0x0002a0f4 r20: 0x r21: 0x0001 r22: 0x r23: 0x r24: 0x0001 r25: 0x91e0 r26: 0x00301fa0 r27: 0xd5ec r28: 0x000961e8 r29: 0x00096288 r30: 0x5b8f r31: 0x3db4 Binary Images Description: 0x1000 -0x28fff dovecot /usr/local/sbin/dovecot 0x8fe0 - 0x8fe52fff dyld 46.16 /usr/lib/dyld 0x9000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib 0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/ libmathCommon.A.dylib You may remember an obscure OS X bug relative to the syslogd restart. For over a year I've been sending the 'killall' in a daily.local or else dovecot's log entries would not get written to mail.log after the syslogd gets restarted. Since I'm using the OS X launchdaemons, dovecot gets restarted after the 'killall'. Anyway, for over the year, this crash had never been written to the logs prior to last night and upgrading to 1.1.11. All continues to work fine but something has definitely changed since 1.1.10. B. Bodger
[Dovecot] Starting using LaunchDaemons
I've figured this one out... Just wanted to get it into the dovecot mailing list archive so that somebody in the future might find it if they need it. Running Dovecot on Mac OS X 10.4.11 and using LaunchDaemon to start. Following a system crash, dovecot failed to restart with this in the system log... Feb 4 10:04:29 G520X2 launchd: org.dovecot: exited with exit code: 89 Feb 4 10:04:29 G520X2 launchd: org.dovecot: respawning too quickly! throttling Feb 4 10:04:29 G520X2 launchd: org.dovecot: 7 more failures without living at least 60 seconds will cause job removal Feb 4 10:04:29 G520X2 launchd: org.dovecot: will restart in 10 seconds Feb 4 10:04:39 G520X2 launchd: org.dovecot: exited with exit code: 89 Feb 4 10:04:39 G520X2 launchd: org.dovecot: respawning too quickly! throttling Feb 4 10:04:39 G520X2 launchd: org.dovecot: 6 more failures without living at least 60 seconds will cause job removal Feb 4 10:04:39 G520X2 launchd: org.dovecot: will restart in 10 seconds Feb 4 10:04:49 G520X2 launchd: org.dovecot: exited with exit code: 89 Feb 4 10:04:49 G520X2 launchd: org.dovecot: respawning too quickly! throttling Feb 4 10:04:49 G520X2 launchd: org.dovecot: 5 more failures without living at least 60 seconds will cause job removal Feb 4 10:04:49 G520X2 launchd: org.dovecot: will restart in 10 seconds The problem turned out to be an old master.pid file (/usr/local/var/ run/dovecot/master.pid) that was left over from the crash. Deleting the file allowed dovecot to restart. Actually, dovecot told me what the problem was when I attempted to start it from the command line as opposed to starting it with the LaunchDaemon... G520X2:root# /usr/local/sbin/dovecot -F Fatal: Dovecot is already running with PID 59 (read from /usr/local/ var/run/dovecot/master.pid) Hope it helps someone else. B. Bodger
Re: [Dovecot] v1.1.10 released
On Jan 26, 2009, at 6:32 PM, Timo Sirainen wrote: http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz.sig Timo: Did you get around to modifying deliver wherein the '-e' has become default behavior... per the earlier discussion? B. Boger
Re: [Dovecot] Setting IMAP keywords/flags on delivery
On Jan 7, 2009, at 9:34 PM, Matt Doran wrote: Dovecot sieve will do exactly what you are looking for. It's described quite well in the WIKI. The operator that you're looking for is, 'setflag' We're currently using maildrop for filtering and local delivery. Do you know if there's a way to integrate the two? I'd prefer not to burden the list with this, but we highly recommend a product called MPP (Message Processing Platform) which not only provides a myriad of filtering and archiving features on its own but it also acts / can act as your interface to spam and virus detectors. You may check it out here http://www.raeinternet.com/category/mpp/mpp-home/ We've been using it for years: the support staff is terrific. 'nuff said in this forum about it. Good luck, Bruce
[Dovecot] Parameters to pass to configure - Mac OS X
Timo, Many months back you recommend that, when compiling on Mac OS X systems, that we pass the '--with-notify=kqueue' swith to 'configure'. For many, many months we've been configuring using this command... ./configure --with-ssldir=/System/Library/OpenSSL --with-ssl=openssl --with-notify=kqueue ...and all has been well. Do you still consider that the appropriate command line for OS X systems? Thank you, B. Bodger
Re: [Dovecot] Parameters to pass to configure - Mac OS X
On 1/7/09 3:02 PM, Timo Sirainen wrote: Do you still consider that the appropriate command line for OS X systems? It's not necessary since it's used by default anyway (verify that it says File change notification method .. kqueue after configure). It did indeed. Thank you. I just compiled 1.1.8. Should there be any concern regarding these errors in config.log... configure:8771: checking how to run the C++ preprocessor configure:8807: g++ -E conftest.cpp configure:8813: $? = 0 configure:8844: g++ -E conftest.cpp conftest.cpp:21:28: error: ac_nonexistent.h: No such file or directory configure:8850: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME dovecot | #define PACKAGE_TARNAME dovecot | #define PACKAGE_VERSION 1.1.8 | #define PACKAGE_STRING dovecot 1.1.8 | #define PACKAGE_BUGREPORT dovecot@dovecot.org | #define PACKAGE dovecot | #define VERSION 1.1.8 AND configure:16884: checking how to link with libiconv configure:16886: result: -liconv configure:16897: checking for iconv declaration configure:16936: gcc -c -g -O2 conftest.c 5 conftest.c:31: error: conflicting types for 'libiconv' /usr/include/iconv.h:82: error: previous declaration of 'libiconv' was here configure:16942: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME dovecot | #define PACKAGE_TARNAME dovecot | #define PACKAGE_VERSION 1.1.8 | #define PACKAGE_STRING dovecot 1.1.8 AND configure:21053: checking for uoff_t configure:21083: gcc -c -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-ca st -Wstrict-aliasing=2 conftest.c 5 conftest.c:105: error: parse error before 'ac__type_new_' conftest.c:105: warning: type defaults to 'int' in declaration of 'ac__type_new_' conftest.c:105: warning: data definition has no type or storage class conftest.c: In function 'main': conftest.c:109: error: parse error before ')' token AND quite a few others pointing to confdefs.h Thank you, B. Bodger
Re: [Dovecot] Setting IMAP keywords/flags on delivery
On Wed, January 7, 2009 8:24 pm, Matt Doran wrote: I'd like to be able to set this flag/keyword when the mail is delivered to the inbox, on the server side. Dovecot sieve will do exactly what you are looking for. It's described quite well in the WIKI. The operator that you're looking for is, 'setflag'. B. Bodger Oklahoma City, OK
Re: [Dovecot] Source patches from Apple
On Dec 13, 2008, at 9:07 AM, Charles Marcus wrote: On 12/13/2008, mouss (mo...@netoyen.net) wrote: Wow.. I can't imagine NOT running a mail server without a firewall... Different strokes for different folks I guess... :) He said _ON_ my mail server. he didn't say that he doesn't have a firewall between the mail server and the jungle notwork ;-P I know... but I believe in layered security. I run a firewall in front of the mail (or other) server, but I also run one ON the mail (or other) server... ;-p It's not like it costs anything extra :) May I suggest you'all change the subject of your (new) thread. Many of us are anxious to stay abreast of the Apple patch discussion and you're taking it far afield. Thank you, B. Bodger
[Dovecot] auth failed, 0 attempts
Does anyone have any ideas what this may be? Aug 25 12:19:01 G520X2 dovecot: imap-login: Disconnected (auth failed, 0 attempts): rip=192.168.1.1, lip=192.168.1.10 Aug 25 12:19:01 G520X2 dovecot: imap-login: Disconnected (auth failed, 0 attempts): rip=192.168.1.1, lip=192.168.1.10 Hits the server every minute. Running v 1.1.2 on OS X 192.168.1.1 is the router 192.168.1.10 is the server on which dovecot is running. Just started noticing it. Thanks, B. Bodger
Re: [Dovecot] auth failed, 0 attempts RESOLVED
On Aug 25, 2008, at 1:23 PM, Bruce Bodger wrote: Does anyone have any ideas what this may be? Aug 25 12:19:01 G520X2 dovecot: imap-login: Disconnected (auth failed, 0 attempts): rip=192.168.1.1, lip=192.168.1.10 Aug 25 12:19:01 G520X2 dovecot: imap-login: Disconnected (auth failed, 0 attempts): rip=192.168.1.1, lip=192.168.1.10 Figured it out. Some user had inadvertently removed their password from their mail setup. Sorry for the noise. B. Bodger New York
Re: [Dovecot] POP3 dictionary attacks
On Aug 15, 2008, at 5:39 PM, Charles Marcus wrote: You're kidding, right? Dictionary attacks are a fact of life these days. Just install some kind of blocking on your firewall (fail2ban is a good one), and let it take care of the worst of it... fail2ban will not work for this as the incoming ip addresses are spoofed. fail2ban would end up blocking legitimate servers. B. Bodger
Re: [Dovecot] Install from source of dovecot 1.1.2
On Aug 10, 2008, at 12:50 PM, John and Catherine Allen wrote: Guy wrote: I have what I'm sure is a stupid question. I'm trying to install Dovecot 1.1.2 from source and my command sequence is this: cd dovecot-1.1.2 ./configure --prefix=/usr --exec-prefix=/usr --with-mysql --with-storagesmaildir --sysconfdir=/etc/dovecot make make install cd ../dovecot-sieve-1.1.5 ./configure --with-dovecot=../dovecot-1.1.2 make make install It is recommended to use... 'sudo make install' ...in both places. B. Bodger
Re: [Dovecot] v1.1.2 released - OK TO INSTALL?
On Jul 27, 2008, at 12:41 PM, Ralf Hildebrandt wrote: * Bruce Bodger [EMAIL PROTECTED]: Timo, Is this safe to install? The reason that I ask, I read a few reports of problems immediately after your announcement and haven't seen your responses to them. It's giving me less odd warnings in the log than 1.1.1 :) Count that as a yes. Took your advice, Ralf. All is well so far. Running on OS X 10.4.11 Thank you.
Re: [Dovecot] Sort IDs broken
On 6/26/08 2:35 PM, Timo Sirainen wrote: Jun 24 15:03:50 G518X2 dovecot: IMAP(jjohnson): Sort IDs 4 broken in mailbox INBOX, reseting Bug, fixed: http://hg.dovecot.org/dovecot-1.1/rev/7c261c14fe7d Anyway it's transparent to users, so not that big of a deal. Yes, of course... but we do know how you aim for perfection! :-) B. Bodger
[Dovecot] (no subject)
Timo, Running v1.1.1 on OS X. What is dovecot trying to tell me here? Jun 24 15:03:50 G518X2 dovecot: IMAP(jjohnson): Sort IDs 4 broken in mailbox INBOX, reseting Thank you! G518X2:~ root# dovecot -n # 1.1.1: /usr/local/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 768). Either grow the limit or change login_max_processes_count and max_mail_processes settings protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_process_per_connection: no mail_max_userip_connections(default): 25 mail_max_userip_connections(imap): 25 mail_max_userip_connections(pop3): 10 first_valid_uid: 490 mail_access_groups: mail mail_location: maildir:~/Maildir mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): mail_log mail_plugins(imap): mail_log mail_plugins(pop3): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_log_max_lines_per_sec: 0 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: Public/ location: maildir:/var/mail/shared:CONTROL=~/Maildir/control/ public:INDEX=~/Maildir/index/public list: yes subscriptions: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd Thank you! B. Bodger
Re: [Dovecot] v1.1.rc10 released
On Jun 13, 2008, at 7:02 AM, Dan Horák wrote: Just for info - release 1.1.rc10 builds successfully on Fedora Rawhide on all 4 architectures. Also compiles successfully on OS X 10.4.11 using... ./configure --with-ssldir=/System/Library/OpenSSL --with-ssl=openssl --with-notify=kqueue ...as always. B. Bodger
Re: [Dovecot] Time moved backwards
On 5/13/08 3:33 PM, Scott Silva wrote: This would be a good case for running ntpdate on startup at least on the ntp server. Just point it to a reliable outside server. AFAIR RedHat and clones do this in the init script for ntpd. ...and how much more TIME shall we spend rechewing this non-dovecot issue ? B. Bodger
Re: [Dovecot] Help! OT: Blackberry IMAP client suggestions/experience needed
On Mar 13, 2008, at 12:17 PM, Stewart Dean wrote: The CFO of our college, a most formidable man, had decided to go Blackberry and Something Functional Must Be Done. We've had some users who we've not supported (and things got better for them when we switched from UWIMAP to Dovecot). Probably not what you want to hear, but we scrapped our BB's in favor of iPhone's and haven't had a bit of mail trouble since. IPhones seem to love Dovecot. Maybe buy one and let your CFO play with it for a day or two. He'll make your decision for you :-) B. Bodger New York, NY
Re: [Dovecot] v1.1.rc2 released
On Mar 9, 2008, at 4:36 AM, Timo Sirainen wrote: Fixed: http://hg.dovecot.org/dovecot-1.1/rev/85934050fdbd I also did a related http://hg.dovecot.org/dovecot-1.1/rev/ 2bef36355718 change.. I guess I'll release rc3 soon, and a few days after that if everything seems to work yet another v1.0 with the same changes.. I applied the patches (in fact, downloaded the entire new file). Ran 'make clean', './configure --with-ssldir=/System/Library/OpenSSL --with-ssl=openssl --with-notify=kqueue', 'make', 'sudo make install' ...and still get... G518X2:~/Temp/dovecot-1.1.rc2 root# dovecot -F Fsetregid(65534,6) failed with euid=0: Operation not permitted Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /usr/local/etc/dovecot.conf
Re: [Dovecot] v1.1.rc2 released
On Mar 9, 2008, at 7:46 AM, Timo Sirainen wrote: G518X2:~/Temp/dovecot-1.1.rc2 root# dovecot -F Fsetregid(65534,6) failed with euid=0: Operation not permitted And this happens with rc3 too? It's working in my Leopard at least.. I don't see why setregid() would fail since it's still running as root (euid=0). Maybe this is a Tiger-problem that's been fixed since. Try switching mail_drop_priv_before_exec setting? It might help, or maybe not. Just compiled and installed rc3. Tried with and without mail_drop_priv_before_exec setting. Still get... G518X2:~/Temp/dovecot-1.1.rc3 root# dovecot -F Fsetregid(65534,6) failed with euid=0: Operation not permitted Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /usr/local/etc/dovecot.conf Relevant portion of dovecot.conf: # Group to enable temporarily for privileged operations. Currently this is # used only for creating mbox dotlock files when creation fails for INBOX. # Typically this is set to mail to give access to /var/mail. mail_privileged_group = mail # Grant access to these supplementary groups for mail processes. Typically # these are used to set up access to shared mailboxes. Note that it may be # dangerous to set these if users can create symlinks (e.g. if mail group is # set here, ln -s /var/mail ~/mail/var could allow a user to delete others' # mailboxes, or ln -s /secret/shared/box ~/mail/mybox would allow reading it). #mail_access_groups = mail B. Bodger New York, NY
Re: [Dovecot] v1.1.rc2 released
On Mar 9, 2008, at 8:08 AM, Timo Sirainen wrote: Could it be that 65534 is the problem? I remember there was before some problems with that. What happens if you temporarily try without mail_plugins? dump-capability isn't run then and Dovecot starts, but does this same error happen when a user logs in? Disabled all mail_plugins... had been running mail_plugins = mail_log mail_plugin_dir = /usr/local/lib/dovecot/imap and mail_plugins = cmusieve mail_plugin_dir = /usr/local/lib/dovecot/lda Set mail_privileged_group = mail and #mail_access_groups = mail Appears to start ok but then when user logs in... from mail.log... Mar 9 08:18:48 G518X2 dovecot: Killed with signal 15 Mar 9 08:18:52 G518X2 dovecot: Dovecot v1.1.rc3 starting up Mar 9 08:19:26 G518X2 dovecot: imap-login: Login: user=bb, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Mar 9 08:19:26 G518X2 dovecot: Fatal: IMAP(bb): setregid(501,6) failed with euid=0: Operation not permitted Mar 9 08:19:26 G518X2 dovecot: imap-login: Login: user=bb, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Mar 9 08:19:26 G518X2 dovecot: Fatal: IMAP(bb): setregid(501,6) failed with euid=0: Operation not permitted Mar 9 08:19:26 G518X2 dovecot: imap-login: Login: user=bb, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Mar 9 08:19:26 G518X2 dovecot: Fatal: IMAP(bb): setregid(501,6) failed with euid=0: Operation not permitted
Re: [Dovecot] v1.1.rc2 released
On Mar 7, 2008, at 11:33 PM, Jeff Grossman wrote: Here is my dovecot -n (without the squat entries): # 1.1.rc2: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ Jeff, I've noticed that you've been having a few issues that might appear to be OS X related. We've been running Dovecot here on OS X (now 10.4.11) for a real long time and thought we'd share our trouble-free configuration with you. Bear in mind that we service only a very few users. Hope it helps. B. Bodger New York, NY We configure with this command line: ./configure --with-ssldir=/System/Library/OpenSSL --with-ssl=openssl --with-notify=kqueue After installing today's v1.1.rc2, here's the output of our dovecot -n # 1.1.rc2: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_process_per_connection: no mail_max_userip_connections(default): 25 mail_max_userip_connections(imap): 25 mail_max_userip_connections(pop3): 10 first_valid_uid: 490 mail_location: maildir:~/Maildir mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): mail_log mail_plugins(imap): mail_log mail_plugins(pop3): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_log_max_lines_per_sec: 0 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: Public/ location: maildir:/var/mail/shared:CONTROL=~/Maildir/control/ public:INDEX=~/Maildir/index/public list: yes subscriptions: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd
Re: [Dovecot] v1.1.rc2 released
On Mar 7, 2008, at 11:10 PM, Timo Sirainen wrote: http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz.sig Changes since rc1: * mail_extra_groups setting was commonly used insecurely. This setting is now deprecated. Most users should switch to using mail_privileged_group setting, but if you really need the old functionality use mail_access_groups instead. Timo, When I set... mail_privileged_group = mail ...dovecot refuses to start. We are NOT using mbox here, only Maildir. mail_access_groups = mailworks as before just fine. Output of working 'dovecot -n' (with mail_access_groups set as above) # 1.1.rc2: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_process_per_connection: no mail_max_userip_connections(default): 25 mail_max_userip_connections(imap): 25 mail_max_userip_connections(pop3): 10 first_valid_uid: 490 mail_access_groups: mail mail_location: maildir:~/Maildir mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): mail_log mail_plugins(imap): mail_log mail_plugins(pop3): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_log_max_lines_per_sec: 0 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: Public/ location: maildir:/var/mail/shared:CONTROL=~/Maildir/control/ public:INDEX=~/Maildir/index/public list: yes subscriptions: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd
Re: [Dovecot] v1.1.rc2 released
On Mar 8, 2008, at 8:04 PM, Timo Sirainen wrote: On Mar 9, 2008, at 3:02 AM, Timo Sirainen wrote: On Mar 9, 2008, at 2:58 AM, Bruce Bodger wrote: Mar 8 14:02:14 G518X2 launchd: org.dovecot: exited with exit code: 89 89 is a generic exit code meaning that Dovecot should have logged something before exiting. If you can't find anything from existing logs, try setting log_path = /tmp/dovecot.log and see if it logs anything in there? Oh, actually the other possibility is that it wrote the error to stderr, and launchd simply doesn't write it anywhere? What if you run dovecot -F from shell directly? You're right... nothing written to log, but starting from shell... G518X2:~/Library root# /usr/local/sbin/dovecot -F Fsetregid(65534,6) failed with euid=0: Operation not permitted Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /usr/local/etc/dovecot.conf Here's the stanza from dovecot.conf # Group to enable temporarily for privileged operations. Currently this is # used only for creating mbox dotlock files when creation fails for INBOX. # Typically this is set to mail to give access to /var/mail. mail_privileged_group = mail
Re: [Dovecot] v1.1.rc1 released
On Feb 21, 2008, at 4:22 PM, Timo Sirainen wrote: http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz Timo, You probably want to announce the availability of Sieve plugin v1.1.4 as well. Here, running OS X 10.4.11, it is required after the upgrade to 1.1.rc1. Without upgrading to dovecot-sieve-1.1.4 I get these errors during the 'make': sieve-cmu.Tpo -c sieve-cmu.c -fno-common -DPIC -o .libs/sieve-cmu.o sieve-cmu.c: In function 'parts_add_missing': sieve-cmu.c:323: error: too few arguments to function 'message_parser_deinit' make[3]: *** [sieve-cmu.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 B. Bodger New York, NY
Re: [Dovecot] Scheduled folder purging
On Feb 19, 2008, at 6:06 AM, Timo Sirainen wrote: Still, the expire plugin is not the easiest plugin to configure. Getting the error Unknown dict module: db which, on Sept. 24, 2007, you explained as... The problem is that imap binary isn't linked with libdb, so this doesn't work. You'll have to somehow kludge this yourself, or an easier way is to use dict proxy. It's configured the same way as SQL for dict quota: http://wiki.dovecot.org/Quota/Dict Shouldn't there be an easier way, Timo? B. Bodger New York, NY
Re: [Dovecot] dovecot + antispam + sendmail
On Jan 24, 2008, at 7:14 PM, Anil wrote: Whats a good antispam solution? I am using sendmail and dovecot 1.1. I came across dovecot's antispam plugin, but it seems it does not support 1.1 yet. I am also looking for something non-perl based. I suggest looking into MPP (Message Processing Platform) at http:// www.raeinternet.com/ It's been running famously here for a couple of YEARS! B. Bodger New York, NY
Re: [Dovecot] v1.1.beta14 released (Compile Error)
On Jan 20, 2008, at 6:34 PM, Adam McDougall wrote: Tomi Hakala wrote: Timo Sirainen wrote: On 20.1.2008, at 19.40, Jerry Yeager wrote: Undefined symbols: _posix_fallocate, referenced from: _file_set_size in liblib.a(file-set-size.o) Fixed: http://hg.dovecot.org/dovecot/rev/6c868e7fe7b2 You can also fix it by removing HAVE_POSIX_FALLOCATE from config.h Same problem and fix applies to Solaris 10. Tomi The patch did not work for me on FreeBSD 6.3, I had to edit config.h.in because my build procedure apparently overwrote config.h after I patched it. Running OS X 10.4.11 here. Also found that 1. Applying the referenced patch did not result in a clean compile 2. Had to manually comment lines referring to HAVE_POSIX_FALLOCATE in BOTH config.h AND config.h.in in order to get a clean compile. B. Bodger New York
Re: [Dovecot] Webmail Recommendation
On Jan 12, 2008, at 6:18 AM, Ronald MacDonald wrote: I did actually write a little extension to RC mail myself about a month ago - which you could try. http://www.rmacd.com/downloads/howto/add-csv-to-roundcube.php Mr. McDonald, I haven't investigated too deeply but I presume your patch requires a bit of modification to apply to roundcubemail-0.1-rc2. BTW, my kids just LOVE your burgers! B. Bodger
Re: [Dovecot] v1.1.beta13 released
On Jan 5, 2008, at 5:50 PM, Timo Sirainen wrote:
Attempts to delete
the .INBOX from a mail client results in an error: Inbox can't be
deleted. Any ideas?
I did some fixes now though so that it's possible to create ns/
INBOX and
use it as a normal mailbox (including delete it).
http://hg.dovecot.org/dovecot/rev/d5dd0841b2db
Installed today's tarball, 20080106. Yes, now the public/.INBOX can
be deleted without error but dovecot insists on recreating it time
and time again. I don't think that's the behavior that either of us
had in mind. I would think that the public/.INBOX should not be
created unless specifically defined in dovecot.conf. Once again,
here is the relevant part of my dovecot.conf:
## PUBLIC NAMESPACE
namespace public {
separator = /
prefix = Public/
## location = maildir:/var/mail/shared
location = maildir:/var/mail/shared:CONTROL=~/Maildir/control/
public:INDEX=~/Maildir/index/public
}
## PRIVATE NAMESPACE
namespace private {
separator = /
prefix =
inbox = yes
}
Now another observation: only tested with Apple Mail v2.1.2. When
deleting the public/.INBOX it appears that dovecot is attempting to
do it twice as immediately after the .INBOX is deleted an ERROR
message appears stating that the mailbox can not be deleted because
it doesn't exist. Of course, it was already deleted.
Thank you,
B. Bodger
New York
Re: [Dovecot] v1.1.beta13 released
On Jan 6, 2008, at 9:51 AM, Timo Sirainen wrote: What plugins do you use? mail_log and cmusieve (dovecot-sieve-1.1.3) Well, I can't reproduce this with my setup, so there must be something special that's causing this. Unless it's your client that creates the mailbox itself? Perhaps you're right. I just tried using Thunderbird (Mac) and it does not exhibit this behavior. Apple Mail has an option, Automatically synchronize changed mailboxes which I do NOT have checked so the problem must be within Apple Mail as you surmised. In fact, Apple Mail is now displaying public/INBOX in it's list of mailboxes even though it hasn't been created under ~/Maildir/control/ public G518X2:~/Maildir/control/public root# ls -la total 8 drwx-- 5 bb admin 170 Jan 6 10:20 . drwx-- 3 bb admin 102 Jul 28 22:38 .. drwx-- 4 bb admin 136 Jan 6 09:54 .HAM drwx-- 4 bb admin 136 Jan 6 10:10 .SPAM -rw--- 1 bb admin9 Sep 9 07:06 subscriptions ...and INBOX in not listed in 'subscriptions'. Sorry for the goose chase, unless you like goose, of course :-) B. Bodger
Re: [Dovecot] v1.1.beta13 released
On Dec 29, 2007, at 5:09 PM, Timo Sirainen wrote:
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta13.tar.gz
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta13.tar.gz.sig
Timo,
This week I switched from v1.0.10 to v1.1.beta13. I'm using OS X
10.4.11. Had no compile or installation problems. I have discovered
what I think is an undocumented change in behavior between the two
versions regarding public namespaces.
I have used a public name space for many months which gives all users
access to a public SPAM and HAM mailbox. Every few hours spamassasin
runs against the mailboxes and does whatever reporting is needed.
The namespaces are defined in dovecot.conf like so:
## NAMESPACES
namespace public {
separator = /
prefix = Public/
location = maildir:/var/mail/shared:CONTROL=~/Maildir/control/
public:INDEX=~/Maildir/index/public
}
namespace private {
separator = /
prefix =
inbox = yes
}
##
G518X2:~/Maildir/index/public root# ls -la
total 0
drwx-- 5 bb admin 170 Sep 9 07:06 .
drwx-- 3 bb admin 102 Jul 28 22:38 ..
drwx-- 5 bb admin 170 Dec 17 06:10 .HAM
drwx-- 3 bb admin 102 Jan 3 18:02 .INBOX
drwx-- 5 bb admin 170 Jan 5 13:52 .SPAM
Since the upgrade dovecot insists on creating an inbox in the public
space even though the conf notes state, There can be only one INBOX,
and this setting defines which namespace has it. Clearly the
private namespace has the inbox defined. Attempts to delete
the .INBOX from a mail client results in an error: Inbox can't be
deleted. Any ideas?
B. Bodger
Re: [Dovecot] v1.0.10 released
On Dec 29, 2007, at 1:13 AM, Timo Sirainen wrote: http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz.sig Timo: is dovecot-sieve-1.0.2 still the latest and good-to-go with v1.0.10? Thank you very much. B. Bodger New York
Re: [Dovecot] v1.0.6 released
On Oct 27, 2007, at 8:16 PM, Timo Sirainen wrote: http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig Thanks for the release, Timo Should dovecot-sieve-1.0.2 work ok with v1.0.6 ? B. Bodger
Re: [Dovecot] v1.0.5 released
On Sep 9, 2007, at 12:21 AM, Timo Sirainen wrote: http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz.sig Just a reminder: http://www.dovecot.org/download.html needs updating to reflect the availability of the new version. B. Bodger New York
Re: [Dovecot] IDLE with inotify problem
On Aug 12, 2007, at 1:00 PM, Michael Guntsche wrote: Running Dovecot 1.0.3 on OS X 10.4.10 here. Which --with-notify compile time option would you suggest? dnotify, inotify, kqueue, or none. You should use kqueue under macosx since dnotify and inotify are linux only. Thanks for that, Mike! Adding --with-notify=kqueue made a world of difference here! Really appreciate the advice. B. Bodger
Re: [Dovecot] IDLE with inotify problem
On Aug 12, 2007, at 11:20 AM, Michael Guntsche wrote: So my question is can I check that dovecot is actually using inotify? Which brings me to another question for Timo.. Running Dovecot 1.0.3 on OS X 10.4.10 here. Which --with-notify compile time option would you suggest? dnotify, inotify, kqueue, or none. P.S. The version of 1.0.3 that we're currently running was compiled without a with-notify instruction. It still appears to implement some form of idle / notify. We've tested with Thunderbird and Apple's Mail.app (with imap-idle-plugin installed). Even though both clients have been set NOT to check mail on an interval we are still notified when mail arrives. B. Bodger
[Dovecot] Shared mailboxes v1.0.3
On Jul 28, 2007, at 3:47 PM, Sergey A. Kobzar wrote: BTW /home/mail/public/ is not a mailbox and must not contain cur new and tmp folders. As Timo said this bug was fixed in 1.1. Just for the record, and I realize it's not scheduled to be fixed until v1.1, this is still broken in v 1.0.3. Dovecot still creates cur, tmp, and new in /home/mail/public (or applicable, as configured). Doesn't hurt anything but just wanted to make the point. http://wiki.dovecot.org/SharedMailboxes B. Bodger
Re: [Dovecot] sieve discard
On Aug 1, 2007, at 6:29 AM, Timo Sirainen wrote: Since the last changes for http://hg.dovecot.org/dovecot-sieve-1.0/ are: Added tag 1.0.2 for changeset 0afb958e7e71 Released v1.0.2. There isn't really anything to be released as v1.0.3. :) Timo, This comment still remains in the dovecot-sieve INSTALL... It's also not a good idea to build the plugin against self-compiled Dovecot sources, but then actually use a prebuilt binary package of Dovecot. That might work if the Dovecot versions are the same, but it's not guaranteed. Being a Mac System, I've ALWAYS built dovecot-sieve against self- compiled Dovecot sources and have never had an issue with sieve (that others also haven't had.) So maybe that comment is no longer required? (For me, it's just confusing :-)) Thanks, B. Bodger
[Dovecot] Sieve Vacation Auto-Reply Exclusions
The Dovecot Wiki is quite clear regarding its vacation auto-reply mechanism http://wiki.dovecot.org/LDA/Sieve and under what circumstances the automatic replies will NOT be sent. However, is it possible to manually add a list of envelope senders that the script will not respond to? Thank you, B. Bodger
Re: [Dovecot] v1.0.2 released
On Jul 15, 2007, at 3:16 AM, Timo Sirainen wrote: http://dovecot.org/releases/dovecot-1.0.2.tar.gz http://dovecot.org/releases/dovecot-1.0.2.tar.gz.sig Timo, Will a recompile of the sieve-plugin or a new version of the sieve- plugin be required? Thank you, B. Bodger
[Dovecot] Force rebuild v1.0.1
Haven't seen a thread discussing forcing rebuilding of indexes / cache, so the question is, if these files in a users home directory were deleted... -rw--- 1 bb admin 80 May 17 15:05 dovecot-keywords -rw--- 1 bb admin 85449 Jul 2 06:15 dovecot-uidlist -rw--- 1 bb admin6832 Jul 2 06:15 dovecot.index -rw--- 1 bb admin 752640 Jul 2 06:19 dovecot.index.cache -rw--- 1 bb admin 95416 Jul 2 06:20 dovecot.index.log -rw--- 1 bb admin 131104 Jun 27 21:32 dovecot.index.log.2 ...would they be rebuilt by dovecot? Thank you, B. Bodger
Re: [Dovecot] Force rebuild v1.0.1
On Jul 2, 2007, at 1:25 PM, Timo Sirainen wrote: On Mon, 2007-07-02 at 06:23 -0400, Bruce Bodger wrote: Haven't seen a thread discussing forcing rebuilding of indexes / cache, so the question is, if these files in a users home directory were deleted... -rw--- 1 bb admin 80 May 17 15:05 dovecot-keywords -rw--- 1 bb admin 85449 Jul 2 06:15 dovecot-uidlist -rw--- 1 bb admin6832 Jul 2 06:15 dovecot.index -rw--- 1 bb admin 752640 Jul 2 06:19 dovecot.index.cache -rw--- 1 bb admin 95416 Jul 2 06:20 dovecot.index.log -rw--- 1 bb admin 131104 Jun 27 21:32 dovecot.index.log.2 ...would they be rebuilt by dovecot? Sure. Although you shouldn't delete dovecot-uidlist and dovecot-keywords, they're not indexes. http://wiki.dovecot.org/MailLocation/Maildir Thank you, Timo. One more thing: would you explain the existence of this file: -rw--- 1 bb admin 131104 Jun 27 21:32 dovecot.index.log.2 I can understand dovecot-keywords having the old creation date but dovecot.index.log.2 being old makes me think it's no longer needed. Under what conditions is it created and should it be kept around? Thanks, B. Bodger
Re: [Dovecot] parameters to deliver
On Jun 19, 2007, at 5:05 AM, Steffen Kaiser wrote: net_connect(/usr/local/var/run/dovecot/auth-master) failed: No such file or directory It looks like your Dovecot Auth Master is missing, didst you read: http://wiki.dovecot.org/LDA section With a lookup? I understand your point and thank you for your reply. Even though your response is valid I don't think it's the answer to my question since, in my case, I have no virtual users so I really shouldn't need to define a lookup. The question: Is -d required any longer... and if so, how, please. My overall goal relates to incorporating the use of the dovecot sieve module. My current 'deliver' command line within postfix's main.cf mailbox_command = /usr/local/libexec/dovecot/deliver -e is working fine. When incorporating the sieve filter I came across this in the wiki, The envelope sender is taken from a Return-Path: header in the message. The envelope recipient is taken from -d option passed to deliver and wondered if I MUST modify the 'deliver' command line to properly run sieve (and its vacation script). Thank you again, B. Bodger
Re: [Dovecot] Locking problems on Dovecot 1.x in Maildir
Sorry, Ronald. Had to say it before somebody else did. My kids LOVE your burgers!! :-)
[Dovecot] parameters to deliver
Read this in the dovecot sieve wiki:
The envelope sender is taken from a Return-Path: header in the
message. The envelope recipient is taken from -d option passed to
deliver.
Is -d still a valid deliver switch? When I configure postfix's
main.cf like so...
mailbox_command = /usr/local/libexec/dovecot/deliver -d -e
..it sqwaks with, Jun 18 18:44:50 G518X2 deliver(-e): net_connect(/
usr/local/var/run/dovecot/auth-master) failed: No such file or
directory
when configured like so... mailbox_command = /usr/local/libexec/
dovecot/deliver -e -d ${recipient}
..it burps with, Jun 18 18:56:40 G518X2 postfix/local[19766]:
3BBC16C96E0: to=[EMAIL PROTECTED], relay=local, delay=0,
status=bounced (command line usage error. Command output: Fatal:
Missing destination argument )
It doesn't like... mailbox_command = /usr/local/libexec/dovecot/
deliver -e -d $recipient either!
Is -d required any longer... and if so, how, please.
B. Bodger
Re: [Dovecot] v1.0.1 released
Timo, Please entertain this elementary question regarding this new feature. On Jun 15, 2007, at 12:55 PM, Timo Sirainen wrote: + deliver: Added -e parameter to write rejection error to stderr and exit with EX_NOPERM instead of sending the rejection by executing sendmail. Using postfix / dovecot / deliver in a single domain mail host would it make sense to incorporate the -e parameter? We're now, using v1.0.0, andmailbox_command = /usr/local/libexec/ dovecot/deliver in main.cf is working very well. Would modifying it to mailbox_command = /usr/local/libexec/dovecot/deliver -e provide any benefit? Thank you, B. Bodger New York, NY
Re: [Dovecot] Converting mbox to Maildir, all prior read messages are downloaded as new
On May 26, 2007, at 11:30 AM, Timo Sirainen wrote: I have all my mbox-es in /raid/mbox/%u I have set convert_mail = mbox:/raid/mbox/%u:INBOX=/var/mail/%u in the dovecot.conf. But for some reason the folder with mail doesn't get renamed after conversion. Is that the way it should be? And the destination isn't /raid/mbox/%u? It should have renamed the %u to %u-converted. ...and as a reminder, the old mbox inbox, in this case /var/mail/%u, will not be renamed. B. Bodger
[Dovecot] IMAP and Apple Mail
On May 24, 2007, at 6:54 AM, Robert Schetterer wrote: but there are a lot of problems with apple mail and imap Neither I nor any of our users has discovered any problems using apple mail (mail.app) in imap mode with dovecot. What sometimes appears to be a problem is the use (or mis-use) of mail.app's Use This Mailbox For.. function. You might direct your users to this link http://superfluousbanter.org/archives/2007/04/setting-up-imap- in-apple-mail/ BestOfLuck, B. Bodger New York, NY
[Dovecot] Wiki relating to subscriptions
On this wiki page http://wiki.dovecot.org/Migration/UW appears this
information:
It's possible to keep using the .mailboxlist}} filename (as long as
it's in the same directory) by modifying {{{SUBSCRIPTION_FILE_NAME
define in src/lib-storage/index/mbox/mbox-storage.h
However, if a user wanted to continue using .mailboxlist wouldn't
they also have to change the same define in src/lib-storage/index/
maildir/maildir-storage.h?
Also, (regarding v1.0.0 code) the default define in mbox-storage.h is
.subscriptions whereas the default define in maildir-storage.h is
subscriptions (no dot)
B. Bodger
New York, NY
[Dovecot] Dovecot DELIVER
Tried today to use Dovecot's DELIVER LDA. I'm running Postfix 2.1.5. I simply added the line... mailbox_command = /usr/local/libexec/dovecot/deliver to main.cf and made no other changes. First email resulted in this in mail.log: May 16 06:29:56 G518X2 deliver(bb): open(/var/mail/bb.lock) failed: Permission denied May 16 06:29:56 G518X2 deliver(bb): file_lock_dotlock() failed with mbox file /var/mail/bb: Permission denied May 16 06:29:56 G518X2 deliver(bb): msgid=[EMAIL PROTECTED]: save failed to INBOX May 16 06:29:56 G518X2 deliver(bb): open(/var/mail/bb.lock) failed: Permission denied May 16 06:29:56 G518X2 deliver(bb): file_lock_dotlock() failed with mbox file /var/mail/bb: Permission denied Permissions on all inbox files in /var/mail was 600. Owned by username:mail I tried changing to 660 but got the same result. Dovecot user is member of mail group. Any ideas? Thanks in advance.
Re: [Dovecot] Dovecot DELIVER
On May 16, 2007, at 7:53 AM, Timo Sirainen wrote: On Wed, 2007-05-16 at 06:58 -0400, Bruce Bodger wrote: May 16 06:29:56 G518X2 deliver(bb): file_lock_dotlock() failed with mbox file /var/mail/bb: Permission denied See http://wiki.dovecot.org/MailLocation/Mbox#dotlocks Thank you, Timo. I have followed the directions in the wiki. The user dovecot belongs to group mail and I gave the mbox 660 permissions. I also have mail_extra_groups = mail set in dovecot.conf. Am I missing something? Thank you again.
Re: [Dovecot] Dovecot DELIVER
On May 16, 2007, at 7:58 AM, Timo Sirainen wrote: On Wed, 2007-05-16 at 14:53 +0300, Timo Sirainen wrote: On Wed, 2007-05-16 at 06:58 -0400, Bruce Bodger wrote: May 16 06:29:56 G518X2 deliver(bb): file_lock_dotlock() failed with mbox file /var/mail/bb: Permission denied See http://wiki.dovecot.org/MailLocation/Mbox#dotlocks Hmm. Actually with deliver the mail_extra_groups doesn't work. So I think you have two possibilities: 1. Set /var/mail sticky 2. Don't use dotlocks (but if you use other programs to access the mboxes make sure they don't break) Set dovecot user back to its own group. I set /var/mail to sticky... drwxrwxr-t 10 rootmail 340 May 16 08:11 mail Still get this: May 16 08:11:31 G518X2 deliver(bb): open(/var/mail/bb.lock) failed: Permission denied May 16 08:11:31 G518X2 deliver(bb): file_lock_dotlock() failed with mbox file /var/mail/bb: Permission denied May 16 08:11:31 G518X2 deliver(bb): msgid=[EMAIL PROTECTED]: save failed to INBOX May 16 08:11:31 G518X2 deliver(bb): open(/var/mail/bb.lock) failed: Permission denied May 16 08:11:31 G518X2 deliver(bb): file_lock_dotlock() failed with mbox file /var/mail/bb: Permission denied Bruce
Re: [Dovecot] Dovecot DELIVER
On May 16, 2007, at 8:24 AM, Timo Sirainen wrote: On Wed, 2007-05-16 at 08:14 -0400, Bruce Bodger wrote: I set /var/mail to sticky... drwxrwxr-t 10 rootmail 340 May 16 08:11 mail You have to make it world-writable also. I'll update the wiki to mention that too. That may present a problem, Timo, as postfix's local LDA wants exclusivity on the files in /var/mail. May 16 08:34:11 G518X2 postfix/local[26583]: 7E613630295: to=[EMAIL PROTECTED], orig_to=[EMAIL PROTECTED], relay=local, delay=581, status=deferred (cannot access mailbox /var/mail/bb for user bb. unable to lock for exclusive access: Resource temporarily unavailable) I realize that the intent here is to have Dovecot's LDA replace Postfix's but it would seem logical if their behaviors (and expectations regarding directories) were in sync. Bruce
Re: [Dovecot] Getting rid of the common newbie problems
On May 16, 2007, at 9:29 AM, Charles Marcus wrote: I see what you're getting at, but personally i really like having plenty of documentation in the config files. That way when you're editing the config file, you can know exactly what you're doing and have good descriptions right in front of you Of course this is no substitute for other documentation like manual/wiki etc On the subject of newbie questions... The dovecot-example.conf file, under Mailbox locations and namespaces, states, If you're using mbox, giving a path to the INBOX file (eg. /var/mail/ %u) isn't enough. You'll also need to tell Dovecot where the other mailboxes are and where Dovecot can place its index files. This is called the root mail directory, and it must be the first path given in the mail_location setting. Yet both mbox examples describe otherwise. The first example, mail_location = mbox:~/mail:INBOX=/var/mail/%u has no INDEX definition and the second example, mail_location = mbox:/var/mail/%d/ %1n/%n:INDEX=/var/indexes/%d/%1n/%n shows the INDEX definition last when the instructions state that it must be first. I happen to be using (under OS X), mail_location = mbox:~/Library/Mail/IMAP:INBOX=/var/mail/%u:INDEX=%h/ Library/Mail/DOVECOT.indexes ...without any problems so basically, I find the instructions a bit confusing. B. Bodger New York, NY
Re: [Dovecot] OS X Mail Administration
On May 16, 2007, at 11:27 AM, Timo Sirainen wrote: On Wed, 2007-05-16 at 10:41 -0400, Bruce Bodger wrote: I'd like to request some feed back from any OS X Mail Admins on the list, please. Set dotlock_use_excl=yes. Without it you can run into all kinds of trouble with HFS+. Got it! Thanks.
Re: [Dovecot] CONVERT Plugin
On May 16, 2007, at 7:21 PM, Timo Sirainen wrote: It's not supposed to be renamed. The most important reason why the renaming is done at all is so that convert plugin doesn't try to convert the same mailboxes twice. It's enough to rename the mbox root directory for that. I think renaming INBOX could just cause problems. The WIKI sounds like it should be renamed to something, too. Any suggestions how to change it so it doesn't sound like that? I thought it was pretty clear. :) Perhaps change this: Once everything is finished, ~/mail is renamed to ~/mail-converted and at next login the conversion isn't done, because the ~/mail directory no longer exists. to this: Once everything is finished effected directories are renamed: ~/mail is renamed to ~/mail-converted, etc. and at next login the conversion isn't performed because the ~/mail directory no longer exists. Mail files, such as the INBOX (~/var/mail/$USERNAME) are not renamed. ??
Re: [Dovecot] BUG REPORT - Stops logging after sleep
Please disregard the below reported bug report. I experienced the same problem today and this time sleep was not involved. I rotate mail.log weekly. This morning I noticed that dovecot was no longer logging to mail.log although, again, it was running fine. Is it possible that dovecot has a problem after midnight and will not log with the new day? Something is stopping dovecot from logging and it appears that it might have to do with change of the day? This is a new (two day old) dovecot installation. Coming from uw- imap. It never exhibited this problem. Thank you, B. Bodger Ronkonkoma, NY On May 10, 2007, at 7:34 AM, Bruce Bodger wrote: Version: dovecot --version: 1.0.0 OS: OS X - 10.4.9 Architecture: G5 Dual/1.8Ghz Had a fairly normal time correction last night: May 9 20:56:56 G518X2 ntpd[219]: time set -1.212733 s Which dovecot duly noted: May 9 20:56:56 G518X2 dovecot: auth(default): Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. This morning all of the dovecot processes are running fine but dovecot has stopped logging. (I have modified nothing in dovecot.conf relative to logging: dovecot logs to syslog using the mail syslog_facility.) ps -aux | grep dovecot root53 0.0 -0.027772544 ?? Ss4:23PM 0:04.69 /usr/local/sbin/dovecot -F root79 0.0 -0.028176556 ?? S 4:23PM 0:03.21 dovecot-auth dovecot 9548 0.0 -0.027780496 ?? S 7:12AM 0:00.05 imap-login dovecot 9631 0.0 -0.027780500 ?? S 7:17AM 0:00.03 imap-login dovecot 9632 0.0 -0.027780500 ?? S 7:17AM 0:00.03 imap-login I am starting dovecot via OS X's launchdaemon facility thus the - F command line switch requirement. Sending a kill -HUP to the process did not get it to start logging. Sending a Kill -9 to the process forced a restart and logging began again. ps -aux | grep dovecot root 9738 0.0 -0.027772540 ?? Ss7:26AM 0:00.03 /usr/local/sbin/dovecot -F root 9739 0.0 -0.028176544 ?? S 7:26AM 0:00.02 dovecot-auth dovecot 9740 0.0 -0.027780500 ?? S 7:26AM 0:00.02 imap-login dovecot 9751 0.0 -0.027780500 ?? S 7:27AM 0:00.01 imap-login dovecot 9762 0.0 -0.027780500 ?? S 7:27AM 0:00.01 imap-login Before posting this bug I compared v1.0.0's /src/lib/ioloop.c to that in the nightly snapshot and saw no adjustments in, what I presumed to be, the relevant portion of the code. Output of dovecot -n protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 490 mail_extra_groups: mail mail_location: mbox:~/Library/Mail/IMAP:INBOX=/var/mail/%u:INDEX=%h/ Library/Mail/DOVECOT.indexes dotlock_use_excl: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd Thank you.
Re: [Dovecot] BUG REPORT - Stops logging after sleep
It appears as though dovecot doesn't like syslogd being restarted. My system.log is rotated nightly followed by a pretty standard syslogd restart... if [ -f /var/run/syslog.pid ]; then kill -HUP $(cat /var/run/ syslog.pid | head -1); It appears from that point on dovecot no longer writes to mail.log. Killing and restarting dovecot causes it to write to the log again. If you care to take a stab at a suggestion, please kind in mind that I'm having to run dovecot with the -F switch (see below). Thanks in advance, B. Bodger Ronkonkoma, NY On May 11, 2007, at 6:17 AM, Bruce Bodger wrote: Please disregard the below reported bug report. I experienced the same problem today and this time sleep was not involved. I rotate mail.log weekly. This morning I noticed that dovecot was no longer logging to mail.log although, again, it was running fine. Is it possible that dovecot has a problem after midnight and will not log with the new day? Something is stopping dovecot from logging and it appears that it might have to do with change of the day? This is a new (two day old) dovecot installation. Coming from uw- imap. It never exhibited this problem. Thank you, B. Bodger Ronkonkoma, NY On May 10, 2007, at 7:34 AM, Bruce Bodger wrote: Version: dovecot --version: 1.0.0 OS: OS X - 10.4.9 Architecture: G5 Dual/1.8Ghz Had a fairly normal time correction last night: May 9 20:56:56 G518X2 ntpd[219]: time set -1.212733 s Which dovecot duly noted: May 9 20:56:56 G518X2 dovecot: auth(default): Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. This morning all of the dovecot processes are running fine but dovecot has stopped logging. (I have modified nothing in dovecot.conf relative to logging: dovecot logs to syslog using the mail syslog_facility.) ps -aux | grep dovecot root53 0.0 -0.027772544 ?? Ss4:23PM 0:04.69 /usr/local/sbin/dovecot -F root79 0.0 -0.028176556 ?? S 4:23PM 0:03.21 dovecot-auth dovecot 9548 0.0 -0.027780496 ?? S 7:12AM 0:00.05 imap-login dovecot 9631 0.0 -0.027780500 ?? S 7:17AM 0:00.03 imap-login dovecot 9632 0.0 -0.027780500 ?? S 7:17AM 0:00.03 imap-login I am starting dovecot via OS X's launchdaemon facility thus the - F command line switch requirement. Sending a kill -HUP to the process did not get it to start logging. Sending a Kill -9 to the process forced a restart and logging began again. ps -aux | grep dovecot root 9738 0.0 -0.027772540 ?? Ss7:26AM 0:00.03 /usr/local/sbin/dovecot -F root 9739 0.0 -0.028176544 ?? S 7:26AM 0:00.02 dovecot-auth dovecot 9740 0.0 -0.027780500 ?? S 7:26AM 0:00.02 imap-login dovecot 9751 0.0 -0.027780500 ?? S 7:27AM 0:00.01 imap-login dovecot 9762 0.0 -0.027780500 ?? S 7:27AM 0:00.01 imap-login Before posting this bug I compared v1.0.0's /src/lib/ioloop.c to that in the nightly snapshot and saw no adjustments in, what I presumed to be, the relevant portion of the code. Output of dovecot -n protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 490 mail_extra_groups: mail mail_location: mbox:~/Library/Mail/IMAP:INBOX=/var/mail/%u:INDEX=% h/Library/Mail/DOVECOT.indexes dotlock_use_excl: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd Thank you.
Re: [Dovecot] BUG REPORT - Stops logging after sleep
Thank you very much, Charles. I have resorted to that workaround (restarting dovecot) which does, indeed, work. I just wanted to document the situation since dovecot's behavior in this regard is unlike other imap servers. Best regards, Bruce On May 11, 2007, at 8:27 AM, Charles Marcus wrote: Bruce Bodger wrote: It appears as though dovecot doesn't like syslogd being restarted. Hmmm... could this possibly be a fix, or at least a workaround? www.dovecot.org/list/dovecot/2004-November/005219.html -- Best regards, Charles
Re: [Dovecot] BUG REPORT - Stops logging after sleep
Applied the patch, recompiled v1.1.0 using same line to config as before.. ./configure --with-ssldir=/System/Library/OpenSSL --with-ssl=openssl Sorry... no change: does not fix it. Regards, Bruce On May 11, 2007, at 10:24 AM, Timo Sirainen wrote: On Fri, 2007-05-11 at 09:26 -0400, Bruce Bodger wrote: That would be accurate, Bill. I suspect the problem to be within dovecot since, as I mentioned earlier, neither uw-imap or other running daemons exhibit this problem. That's probably because UW-IMAP and most other servers keep creating new processes which open new connections to syslog, while Dovecot has one long-running dovecot process. If you apply the patch below and send SIGUSR1 signal to dovecot process, does it fix it?
[Dovecot] BUG REPORT - Stops logging after sleep
Version: dovecot --version: 1.0.0 OS: OS X - 10.4.9 Architecture: G5 Dual/1.8Ghz Had a fairly normal time correction last night: May 9 20:56:56 G518X2 ntpd[219]: time set -1.212733 s Which dovecot duly noted: May 9 20:56:56 G518X2 dovecot: auth(default): Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. This morning all of the dovecot processes are running fine but dovecot has stopped logging. (I have modified nothing in dovecot.conf relative to logging: dovecot logs to syslog using the mail syslog_facility.) ps -aux | grep dovecot root53 0.0 -0.027772544 ?? Ss4:23PM 0:04.69 /usr/local/sbin/dovecot -F root79 0.0 -0.028176556 ?? S 4:23PM 0:03.21 dovecot-auth dovecot 9548 0.0 -0.027780496 ?? S 7:12AM 0:00.05 imap-login dovecot 9631 0.0 -0.027780500 ?? S 7:17AM 0:00.03 imap-login dovecot 9632 0.0 -0.027780500 ?? S 7:17AM 0:00.03 imap-login I am starting dovecot via OS X's launchdaemon facility thus the -F command line switch requirement. Sending a kill -HUP to the process did not get it to start logging. Sending a Kill -9 to the process forced a restart and logging began again. ps -aux | grep dovecot root 9738 0.0 -0.027772540 ?? Ss7:26AM 0:00.03 /usr/local/sbin/dovecot -F root 9739 0.0 -0.028176544 ?? S 7:26AM 0:00.02 dovecot-auth dovecot 9740 0.0 -0.027780500 ?? S 7:26AM 0:00.02 imap-login dovecot 9751 0.0 -0.027780500 ?? S 7:27AM 0:00.01 imap-login dovecot 9762 0.0 -0.027780500 ?? S 7:27AM 0:00.01 imap-login Before posting this bug I compared v1.0.0's /src/lib/ioloop.c to that in the nightly snapshot and saw no adjustments in, what I presumed to be, the relevant portion of the code. Output of dovecot -n protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 490 mail_extra_groups: mail mail_location: mbox:~/Library/Mail/IMAP:INBOX=/var/mail/%u:INDEX=%h/ Library/Mail/DOVECOT.indexes dotlock_use_excl: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd Thank you.
