Thanks for the hint. I enabled 'socket listen' it in dovecot.conf as you pointed it out.
Now dovecot.err log has these error messages: May 04 14:57:19 deliver(us...@some_domain.com): Error: User us...@some_domain.com is missing UID (set mail_uid) May 04 14:57:19 deliver(us...@some_domain.com): Error: User us...@some_domain.com is missing UID (set mail_uid) May 04 14:57:25 deliver(us...@some_domain.com): Error: User us...@some_domain.com is missing UID (set mail_uid) I tried to set necessary mail_uid in dovecot-sql.conf in user_query: user_query = SELECT maildir as mail, 51 as userdb_uid, 51 as userdb_gid, 51 as mail_uid FROM dovecot_email_maps WHERE email = '%u' However it didn't help. I see the same messages in dovecot.err log Could somebody clarify for me where do I have to specify mail_uid in this case? Thanks in advance, Alex On 05/04/10 14:20, mail...@securitylabs.it wrote: > Il 04/05/2010 23:14, Alex ha scritto: >> Hello folks, >> I was trying to set up Dovecot deliver LDA instead of Postfix default >> virtual LDA >> >> >> May 04 10:43:10 deliver(some_addr...@some_domain.com): Error: userdb >> lookup: connect(/var/run/dovecot//auth-master) failed: No such file or >> directory >> > > Hello, I think you are missing the master authentication socket in > yout dovecot.conf > > http://wiki.dovecot.org/LDA > > Under Virtual users: > > auth default { > .. > socket listen { > # Note that we're setting a master socket. SMTP AUTH for Postfix > and Exim uses client sockets. > master { > # Typically under base_dir/, if not the directory must be created. > path = /var/run/dovecot/auth-master > > # Auth master socket can be used to look up userdb information for > # given usernames. This probably isn't very sensitive information > # for most systems, but still try to restrict the socket access > if possible. > mode = 0600 > user = vmail # User running deliver > #group = mail # Or alternatively mode 0660 + deliver user in > this group > } > } > .. > } > >