similar to: listen parm questions

So far so good...other than a my-bad fubar with the permission on the index directory that kept DC from creating index dirs for the entering-for-the-first-time users, quickly noticed (thanks to the excellent logging) and corrected. Some questions 1) the max_mail_processes parm in dovecot.conf...is that *all* processes owned by dovecot? 2) I thought there was a parm to limit how many processes

I want to test out my first V1.2 Dovecot (upgraded from V1.1) instance. What I have in mind to do is to run it on another machine that has the Inbox dir and homedirs NFS import mounted from the production mailserver. I then have 5 people test it in this test environment.... A) Then I can deal with the index filesystem in one of two ways: 1) Make it local OR 2) NFS import it from the

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'm currently runing UW-IMAP (compiled vanilla) with procmail and mbox and am making my usual careful crawl (at turtle speed) through figuring out DC config. Some questions: a) I have something like 3-4 root imapd sessions so I presume that the default *login_processes_count* = 3 will be OK. I'm less clear about login_max_processes_count and login_max_connections = 256. A common

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

This is probably an idiot (and certainly so basic as to be non-Dovecot) question, but I have been chasing my tail for a day or so on it, so I will, with humiliation, ask for guidance on it. Some time back I had asked if dovecot had to have a whole build tree of stuff to run or if any upgrade could be limited to just the executable and some libraries. I was told the latter, and given this

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

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

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

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