I have set up an area of shared folders with Dovecot 1.2 that is accessed by several people (by way of one account, and everyone who logs in sees these same folders), and the only problem with this setup is that occasionally somebody moves one of the folders underneath another folder or somewhere else in the folder structure, and this sometimes disrupts some automatic procmail filters and the like. Is there a way to keep folders in a shared setup such as this "static" or "unmovable" so that the users can't disrupt the structure? Like, where the folder structure itself can't be changed, but new messages can still come in to the folders? David
On Ter, 2011-01-11 at 12:27 -0600, Dave wrote:> I have set up an area of shared folders with Dovecot 1.2 that is > accessed by several people (by way of one account, and everyone who logs > in sees these same folders), and the only problem with this setup is > that occasionally somebody moves one of the folders underneath another > folder or somewhere else in the folder structure, and this sometimes > disrupts some automatic procmail filters and the like. > > Is there a way to keep folders in a shared setup such as this "static" > or "unmovable" so that the users can't disrupt the structure? Like, > where the folder structure itself can't be changed, but new messages can > still come in to the folders? >You may be able to do that with ACLs. -- Jose Celestino | http://japc.uncovering.org/files/japc-pgpkey.asc ---------------------------------------------------------------- "Assumption is the Mother of Screw-Up" -- Mr. John Elwood Hale
Well, I just noticed this in my logs after I re-loaded the latest Dovecot config I tried: Jan 13 15:09:45 mail dovecot: SIGHUP received - reloading configuration Jan 13 15:09:45 mail dovecot: read(imap dump-capability process) failed: Interrupted system call Jan 13 15:09:45 mail dovecot: Invalid configuration, keeping old one Jan 13 15:09:45 mail dovecot: child 2085 (unknown) returned error 82 (Internal logging error) It's apparently been doing this every time I've reloaded the config, so this is probably why none of my changes with the ACLs are working. :/ Any thoughts on what could be causing this kind of error?? Does that error just basically mean something's set wrong somewhere in dovecot.conf? David