August 2005 - dovecot

[Dovecot] verbose pop3 logging
by Ilo Lorusso 17 Oct '05

17 Oct '05

Hi Im new to dovecot and am looking for some options in the /etc/dovecot.conf to make dovecot a bit more verbose in terms pop3 usage, What ip a user is coming from? How many mails the user downloaded? Timing? Errors occurred while downloading mail?? Is this all possible with dovecot?

3 2

[Dovecot] a few questions about my experience with alpha1
by Glenn Leavell 16 Oct '05

16 Oct '05

Hi all, I've just switched from 0.99.10.6 to alpha1 on a Solaris 9 system, and I have a few questions: 1) I'm using "verbose_proctitle = yes" but I don't see the special username or IP address information in the output of ps. I've used: ps -fu dovecot ps -ef | grep dovecot /usr/ucb/ps aux | grep dovecot The process table simply shows the /usr/local/sbin/dovecot, dovecot-auth, and imap-login processes. Is there something else that I need to do, or is there a special way that I should use ps? 2) After sending dovecot a HUP signal, the logs will report something like: Warning: SIGHUP received - reloading configuration And everything seems to work fine. However, *sometimes* after sending a HUP signal, logging will stop indefinitely. Has anyone else noticed anything similar? 3) We use UW in production, and I'm new to any real use of namespaces. Almost all of our clients use the root "~/Mail/" to find their folders (in $HOME/Mail/) and their INBOXes are located in $HOME/.inbox. A few people actually find their folders with the direct path Mail/foldername. So, I'm trying to configure Dovecot to work with any of these roots / prefixes: ~/Mail/ Mail/ "" (empty/blank) I'm using the namespace configuration below, and it seems to work with any of the above prefixes. However, the logging that I see makes me wonder if I'm doing it the best way. Note the attached log file. All of this output was generated with this single IMAP command: A01 LOGIN bozo mypassword Here's my configuration: **************************************************************************** # Default namespace private { separator = / prefix = location = mbox:%h/Mail/:INBOX=%h/.inbox:INDEX=%h/Mail/ inbox = yes hidden = no } # This is the standard ~/Mail/ namespace that our clients tend to use namespace private { separator = / prefix = ~/Mail/ location = mbox:%h/Mail/ hidden = yes } # This namespace is for a few folks who might actually try to # directly access "Mail/foldername" -- as if they were accessing a real # filesystem path. namespace private { separator = / prefix = Mail/ location = mbox:%h/Mail/ hidden = yes } **************************************************************************** So, is this the best way to configure the namespaces for what I'm trying to accomplish? And any pointers on how to interpret what Dovecot is working through with regard to the attached logs would be appreciated. Notice the "Sending log messages too fast, throttling.." message (again, generated from that single login command). What might be causing that? By the way, is there any real difference between the use of %h/Mail and the possible use of ~/Mail in the location fields above? Thanks very much! -- Glenn Leavell <glenn(a)usg.edu> Office of Information and Instructional Technology Board of Regents of the University System of Georgia

3 9

[Dovecot] Still crashing with test-80
by Matt Juszczak 05 Oct '05

05 Oct '05

Here is the log over a 12 hour period: pid 91923 (pop3), uid 25039: exited on signal 6 pid 98265 (pop3), uid 25039: exited on signal 6 pid 95547 (pop3), uid 25039: exited on signal 6 pid 235 (pop3), uid 25039: exited on signal 6 pid 239 (pop3), uid 25039: exited on signal 6 pid 318 (pop3), uid 25039: exited on signal 6 pid 386 (pop3), uid 25039: exited on signal 6 pid 415 (pop3), uid 25039: exited on signal 6 pid 427 (pop3), uid 25039: exited on signal 6 pid 434 (pop3), uid 25039: exited on signal 6 pid 468 (pop3), uid 25039: exited on signal 6 pid 653 (dovecot-auth), uid 0: exited on signal 6 (core dumped) Here is the GDB Backtrace: orion# gdb /usr/local/libexec/dovecot/imap dovecot-auth.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)... warning: core file may not match specified executable file. Core was generated by `dovecot-auth'. Program terminated with signal 6, Aborted. #0 0x181327af in ?? () (gdb) bt full #0 0x181327af in ?? () No symbol table info available. #1 0x18127856 in ?? () No symbol table info available. #2 0x0000028d in ?? () No symbol table info available. #3 0x00000006 in ?? () No symbol table info available. #4 0x00000000 in ?? () No symbol table info available. #5 0x00000000 in ?? () No symbol table info available. #6 0x00000286 in ?? () No symbol table info available. #7 0x181abf4c in ?? () No symbol table info available. #8 0xbfbfea78 in ?? () No symbol table info available. #9 0x1819b0df in ?? () No symbol table info available. #10 0x00000006 in ?? () No symbol table info available. #11 0xbfbfea48 in ?? () No symbol table info available. #12 0x00000000 in ?? () No symbol table info available. #13 0x1819b0aa in ?? () No symbol table info available. #14 0x00000001 in ?? () No symbol table info available. #15 0x18095400 in ?? () No symbol table info available. #16 0xffffffdf in ?? () No symbol table info available. #17 0xffffffff in ?? () No symbol table info available. #18 0xffffffff in ?? () No symbol table info available. #19 0xffffffff in ?? () ---Type <return> to continue, or q <return> to quit--- No symbol table info available. #20 0x18072a11 in ?? () No symbol table info available. #21 0x18095000 in ?? () No symbol table info available. #22 0x00000150 in ?? () No symbol table info available. #23 0x0807a000 in mail_cache_header_fields_read () No symbol table info available. #24 0x08071000 in istream_raw_mbox_next () No symbol table info available. #25 0x00000000 in ?? () No symbol table info available. #26 0x080710d0 in istream_raw_mbox_seek () No symbol table info available. #27 0x083c1ac0 in ?? () No symbol table info available. #28 0xbfbfea98 in ?? () No symbol table info available. #29 0x0805efd4 in imap_thread () No symbol table info available. Previous frame inner to this frame (corrupt stack?) (gdb) Thanks in advance for any help anyone can provide. -Matt

3 6

[Dovecot] Fatal: EOF reading environment from master
by Marcathian Alexander 24 Sep '05

24 Sep '05

