similar to: No authentication sockets found

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

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

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

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:

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

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

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've been lurking for a year or more and am now actually bringing Dovecot up (it seems that any time I make a serious effort at this, something else falls in the pot and I have to give it up yet again). Index questions: I understand the indices should be placed in a non-file-system-quoted place. I have in mind to create /var/dcndx 1) Roughly how much space do indices take up (so I can size

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

<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

I purely love that kind of crap. As if presentations meant anything, as if there aren't all kinds of scholarly work about theoretical perfect world algorithms and conceptual systems that will never be implemented and are as practical and effective as wings on a pig. Please. I'm reminded of the story about how, during the American Civil War, when the North had finally, after years of

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

I'm sure it comes from my being a gormless idiot, but whatever is the -UKWS argument immediately after the mb2md.pl invocation? > $MB2MD -UKWS -s "$INBOX" -d "$WORKING" As always, reading the idiom of someone else's scripting is an education. And some of it wouldn't work with native AIX sh/ksh, so changed the functions: > folders_hash() { > local

The day I switch our user to dovecot and it goes into production, there will be a few thousand people all generating their indices for the first time (we have a legacy requirement for procmail, at least for now), so I wondered: 1) Is there is anyway to pre-emptively force indexing? 2) Is there any value in doing so? That is, will I gain much in terms of making the first time everyone connects

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

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

Doing a cursory Google scan on journaled Linux filesystems, it seems that the three ground-up journaled FSes: XFS, reiser and JFS all have their separate strong points but all compare favorably. Reiser does a better job with many small files...which would seem to be the reality of maildir formatted inboxes. Any comments on that? Any war stories, that is, any comments on reliability,