similar to: Locking foolishness - Better info

I'm working on getting Dovecot set up on my school's mailserver, as an IMAP and POP server. Everything is going well, move over to maildir went well, and all that... The catch: When I coverted from mbox to maildir (as part of this whole process), I put the Maildir folders under user home dirs -- and the home dirs are mounted via NFS from a server. This is for reasons of space as well as

I have a really weird problem. To whit: I compiled dovecot 0.99.10 on two different systems: a linux-ppc box running Debian, and a Mac OS X Server v. 10.2.8. It compiled fine on both. The same Maildir's are being served up on both -- the OS X server exports home directories to the clients via NFS. BUT the OS X box orders mailboxes this way: INBOX Deleted Items Sent Items . . . And the

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

/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 all, I have some machines running FreeBSD and dovecot deployed. User's home dir is on NFS mount and I've found that dovecot only works with dotlock file locking mechanism, fcntl and flock failed. Now it causes problem with thunderbird (thunderbird is cachine connections) waiting forever and I noticed that dovecot is trying to acquire a lock but unsuccessful since the lock file is in

I just migrated from a FreeBSD/Sendmail/UW-IMAP setup to RHEL 3/Postfix/Dovecot (1.0a5 currently). Both systems used Procmail as the final delivery agent (into inboxes or . Since the changeover, things have *mostly* been going ok, but I've been having some problems that I think are locking-related. I'm getting reports from users about IMAP hangs (mostly from Thunderbird). Sometimes I see

Hi All, I upgrade my mail server from doveot 1.1.7 to 2.2.13 and encounter problems with file locking issues. The server has around 400 clients using IMAP and I get tons of "Warning: fscking index file .. dovecot.index" and "Error: Corrupted transaction log". Sometimes the transaction log problem is followed by "Panic: file mail-transaction-log.c: line 350

I have to make dotlock work because this openwebmail thing only supports one of dotlock or flock, but procmail delivery does dotlock and fcntl. procmail correctly creates a dotlock file in /var/spool/mail/username.lock when delivering, I can watch this with `while :; do ls -la | grep lock; done`. It works fine when lock_method=fcntl, but no dotlock file shows up in /var/spool/mail.

On Tue, 2018-10-09 at 15:30 +0200, Selmeci Tam?s wrote: > On Tue, 9 Oct 2018 12:08:00 +0200 Sami Ketola <sami.ketola at dovecot.fi > > wrote: > > > How do you deliver then mails to the server?? > > > > OpenSMTPD and Dovecot run on the same machine. OpenSMTPD receives > incoming mails and stores them in a mailbox (/var/spool/mail/user). > Dovecot then

Hi All, We're currently in the process of migrating from a NetApp storage to a ZFS storage, both shared over NFS. We've ran into some problems which were solved by switching to dotlocks instead of flock. But now there's one problem left with the dotlock method. When connecting to Dovecot/IMAP, and moving messages from one folder to another, it is very slow and I'm suspecting this

Hi, i have a problem with dovecot and quotas, when a user has over-quota he can't access the mail account to download mails and solve the quota problem. I'm using debian sarge (stable) and quota v1 (vfsold), i have installed dovecot in debian way apt-get install dovecot dovecot-common dovecot-pop3d users only can access via pop3 to their mails. This is the error i get when i try to access

Hi All, after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of messages about corrupted index files in the syslog ("Error: Corrupted transaction log" and "Warning: fscking index file .. dovecot.index". I tried flock and even dotlock, but the problems persist. The system is a VPS with an overlay filesystem which did work flawlessly with the old dovecot

Hey, I am setting up Dovecot on Debian with Postfix. I am telling Dovecot to use maildir:~/Maildir but it persists in dumping mail in mbox format in /var/mail/username. Can anyone suggest ideas? My config file is attached. Thanks Kevin -------------- next part -------------- ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment #

Steven Vaughan-Nichols at Ziff-Davis said: | Unlike all other previous Microsoft operating systems, XP | Home will simply not work in an office network environment | with NetWare, NT, Samba, or Windows 2000 servers. Period. | You simply can't connect to the servers' domains or their | file/print services. Which sounds like they took the SMB client out... | XP Home also has a built-in

Folks - I've been using Dovecot for some time now, but have only recently upgraded to 1.0alpha4. I'm struggling to get my configuration right and I'm seeing some truly bizarre issues. My Setup: Solaris 2.8 / Thunderbird / Procmail / Dovecot 1.0alpha4 My mail setup is only for me, so Dovecot runs at an odd port and under my userID. All my mail is in my home directory, which

Hi, I am running dovecot 0.99.10.4 on SuSE 9. I installed it using apt-get from the gwdg repository. The dovecot service is configured to start at boottime in run level 3 and 5. However, it dies immediately with this error (/var/log/mail.err): dovecot: Login process died too early - shutting down Starting the service afterwords from a prompt as root with the command: /etc/init.d/dovecot

Hi, I'm using dovecot 2.0.13 that ships with Ubuntu 11.10. I tried setting up a shared namespace as documented in the wiki to enable the sharing of a mailbox between two users. I have a Maildir(++) directory for each user. Each user has a system account. The Maildir of each user is owned by the user's system account and group read/writable by the group mail (hence

I have a user who has Mac OS 10.4.8 with Entourage X. The email server is sendmail 8.13.8 and is setup to use STARTTLS on a CentOS 4.4 system. It appears from everything I have googled that only Entourage 2004 will properly function with STARTTLS. Has anybody any experience with Entourage X ... specifically is there something I am missing regarding the CentOS server setup or are all Entourage

I having a hard time working this out, I've looked in the wiki and various other places but am still cueless (stupid me) mercury:/etc/dovecot# imtest -a graeme 203.96.154.204 S: * OK dovecot ready. C: C01 CAPABILITY S: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN S: C01 OK Capability