similar to: Newbie index infrastructure and location questions

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

Thunderbird (2.0) is all of a sudden checking mail server capabilities and keep posting a popup saying: "Mail Server imap.bard.edu is not an IMAP4 mail server". To the best of my knowledge, neither Tbird nor DC have been updated, though the DC imap host was rebooted today 3 hours ago. Any info on what this is about? DC is currently serving out of a special port and in evaluation

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

It never hurts to ask...... I am bringing up DC on my production mailserver (which runs UWIMAP for production IMAP service) to learn and test it, much as I did when I introduced SSL protected IMAP, using an unpublicized non-standard port. The folder and mailbox location and format will remain the same. Questions: 1) Will DC be building indices for everything or just for the userid that I use

As is usually the case, I'm not sure enough of what the DC docs are referring to; there are some implicit info assumptions that I, the Newbie, miss... Anyway, here is my situation Dovecot is to run on one machine only, its index files are stored in on a separate, non-quotaed, not NFS filesystem. INBOX and folder filesystems (all mbox format) are native to this machine and are NFS

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

If I've made configuration changes, is there a way to refresh...without killing and restarting....Dovecot? -- ==== 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

If a host is running NIS (passwd file ends in +::0:0:::) authentication, will dovecot be able to authenticate with auth_userdb = passwd directly and automagically or do you have to do a ypcat passwd > pwfile periodically to generate a passwd file that dovecot can use? ? Thanks! -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College,

I get the errmsg: auth|security:err|error dovecot-auth PAM: load_modules: can not open module /usr/lib/security/pam_prohibit That file is 444 root:security What is wrong here? Also, I'm using plain UINX authentication, but PAM keeps trying to run. How do I turn it off? I'll probably eventually want to use PAM; how do I get it to look in /etc/pam.conf instead /etc/pam.d...or will it

I now have Dovecot in production and things are apparently trouble-free. The one known problem is that initial client inbox load can take 30 seconds - 2 minutes. For instance: 'I got fed up waiting and went and got coffee'...this with a 3MB mbox inbox...and my mail server is a substantial machine consuming 25% CPU just for this person's IMAP session. I realize that a certain

I know how to run a second instance of the *base* code (to check different functionality/config) and documented it in http://wiki.dovecot.org/RunningDovecot What I realize I don't know how to do is to run an altogether different version or build of the code as that second instance, which would be good to have to check out upgrades before they go into production. While I could do a build

For the record/archive, so some other unfortunate dovecot implementer won't spend weeks figuring out this particular way dotlocks can have problems... here is what was trashing our dotlocks Basically, I was seeing this: May 14 15:59:58 mercury mail:warn|warning dovecot: IMAP(sdean): Our dotlock file /var/spool/mail/sdean.lock was deleted (kept it 1 secs) > May 14 15:59:58 mercury

I am finishing up getting SSL/IMAP working on our mail server and I notice the Use secure authentication box....very little I can find out about it, except that everyone says NOT to use it and maybe it's only for POP, not IMAP. Can you confirm?...googled you on this. Also, isn't authentication secure with SSL/IMAP anyway????? -- ==== Stewart Dean, Unix System Admin, Henderson Computer

WIBNI if the clients' message composition windows displayed the size of the prospective outgoing message as a color-coded BIG number... <50K green <200K yellow <500K orange >1MB red ...or some such.. Idiot clueless users occasionally send inadvertantly huge messages...the problem is that there is currently no feedback loop (like this suggestion)....nobody would mail a 100

On second thought (unless someone is fantastically charitable), I suppose I need to seriously concentrate on modifying the current configure script to work with the current AIX operating system and compiler. Can someone direct me to documentation on configure so I can begin my trek through the wilderness? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard

This ought to be a simple question. Have I got this right? drwxr-xr-x 2 root system 512 Mar 03 15:16 certs drwxr-x--- 2 root system 512 Mar 03 15:10 private ./certs: -rw-r--r-- 1 root system 1403 Mar 03 15:16 dovecot.pem ./private: -rw------- 1 root system 887 Mar 03 15:16 dovecot.pem -- ==== Stewart Dean, Unix System Admin,

...and what permissions should they have. I am thinking of /var/run/dovecot and the index directory. What ownership, group and permissions should they be? Are there any other files/dirs created for dovecot alone (not the mail folders and INBOXes); if so, how should they be owned and permed? I had thought they were to be owned by dovecot, but it turns out that they should not -- ====

Back a year ago, I asked what the key DC executables where that I had to bring from my compile host to the production imap server to install or upgrade DC. I was told: dovecot, dovecot.conf, dovecot-auth, imap & imap-login I recently got DC up and running unencrypted and that worked fine. Then I tried to enable SSL and the logs said I was missing

I previously asked about this problem with pam on IBM's AIX Unix > I get the errmsg: > auth|security:err|error dovecot-auth PAM: load_modules: can not open > module /usr/lib/security/pam_prohibit FWIW, it turned out that the default PAM libraries are 32 bit, while I had compiled DC at 64bit. The /etc/pam.conf lines come standard like this: telnet auth required

I'm used to putting things in inetd and, 1) should dovecot crash, I'd think it would get restarted if it was invoked from inet's imap-login 2) it would get started well after the boot ...wouldn't that be preferable. Enlighten me, please -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean at