similar to: who owns dovecot files and dirs?

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

Many good suggestions and comments. But while I was trying to do it right (silly me), the brass hat got it working with whatever is on the phone and I am told that everything is fine (until it isn't). Thanks to all who responded -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean at bard.edu voice:

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

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 thought this would be relatively straightforward....I would create .subscriptions by doing an ls -1 of ~/mail. I'm running into some problems. 1) the ~/mail directories haves directories in them for 5% of the accounts! AFAIK, our mail sevice has always been UWIMAP with mbox format INBOXes, and it was my understanding that the mbox format is flat and NOT hierarchical and thus I'd

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

Don't know if anyone else uses Berkeley derived filesystem quota, but IBM's AIX does. A little over a week after migrating from UWIMAP to DC (with mbox format unchanged) everything is clean except for this one problem: When users go over quota, when they login the next time, the folder list is blank. You can imagine the panicked calls to the Helpdesk. If their quotas are raised or

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

I guess the alert function is not part of the spec, because it appears to be unimplemented in Dovecot, even though most clients implement it. Timo, I would hope this would be easy to implement, and it's functionality that will be valuable to every installation. Here's why. America recently had the tragedy of a shooting rampage on a large university campus (yes, America should do

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 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

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,

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