similar to: "userdb didn't return a home directory" with v1.1.7

Hi all, I am running Dovecot v1.1.7 in a relatively quiet and calm environment. Suddenly overnight cron job has started throwing out errors like: /usr/sbin/dovecot --exec-mail ext /usr/lib/dovecot/expire-tool Error: userdb(user1 at mail.example) didn't return a home directory Error: userdb(user2 at mail.example) didn't return a home directory Indeed, running this command produces:

http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig I should have released this earlier since v1.1.6 had that annoying startup problem, but surprisingly few people complained about it so I kind of forgot about it then. BTW. v1.2 progresses nicely. Now that shared mailboxes are finally fully supported, there aren't any widely used IMAP

http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig I should have released this earlier since v1.1.6 had that annoying startup problem, but surprisingly few people complained about it so I kind of forgot about it then. BTW. v1.2 progresses nicely. Now that shared mailboxes are finally fully supported, there aren't any widely used IMAP

Hello all, sorry, I'm new to Wine and Debian distribution therefore this simple question. Could you, please, share some advice or point me to a right direction on how to compile and assemble the latest wine packages on Debian stable? There are dependencies which cannot be met with "stable" (gcc-4). Also, because of wine 0.9.3 dependencies on gcc-4, is it possible to assemble a

The problem is the file glob on line 344 in convert_subscriptions() # read updates from the directory my %updates; foreach (<$keyword_dir/*>) { This isn't going to pick up any files beginning with a dot, so most of the update files in the courierimapkeywords directory are going to be skipped.

Hi there, I'm fairly new to libvirt and LXC, please forgive my ignorance. I was looking for a graphical tool to manage LXC containers and noticed that libvirt has support for LXC. Actually, I expected libvirt to be able to display and manage LXC hosts much like KVM. But it does not happen this way. The only thing I can see with virsh/virt-manager is storage pool with LXC containers, but not

Hi, all. I upgrade to 1.1.6, but the same config didn't work now. Error message while start dovecot: ----<---- Starting Dovecot Imap: Fatal: userdb didn't return a home directory, but mail location used it (%h): /%Lh/%Ld/%Ln/:INDEX=/%Lh/%Ld/%Ln/ Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /etc/dovecot.conf ----<---- Here is my dovecot.conf

dovecot-request at dovecot.org demis ki:: > Send dovecot mailing list submissions to > dovecot at dovecot.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > or, via email, send a message with subject or body 'help' to > dovecot-request at dovecot.org > > You can reach the person managing

hi Today I have been in a puzzling fight with 2 dovecot versions that I would like to ask some comments on. The situation is this: - I have a considerable mail archive in mbox format (yes, I know, but that is what I have..). - My mail reader is mutt 1.5.20 by the way. - Some of these mbox files have names like firstname.initial.lastname Note the . seperating the parts of the email-ers name.

On Nov 30, 2010, at 5:02 PM, Zhanyong Wan (λx.x x) wrote: > Thanks for the comments, Chris! Glad that we are making progress. > > I'll make most of the edits you suggested later today. Before that, > there are a couple of high-level points I'd like to go over with you. > > 1. I totally agree that the biggest benefit of a naming convention is > uniform APIs. On

I am new to LLVM and couldn't find any llvm-user list, so I am posting my user question here, sorry. I am trying to create a simple "puts" call accepting the static string, with the code below. The last line (CallInst::Create) fails with an assert: "Calling a function with a bad signature!" Because the type of function is void(u8*) and the argument supplied is:

On Tue, Nov 30, 2010 at 5:07 PM, Chris Lattner <clattner at apple.com> wrote: > > On Nov 30, 2010, at 5:02 PM, Zhanyong Wan (λx.x x) wrote: > >> Thanks for the comments, Chris!  Glad that we are making progress. >> >> I'll make most of the edits you suggested later today.  Before that, >> there are a couple of high-level points I'd like to go over

Hi Chris, I've uploaded a new patch to http://codereview.appspot.com/3264041. It's also attached to this message. I think I've addressed all your comments, except "when in doubt, an enum should be a 'Kind'". I don't think I fully understand that point, and it strikes me as a bit ad hoc for the coding standards. Do we really want it? If you feel that's

Thanks for the comments, Chris! Glad that we are making progress. I'll make most of the edits you suggested later today. Before that, there are a couple of high-level points I'd like to go over with you. 1. I totally agree that the biggest benefit of a naming convention is uniform APIs. On the other hand, an inconsistent local naming style hurts the productivity of contributors and

A recently found security hole in Cyrus Sieve exists also in Dovecot, because Dovecot's Sieve plugin is based on libsieve from Cyrus project. I also found and fixed a few additional buffer overflows that I can't really understand why I hadn't noticed/fixed before. This security hole affects all installations that give their users any kind of ability to modify their Sieve scripts. Even

A recently found security hole in Cyrus Sieve exists also in Dovecot, because Dovecot's Sieve plugin is based on libsieve from Cyrus project. I also found and fixed a few additional buffer overflows that I can't really understand why I hadn't noticed/fixed before. This security hole affects all installations that give their users any kind of ability to modify their Sieve scripts. Even

Hi, I read a lot of howto's and I got problems with LDAP and Dovecot to work together. I'm using: Gentoo Linux 2008.0 hardened Dovecot 1.1.7 Kernel 2.6.26 OpenLDAP 2.3.43 My dovecot-ldap.conf is: uris = ldaps://auth.mydomain.com:636 auth_bind = yes auth_bind_userdn = uid=%u,ou=People,dc=mydomain,dc=com ldap_version = 3 base = ou=People,dc=mydomain,dc=com deref = never scope = subtree

On Nov 29, 2010, at 11:07 AM, Zhanyong Wan (λx.x x) wrote: > C++ is such a complex language that no single naming convention will > be able to cover all cases. Therefore we aim at a reasonable default > that works for the majority of the cases. As Chris put at the > beginning of the coding standards, "no coding standards should be > regarded as absolute requirements to be

On Apr 5, 2013, at 9:19 PM, Jonathan wrote: > I got the following compile error. Did the message-arrays.m can be compiled into .bc? Or need include something for Object C language compile. Those are warnings, not errors. They otherwise compiled just fine. You should have a bitcode file named '1.ll' from each of those commands. Chip > > Jonathan > >

For lambdas, you have more contexts to confuse yourself, so why would a discriminator like '_' not be helpful here? David On Mon, Oct 13, 2014 at 5:10 PM, Chandler Carruth <chandlerc at google.com> wrote: > > On Mon, Oct 13, 2014 at 4:42 PM, Richard Smith <richard at metafoo.co.uk> > wrote: > >> On Mon, Oct 13, 2014 at 4:25 PM, Xinliang David Li