similar to: MasterUser and old rev of Dovecot (0.99.14)

Greetings to all I need a masteruser/proxy account for some applications to be implemented and i am having some problems. Normal users are proxyied through ldap queries to the remote machine and this is working like it sopose to, but i can't make the master user to work. Below are both the dovecot.conf and dovecot-ldap.conf and verbose logs on the proxy machine. If i log directly on the

Thank you, How and where ? I configured only this: cat /Library/Server/Mail/Data/shared/shared-mailboxes * user=masteruser lr masteruser is ok for all masters (mailmaster) ? Luda > Am 09.04.2019 um 09:33 schrieb Aki Tuomi <aki.tuomi at open-xchange.com>: > > Hi! > > You need to grant the master user rights in your ACL file. > > Aki -------------- next part

a "masteruser" login fails: Oct 8 15:12:54 postamt dovecot: auth: Debug: auth(masteruser,141.42.206.38,master): Master user lookup for login: nonworkinguser Oct 8 15:12:54 postamt dovecot: auth: passdb(masteruser,141.42.206.38,master): Master user logging in as nonworkinguser Oct 8 15:12:54 postamt dovecot: auth: Debug: cache(nonworkinguser,141.42.206.38): expired Oct 8 15:12:54

Hello, Please somebody suggest me how to remove the "*masteruser" appendix from the dovecot director database while using masteruser authentication. My situation is: - all users get authenticated in LDAP on the dovecot-director frontend - then they are forwarded to dovecot backend as username*masteruser ( this is a way how to proxy users with encrypted passwords). To enable it a added

Hello list, i would like to use master user functionality in dovecot v1.2, but i just cant get it to work: Here?s my configuration: # dovecot -n # 1.2.9: /etc/dovecot.conf # OS: Linux 2.6.18-164.10.1.el5PAE i686 Red Hat Enterprise Linux Server release 5.4 (Tikanga) login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap):

Hi dovecot masters, This is my first post here, since I desperately need some advices from the dovecot community. I've tried to get an answer on the Apple Forums but til now no luck....here we go: I've tried to sync our users emails (Mac OS X Server 10.6.8 Snow Leopard with dovecot 1.1.20-apple0.5) via imapsync to our new server by using the masterusers authentication method on the old

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

I have very strange problem with masteruser. See two logs below: # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Welcome to our post server! x login nevorotin password x OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT

Hi List, I just updated an old sendmail installation to a modern postfix/dovecot system with mysql backend. Everything works fine but SMTP-AUTH fails with some clients. The problem is, that with PLAIN (old) clients send the base64 coded form: USERNAME\0USERNAME\0PASSWORD which, as i understand dovecot interprets as MASTERUSER\0USERNAME\PASSWORD. New clients send \0USERNAME\0PASSWORD which works

Hi, you can do it via post-login script as explained in https://wiki.dovecot.org/Authentication/MasterUsers I have a post login script similar to: #!/bin/bash export USERNAME=${USER%@*} export DOMAIN=${USER#*@} exec "$@" and works fine. Ciao Il 09/04/19 09:46, Ludwig Wieland via dovecot ha scritto: > Thank you, > > How and where ? > > > I configured only this:

On 5/29/2015 9:25 AM, Dominik Breu <dominik at dominikbreu.de> wrote: > Hello Charles, > > the bare minimum ist just the first passdb entry > auth_master_user_separator = * > passdb { > driver = passwd-file > args = /etc/dovecot/passwd.masterusers > master = yes > pass = yes > } > > this will do the trick. Ok, this isn't working, I'm

Hi, the Dovecot Director determines the backend host in some way by hashing the username: http://wiki2.dovecot.org/Director For normal logins username at example.org, the director always gets the same hash for the same username and ensures that the login is always proxied to the same backend. But what about MasterUsers in combination with Dovecot Director?

Hello, i am currenty testing dovecot 2.0.beta3 and ran into a problem with the master-db setting. For our webmail access we are sucessfully using the following settings with dovecot-1.2.10 auth_master_user_separator =* auth default { mechanisms = plain passdb passwd-file { args = /etc/dovecot/passwd.masterusers master = yes pass = yes } passdb ldap {

hello, in which way do you login ? loginuser*masteruser or just masteruser? You have to do the login with loginuser*masteruser masterpass greetings dominik Am Freitag, den 29.05.2015, 10:14 -0400 schrieb Charles Marcus: > Apologies - maybe doveconf -n shows a hint at the problem? > > Maybe it has to do with I'm using the default_realm? But I've tried > adding the user as

Hi, I'm currently using Dovecot version 1.0 and I want to update it to the latest version. I know from version .99 to version 1.0 I had to change a few things on the dovecot config. When compiling the latest stable version should I just be able to use the same config I'm using for version 1.0 without making any changes ? Thank you Paul

Hi, I want to use CRAM-MD5 or DIGEST-MD5 (non-plaintext) authentication for master users, but Dovecot 2.2.13 rejects it with the following log: Sep 1 06:18:08 localhost dovecot: auth: passwd-file(masteruser,10.0.1.20,master,<ZA1s9/oBgAAKAAEU>): Master user logging in as u0001 Sep 1 06:18:08 localhost dovecot: auth: cram-md5(u0001 at example.jp,10.0.1.20,<ZA1s9/oBgAAKAAEU>):

Hi, I'm trying to use imapsync to migrate my accounts and mailbox (mbox) of an server A (Postfix + Dovecot) to a Server B (Zimbra), without having to change user passwords on the server A, using a master user account. I'm using this paper http://wiki2.dovecot.org/Authentication/MasterUsers as guidance. The Dovecot server A, is not letting me authenticate. Follow the testing and debug

Hello, I am trying to use postfix/dovecot as mail server to be the imap storage for my voicemail system.For that I installed postfix and dovecot and trying to follow the instructions in this post http://etel.wiki.oreilly.com/wiki/index.php?title=Storing_Voicemail_on_an_IMAP_server&printable=yes I should add a master user for Asterisk to your IMAP server that has access to all user's

Vielen Dank f?r Ihre Email! Ich bin heute leider nicht im B?ro, erhalte Ihre Email aber trotzdem. In dringenden F?llen k?nnen Sie mich auch per Handy erreichen: 0177-7372923. Mit freundlichen Gr??en aus Sarstedt Hauke Hagedorn -- Hagedorn Internet- & Veranstaltungsdienstleistungen Wenderter Str. 37d 31157 Sarstedt Ust-Id DE 256037115 Tel: +49 5066 917 339 1 Fax: +49 5066 917 339 9

. My debug: Apr 09 09:13:20 imap(pid 82675 user test1): Debug: acl vfile: file /Library/Server/Mail/Config/dovecot/global-acls/INBOX not found Apr 09 09:13:20 imap(pid 82675 user test1): Debug: acl vfile: file /Library/Server/Mail/Data/mail/EB83247B-1A33-4A43-AD30-E6453789072A/dovecot-acl not found Apr 09 09:13:20 imap(pid 82675 user test1): Debug: acl vfile: file