similar to: Dot Lock probelm resolution

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

After V1.2 had been up for a while, I started seeing tons of syslog error messages like this: Nov 5 09:11:52 mercury mail:err|error dovecot: IMAP(sdean): stat(/var/dcindx/sdean/.imap/DadEstate) failed: Permission denied (euid=202(sdean) egid=200(hcrc) missing +x perm: /var/dcindx) Ownernship and Permissions are: The index filesystem 2726 root at mercury:/var/dcindx ## ls -ald drwx--S---

As I explained, I want to be able to run a second instance of DC through another port to do testing while not interrupting the users using the primary instance in the the regular port. I was instructed to create a second config file with different listen ports and a separate base_dir. I did so and invoked dc with -c pointing to dovecot2.conf. Jun 7 10:04:23 mercury mail:info dovecot:

I've built a new mail system with Centos 6.5, and I'm running fetchmail - sendmail - procmail to maildir. I have all of this working at the moment.(I know, postfix was the default, but for lots of other reasons, I switched, and that isn't an issue, I don't think). I am using dovecot as an imap server. Procmail won't update indexes during email delivery, so I'm having some

I am bringing more people onto Dovecot...and am beginning to see syslog error messages I've never seen before...what are they/are they critical? 1 =========================== > Jun 12 09:53:21 mercury mail:err|error dovecot: IMAP(gregory): Corrupted index c > ache file /var/dcndx/gregory/.imap/INBOX/dovecot.index.cache: indexid changed This has the same date stamp as the user's

Last Wednesday at 12:21 I made this switch, which seemed to be uneventful. In any case, no user has reported problems since the migration. Not content to leave well enough alone, this morning I scanned the syslog and maillog for dovecot related errors. What I found was that: Before the Migration=========================== I saw a lot of SSL errors that look like this: > Jan 14 11:49:23

Our DC has been using a Verisign certificate. Over the past year, we've been using a Digicert Wildcard Plus certificate for almost all of our machines, and I wanted to switched over our DC mailserver. I used the following command to generate the CSR and key: openssl req -new -newkey rsa:1024 -nodes -out star_bard_edu.csr -keyout star_bard_edu.key -subj "/C=US/ST=NY/L=ourtown/O=Bard

So much changes in this migration that the ideal way to do it would be to begin with a few users or a department, then migrate the users affinity group by affinity group: first an institute or so, then the faculty, then the staff, then the students, moving to bigger and bigger groupings as the bugs work out of the migration and the move becomes more assured. We use sendmail and procmail.

I am looking to migrate my DC V1.2 from mbox to maildir format....and want to do this in stages, user group by user group rather than in one horrendous fell swoop....since I'd rather fell things didn't happen. Since I'm running sendmail/procmail, I can change the ~/.procmailrc to change the writing of the INBOX, but the IMAP mail location access info is knottier when one wants to

I have a 6.5 machine that had everything set up and working correctly (fetchmail, sendmail w/ starttls, procmail, spamassassin) but the MB cratered. I bought a new machine, and installed Centos 6.6 and all is not well. I used the config from the previous incarnation (via backups) for fetchmail (works fine), sendmail (works fine for sending via relay and tls), but procmail now refuses to pick up

My production DC machine owns the mail filesystems and is running DC V1.0.15 and mbox folder format. I am looking to test V1.1.3 on another machine, which NFS mounts the mail filesystems, but has its own local index FS. I have made this test environment my default connection in TBird, and it seems to work just fine. Also, I have made sure that my TBird client isn't connecting to the

From reading the wiki for a filesystem quota, I took my shot at 1) building my binaries using the mods in AIXPluginsSupport 2) changing dovecot.conf and 3) putting the plugins in the library But I'm getting this error message when I invoke dovecot: Plugin imap_quota not found from directory /usr/local/lib/dovecot Error: imap dump-capability process returned 89 It would seem that a) I have

I need to have multiple invocations of dovecot running, one for productions and then one or more for test/dev, doing things like trying different authentication methods, getting quota working, etc. I knew how to do this with inetd, but I have been convinced that direct invocation is preferable, so I need to know how to do multiple invocations of dovecot. I had thought that perhaps I could

Back in late March I asked what ownership and permissions Dovecot's own directories and files should have; I have an obsessive nature, and wanted to get things right :(.. On April Fool's Day :), Timo responded: > Dovecot opens pretty much all the configuration etc. files as root > before dropping the privileges. So in general they could all be 0600 > owned by root In my

In V1.1.15 that I fell back to. Again: # 1.1.15: /usr/local/etc/dovecot.conf # OS: AIX 3 0001378F4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 200

Am seeing: > Jul 19 14:59:19 mercury mail:err|error dovecot: IMAP(jab): dotlock /var/spool/mail/jab.lock was immediately delet > ed under us > Jul 19 14:59:19 mercury mail:err|error dovecot: IMAP(jab): file_lock_dotlock() failed with mbox file /var/spool/m > ail/jab: No such file or directory what does it mean, what should I be doing to alleviate or troubleshoot the problem? -- ====

I am using the base AIX Unix authentication with NIS. There is a base /etc/password file (though the passwords are in a funny, IBM-peculiar file, /etc/security/passed) of just 18 lines...since NIS is in use, the last line is the standard for-anything-you-don't-find-here-try NIS indicator: +::0:0::: When I start up DC, I get these error massages: Apr 9 14:44:59 mercury mail:err|error

I am in the throes of trying to understand all the issues of transforming an old UW Imap server with mbox (I think) INBOX format running sendmail and procmail serving 3500 users to dovecot and maildir format. Currently, the folders are under ~/mail and the INBOXes are under /var/spool/mail. If I understand correctly, the typical default Dovecot/maildir format installation will have both the INBOX

My production imap is currently UWIMAP with mbox.. One of the problems commonly observed is mailbox lock loss, which happens when: a) a VIP has multiple secretaries accessing a single mailbox (actually, they are professional enough to have figured the realities of conflicting access and rarely have a problem), b) somebody leaving their machine on at home and coming in and firing up their work

It's been a month since 1.1.2....I'm about to do some V1.0 to V1.1 move work and I'd rather start on the curve instead of behind it.......... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean at bard.edu voice: 845-758-7475, fax: 845-758-7035