- dovecot - dovecot.org

[Dovecot] Only one malfunction in months - now running dovecot-1.0-test52
by Kim Culhan 29 Nov '04

29 Nov '04

Dont think there has been even one failure in some months of use but tonight we're seeing this running test-52 While running squirrelmail 1.5.1-CVS a certain message causes: dovecot: Nov 17 22:25:14 Error: IMAP(kimc): file ostream-file.c: line 643 (_send_istream): assertion failed: (instream->v_offset <= in_size) dovecot: Nov 17 22:25:14 Error: child 72172 (imap) killed with signal 6 FWIW squirrelmail shows: ERROR : Connection dropped by imap-server. Query: FETCH 5 BODY[1] If I retrieve the message with Outlook, it shows the message has no text and a single jpeg attachment. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

[Dovecot] SASL authentication
by Tom Allison 29 Nov '04

29 Nov '04

I was browsing the wiki and found a section on what appears to be as close to "exactly what I'm looking for" as I've seen in a long time. http://wiki.dovecot.org/moin.cgi/DovecotPostgresql However, I'm not inclined to do very much "blind" configuration on my machines without first understanding the what/why of it all. My theory is that this helps me with the RTFM syndromes later. Hopefully. My current dovecot installation is based on pgsql authentication with a single domain and files being placed in a $HOME. It's as if it were /etc/passwd based, but the passwords are different. I would very much like to migrate this into a system which supports multiple domains and this Wiki seems to be the best means for that. However, I didn't use SASL authentication. I was emotionally scarred trying to use SASL with a venture with Cyrus-IMAP under different circumstances. Could someone explain why SASL is a good thing in this case? Does it allow for something more, lead into future developements? Most of the rest of this general paper I do understand, but the SASL is the only part where I'm not sure if I must do that, want to do that, or can live without it.

2 1

[Dovecot] NFS, test52, maildir, freebsd 4.x and OS X (Panther) Server
by Sean Porter 29 Nov '04

29 Nov '04

I've been working on setting up a Dovecot server with a maildir mailboxes stored over NFS. Initially, everything was working great, and then I started seeing this error as previously discussed on the list in my maillog: (mail_index_expunge): assertion failed: (!t->view->external) Timo, in another thread, suggested to remove line 247 in mail-index-transaction.c in the test52 source, which I blithely ignored as I thought this would remove only the error message from the logfile and not fix the problem. At Mark Lidstone's helpful off-list insistence I did remove the line, recompile, and everything did seem to be working, until I encountered a different error. I started doing some light load testing from multiple clients (essentially, clicking like a rabid monkey on Get Mail in Thunderbird and hitting different mailbox links in Squirrelmail as the same user) and started running into this error in the logs: Nov 22 20:10:46 server dovecot: IMAP(mailuser(a)example.com): rename(/host/mail/mailboxes/mailuser(a)example.com/dovecot-uidlist.lock, /host/mail/mailboxes/mailuser(a)example.com/dovecot-uidlist) failed: Input/output error Nov 22 20:10:46 server dovecot: IMAP(mailuser(a)example.com): file_dotlock_replace(/host/mail/mailboxes/mailuser(a)example.com/dovecot- uidlist) failed: Input/output error Oddly, the dovecot-uidlist.lock file was unremovable on the NFS server (OS X Panther Server) with a simple 'rm', so I started digging into things a little further. It seems that the OS X NFS code is based on the FreeBSD 5.x codebase. The server that Dovecot (and my NFS client) lives on is FreeBSD 4.x, which doesn't support NFS locking at all(incidentally, the FreeBSD NFS Server is apparently incompatible with Linux NFS clients as well -- nice!). Per the suggestion in http://www.dovecot.org/doc/nfs.txt I'd already been storing my index files locally, but it appeared that the control files were somehow blowing up, even with NFS-safe dotlocking. All hope was nearly lost when I came across this tidbit in a post from Timo(http://www.dovecot.org/list/dovecot/2003-May/001489.html): - :CONTROL=dir in default_mail_env can specify where to save dovecot-uidlist and .customflags files. Useful for above problems. I then changed my dovecot.conf to retreive the mailboxes from the NFS mount, but store the indexes and the control files locally: default_mail_env = maildir:/host/mail/mailboxes/%u:INDEX=/home/dovecot/%u/indexes: CONTROL=/home/dovecot/%u/control All seems well so far. I know this is a relatively unique setup, but I thought it might help some of the other people that are running into NFS-related issues. Suggestion: perhaps the :CONTROL directive could be added to mail-storages.txt or dovecot-example.conf? A hint may also want to be added to http://www.dovecot.org/doc/nfs.txt. Sean

2 1

[Dovecot] AppleMail causes dovecot error: file mbox-rewrite.c: line 429 assertion failed
by Adam Rosi-Kessel 29 Nov '04

29 Nov '04

I get the following error message in my syslog frequently when a user accesses the dovecot (IMAP) server from his OS X AppleMail client: Nov 24 09:45:42 myhost imap(someuser): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) Nov 24 09:45:42 myhost dovecot: child 23277 (imap) killed with signal 6 Usually each message appears 5-6 times. The user on the other end doesn't notice any problems. Any idea why this occurs and what I can do to prevent it? I'm using dovecot from Debian sid, 0.99.11-3. Otherwise a fairly standard configuration. -- Adam Rosi-Kessel http://adam.rosi-kessel.org

