similar to: ACL with IMAP proxying

Hello, In my current setup, I uses two mailservers to handle the users connections, and my emails are stored on a distant server using NFS (maildir architecture) Dovecot is both my IMAP server and the delivery agent (LMTP via postfix) To avoid indexing issues related to NFS, proxying is enabled both on IMAP and LMTP. But when a mail is sent to users that are shared between the servers, I got the

Hi, I'm attempting to proxy lmtp using director to hash to the same backend as pop3/imap. My pop3/imap users are of the form: username and my lmtp users are of the form: <username at domain> Where domain is fairly redundant but does carry some useful information. Now, I can proxy lmtp using user=%{username} and destuser=%{orig_user}, and this all appears to work correctly.

Dovecot 2.0.9 on Centos 6.6 I have some local users and some Postfix virtual mailboxes. The config currently has: > # 2.0.9: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-504.12.2.el6.x86_64 x86_64 CentOS release 6.6 (Final) > first_valid_uid = 190 > log_path = /var/log/dovecot.log > mail_access_groups = mail > mail_location = mbox:~/mail:INBOX=/var/mail/%u >

Fix typo, you have schme. Aki On 07.03.2018 15:47, Sergio Belkin wrote: > Hi, > > I get this error even when user logins succesfully: > > Mar? 7 10:41:16 mail dovecot: auth: Debug: client in: > AUTH#0111#011CRAM-MD5#011service=imap#011secured#011session=maOgttJmCADAqHoB#011lip=192.168.122.202#011rip=192.168.122.1#011lport=993#011rport=36872 > Mar? 7 10:41:16 mail dovecot:

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 =

Hi, I get this error even when user logins succesfully: Mar 7 10:41:16 mail dovecot: auth: Debug: client in: AUTH#0111#011CRAM-MD5#011service=imap#011secured#011session=maOgttJmCADAqHoB#011lip=192.168.122.202#011rip=192.168.122.1#011lport=993#011rport=36872 Mar 7 10:41:16 mail dovecot: auth: Debug: client passdb out: CONT#0111#011PDYyMjM4NTMwODIyODI0MDguMTUyMDQzMDA3NkBtYWlsLmV4YW1wbGUuY29tPg==

My bad. Userdb does not support scheme keyvalue, just remove it. Aki > On 07 March 2018 at 15:57 Sergio Belkin <sebelk at gmail.com> wrote: > > > Aki, > > thanks, I fixed typo but error persists: > Mar 7 10:55:54 mail dovecot: auth: Debug: auth client connected (pid=10828) > Mar 7 10:55:55 mail dovecot: auth: Debug: client in: >

Hi All My first post to the list, so "hello world"! Having searched the list archives and the wiki for an answer to this, I don't think it is possible. However, let me ask nonetheless... Is it possible for a Dovecot proxy's login process (IMAP and POP3) to include the "destuser", i.e. the uid used to authenticate to the backend IMAP/POP3 server, in its logging?

Aki, thanks, I fixed typo but error persists: Mar 7 10:55:54 mail dovecot: auth: Debug: auth client connected (pid=10828) Mar 7 10:55:55 mail dovecot: auth: Debug: client in: AUTH#0111#011CRAM-MD5#011service=imap#011secured#011session=FIH/6tJm4gDAqHoB#011lip=192.168.122.202#011rip=192.168.122.1#011lport=993#011rport=37090 Mar 7 10:55:55 mail dovecot: auth: Debug: client passdb out:

I tried setting the "destuser" setting on the LMTP director as follows, to preserve the original envelope rcpt: protocol lmtp { auth_socket_path = director-userdb passdb { driver = ... override_fields = destuser=%{orig_user} } } The passdb driver would return the appropriate "user" for each alias. Suppose, for example, user1 has emails user1 at domain.tld,

Hi Timo, I'm writing to alert you that even in version 2.1. we have the error: "Can't handle mixed proxy/non-proxy destinations" when we write to two users: one existent and one not. The error occurs randomly. I configure LDAP query in the file : dovecot-ldap.conf in this way: pass_attrs = mail=user,userPassword=password,=proxy=y,mailHost=host, =proxy_timeout=600

Hi, I'm stuck with a problem we have with dovecot. My suspicion is, that it has to do with accessing the same mailbox/mail stored on a NFS-share from two machines at the same time. setup We have to mail servers running, both run a Ubuntu 10.04, Postfix 2.70 and Dovecot 1.2.9. The mailboxes are stored in maildir format on a NFS-Share. In front of those to mail servers we have a load

Hello, In my current setup, I have a spam filter upstream that adds a specific header - X-Spam-Level on every incoming mail. Based on this level, the mail will be moved to the user spam folder using sieve by doing "fileinto :create 'spam';" Unfortunately, some legitimate email may end up in this spam folder, so I have kind of a whitelist that performs an explicit keep over

Hello, I'm using proxy_maybe and auth_default_realm. It seems that when a user logs in without the domain name, relying on auth_default_realm, and the "host" field points to the local server, I get the Proxying loops to itself error. It does work as expected - log on to the local server without proxying, if the user does include the domain name in the login. (IP's and

Hi, I have setup freebsd, postfix, dovecot and maia, but all the time i get the following error in /var/log/maillog - and i cant google me to the solution, please advice. Aug 9 12:18:49 mail02 dovecot: auth(default): Authentication client trying to connect to master socket Aug 9 12:18:49 mail02 postfix/smtpd[1356]: fatal: no SASL authentication mechanisms Aug 9 12:18:50 mail02

Hi all, i have some troubles in the implementation of my proxyconfiguration. i have two kind of users, the first will be proxied to a dovecot backend with masteruser-login, the other one will be proxied to another non-dovecot imapserver with nopassword. Everything looks to work if i use passwd-file like this: user1:{PLAIN}pass1:::::::proxy=y host=192.168.1.1 destuser=user1*masteruser

Hello to everybody, first of all: thanks a lot for your hard work and for this nice piece of software! After many search about the following SIGSEGV, I decide to post the backtrace and I hope to have avoided duplicated thread. The problem arise after I enable clucene fts. I tryed the clucene ports version (I am using OpenBSD) and a fixed version from github (Blue-Rocket/clucene::feature/pod)

Started implementing the MasterUser changes to my config files so I can finally offer SPA for pop3/imap. Things are working fine with the MasterUser (horray!), however one of my guys started using SPA with Outlook Express and started getting another users mailbox. Turns out to be related to NTLM. His Outlook express is configured for the username of 'johnsmith'. However, you'll see

Hi list, I just recently installed Dovecot 2.0.15. Unfortunately, doveadm segfaults when I attempt to connect to the local dovecot instance. When this occurs, my logs show: 2011-10-19T12:31:23-07:00 mail02 dovecot: doveadm: Error: doveadm client not compatible with this server (mixed old and new binaries?) I am using the settings listed on the wiki page http://wiki2.dovecot.org/Director [root

Hi, having the attached configuration with Dovecot 2.2.9, Dovecot's crashing when moving a mail from a shared folder into another shared folder. Moving that mail into a "real" folder of the user or moving that mail from a real folder into the shared folder is always working. But moving from a shared folder into a shared folder doesn't work. Sep 2 11:47:42 mail02 dovecot: