search for: masterusers

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

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

...ovecot (1.0.7; as shipped with CentOS 5.2). My plan was to use the imapsync utility as this will "seamlessly" do the conversion from mbox to maildir between the boxes as well. I've got the MasterUser authentication working fine on the new host and was just about to start getting MasterUsers working on the old host. I noticed that the old .99 version dovecot.conf seems to have a mildly different syntax from 1.0 dovecot.conf. In particular a lot of the directives do not use braces and such. Is the .99 dovecot.conf file essentially able to deal with the same sort of syntax as out...

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

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

...in_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: postmaster_address: postmaster at example.com auth default: master_user_separator: * debug: yes passdb: driver: passwd-file args: /etc/dovecot.passwd.masterusers pass: yes master: yes passdb: driver: pam userdb: driver: passwd # cat /root/dovecot-master-postlogin #!/bin/bash MASTER_USER=$USER export MASTER_USER exec /usr/libexec/dovecot/imap "$@? # cat /etc/dovecot.passwd.masterusers masteruser:{PLAIN}Heslo42 Trying login as n...

...cot 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? http://wiki2.dovecot.org/Authentication/MasterUsers Which configuration directives should be used to make sure that logins username at example.org*masteruser1 at example.org username at example.org*masteruser2 at example.org username at example.org*masteruse...

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 below: Testing: # telnet <ip_address> 8143 Trying <ip_address>... Connected to <ip_address>. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFER...

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: > cat /L...

...t/libexec/dovecot/managesieve managesieve_max_line_length = 65536 managesieve_implementation_string = dovecot managesieve_logout_format = bytes ( in=%i : out=%o ) } auth default { mechanisms = plain login user = vmail passdb passwd-file { args = /etc/dovecot/passwd.masterusers master = yes pass = yes } passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group = vmail } client { path = /var...

...; > mailbox Trash { > > special_use = \Trash > > } > > prefix = > > separator = . > > } > > passdb { > > args = /etc/dovecot/dovecot-sql.conf.ext > > driver = sql > > } > > passdb { > > args = /etc/dovecot/passwd.masterusers > > driver = passwd-file > > master = yes > > pass = yes > > } > > plugin { > > sieve = ~/.dovecot.sieve > > sieve_dir = ~/sieve > > } > > protocols = imap lmtp > > service auth-worker { > > user = $default_internal_user...

...lugin_dir(imap): /usr/lib/dovecot/imap > mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 > lda: > postmaster_address: postmaster at example.com > auth default: > master_user_separator: * > debug: yes > passdb: > driver: passwd-file > args: /etc/dovecot.passwd.masterusers > pass: yes > master: yes > passdb: > driver: pam > userdb: > driver: passwd > > > # cat /root/dovecot-master-postlogin > #!/bin/bash > MASTER_USER=$USER > export MASTER_USER > exec /usr/libexec/dovecot/imap "$@? > > > # c...

Hello, I have Director setup to proxy requests to backend servers. This works fine when using "standard" username/passwords. I am not try to enable the use of the Dovecot Master user through Director into the backend servers. a.) username is being sent as masteruser*username b.) request hits the proxy and authenticates, and then is passed to the backend servers and fails auth. - logs

...unicate to the back-end server. On the back-end Dovecot server it is working fine, I can log in as normal user/user_password or as user*masteruser/master_password. The back-end config is: auth_master_user_separator = * passdb { driver = passwd-file args = /usr/local/dovecot/etc/dovecot/passwd.masterusers master = yes pass = yes } passdb { driver = ldap args = /usr/local/dovecot/etc/dovecot/dovecot-ldap.conf.ext } userdb { driver = ldap args = /usr/local/dovecot/etc/dovecot/dovecot-ldap.conf.ext } Now front-end: how to get director forward the user to the back-end after authenticati...

Per Timo's direction, I decided to give the MasterUser a try in connecting my proxy to my destination server. This might allow for the use of 'secure password' for my clients that like to check that box by default. A couple of problems I'm running into running RC15: #1: My Proxy's SQL password_query line: password_query = SELECT a.clearpasswd AS password, v.storeIP AS host,

Hi all, Ok, just need a quick-n-dirty way to enable a master user for a migration... Reading the docs, I'm not sure what the bare minimum is I need to do this... At: http://wiki2.dovecot.org/Authentication/MasterUsers The Example config shows: auth_master_user_separator = * passdb { driver = passwd-file args = /etc/dovecot/passwd.masterusers master = yes pass = yes } passdb { driver = shadow } userdb { driver = passwd } But, if I'm using a non-real user (just need a master user that can log in...

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

...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 10.6.8 server... The main problem on OS X Server 10.6.8 is that dovecot 1.1.20 uses the OD (OpenDirectory) driver (well I think), so that when following the directions of Master users/password from this page I can't login with the http://wiki1.dovecot.org/Authe...

Hi. I'm trying to use checkpassword for simple auth and masteruser auth. I have two programs, one called checkpassword-master (for masteruser lookup) and another called checkpassword for normal passdb and userdb lookup). All works fine for non-masteruser authentication (in this case dovecot makes a single call to checkpassword binary). But if a master-user authenticates, dovecot execute