2 1

[Dovecot] Runtime root directory
by Brad Robel-Forrest 29 Nov '04

29 Nov '04

I'm considering modifying the Dovecot source to support a runtime designation for the root directory instead of relying on the prefix provided via configure. Once complete, it would be possible to move the root directory around somewhat ad-hoc after installation without having to rebuild the source. The primary driver for this is that I'd like to wrap a binary build of Dovecot within an OSX application bundle. These bundles can be placed anywhere the user desires, so Dovecot couldn't rely on a particular build-defined root directory. Before I get too far down the path, I'd like to know if there's a desire for this type of enhancement. If so, I'd like to provide a diff that would meet any other requirements for this change. There are two methods I was considering. Feel free to suggest a better alternative as I'm not ecstatic about either at the moment. 1. Find and change all uses of the prefix directory to instead prepend a value obtained from the environment (say, DOVECOT_ROOT_DIR). 2. Find and change all uses of the prefix directory to instead prepend a value obtained from the configuration file (say, a new setting called "dovecot_root_dir"). In either case, if the value was not available or not a valid directory, I would fall back to the build prefix. I would also make this functionality optional via configure--defaulted "off". -brad

2 1

[Dovecot] Dovecot 1.0-test52 and LDAP authentication
by Jonathan Salomon 26 Nov '04

26 Nov '04

