similar to: Shared mailboxes support status

Hello, I'm trying to set up, as explained in the wiki, shared mailboxes with symlink. I'm running dovecot-1.1.8 with LDAP pass/userdb. The Maildir layout goes like this : /courriel/boites/foobar : Maildir of user foobar (nfs) /courriel/meta/foobar : control files of user foobar (nfs) /var/dovecot/indexes : indexes (locally stored) I created : /courriel/boites/doveshared/.box/ :

Hello, I'm running dovecot-1.1.8/Maildir/ACL plugin. I sucessfully set up a Maildir shared between users of the unix group 'doveshared' via a public namespace, unix permissions and ACL files. The location of my public namespace is /path/to/public. I tried 2 sub-setups : First setup ---------- drwxrws--- 4 root doveshared 4096 Jan 30 13:39 public -rw-r----- 1 root doveshared

Hello Timo, With dovecot-2.0.8/Maildir, in a simple shared mailboxes setting I noticed the following : - user "doveimap" has 2 mailboxes : "Common" and "Private" - he shares only the "Common" mailbox to user "dovepop" doing : x setacl "Common" dovepop lrwstipekxacd x OK Setacl complete. - he subscribed to both x lsub

Hello Timo, I'm running dovecot-1.2.11/Maildir and plan to migrate to single UID mailboxes some day, but for now, I've got "system" users and I'm testing permissions handling in order to set up shared mailboxes. The private namespace mailboxes location is location = maildir:/courriel/boites/%u:CONTROL=/courriel/meta/%u:INDEX=/var/dovecot-test/indexes/%1u/%u I've

Hello Timo, On a production (by that I mean many users) dovecot-1.1.8/Maidir server where ACL plugin has been enabled, I ran on a log verbosity problem : For some reason (in fact, due to mbox -> Maildir migration script), some people have in their Maildir a .procmail.logfile file. The problem is that dovecot (or the ACL plugin) wants to find a dovecot-acl file in what it would like to be a

Hello, let me re-state, hopefully in clearer terms, what I tried to described in a previous thread : With dovecot-1.1.8/Maildir/LDAP pass/userdb (prefetch), I'm trying to set up a Maildir ".box" shared in rw between 2 users in a "Public" namespace. I can't get it to work unless I chmod 777 everything, which obiously is not what I want. 1) am I correct thinking that

Hello Timo, In my trials to setup a shared namespace with dovecot-1.1.8/LDAP passdb/userdb (prefetch)/Maildir, I found out that : 1) ACL are mandatory (at least if the acl plugin is triggered in dovecot.conf) Am I correct ? I'm still not sure if we can do without ACL at all (only with unix permissions and system_user userdb extra field). 2) the system_user userdb extra field is

Hello Timo, I'm trying to set up shared mailboxes with dovecot-1.2.11/Maildir. I previsouly used public namespaces with 1.1+ to somehow implement them but I'm looking at the real ones now. I've read the Wiki but I'm still confused or not 100% sure about the following (basic) points : 1. Namespaces prefixes My understanding is that a namespace prefix is just an escape mechanism

Hello, I run dovecot-2/Maildir/LDAP user/passdb and would like to be able to deny acess to users who connect from certain domains/IP (google.com for instance since in that case they gave their credentials to a third party). My understanding is that I cannot use some negative form of "allow_nets". The only mechanism I can think of is tcp_wrappers. However, dovecot documentation mention

Hello, I'm wondering if the following situation is valid (though I think it isn't since I still cannot authenticate with ldap pass/userdb on test67 running on FreeBSD-5.3). Is it normal that the passdb_ldap_conn->attr_names second element (for instance) "turns to" "homeDirectory" as the following step by step gdb run sample shows ? : -- Breakpoint 1,

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the

Hi all, I'm still using beta8 (on FreeBSD 5.4-RELEASE). Recently I put a co-worker who's using Thunderbird (1.5.0.4) on it and he seemed to have lost some messages (which were delivered on the spool since seen on procmail logfile). I switched him on another server to play safe and tried to test it myself but failed to reproduce the issue. I myself use mutt on a daily basis with no

Hello Timo, your patch introducing pass_attr_names and user_attr_names fixed the problem of the 'shared' attr_names member of [passdb|userdb]_ldap_conn as I answered in the relative thread. Now I think there is a problem while comparing user-provided and ldap-provided passwords causing a false 'password mismatch' situation, while using PLAIN mechanism with LDAP authentication.

Hello Timo, I just switched from dovecot-1.0.14 to dovecot-1.1.2 and noticed a significant drop in the server load average (which has become lower and above all doesn't seem to have unexplained peaks). Indexes are still locally stored and nfs attribute caching is still off). I searched the list archives for an explanation of what changed in the code that could explain such an improvement but

Hello Timo, I switched this morning from dovecot-1.2.12 to 2.0.8 with a basic setup (high performance login mode, Maildir, everyhing on NFS, one shared but unused namespace). No problem so far except that some Thunderbird users who wouldn't succeed in moving messages from some one folder to another. They'd get a message about some illegal character in the mailboxname (already existing

Hello Timo, How exactly would translate the "passdb" userdb example which is in the Wiki for SQL auth with LDAP auth, both in dovecot.conf and dovecot-ldap.conf ? -- Thomas Hummel | Institut Pasteur <hummel@pasteur.fr> | P?le informatique - syst?mes et r?seau

Hello Timo, is there a way, either in 1.2.x or in 2.x to activate disable_plaintext_auth=yes only for some address or network ? The idea would be to enable clients from the internal networks to keep making clear text connections while forbidding it to the rest of the world. Thanks. -- Thomas Hummel | Institut Pasteur <hummel at pasteur.fr> | P?le informatique - syst?mes et

Hello Timo, I'm experiencing the following different behaviors with dovecot-1.1.8/Maildir. My Maildir hierarchy separator is the "." (dot) character. My namespaces, when I use them, separator is "/". When I run the server without any namespaces, I can create mailboxes named something like first.name which, of course, are shown to the client as first/ (non

Hello, I was asking what was the motivation for not having the envelope From in the Maildir format, as defined in the qmail spec : "The message is delivered without an extra UUCP- style From_ line, without any >From quoting, and without an extra blank line at the end." which may sound silly since we lose an important piece of information. Same question about the motivation in

Hello Timo, I'm trying to get a clear understanding of dovecot's (1.2.x) flags and keywords sharing possibilities or impossibilities in a shared-mailboxes setup. By definition, a shared mailbox is a mailbox from a personal namespace which has been made available to someone else who sees it in a shared namespace. There can be some combinatorics according to the fact that INDEX and