similar to: Proxying for some users and having the rest local?

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

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

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

On Dec 7, 2015, at 4:21 PM, Gernot Zander <debian at scorpio.in-berlin.de> wrote: > > Hi, > > am 7 Dez schrieb Marks, Connor: >> Well I just need to monitor the UPS battery for testing and I do about >> 10 UPS's a day. So having to restart my computer every time gets old >> real quick. > > In that case - what about not starting nut-client (upsmon)

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

On Wed, 8 Feb 2023, Aki Tuomi wrote: > Can you try setting imapc_sasl_mechanisms to login, maybe it works better? And Stephan Bosch <stephan at rename-it.nl> wrote: > Can you make a protocol log (tcp dump of commands sent by client and > replies sent by server) for one of these sessions? e.g. using ngrep if > connections aren't secured. I was using imaps initially.

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, It seems that master user login does not work with the 'pass=yes' option as recommended and documented. I defined a master user passdb as documented. In addition, I have a passdb sql. If 'pass=yes' is defined then it seems that dovecot recognizes the master login, verifies the master password but then attempts to verify the ***master*** password again with the ***user***

using successfully active/active replica. trying to add a proxy node in front. this proxy node should do the auth with the same ldap passdb settings as the replica in addition (later with kerberos). so i add to 10-auth.conf on the proxy: default_fields = proxy=y host=imap.myserver.lan port=993 any idea why on the backend the user is empty in the logs? on the proxy: imap-login: Error:

Hello, I'm running dovecot 1.2.15 and I'm having a problem proxying a user to another host, when this user is logged in with a masteruser. I have two dovecot servers configured to serve half of the users locally and to proxy the other half to the other host. Proxying is done using the masteruser feature (username*proxy) and it works as expected as the following test shows: # nc

Greetings, cvsup.uk.FreeBSD.org is outdated. I know this is not the proper list, but which one is? -- Best Wishes, Stefan Lambrev ICQ# 24134177

Well I just need to monitor the UPS battery for testing and I do about 10 UPS's a day. So having to restart my computer every time gets old real quick. -----Original Message----- From: Rob Crittenden [mailto:rcrit at greyoak.com] Sent: Monday, December 07, 2015 11:49 AM To: Marks, Connor; nut-upsdev at lists.alioth.debian.org Subject: Re: [Nut-upsdev] Stopping Machine powering off On

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

Dear all, We're slowly progressing towards migration, and now run into dscyn dumping core when trying to sync mailboxes from the old imap server. Needless to say that not one byte get's transferred. On the old.server all I see is a correct login. This is what we get for one example user: server:~# doveadm -v -D backup -R -u USER imapc: doveadm(root): Debug: Loading modules from

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

Hi, am 7 Dez schrieb Marks, Connor: > Well I just need to monitor the UPS battery for testing and I do about > 10 UPS's a day. So having to restart my computer every time gets old > real quick. In that case - what about not starting nut-client (upsmon) at all? upsc (to see the output of the ups) requires nut-server only. Or, if you really want upsmon: - Set up a dummy ups _and_

Hi, am 7 Dez schrieb Charles Lepple: >> MONITOR dummyups at localhost 1 monmaster masterpass master >> MONITOR testups at localhost 0 monmaster masterpass master >> MINSUPPLIES 1 > To simplify, you could eliminate "dummyups" and use "MINSUPPLIES 0". Maybe there's a bug. To monitor an UPS wich doesn't supply power to a raspi I used: MONITOR

Hey folks, So what's the word on AHCI and bios drive geometry? I'm having a real pain of a time trying to get some 750gb sata drives running on my FreeBSD7 box in AHCI mode. It doesn't seem to matter what disk geometry I suggest to sysinstall, something complains of an invalid disk upon booting it. Actually, in AHCI mode the bios screen doesn't report any information on