similar to: [Fwd: Re: University of Washington lays off 66 technology workers.]

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

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

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

The CFO of our college, a most formidable man, had decided to go Blackberry and Something Functional Must Be Done. We've had some users who we've not supported (and things got better for them when we switched from UWIMAP to Dovecot). BB, of course, has their half-baked sorta-IMAP-compliant client (and we do NOT want the BB Enterprise Server) that persistently keeps grabbing the

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

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

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

Thanks in advance for your patience and assistance. Since a system administrator's work is most successful when nobody knows you've done anything....(ugly that...you get neither raises nor equipment funding as a result), I prefer to learn from other's experiences rather than fail in the same pits. We are considering a switch from UW to Dovecot, since our users persist in using

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

<permit me my perhaps foolish preference...an explanation> I run mail service for a small college. I've long joked that if someone stole the mail server, the phone would ring before the alarm (which has a 1 minute delay) did, that the user base expected 25x8x367 coverage. Making updates/upgrades to the mail server feels like a tightrope walk with no net. I always appreciated

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

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

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