similar to: Director centralized authentication

Displaying 20 results from an estimated 70000 matches similar to: "Director centralized authentication"

2015 May 06
0
dovecot-proxy with managesieve, director and backend dovecot imap
hi all, I've been tasked to add sieve/managesieve to an existing dovecot cluster running 2.1.7 on debian wheezy which is made up of 2 dovecot-proxy hosts as directors and some back end dovecot imap hosts all running the same version. My problem is that I thought to put the service on the director/proxy hosts since they wouldn't have too much load on it, but when I do I get the
2015 Oct 27
1
Proxy with director accept only plain login
Hello, i'm test system dovecot (proxy with director) and backend storage, auth LDAP server (user plain passwords) If i use plain auth, work fine. If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection (Requested DIGEST-MD5 scheme, but we have a NULL password) ### Frontend proxy+director # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE amd64
2015 Jul 20
0
Problems with IMAP/POP and dovecot director on backend (director_proxy_maybe)
Hello dovecot community, first of all: dovecot ist great! ;) ...nevertheless I?ve got some problems to get my director scenario running as needed/expected :( My scenario: I?d like to configure two dovecot backends, without the need for multiple dovecot instances. Both backend servers are active/active and act on top of a glusterfs storage, which implies the need for dovecot director. As
2014 Jun 03
2
director with multiple instances
I'm experiencing some problems similar to those described in http://dovecot.org/list/dovecot/2012-July/137250.html except with 2.0.9. Adding http://dovecot.org/list/dovecot/2012-July/084906.html to the main config didn't seem to help, nor did setting the list of director and backend servers to just the system itself. I get a banner connecting to port 143: [root at retr01 log]# telnet
2012 Aug 27
1
doveadm commands returning 139 at director servers
Hello, I have configured director in front of dovecot imap/pop/lmtp servers. When I need to manipulate a user mailbox, I use doveadm commands at director server's, with -S option. But some commands return exit code 139 when command returns more than 40 entries (I think). For example, the command: sudo doveadm fetch -u amateo hdr mailbox Trash HEADER Subject "nyctalus11/"
2010 Jul 07
1
Director service for LMTP in 2.0rc1
Hello, has anyone a running setup for LMTP proxy and the director service ? pop3/imap/managesieve is properly working, but i have problems with LMTP. I set it up as described in the conf.d/10-director.conf From the user_db i get proxy=y and no proxyhost as described for imap/pop3 But lmtp is complaining about the missing host: Jul 07 15:00:48 auth: Debug: master in: PASS 1 user56
2011 Jul 01
1
auth error using director
Hello, I am trying to configure director as described at http://wiki2.dovecot.org/Director. I have previously tried the proxy and it worked. The problem I have is that whenever I try to connect I get the error: Jul 1 11:41:41 myotis40 dovecot: pop3-login: Error: auth: connect(director) failed: No such file or directory This is my doveconf -n: # 2.0.13: /etc/dovecot/dovecot.conf # OS:
2020 Jan 27
2
Dovecot authentication through proxy
Hi everybody, I run two redundant Dovecot servers with a shared Maildir on a GlusterFS volume and a SQL authentication backend based on a mirrored MariaDB database. Because of the splitbrain situation I would like to add two Dovecot Director as proxies. Since a few days I am trying to get the setup running. In the meantime I have achieved that the clients can successfully authenticate on the
2012 Jun 29
2
doveadm purge -A via doveadm-proxy director fails after some users
Hi, we have configured userdb and passdb in the director and try to iterate all users and pass the "purge" command via doveadm proxy to port 19000 on the correct director backend host. A single purge -u username at example.org via doveadm-proxy works correctly, but iterating over some users with -A fails. Note: users/domains have been anonymized in output:
2012 Jun 08
1
Corrupted mdbox on LMTP director delivery while user is logged in via IMAP
Hi, we get errors about corrupted indexes and we are losing flags with mdbox on NFSv4: Error: Recent flags state corrupted for mailbox Error: Corrupted dbox file Error: Corrupted transaction log file It looks like a LMTP director problem. The user has IMAP IDLE connections open and lmtp delivers to another host. This leads to nfs corruption problems. The user is logged into mail04 and has some
2013 Mar 21
0
director's imap/pop3 login timeout
Hello, We have two (load balanced) director servers in front of 4 dovecot backend servers. Yesterday we had a problem at backend servers for some users (our SSO was down, so IMAP users couldn't authenticate) and this triggered a problem in director servers where almost nobody could open a new session. In our director's logs I could see errors like this: Mar 20 20:52:47 myotis41
2014 Dec 25
0
director + lmtp + ldap user
Hi, recently I have migrated our prevoius dovecot-lda to 2.2 with director + lmtp. And we are having some issues. When lmtp delivers to ldap uid names everything works except sieve vacation (login is not found in headers so reply is not sent). When using full email addresses in rcpt to vacation works but usernames are inconsistent (one user can login using his email address, or aliases, or
2012 Dec 20
1
Director and forwarding LDAP user as Master user
Hello guys, Would you be able to help me with this little issue. I bet someone has the same config so if you can copy-paste it I will very appreciate it. So main idea is to enable Dovecot director to authenticate a LDAP user with plain or encrypted password and send the user to back-end Dovecot server after the authentication. According to Wiki it is only possible if we use the master user to
2012 Jul 17
3
doveadm director status username != doveadm director status username@mailserver
Hi, I've almost finished my new director based setup, but in the first test I discovered that imap and lmtp connections were not always being proxied to the same server. After some research now I think that the main problem is that in imap connections users connect as 'username' while lmtp connections are as 'username at mailserver'. In my current setup I receive mail via
2010 Nov 01
3
Wrong protocol in socket (director-doveadm vs director) ?
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
2013 Nov 06
0
2.2.6 auth process crash using LMTP and LDAP on director.
I'm upgrading my configuration to use director and lmtp for delivery. (doveconf -n at end of the mail). I use the same config for auth on mail backends and see no errors. My setup seem to work nicely but i have some auth process crashing when using lmtp protocol. Everything is working a sexpected then i've got 5-6 errors like this in logs and a crach of the auth process: dovecot:
2014 Feb 06
0
Trying to get Dovecot Director Proxying working
Hi All, Firstly, thanks for all the really helpful responses to my previous questions "Architecture for large Dovecot cluster" and "Sizing MTA servers". I am now trying to get a Dovecot director proxy working with a single backend mail server. When I try to connect to the dovecot proxy on the pop3 and imap ports I get connection refused. I want the authentication to
2012 Jun 06
1
Director problems
Hi, I've just setup a testing enviroment for director, and it's not working as expected. I have just 1 director (called director) and 2 dovecot servers (dovecot1 and dovecot2); these are exact copies. First problem: when both dovecot servers are up, every imap connection is redirected to the same server as you can see here: $ sudo doveadm director map user
2011 May 16
0
Dovecot mail_location creating duplicate mbox mail directories
Hi all, I'm using dovecot v2.0.11 on fedora14 with postfix. This system was migrated from an old UW mbox system, so users already have ~/mail/INBOX.* files. Now for some reason, dovecot is creating ~/mail/mail/INBOX.* files and somehow not seeing the mail_location properly. I've set mail_location to "mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u", which has worked on a
2014 Jun 16
0
connection to director (lmtp) time out
Hi all, I'm running two directors with lmtp proxy as relay transport for my mail exchangers. relay_transport = lmtp:inet:dovecot-directors.example.net dovecot-directors.example.net resolves to 172.17.1.3 and 172.17.1.4 Now, .3 is down and Postfix tries to deliver it to .4 but this connection gets a timeout: (delivery temporarily suspended: connect to 172.17.1.4[172.17.1.4]:24: Connection