similar to: Master user creds for proxy stored statically/locally?

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'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 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?d like to migrate to a new server. I only need to transfer the mail store, have already done the users. I?ve seen different recommendations: IMAP-Sync Rsync Doveadmin backup and dsync What are the pros and cons of each? What would be best for me? I?m thinking that Doveadmin backup is the way to go. Both old and new servers are on same network. New server is running Dovecot 2.3.2.1, old server

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

Thanks Sam Users not using new mail server yet. Both old and new using maildir. Sounds like rsync is the way to go. Thanks for your help. James. Sent from my iPhone XI > On 4 Sep 2018, at 5:41 pm, Sami Ketola <sami.ketola at dovecot.fi> wrote: > > > >> On 4 Sep 2018, at 10.20, James Brown <jlbrown at bordo.com.au> wrote: >> >> I?d like to

While toying around with Doveadmin HTTP api I noticed, there is not much hype around it. Let's change that. Doveadmin REST API so to speak provides a web server. When doing /ajax/ requests, modern browsers block that, unless the response comes with a specific CORS header. Here how to work around with a proxy: > # /etc/dovecot/local.conf > doveadm_allowed_commands = fetch >

Hi list, I have a question on auth caching in 2.2.18. I am using acl_groups for a master user, appended in a static userdb file # snip ############################### master at uma:{SHA}XXXX=::::::userdb_acl_groups=umareadmaster allow_nets=127.0.0.1 # snap ############################### and use this group in a global ACL file. I discovered this only works on first NOT-cached login

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

Hello, I'm trying to use ACLs to restrict subscription on public mailboxes, but I went into trouble. My setup is made of two servers, and users are shared between them via a proxy. User authentication is done with LDAP, and credentials aren't shared between the mailservers. Instead, the proxies are using master password. The thing is that when the ACLs are checked, it actually doesn't

hi timo, I checked out the commit causing this. its this one: http://hg.dovecot.org/dovecot-2.2/diff/5e445c659f89/src/auth/auth-request.c#l1.32 if I move this block back as it was. everything is fine diff -r a46620d6e0ff -r 5e445c659f89 src/auth/auth-request.c --- a/src/auth/auth-request.c Tue May 05 13:35:52 2015 +0300 +++ b/src/auth/auth-request.c Tue May 05 14:16:31 2015 +0300 @@ -618,30

How would I go, If I wanted ACL processing to start with %{auth_user} instead of %{user} when determining rights? -- peter

Hello list, Still need your help configuring proxy infrastructure. Today, I really struggle configuring master passwords forwarding. What I want: master user can connect to any other account, on proxy. Could please somebody help me, I read both articles about this on wiki, but still can't connect :( What I did: on proxy: auth_master_user_separator=* passdb sql { args =

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

Hi, I hope you're all right. I describe below the scenario where the problem occurs. I'm trying to activate a master user [1] to be able to access all the boxes of all users by imap. I have configured the dovecot-master-users [2] file with the appropriate permissions. When I try to access, for example with roundcube, through user at mydomain.com*my_master_user at not-exist.com I see in the

Dear, We are integrating Samba with Active Directory in the company. The goal is to provide a samba share to users of AD. In this case, we need all users to write on the share, but nobody modify or delete any files. Even the user who owns it. With this, we would create only one AD user, if necessary with root powers, which could erase everything. For this, we test several lines, such as

I am a little confused here. I have been running 2.2.34 which I installed in /opt/dovecot2.2 I installed 2.3.0.1 to /opt/dovecot23 I then used config files from /opt/dovecot2.2/etc/dovecot to /opt/dovecot2.3/etc/dovecot and all I did was sed -i.BAK 's/dovecot2.2/dovecot2.3/g'. Dovecot started and was running file. Next, I manually crafted config files for 2.3.0.1 based on the example

Hi, Quick question...I read in the docs that: "Master user is still subject to ACLs just like any other user, which means that by default the master user has no access to any mailboxes of the user." ... and that the standard workaround is to return master_user=%u from the userdb. But why is the master_user authn-id used in the ACLs and not the authz-id (requested-login-user) ?

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

Hi I have two server directors in ring and 5 dovecot servers (2.2.36) IP for IMAP and POP3 is a VIP (keepalived) What is the best solutions to get realy HA for 5 dovecot servers ? Maby corosync+pacemeker ? But this solution is too problematic and hardcore Why I need HA ? Doveadmin is too lazy and doveadm director does not know that one machine broke down and still sends traffic