similar to: Maildir hierarchy sep bug ?

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 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, 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 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 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 Timo, let's say you want to implement several distinct groups of shared mailboxes via one (several) public namespace(s) with dovecot-1.1.x/Maildir. For instance, team1, team2 and team3 work on different projects (project1, project2, project3). Obviously, as many public namespaces (#team1, #team2, #team3) would do the trick, but then, any user (including users who don't belong to

Hello, I've noticed that Thunderbird (3.0.3) seems to wrongly "repeat" the namespace prefix when selecting the top level maildir of a namesapce. It doesn't occur if "list=yes" and TB has no clue about the namespace prefix. But it seems to happen only when TB is aware of the namespace prefix, either via the NAMESPACE command (so in "hidden=no" setups) or via

Hello Timo, I'm having a hard time trying to understand why Thunderbird 3.0.3 doesn't allow me to subscribe to a shared mailbox which I can subscribe to via Kmail for instance. I'm running dovecot-1.2.11/Maildir. The user 'doveimap' shares his mailbox folder/subfolder to the 'dovepop' user which should see it in the '#shared' shared namespace at the following

Hi Timo, just to report that . dovecot-1.2.12 which ran fine for several month . on FreeBSD 7.2-STABLE (/usr/obj/usr/src/sys/GENERIC amd64) . using Maildir (mailboxes, control and indexes on NFS) has crashed this morning on our server. I found nothing special in the logfile. Attached are dovecot -n output and a gdb backtrace of the core file. Thanks -- Thomas Hummel | Institut

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 using dovecot-2.1.15 with Maildir mailboxes located on an NFS filer. Postfix is used to deliver mail through procmail ("mailbox_command) as LDA. Our team has bought another filer and everything is meant to go on it, so we're planning to migrate those mailboxes to the new filer. To test it only on a subset of users, I ended up to the following solution : 1. keep

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

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, I would like to know what is the proper way to restore a Maildir : Assuming someone has got a foobar/[cur|new|tmp] maildir, loses for some reason its content and that some new mail (seen and/or unseen) comes into that mailbox inbetween (that is before the restore procedure takes place, thus creating the need to merge restored messages and new ones). I'd like to check the following (I

Hello Timo, I'm trying to configure dovecot-2.1.15 master correctly regarding imap-login limits. I want to use service_count=0 and I'm starting with something like this : #default_process_limit = 100 #default_client_limit = 1000 service imap-login { [...] service_count = 0 process_min_avail = 8 vsz_limit = 1024M } -> Does it make sense to set a process_limit if

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

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

Hello Timo, I just tried the master user feature with a very simple setup (Dovecot v2.2.15) : !include auth-master.conf.ext -> passwd-file passdb !include auth-ldap.conf.ext -> ldap passdb (userdb prefetched) without auth_bind=yes without pass=yes I get this userdb lookup error : dovecot: auth: passwd-file(masteruser,157.99.64.42,master,<4Pgesh0OygCdY0Aq>): Master user logging in

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,

Hello Timo, I want to deny access to some users. For now I'm doing it using 2 passdb's and listing users in a text file. !include auth-deny.conf.ext -> passwd-file driver !include auth-ldap.conf.ext -> ldap driver I want to do the same using only LDAP. I'm not quite sure how to do it : a) should I . change the driver of the first passdb from passwd-file to ldap . for user