Hi all! I have upgraded Dovecot 0.99.11 installation that's worked with LDAP to Dovecot 1.0-test52 and I can't get LDAP to work. I noticed the /etc/dovecot.conf is slightly different, so I have adjusted changes. If I use the standard auth (passw & pam) everything works fine, however when I user ldap for auth Dovecot starts but then dies: dovecot: Nov 26 14:14:36 Error: Auth process died too early - shutting down dovecot: Nov 26 14:14:36 Error: child 16454 (auth) killed with signal 11 As far as I can tell the /etc/dovecot-ldap.conf hasn't changed since 0.99.11 and the LDAP server is working properly. What is happening here? I did a 'strace -f dovecot 2>log' because I saw this in the mailing list archive, but it doesn't really tell me anything, so I have someone can tell me what is happening here. I have included the tail below. Thank you in advance! Jonathan [pid 16545] rt_sigaction(SIGTERM, {0x8056330, [TERM], SA_RESTART}, <unfinished ...> [pid 16546] <... sendmsg resumed> ) = -1 EPIPE (Broken pipe) [pid 16545] <... rt_sigaction resumed> {SIG_DFL}, 8) = 0 [pid 16546] --- SIGPIPE (Broken pipe) @ 0 (0) --- [pid 16545] rt_sigaction(SIGPIPE, {SIG_IGN}, <unfinished ...> [pid 16546] write(2, "\1Ffd_send(-1) failed: Broken pip"..., 34 <unfinished ...> [pid 16545] <... rt_sigaction resumed> {SIG_IGN}, 8) = 0 [pid 16546] <... write resumed> ) = -1 EPIPE (Broken pipe) [pid 16545] rt_sigaction(SIGALRM, {SIG_IGN}, <unfinished ...> [pid 16546] --- SIGPIPE (Broken pipe) @ 0 (0) --- [pid 16545] <... rt_sigaction resumed> {SIG_IGN}, 8) = 0 [pid 16546] exit_group(82) = ? Process 16546 detached [pid 16545] open(".", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6 [pid 16545] fstat64(6, {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 [pid 16545] fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 [pid 16545] getdents64(6, /* 2 entries */, 4096) = 48 [pid 16545] getdents64(6, /* 0 entries */, 4096) = 0 [pid 16545] close(6) = 0 [pid 16545] getsockname(0, {sa_family=AF_INET, sin_port=htons(143), sin_addr=inet_addr("0.0.0.0")}, [16]) = 0 [pid 16545] getsockname(1, <unfinished ...> [pid 16547] <... select resumed> ) = 1 (in [5]) [pid 16545] <... getsockname resumed> 0xfef3d050, [28]) = -1 ENOTSOCK (Socket operation on non-socket) [pid 16547] read(5, <unfinished ...> [pid 16545] sendmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 56}], msg_controllen=0, msg_flags=0}, 0 <unfinished ...> [pid 16547] <... read resumed> "0\f\2\1\2e\7\n", 8) = 8 [pid 16545] <... sendmsg resumed> ) = -1 EPIPE (Broken pipe) [pid 16547] read(5, <unfinished ...> [pid 16545] --- SIGPIPE (Broken pipe) @ 0 (0) --- [pid 16547] <... read resumed> "\1\0\4\0\4\0", 6) = 6 [pid 16545] write(2, "\1Ffd_send(-1) failed: Broken pip"..., 34 <unfinished ...> [pid 16547] time( <unfinished ...> [pid 16545] <... write resumed> ) = -1 EPIPE (Broken pipe) [pid 16547] <... time resumed> NULL) = 1101483703 [pid 16545] --- SIGPIPE (Broken pipe) @ 0 (0) --- [pid 16547] time( <unfinished ...> [pid 16545] exit_group(82) = ? Process 16545 detached <... time resumed> [1101483703]) = 1101483703 geteuid32() = 0 geteuid32() = 0 time(NULL) = 1101483703 write(5, "0s\2\1\3cn\4\35ou=Groups,dc=2male"..., 117) = 117 time([1101483703]) = 1101483703 select(1024, [5], [], NULL, NULL) = 1 (in [5]) read(5, "0\f\2\1\3e\7\n", 8) = 8 read(5, "\1\0\4\0\4\0", 6) = 6 time(NULL) = 1101483703 geteuid32() = 0 setgroups32(1, [97]) = 0 open("/etc/localtime", O_RDONLY) = 6 fstat64(6, {st_mode=S_IFREG|0644, st_size=1074, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6f0f000 read(6, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\r\0\0\0\r\0"..., 4096) = 1074 close(6) = 0 munmap(0xf6f0f000, 4096) = 0 chroot("/var/run/dovecot/login") = 0 chdir("/") = 0 setuid32(97) = 0 setuid32(0) = -1 EPERM (Operation not permitted) getgid32() = 97 getegid32() = 97 setgid32(0) = -1 EPERM (Operation not permitted) setrlimit(RLIMIT_NPROC, {rlim_cur=1, rlim_max=1}) = 0 gettimeofday({1101483703, 638988}, {4294967236, 0}) = 0 rt_sigaction(SIGHUP, {0x8056320, [], 0}, NULL, 8) = 0 rt_sigaction(SIGINT, {0x8056330, [INT], SA_RESTART}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGTERM, {0x8056330, [TERM], SA_RESTART}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 rt_sigaction(SIGALRM, {SIG_IGN}, {SIG_IGN}, 8) = 0 open(".", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6 fstat64(6, {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 getdents64(6, /* 2 entries */, 4096) = 48 getdents64(6, /* 0 entries */, 4096) = 0 close(6) = 0 getsockname(0, {sa_family=AF_INET, sin_port=htons(143), sin_addr=inet_addr("0.0.0.0")}, [16]) = 0 getsockname(1, 0xfef8b470, [28]) = -1 ENOTSOCK (Socket operation on non-socket) sendmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 56}], msg_controllen=0, msg_flags=0}, 0) = -1 EPIPE (Broken pipe) --- SIGPIPE (Broken pipe) @ 0 (0) --- write(2, "\1Ffd_send(-1) failed: Broken pip"..., 34) = -1 EPIPE (Broken pipe) --- SIGPIPE (Broken pipe) @ 0 (0) --- exit_group(82) = ? Process 16547 detached

1 0

[Dovecot] [OT] Apple Mail.app access to localhost imap when no network
by Alan Schmitt 26 Nov '04

26 Nov '04

Hello, Sorry for the offtopic subject, but I tried asking this on some Apple mailing lists and could not find an answer there, and as it's related to imap (provided by dovecot), someone might know something about this. The problem is the following: I have a local IMAP server provided by dovecot, so that I can store my mail in maildir format, and read it both using mutt and Apple Mail.app. Mail.app is configured to access localhost:143 to access mail. However, I discovered that when there is no network connection (no ethernet cable plugged in and no wifi network), Mail.app is saying that it's working in disconnected mode and refuses to access the imap server. Would someone have a suggestion as to what to do to allow connected access to localhost when no network is present? I'm very new to OS X (I come from Linux). Thanks a lot, Alan Schmitt

6 12

Re: [Dovecot] dovecot only answers to imap connections
by Mitch Pirtle 25 Nov '04

25 Nov '04

Nope, just sticking with simple pop3 at this point ;-) The second issue I am having is that Thunderbird seems to 'freeze' from time to time on directories that have more than 1000 messages in them. I remember reading earlier that there were some performance tweaks for Thunderbird, but I lost the link :-( I cannot replicate the authentication problem, and will wait to see if it is a layer 8 protocol error (between the ears). Thanks for the help, you have been stupendous! -- Mitch On Wed, 24 Nov 2004 19:01:29 -0700, Saurabh Barve <sa(a)atmos.colostate.edu> wrote: > Are you using simple POP3 or secure POP3? If you are using secure POP3, > then you have to tell the clients that they need to accept your > certificate permanently, not just for that session. Otherwise, the mail > clients will complain about self-signed certificates every time they > log in.

1 0

[Dovecot] Cannot see contents of ~/mail folder
by Saurabh Barve 25 Nov '04

25 Nov '04

Hi, I just installed dovecot-0.99 on my Fedora Core 2 machine. When I start the secure IMAP daemon, I am able to see my Inbox, but not the other folders in the 'mail' folder in my home directory (sent-mail, saved-messages, etc.) These folders were created when I was using pine earlier on the machine. In my dovecot.conf file, I have set: default_mail_env = mbox:~/mail:INBOX=/var/mail/%u I am using Mozilla Mail as my mail client, if that makes a difference. Dovecot seems to be creating a directory called .imap inside the 'mail' folder, where it is storing the inbox and a Trash folder. I have set "mail_full_filesystem_access = no" so that users don't access any of their other files except the mail folder. From what I understand, I don't have to set IMAP path in Mozilla Mail. I tried doing that too, just to try it out, but as expected, it didn't work. What do I need to set in order to see my other folders in the 'mail' directory? Thanks, Saurabh. ------------------------------------------------------------------------ --------------------------- Saurabh Barve Phone : (970) 491-7714 E-mail : sa(a)atmos.colostate.edu System Administrator, Montgomery Research Group, Deptt of Atmos. Sci., CSU, Fort Collins, CO - 80523

4 6

[Dovecot] ssl_ca_file
by Jacob Elder 25 Nov '04

25 Nov '04

I am very fond of Dovecot, but it would be nice to have a more useful SSL implementation. When do you think we'll see a non-beta version that supports ssl_ca_file? I am running 0.99.11-3 from Debian testing. -- Jacob Elder

1 0