similar to: sqlite queries for master user

El 09/02/16 a las 13:44, Matthias Fechner escribi?: > > do you maybe mean shared mailboxes: > http://wiki.dovecot.org/SharedMailboxes > I don't want shared mailboxes. I have to access the other mailbox as a complete separate account from my personal one. I think I can achive this with master user, but I need to found a way to configure permissions so the real user has access

Here's what I'd like. Limited master users, where someone can be a master users for some domains but not others. I think I could do what I want with the right kinds of variable passing that doesn't yet exist. Let me see if I can explain clearly. From the example in the wiki: auth_master_user_separator = * passdb { driver = sql args = /etc/dovecot/dovecot-sql-master.conf.ext

Hi, I try to configure a proxy accepting GSSAPI and PLAIN authentication. When authenticating with Kerberos, Dovecot uses master user and password to authenticate to backends (backends can be Cyrus or Exchange servers too) When authenticating with PLAIN passwords, Dovecot sends user's login and password to the backend. For GSSAPI, I use extrafields : k5principals=principal at REALM proxy=Y

Hi there! I can't get ACL working for master users. Login as master user works fine though, and I am able to access any mailbox using the auth_master_user_separator "*", tested e.g. via Python's imaplib: import imaplib imap = imaplib.IMAP4_SSL('imap.example.com') imap.login('foo at example.com*admin-acldemo', '**********') ('OK', [b'Logged

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

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):

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

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

Awesome, thanks for the advice. Using the following now works... passdb { driver = static args = proxy=y password=doesnotmatter } Cheers. On Feb 15 2018, at 2:40 pm, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > On 15 February 2018 at 20:22 Travis Dolan <travis.dolan at gmail.com> wrote: > > > Hello, > > I have Director setup to proxy

Hi, I'm using Dovecot 2.2.33.2 on a RHEL 7, new installation. My log is full of : Error: INDEX_FOLDER/dovecot.index.pvt reset, view is now inconsistent or Error: INDEX_FOLDER/dovecot.index.pvt view is inconsistent when shared folder is never touched and empty. UserA share XXXXX folder with UserB, if XXXXX folder is new (never touched) and empty every time UserB looks in that folder, an

Hello, Is there any way to easily check a master user's password, for itself, without having to refer to another user or to weak the security by allowing master users to log in for themselves? For example, this works: # doveadm auth test 'someuser*masteruser' Password: <enter master user's password here> passdb: someuser*masteruser auth succeeded but depends on the

Hi all, we are able to observe a very strange behaviour: User A wants to copy a mail to a shared mailbox of user B. This works like a charme if the quota of user A is lower than the used space of user B. But is the used space of user B higher than the quota size of User A, "User A" is not longer able to copy the message to the shared folder of user B. His IMAP Client says something

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

Hi, I'm getting errors with my IMAP setup. Basically, everything seems to work. Mail is delivered nicely from Postfix to Dovecot via LMTP. Dovecot does the authentication to LDAP (also for Postfix). Users are able to send mail via authenticated submission (Postfix) and login into IMAP and POP. However, IMAP connections are dropped frequently with an "ERROR: Connection dropped by IMAP

Hi, My samba is 3.0.13 version. I got a funny problem. UserA logs on to a shared (all users can read/write/execute rights) drive and opens an excel file. UserA closes the file or modifies it. When UserA reopens the file in 5 secs or less, the file seems to be lock by the computer that UserA is on! When UserA had closed the file, UserB on another computer tries to open the file and it says

> On 15 Feb 2018, at 22.16, Travis Dolan <travis.dolan at gmail.com> wrote: > > It would look as though the changes have now negatively affected a "normal" user from logging in. > > > telnet host 143 > > a login username password > > > a NO [AUTHENTICATIONFAILED] Authentication failed. > > > telnet host 143 > > 1 login

Hello, I tried to configure a very simple case of Asterisk using SIP userA --- Asterisk server ---- userB sip.conf [userA] type=friend username=userA host=dynamic nat=no context=test [userB] type=friend username=userB host=dynamic nat=no context=test In extensions.conf [test] exten => 1000,1,Dial(SIP/userA) exten => 2000,1,Dial(SIP/userB) I make a call from userA to userB, it works,

Hi After successfully setting up dovecot, I see this error in the logs. Aug 30 22:41:45 mail dovecot: auth-worker(default): sql(sbrereton at domain.co.uk,64.88.168.84): Password query returned multiple matches Aug 30 22:41:52 mail dovecot: pop3-login: Aborted login (auth failed, 1 attempts): user=<sbrereton at domain.co.uk>, method=PLAIN, rip=64.88.168.84, lip=127.0.0.1, TLS Can you tell

Hi all, Has anyone encountered this: On ServerA, I make this directory: /var/ftp/pub/userA with ownership root.root It gets rsynced to serverB with this command: rsync -avzgorp --delete -e ssh /var/ftp/pub/ root at serverB:/var/ftp/pub/ However, when I change the ownership of /var/ftp/pub/userA to userA.userA, this change is not rsync-ed to serverB. Is there any option to achieve this? Thank