Re: [Dovecot] Small typo
On 3.11.2007, at 7.54, Abhijit Hoskeri wrote: There is a small typo in src/lib/network.c line 624 return "A non-recovable name server error occurred"; Fixed: http://hg.dovecot.org/dovecot-1.0/rev/90b7671c8f2e Sorry about the pedantry. BTW, I am getting this error whenever I am trying to resolve a name from inside dovecot, but I can using the system tools. I am trying to get the proxying code to use hostnames as well as IP addresses. The problem is most likely that login process is running chrooted. login_chroot=no would help. Another way would be to do this in dovecot-auth, but if it's done there it should be done asynchronously (or in auth worker processes) and doing async dns lookups would require some async dns library.. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Small typo
On Sat, Nov 03, 2007 at 12:15:31PM +0200, Timo Sirainen wrote: > The problem is most likely that login process is running chrooted. > login_chroot=no would help. It does - thanks a lot, I had been struggling for hours! > Another way would be to do this in dovecot-auth, but if it's done > there it should be done asynchronously (or in auth worker processes) > and doing async dns lookups would require some async dns library.. Now, I think I understand why you had not done something like this already. * Copying some files into the chroot may be one way... * When you say auth-worker processes, do you mean I need to create a separate helper program just to do DNS lookups? Let me try... :-) There is one more thing I need to do - create a config variable/file which contains the list of 'host' values which refer to the local system - then we will be set. -Abhijit
[Dovecot] Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged
After updating Dovecot, one of my servers keep spamming these errors in the log: dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Getting size of message UID=4402 failed dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Getting size of message UID=4402 failed dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged The funny thing is the mailbox is empty, there are no mails in the folder that should be needed to be parsed It was perfectly fine before I updated, and the permissions on the folder is correct. It only affects some mailboxes as well. Any ideas? // Tom
[Dovecot] IMAP vs system username logging with checkpassword auth
Hi
After upgrading to dovecot 1.0.7 I noticed that the actual username is
no longer logged, but rather the system user (in my case 'vmail')
under which my virtual set-up runs. Now I'm unable to see which
virtual users log in. Any pointers on how to configure dovecot to log
the actual username given during the IMAP dialogue would be
appreciated.
My dovecot.conf includes the following:
auth default {
mechanisms = plain
passdb checkpassword {
args = /var/qmail/bin/qmail-vauth
}
userdb prefetch {
}
user = auth
}
An example logfile entry:
2007-11-03 15:41:56.027191500 dovecot: Info: imap-login: Login:
user=, method=PLAIN, rip=192.168.0.141, lip=192.168.0.10, TLS
Re: [Dovecot] IMAP vs system username logging with checkpassword auth
On Sat, 2007-11-03 at 18:14 +0200, dale gallagher wrote:
> After upgrading to dovecot 1.0.7 I noticed that the actual username is
> no longer logged, but rather the system user (in my case 'vmail')
> under which my virtual set-up runs.
Upgrading from what version? I don't think I've changed anything for a
long time related to this.
> auth default {
> mechanisms = plain
> passdb checkpassword {
> args = /var/qmail/bin/qmail-vauth
> }
..
> 2007-11-03 15:41:56.027191500 dovecot: Info: imap-login: Login:
> user=, method=PLAIN, rip=192.168.0.141, lip=192.168.0.10, TLS
It looks like your qmail-vauth changes $USER environment to "vmail",
which causes dovecot-auth to change the username internally. Since some
people really want this feature, you'll probably have to write a wrapper
checkpassword that unsets $USER before it calls Dovecot's
checkpassword-reply.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Couldn't init INBOX: Can't sync mailbox: Messages keep getting expunged
On Sat, 2007-11-03 at 14:20 +0100, Tom Sommer wrote: > After updating Dovecot, From what version? > one of my servers keep spamming these errors in > the log: > > dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Getting size of > message UID=4402 failed > dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Getting size of > message UID=4402 failed > dovecot: Nov 03 14:14:18 Error: POP3([EMAIL PROTECTED]): Couldn't init INBOX: > Can't sync mailbox: Messages keep getting expunged > > The funny thing is the mailbox is empty, there are no mails in the > folder that should be needed to be parsed So cur/ and new/ directories are empty? What does dovecot-uidlist's 4402 entry contain? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Small typo
On Sat, 2007-11-03 at 17:25 +0530, Abhijit Hoskeri wrote: > > Another way would be to do this in dovecot-auth, but if it's done > > there it should be done asynchronously (or in auth worker processes) > > and doing async dns lookups would require some async dns library.. > > Now, I think I understand why you had not done something like this already. I hadn't actually even thought this far. My main concern was that the DNS lookups are synchronous without a separate library. > * When you say auth-worker processes, do you mean I need to create a > separate helper program just to do DNS lookups? No, I mean some passdbs in Dovecot are already set with blocking=TRUE flag, in which case Dovecot uses separate "dovecot-auth -w" processes to handle them. But if you're looking up hosts only from files, or if you assume that your DNS lookups are really fast always, you can just ignore this. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] *notify config for 1.0.x doesn't enable inotify
On Fri, 2007-11-02 at 20:42 +0100, Paolo wrote: > indeed, I spent a while to convince the autoconf to look that up, but then I > realized the problem isn't the path, the test program always fails, simply > because the new defs have been splitted in the 2 files mentioned in the wiki, > the problem being that inotify.h doesn't #include inotify-syscalls.h on its > own, and compile fails for undefined functions, eg inotify_add_watch(), which > instead are defined in the single linux/inotify.h. If you do like the wiki says, you should have only a single inotify.h file containing also inotify-syscall.h's contents. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] *notify config for 1.0.x doesn't enable inotify
On Sat, Nov 03, 2007 at 11:23:57PM +0200, Timo Sirainen wrote: > > instead are defined in the single linux/inotify.h. > > If you do like the wiki says, you should have only a single inotify.h > file containing also inotify-syscall.h's contents. > ahh - now I see it - too small a screen, didn't notice the '>> inotify.h' ok, sorry for the noise :] Anyway, I had already recompiled changing back to (distro's kernel-headers pkg) linux/inotify.h as I see little or no point in the sys/notify.h change. As long as one's not using latest, newest glibc which (iirc) has inotify.h on it's own, that is. Not my case till, I guess, Debian Etch moves to oldstable. thanks -- paolo GPG/PGP id:0x1D5A11A4 - 04FC 8EB9 51A1 5158 1425 BC12 EA57 3382 1D5A 11A4
