similar to: Using userdb/passdb data in director_username_hash

> On 12 April 2019 21:09 Mark Moseley via dovecot <dovecot at dovecot.org> wrote: > > > TL;DR: > > Can director_username_hash use %{userdb:...} or %{passdb:...} ? > > ==================================== > > This is on Ubuntu Precise, running dovecot 2.2.36. It's a fully production, director-ized env, so assume everything is working correctly. Happy to

Our directors hash by domain (director_username_hash = %d), as some of our users share folders with other users of the same domain. We now started using director tags to map domains to their backends. Unfortunately doveadm director map seems no to work with director_username_hash = %d user??? hash??? mail server ip expire time <unknown> 432784257 10.44.88.1?? 2020-11-23 13:10:55

Hi, I get this warning when compiling 3.0.25rc1 on SLED 10: Compiling nsswitch/pam_winbind.c nsswitch/pam_winbind.c: In function `pam_sm_authenticate': nsswitch/pam_winbind.c:1623: warning: passing arg 1 of `free' discards qualifiers from pointer target type corresponds to : if ( real_username ) { free( real_username ); } This is the only warning and

On 26/09/2018 08:34, Aki Tuomi wrote: > # before current passbd > passdb { > driver = passwd-file > args = username_format=%Lu /etc/dovecot/aliases > } > > # into /etc/dovecot/aliases > alias at user:::::::user=real_username noauthenticate > > This hopefully works. > > Aki This does appear to work, thanks! As an optimization of the alias

On Wed, Sep 26, 2018 at 09:34:07AM +0300, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > # before current passbd > passdb { > ? driver = passwd-file > ? args = username_format=%Lu /etc/dovecot/aliases > } > > # into /etc/dovecot/aliases > alias at user:::::::user=real_username noauthenticate > > This hopefully works. This seems to work fine and I had the

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

Hi, Our organization is currently using a passwd-file user database for our Dovecot installs. However, we now want to provide simple username aliases. We currently use usernames that are -not- equal to the email address, but due to the fact that many major email clients/providers do not even allow you to specifiy a username, we now want to provide aliases where the username is equal to the

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?

Dovecot version: 2.2.25 (7be1766) I?m looking into an issue we?re having with a new setup. We have one fronted host with two backend hosts, and we?re attempting to use doveadm to allow us to administer sieve on the frontend and have it replicated to the backend hosts. When I attempt to use doveadm sieve put on the frontend host, i get the following on the frontend host: frontend-machine $ cat

On 25.09.2018 16:24, Eirik Rye wrote: > Hi, > > Our organization is currently using a passwd-file user database for > our Dovecot installs. However, we now want to provide simple username > aliases. > > We currently use usernames that are -not- equal to the email address, > but due to the fact that many major email clients/providers do not > even allow you to specifiy a

Hello, when trying to set up a migration scenario from my old mailbox-servers to my new dovecot-cluster, I get a coredump from dovecot/lmtp when proxying mail-delivery to more than one recipient on the old mailbox-server. My setup: 3 director-hosts (Debian stretch) are proxying to a pair of replicator-hosts and during migration also to the old mailbox-server. For migration the not-migrated

On 28.09.2018 00:08, Florian Pritz wrote: > On Wed, Sep 26, 2018 at 09:34:07AM +0300, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: >> # before current passbd >> passdb { >> ? driver = passwd-file >> ? args = username_format=%Lu /etc/dovecot/aliases >> } >> >> # into /etc/dovecot/aliases >> alias at user:::::::user=real_username

Hi Jerry et al, the parsing of the 'username map' file seems to be broken in 3.0.5pre1 and a few earlier releases. The '!' at the beginning of a line is ignored. Something like !lp = lp !chbeyer = chbeyer !guest = guest nobody = * doesn't work anymore :-( from the man page: [ snip ] If any line begins with an '!' then the processing will stop

dovecot 2.3.13 Hi, I'm looking for a way to make director use a user at domain that is returned by the database for hashing but actually send the original user at domain in the proxied request. I cannot seem to find a way. I can change the name used for hashing by just returning a different user from the db. but that user is also the one that is send in the proxied request. this is

I'm in a fairly standard cluster environment: shared storage, bunch of servers each acting as both proxies and backends. We do /bin/checkpassword authentication, allowing a great deal of flexibility...protection against brute force, billing mechanisms, but relevant to this issue, I have it set up to allow users to login with either their username (if they are in one of our default

There seems to be a bug with RFC822 processing in ltmp proxying that doesn't quote local parts that, for example, contain spaces. director config: director_username_hash = %Ln lmtp_proxy = yes recipient_delimiter = + protocol lmtp { auth_socket_path = director-userdb auth_username_chars = auth_username_format = %Ln passdb {

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