search for: ednitido

We have a few dovecot servers all pointing to the same mail location (an NFS mount on a NAS drive). This could lead to a possible bottleneck eventually and we were wondering if it's possible to have dovecot direct x number of users to one message store location while others get their mail on a different mount?

I'm trying to follow the instructions for configuring Dovecot LMTP with postfix for virtual domains but whenever mail arrives, in /var/log/maillog, I see Sep 23 16:01:20 mybox postfix/pipe[572]: 999C83206C6: to=< user at mytest.domain.com>, relay=dovecot, delay=0.08, delays=0.04/0.01/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: pipe: fatal: pipe_command: execvp

I was reading "conf.d/10-director.conf" and it mentions Dovecot proxy. I've been using perdition in the past for my pop/imap proxying needs and wasn't sure if Director could also use perdition or if it only works with Dovecots proxying. Thanks!

Is it possible to have dovecot 2.0.8 using LMTP run a shell script each time it delivers a message to a users mailbox? I see there's an "execute = script /path/to/script" but when i added it to lmtp service in 10-master.conf, it didnt do anything and stopped delivering mail altogether service lmtp { executable = script /usr/local/bin/test.sh u% unix_listener

For example, say the connection between the user and the dovecot proxy is fast/cheap, but the connection from the proxy to the dovecot imap backend server is costly. is there a way to set up the proxy to cache messages to allow faster loading? if so, does it have different levels of caching (full message, headers only, etc)? I'm using dovecot 2.0.9 for both the proxy and the imap backend. if

I'm trying to configure my proxy/director server, which proxies imap/pop/managesieve correctly already, to proxy LMTP to my backend message store server (dovecot+postfix already configured there) This is what I have so far: 10-auth.conf using auth-static.conf.ext instead of auth-ldap.conf.ext (switching to this made proxying imap/pop/managesieve work) 10-director.conf protocol lmtp {

We have a Dovecot installation of several nodes that share an NFS mount for the user data. We are trying to configure Dovecot Proxy with Director in order to have Director select the appropriate IMAP server for a given user on behave of Dovecot Proxy. So far all examples I've seen on the dovecot site require the proxy to know the exact mail server to pass the user to by way of an LDAP

I just noticed this error in my logs: director: Error: doveadm not compatible with this server (mixed old and new binaries?) director: Error: director(10.161.192.28:541/right): Wrong protocol in socket (director-doveadm vs director) The first error I removed by changing director_doveadm_port = 541 to director_doveadm_port = 542 Not really sure why that fixed it. The second error I

I have successfully set up the master user on the destination server (2.0.11) and tests have worked. now I'm working on the proxy Before I had the proxy just forward everything to the backend and had the destination server do the authentication. My authentication is done via LDAP but not really sure how to append the master user and password to the users credentials after authentication is

I have a folder created in dovecot entered by the user as "??o??" On the file system it appears as "&APEA8Q-o&AOkA6Q-" (mUTF7) When creating a sieve rule, to file into the folder ??o??, I am converting the name from UTF8 into UTF7, the rule becomes require ["fileinto"]; if header :contains ["From"] "user at domain.com" { fileinto

Hey all, I've upgraded from a working Dovecot 2.0.17 Proxy with a master user setup to Dovecot 2.1.3 and I've merged my conf settings from 2.0.17 into 2.1.3. I'm able to start up dovecot proxy and telnet localhost, however it creates the users home director on the proxy server instead of going to the backend dovecot server (which has already been successfully upgraded to 2.1.3 from

I'm trying to compile the source for Dovecot 2.0.2 on a Solaris 10 SPARC machine. > uname -a SunOS ommtca013 5.10 Generic_138888-07 sun4v sparc SUNW,Sun-Blade-T6300 Solaris > cat /etc/release Solaris 10 10/08 s10s_u6wos_07b SPARC I've installed the following binaries from sunfreeware for dovecot 1.1 to use with 2.0.2 gcc-3.4.6-sol10-sparc-local

I've just upgraded to Dovecot 2.0.13 from 2.0.12 When I authenticate via telnet it closes the connection and the logs show: May 13 16:59:16 master: Info: Dovecot v2.0.13 starting up (core dumps disabled) May 13 16:59:40 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth May 13 16:59:40 auth: Debug: passwd-file /usr/local/etc/dovecot/master-users: Read 1 users May 13

Hey all long time, I recently upgraded Dovecot from 2.1.15 to 2.2.29.1 on my Debian Wheezy box and thought I'd tackle shared mailboxes. I can grant fine, using SETACL in telnet . SETACL mine vsun at test.domain.com lr . OK Setacl complete (0.596 + 0.000 + 0.595 secs). . GETACL mine * ACL mine vsun at test.domain.com lr edward at test.domain.com lrwstipekxacd However, logging in as vsun at