- dovecot - dovecot.org

[Dovecot] Re: Dovecot inotify problem
by Johannes Berg 22 Aug '05

22 Aug '05

Hi Reuben, I hope you don't mind me copying the dovecot list again. > dovecot: Aug 21 04:08:22 Error: IMAP(reuben): inotify_rm_watch() failed: > Invalid argument Odd. > This is with a 2.6.13-rc6-mm1 release. I've posted to LKML because there is > also a kernel stack produced at one point which looks inotify related (but the > messages above are contant). > See http://www.ussg.iu.edu/hypermail/linux/kernel/0508.2/1180.html and the > followup from akpm. Thanks for the link. I don't think akpm is right, unless something is really odd here. Could you add debugging output for me please? Maybe something like (this is not a patch you can apply, look at line 164 in src/lib/ioloop-notify-inotify.c) ctx->inotify_fd = inotify_init(); + i_warning("inotify_init returned fd %d", ctx->inotify_fd); if (ctx->inotify_fd == -1) { and line 106: IN_CLOSE | IN_MODIFY); + i_warning("inotify_add_watch returned %d", watchdescriptor); if (watchdescriptor < 0) { and line 145: } + inotify_rm_watch("removing wd %d from inotify fd %d", io->notify_context, ctx->inotify_fd); if (inotify_rm_watch(ctx->inotify_fd, io->notify_context) < 0) Or something similar. If that doesn't help and output looks consistent (we're not removing a watch descriptor from a wrong fd etc.), can you try removing the fd_close_on_exec call please (line 171)? I don't know if that could cause trouble (I don't even think that the imap binary ever forks) but you never know. johannes

2 4

[Dovecot] Created Testimonials Page in wiki
by Marc Perkel 22 Aug '05

22 Aug '05

I created a testimonials page. Feel free to add to this. http://wiki.dovecot.org/moin.cgi/Testimonials -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

6 7

Dovecot IDLE problem (was Re: [Dovecot] inotify support in dovecot)
by Reuben Farrelly 22 Aug '05

22 Aug '05

Hi, I've come across some possibly buggy behaviour with regards to Dovecot and the use of the IDLE keyword. Found this while testing out inotify support for Johannes - although after asking him and him reproducing it, he is of the opinion that it's not a inotify specific problem. The behaviour is that when the client is idling, Dovecot seems to only alert to the first new message received, and if a subsequent new message comes in before the client finishes idling, that second new message is not notified to the connected client. To reproduce: $ maildirmake /tmp/imap-test $ cat >/tmp/1 <<EOF From: test To: test Subject: test test! <Ctrl-D> $ MAIL=Maildir:/tmp/imap-test /usr/libexec/dovecot/imap ... A SELECT INBOX B IDLE [now, in a different terminal, copy /tmp/1 to /tmp/imap-test/new, you should instantly be notified of it in your imap session] ** Dovecot correctly responds with: * 1 EXISTS * 1 RECENT [if a second message is delivered, eg by copying /tmp/1 to /tmp/imap-test/new/2 then you should be notified as well, but this never occurs] DONE C LOGOUT $ Timo - what do you think? Reuben

4 5

[Dovecot] Dovecot Feature List
by Marc Perkel 21 Aug '05

21 Aug '05

I've added a new page to the Wiki that's sort of a Dovecot feature list overview. What I have is a good start but if anyone wants to jump in and contribute, go for it. I added it because there isn't any other place I saw that gives new people an overview of what Dovecot does. I personally passed Dovecot over a few times before somone pointed me back to it. http://wiki.dovecot.org/moin.cgi/DovecotFeatures Just my way of giving something back to the Dovecot community. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

1 0

[Dovecot] Failed authentication to a mysql database
by Alexandru Craiu 21 Aug '05

21 Aug '05

Hi, I use devecot-1.0.alpha1 and I can't connect to mysql when user have password. If user don't have password I can connect to mysql server. Aug 21 08:28:30 ca dovecot: Dovecot v1.0.alpha1 starting up Aug 21 08:28:32 ca dovecot: auth-worker(default): mysql: Connect failed to localhost (syscp): Access denied for user 'syscp'@'localhost' (using password: YES) - waiting for 1 seconds before retry I have a system and with ssh access. Best regards, Alexandru Craiu ________ Information from NOD32 ________ This message was checked by NOD32 Antivirus System for Linux Mail Server. part000.txt - is OK http://www.nod32.com

2 1

[Dovecot] Dovecot Problem
by Rob Kettle 21 Aug '05

21 Aug '05

Hi, is there a way to get Dovecot to output a Logout line that includes the IP address that has logged out please ? This would make it a lot easier to use with pop-before-smtp. Thanks Rob -- This message has been scanned for viruses and other dangerous content by MailScanner, and is believed to be clean.

2 1

[Dovecot] Sieve Documentation
by Marc Perkel 20 Aug '05

20 Aug '05

Where do I find the docs on Dovecot Sieve and is there a global sieve config file that I can configure for everyone?

2 1

[Dovecot] 1.0 alpha1 and postfix dovecot auth
by Kevin 19 Aug '05

19 Aug '05

Does the postfix-2.2.1-dovecot-auth patch not work with 1.0alpha1? I was using the stable branch and it was working fine. Tried out 1.0alpha1 and now when I connect to postfix it logs this error. Aug 19 11:25:19 redefine postfix/smtpd[17343]: fatal: SASL: connect failed: No such file or directory I've tried with postfix-2.2.4 and 2.2.5. Right now I'm using auth default but I also tried auth default_with_listener. Anybody else using this patch seeing this?

1 0

Re: [Dovecot] lock file
by Obantec Support 19 Aug '05

19 Aug '05

----- Original Message ----- From: "Simon Waters" <simonw(a)zynet.net> To: "Obantec Support" <support(a)obantec.net> Sent: Thursday, August 18, 2005 12:33 PM Subject: Re: [Dovecot] lock file > On Thursday 18 Aug 2005 12:19 pm, Obantec Support wrote: <snip> > > What is your question? > > Yes it is a lock file, by default (if you must use mbox) Dovecot overrides > them in 30s I believe. > > Either work out if it is genuine, and delete it if not. > > You only need to use dotlock locking if you are using NFS (or similar), and > using "mbox". Hopefully this only affects a small number of big mail servers, > and most of them would presumably switch to maildir when deploying dovecot > over NFS anyway. > > Hi not using NFS. my question is what is it, why is it happening and how do i get my users mbox working again. as soon as i delete it it comes back with 1B contents 0 Mark

2 2

[Dovecot] test80: assert/core debug info
by Jeff A. Earickson 19 Aug '05

19 Aug '05

Timo, Attached is gdb information from core dumps related to the following assert in test-80: IMAP(username): file mbox-sync-update.c: line 442 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid_broken || ctx->mail.uid == mail->uid) My setup: Solaris 9, mbox format. test-80 compiled with gcc 4.0.1 using the following configure options: CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot.test80 --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl --with-rawlog --enable-debug Note that system mailboxes are NFS mounted from the mail server to the IMAP server, which may cause you to groan. The attached debug session was done with gdb 6.3, also compiled with gcc 4.0.1. Note that some of the variables I queried were undefined (or otherwise unknown to gdb). The variable "first_nonexpunged" at line 470 of mbox-sync-rewrite.c is undefined, and I wondered why it was scoped so locally. The value of mails[idx] being undefined at mbox-sync-rewrite.c:353 also seems like bad news. Hope this helps. Jeff Earickson Colby College

3 6