similar to: Locking /var/mail/user issue with postfix and dovecot

Hi there, We're using Dovecot version 1.0.7 and Postfix, and since upgrading our Linux box we're getting this in the maillog: Nov 8 07:49:11 server1 postfix/local[27901]: 04B8E7081DA: to=<xyz at xyz.com>, orig_to=<abc at abc.com>, relay=local, delay=19, delays=0.07/0/0/19, dsn=4.2.0, status=deferred (cannot update mailbox /var/spool/mail/abc for user abc. unable to lock

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) Warren Togami warren at togami.com

Hi, I have a problem with my postfix/dovecot configuration, I can't receive mail from outside, i can send a mail from my mail to myself and others, but i can only receive one i send from myself, but when it comes from outside my domains, it dosn't work. Thaks for your help ! Here is my conf : ----------------------------------------------------------------- DOVECOT

Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue.

There are three applications that have their mitts on files on my mail server, which is running AIXV5.3 and UWIMAP and mbox format. The mail folders and INBOXES are native to that machine, but also are NFS exported to a login server and a mailing list server. All three machines are running the lockd daemon. Everybody wants to lock differently 1) procmail (delivering for sendmail), which

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following

I'm running Dovecot 1.1 RC1. I believe I've done all the due diligence for making things working correctly over nfs. But I run into locking issues if I run over nfs. procmail is doing the delivery over nfs. uw-imap was ruining over nfs. dovecot is fine if its on the nfs server (i.e. it has local access to the disk, no nfs) I run into lock deadlocks if I run dovecot over nfs Users

Dear Colleagues, I use exim's appendfile transport, procmail and a local mutt on my system, they all (to my knowledge) use lockfiles when working with mboxes. However, `doveconf | grep lock` says dotlock_use_excl = yes lock_method = fcntl mail_max_lock_timeout = 0 mbox_dotlock_change_timeout = 2 mins mbox_lock_timeout = 5 mins mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl

Hi Slight problem - linux 2.4 running dovecot, Solaris 2.8 home directory server. Full lockd support etc. I had to make the following code patches (at end of mail for clarity) to get dovecot to read the users mbox files at all. 1) fcntl with F_SETLKW will not work against a Solaris 2.8 server as proved with a small test program. Other forms of fcntl (ie F_SETLK) are OK. I noticed there are

HI, > You could set > > syslog_facility = local5 > > and have all the log messages in the messages file. According to the output of command # doveadm log find every type of message goes to the file I was looking at, "/var/spool/maillog". >> So, is it postfix doing the local mail delivery, not dovecot? >> > To answer this question please post relevant

i'm working with exim 4.60, with mbox, and dovecot dovecot-1.0.beta7, and filesystem quotas default_mail_env = mbox:~/mail::INBOX=%h/mbox:INDEX=/tmp/%u lock_method = dotlock fcntl mbox_read_locks = dotlock fcntl mbox_write_locks = dotlock fcntl The home of users is /home/usuaris/user Where place dovecot the lock file?

Hello, Running dovecot 1.1.6 on centOS 5 and RHEL 5. With the settings: pop3_lock_session = yes mail_privileged_group = mail mail_location = mbox:~/:INBOX=/var/spool/mail/%u mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl and /var/spool/mail permissions: drwxrwx--x 2 root mail 4096 Nov 19 10:16 mail/ Trying to connect via POP3 results in this error: --- Nov 19 09:31:01

I've recently upgraded to 1.0.10 in hopes that this problem would go away but no luck. I've got some users at my company with large inboxes on maildir (say 22,000 messages). Their mailboxes are hosted on nfs and dovecot is configured to do dotlocking. Still I see messages like this continually in the logs (sometimes every hour or so): server dovecot: IMAP(user): dotlock

Hello, I'm using dovecot as a mail relay so that I can back up my providers IMAP mail locally. I'm impressed how easy this was to set up, but I'm having a quirk that I would like help with, if possible. There are many weak links in my set-up chain, if you will, but I think I've narrowed the problem. I'll describe my set-up anyway. I'm running dovecot 1.1.4 on ubuntu

Hi All, Our test users re-download the mail they've left on the server when they switch from Qpopper to Dovecot. Qpopper includes the X-UIDL header - X-UIDL: X8V"!E)<"!58?"!"9C"! - on read messages. Any suggestions are appreciated. I've included my dovecot configuration. Thank you, Tristan --- Tristan Tristan Goguen CEO, ILAP? T: 416-250-5600 ext. 205 F:

We've just cut over to a new mail server running Dovecot 1.0.5. The underlying OS is RHEL 5. User mailboxes are stored in Unix mbox format on a local ext3 file system. The MTA on the system is the default RedHat version of Sendmail 8.13.8 with procmail for local delivery. We're using a combination of dotlock and fcntl style locking. The output of "dovecot -n" for this system

Hello, I'd like to make sure my understanding of the mbox locking strategy is correct : - "mbox_dotlock_change_timeout" directive : a process seeing that an already locked (by another process) mbox he want to access hasn't change for this amount of time, allows himself to override the lock ? If it's using fcntl, is it only possible to override ? -

Hi, Problem: Sockets /var/spool/postfix/private/auth and /var/spool/postfix/private/dovecot-lmtp are not created The only error message I get comes from postfix: no auth (SASL) founhd. Takes np wonder, the s ockets don't exist. Any help is welcome. Thanks. Bernd doveconf: # 2.1.17: /etc/dovecot/dovecot.conf # OS: Linux 3.11.10-11-default x86_64 openSUSE 13.1 (x86_64) ext4

I need to backup some of the mailboxes on our system. We are currently using mdbox with zlib compression plugin. The backups need to be maildir without compression. How can I accomplish this using dsync? The following just causes each msg file in maildir to be compressed as well. dsync -f -u user1 backup maildir:/var/tmp/user1 While this just causes the dsync to fail while spewing a bunch of

How does IMAP lock the /var/spool/mail/user file? Here's my problem: I'm writing a script to expire old or oversize mail through a series of archive folders. I don't want to take the whole server down to do this, nor does it seem like I would have to lock the user out entirely if I can manage to emulate the locks correctly. I am able to lock /var/spool/mail/user (and ~user/mail/*)