I have been running dovecot as an imap server since 22nd July 2005. The server was started from xinetd using /usr/local/libexec/dovecot/imap-auth The sever run successfully until the machine was shut down in a power outage on 12 Aug 2005. Dovecot has failed to start since the reboot. When starting it with the imap-auth it gives the following error: fatal: EOF reading environment from master I have uninstalled dovecot, downloaded, compiled, and installed the stable of 14Aug 2005 and got the same error. I then installed the 0.99.14 version ang got the same error. Can i have assistance in solving and/or diagnosing the problem? -- Marcathian Alexander SDE Assistant Sustainable Development and Environment Section Ministry of Physical Development, Environment & Housing Open Source Software Evaluation Project - WebMail/Groupware/Collaboaration [Open WebMail Project (http://openwebmail.org)]

6 7

[Dovecot] Weird series of errors with dovecot-stable
by Ben Beuchler 21 Sep '05

21 Sep '05

I'm using the dovecot-stable from 7/30, authenticating against an OpenLDAP server. From time to time, dovecot stops responding to new queries. It seems to be a self-correcting problem, lasting about 20 minutes. Here's how it starts: Aug 18 19:38:23 cliff dovecot: imap-login: Disconnected: Inactivity [150.253.42.12] Aug 18 19:38:36 cliff dovecot: pop3-login: Disconnected: Inactivity [68.46.174.217] Aug 18 19:39:35 cliff dovecot: imap-login: Disconnected: Inactivity [150.253.42.12] Normally I see almost no "Disconnected: Inactivity" messages, but when this problem shows up I get an almost non-stop barrage of them. In fact, over the 20 minutes or so, there's about 150 of those entries, so I filtered them out of the log snippets. I also filtered out any "normal" activity during the time period. Here's what's left: Aug 18 19:40:29 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:40:29 cliff dovecot: child 22347 (auth) killed with signal 6 Aug 18 19:42:04 cliff dovecot: auth(ldap): ldap(vmail,150.253.80.31): unknown user Aug 18 19:42:41 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [24.26.184.219] Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:31 cliff dovecot: auth(ldap): Login process has too old (121s) requests, killing it. Aug 18 19:43:43 cliff dovecot: auth(ldap): Login process has too old (121s) requests, killing it. Aug 18 19:43:43 cliff dovecot: auth(ldap): Login process has too old (122s) requests, killing it. Aug 18 19:43:49 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:43:49 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:43:49 cliff dovecot: child 22557 (auth) killed with signal 6 Aug 18 19:43:49 cliff dovecot: child 22562 (login) returned error 89 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:32 cliff dovecot: child 22522 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22561 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22563 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22564 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22566 (login) returned error 89 Aug 18 19:47:54 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:47:54 cliff dovecot: child 22599 (auth) killed with signal 6 Aug 18 19:48:18 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [69.81.39.120] Aug 18 19:48:18 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [69.81.39.120] Aug 18 19:51:32 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:51:32 cliff dovecot: child 22628 (auth) killed with signal 6 Aug 18 19:54:14 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:54:14 cliff dovecot: child 22655 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22683 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22686 (auth) killed with signal 6 Aug 18 19:54:14 cliff dovecot: child 22689 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22690 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22699 (login) returned error 89 Then, magickally, it begins working again. Any thoughts? -Ben

2 1

[Dovecot] Very minor feature request
by Steffen Kaiser 19 Sep '05

19 Sep '05

Hello, I'd suggest a way to get to know the "capabilities" of a compiled Dovecot. The background is that I've run the sequence ./configure --with-ldap && make && make install twice, all three commands tell me that all is fine (ldap is listed in the modules), but still dovecot told me that ldap is no Usedb module. A "make clean" before solved the problem -- well, something one should anyway. Besides, the "dovecot --capabilities" should also list all the defaults. Bye, -- Steffen Kaiser

3 4

[Dovecot] "racing" error ???
by Andy Cravens 18 Sep '05

18 Sep '05

Anybody know what this racing error means? I've got hundreds of them in my Dovecot log file. I tried to search the archives but couldn't find a search link. Nothing on Google search either. dovecot: Aug 30 16:55:54 Error: IMAP(testuser): maildir_file_do(/export/home/testuser/mail) racing -- Andy Cravens

2 2

[Dovecot] Dovecot Deliver Problem
by Marc Perkel 15 Sep '05

15 Sep '05

Trying to use the deliver utility and getting this error: error: net_connect(/var/run/dovecot/auth-master) failed: No such file or directory -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

4 9

[Dovecot] Lot of crashing messages
by Matt Juszczak 09 Sep '05

09 Sep '05

Receiving a lot of the following messags with 1.0-76: pid 633 (dovecot-auth), uid 0: exited on signal 6 (core dumped) Any ideas? Sometimes, our entire port 110/143 servers begin refusing connections. Hardware checks out fine. Thanks in advance, Regards, Matt

3 3

[Dovecot] 1.0-test75 and roadmap for v1.0
by Timo Sirainen 07 Sep '05

07 Sep '05

http://dovecot.org/test/ Keywords are finally stored in maildir filenames and listed in "dovecot-keywords" file. It should be possible to just rename 0.99.x's .customflags file to dovecot-keywords (but it can't be renamed back after modification). Also fixed another uid/sequence mixup bug with setting keywords in general (in mbox too). Fixed SHA1 checksum generation with big-endian machines (used only in passwords). I think I'll forget about the master/config rewrite for a while and leave it for Dovecot v2.0. That would mean the next release will be called 1.0-alpha1. After that there should be only bugfixes and some smaller features and optimizations left. I looked through my TODO and found the following missing features / optimizations that pretty much have to be done before v1.0. Anything important missing? - keywords: - add some limits to how many there can be - send FLAGS/PERMANENTFLAGS untagged replies when they change (required by IMAP RFC) - remove unused keywords from keyword list? (only when adding new ones) - mail cache file - cache _all_ headers that are marked to be cached when headers are being parsed, not just the ones client is requesting at that time. - compression should drop fields with last_used < (latest_mail_index_date - month) - when parsing mbox or saving message, parse the mail through index-mail so things gets saved into cache immediately - mbox - when we're updating flags with lazy writing, we're still parsing the mbox, just not writing to it! - always add empty line after mail. - make the parser require it too? syncing should make sure there always exists two LFs at end of file. raw-mbox-stream should make sure the last message ends with LF even if it doesn't exist in the file - COPY doesn't work to same mailbox (lock assert crash) - keep mbox lock for two extra seconds after sync to make sure we notice changes made by other mbox writer software - maildir - hardlink copying doesn't update indexes (does it even work?) - deliver needs quota integration somehow so it returns out-of-quota failure as fatal instead of temporary Probably after v1.0: - Full NFS support - Try to handle out-of-quota/disk space situations well

8 18