similar to: userdb static and doubled homedir problem

While experimenting a bit, I found that for some reason, locking indexes with flock is problematic, but only if user is taken from passwd-file. The host system is openbsd 3.9, dovecot's configuration is added at the bottom. Authentication is from two places - first from mentioned passwd-file, then from passwd file using bsdauth (in this case, there're no problems with flock). So, if

Originally I've thought that this is related to INBOX field, but it turned out it happens only when you specify mbox. Consider following passwd-file: testms::10000:10000:imap,,,:/home/vmail/ppgk.com.pl/testms/./::userdb_mail=mbox:~/Mail:INBOX=/home/vmail/ppgk.com.pl/%u/inbox or following line from userdb static: args = uid=10000 gid=10000 home=/home/vmail/ppgk.com.pl/%u/./

Recently I've made the post about "double homedir" problem, but I couldn't recreate it later. Here're the exact steps to make it happen (configuration is at the bottom): 1) set configuration as below with passwd-files 2) clean testms dir (not necessary though) 3) reload dovecot (HUP is enough) 4) access the server with any client using testms user (make sure no other

I'm not sure if it's even intended to work in this particular case, but there's a problem when chroot is explicitely defined and rawlogging is used. Rawlog respects chroot point, without being actually chrooted. Consider configurtion as below, with two cases (dovecot.rawlog dir is of course created earlier, with appropriate uid/gid). 1) dovecot.userdb:

Dovecot 1.0.3 Deliver is saying this on two specific emails. Other emails to these 2 users are going through fine. Looking at the mail headers the only thing questionable I see is: From: "AMS Publication Division"@ams.org Is this the problem? # 1.0.3: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3):

Ok, I've ALMOST got this working ... I can run deliver as a user, but when I try using it as the default delivery agent from sendmail, I get deliver(userid): net_connect(/var/run/dovecot/auth-master) failed: Permission denied Does deliver run as root, as the recipient's ID, sendmail's ID or sendmail's GID? (I'm running freebsd) Or am I totally clueless ?? Here is dovecot

I apologise if this is a faq but I couldn't find it in the archives. FreeBSD math 4.11-RELEASE-p26 FreeBSD 4.11-RELEASE-p26 dovecot version 1.0.3 x86 cpu local disk (ufs) Trying to run "deliver" from user's .forward file. sendmail configured with smrsh, forward file says: | "deliver" Imap seems to work fine, but deliver says: deliver(rw): mbox read/write lock list

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've spent the past couple of hours trying to figure this out by checking the wiki and googling, but haven't come up with anything that works yet. I just installed dovecot 1.0.14 with the quota-rewrite (1.09) patch and i'm trying to get the quota overridden via a passwd-file type userdb. I had 1.0.13 without the new quota style patched

Hi, Since the 23rd of March, we encounter mailbox corruption for some users (15 out of 5000) using POP mainly via Thunderbird. Symptoms are : -users can login but fail to receive new mails and fail to read their inbox -Dovecot.log : ar 29 11:00:06 Error: POP3(user_login): Couldn't init INBOX: Mailbox isn't a valid mbox -The mailbox start with either 'FFrom or

Hi, We are using dovecot for some times (a little before 1.0), for IMAP and (a little for the moment) deliver. We have ~20000 logins/day, Maildirs are over NFS (with indexes too, for the moment...) Up to 1.0.5, we sometime have this error in maillog: ________________________________________________________________________ Nov 1 13:55:41 tic dovecot: IMAP(login): file mail-index-view-sync.c:

Today I've been trying to get dovecot (1.0 rc2) to use certificates for client side authentication. If my memory serves right, beta8 had no problems with it (although it was some time ago and on different machine). Similar setup works perfectly well for postfix (for authentication that is, on the same machine). Originally I thought I overdid some certificate settings (keyUsage, nsCertType,

Hello, I'm preparing to convert from qpopper + UW-IMAP to dovecot. So far testing has gone very well. One problem we haven't figured out is that long-running POP sessions keep the mailbox locked, so that the MDA times out while trying to deliver. We're using "maildrop" as our MDA if that matters. We don't see this issue for dovecot IMAP sessions. During long-running

others have found this problem ? this possible bug can be used by user in that way that one password login can use 2 maildirs in filesystem effitively give them all space qoutas and lost of other goodies so to speak: foo at example.com with a password can login with fOO at example.com and fOo at example.com add more chars to get more mailbox :/ confirms ? i found the problem when i had

Hello all, I am struggeling to get my Dovecot SASL to work within postfix. I have used the configuration example listed on the main-site of dovecot and it basically isn't giving me any success at all. I am probably missing something easy, but after spending a few days testing and walking through everything I could think about I thought figured it was better to ask :) Hope someone can point me

Can dovecot-1.1 deliver work with static userdb? I'm currently running dovecot-1.0.12 and postfix-2.4.6, with virtual users' maildirs all owned by vmail and mail_location = maildir:/var/mail/%Lu. The following definition of the dovecot transport in postfix/master.conf works fine with dovecot-1.0: dovecot unix - n n - 1 pipe flags=DRh

Hi all, I'm using 1.0.beta3 and having problems using userdb prefetch in conjuction with passdb sql. Here are my mail logs when I log to virtual account "testuser at mydomain.com" by doing "telnet localhost 143": Mar 26 15:15:47 imapserver dovecot: Dovecot v1.0.beta3 starting up Mar 26 15:15:49 imapserver dovecot: auth-worker(default): mysql: Connected to (null) (mail)

Commit-ID: 11bd4ea5f3d960c4d208180deae91d88aa940149 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=11bd4ea5f3d960c4d208180deae91d88aa940149 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 21 Jan 2019 03:39:34 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Mon, 21 Jan 2019 03:45:04 +0000 [klibc] fcntl: Fix struct flock

Dear all, > Caveats > ======= > Features which OCFS2 does not support yet: > - extended attributes > - readonly mount > - shared writeable mmap > - loopback is supported, but data written will not > be cluster coherent. > - quotas > - cluster aware flock <---------------------------------------- >

Dovecot version dovecot-1.0.rc14-7 (opensuse) Postfix is using Dovecot LDA. I'm getting this error message, and I guess it's going to be a problem on my next task, which is to set up sieve scripts. Is there something wrong/contraditory on my config or I forgot something? I want: /var/dovecot-tests/: where user's inbox resides /var/dovecot-tests/home/: home dir (users will not be

Hi, I am trying to understand file locking and share modes. I am using RedHat Enterprise Linux 4, with kernel 2.6.9-55.ELsmp, samba-3.0.10-1.4E.11 and Windows XP. In particular I am looking at a machine running Linux exporting its local filesystem using Samba, with a Windows client accessing the file share. If I use byte range locking (fcntl() on Linux, LockFile() on Windows) things work as