similar to: dovecot backend on director ?

Hello Timo, I've been using dovecot from many years now using Maildir mailbox format with default layout (Maildir++, everthing in a single directory). What would be the reason(s) to convert to Layout=fs ? I can only think of one : to allow dots in mailbox names. And even in that case, I guess I still have the option to use the litescape plugin. Besides, how would one process to do the

Hello Timo, Although I haven't tried neither director nor deliver, I'm planning to try both. I've been catching up with threads on this list talking about director but I'm not sure about how deliver would fit into a setup using director. Since deliver would touch indexes and dovecot-uidlist, wouldn't it need to be proxied as well through director ? Is that the case ? If not,

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 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 Timo, In order to plan a migration, I want to setup an IMAP proxy (proxy_maybe) with a dovecot server (I'm running the old dovecot-2.1.15 but I could upgrade or use a proxy only dovecot-2.2.x server)/LDAP pass et userdb's. I'm won't be in charge of the migration itself but I think the idea will be to migrate a chunk of users each night and then let the proxy send them to

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

Hello, I want to test dovecot proxying, on a user basis, in a simple set up (proxy, no proxy_maybe and forward the passwd to the remote server). This seem pretty simple except that, in order to test it alongside the production server, I set up 3 servers : . the proxy, listening to pop and imap on non standard ports 9143, 9993, 9110, 9995 . a proxy destination for some users, listening on

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, Before writing them myself, I'd like to figure out if some tools exist (anvil ? ...) and how to use them to extract from dovecot logs things like who is doing what and how hard or how fast in order to do some rate limiting. For instance, I'd like to be able to identify, slow or block users who . read or write to much / slice of time . login/logout too often / slice of time

Hello Timo, I'm running a single instance of dovecot-2.1.15 on a single host running 8.3-RELEASE-p3 FreeBSD amd64 mailboxes (Maildir), control files and indexes are on NFS (v3,tcp) mail_nfs_storage = yes lock_method = fcntl [didn't touch the following] # Mail index files also exist in NFS. Setting this to yes requires # mmap_disable=yes and

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