similar to: Plugins/Mailcrypt: mail_crypt_private_password not assigned by password_query

1) Misspelled message ''killing umanaged domain'' (must be killing UNmanaged domain) 2) more serious. I found this message after disappearance of virtual machine created early. I restart XAPI tool stack and machine was killed (not shutdowned, but completely removing). Here log (from machine where domain was resident) Main line in log file I suspect:

Let's say one has a SQL table with following fields for John Doe: login: u0007 password: {SHA1}... mailhome: /path/to/joeshome email: john.doe at example.com To log in, for internal policy reasons, John MUST make use of his userid "u0007". So, in the password_query, one would need something like: ... WHERE login = '%u' ... On the other hand, for receiving mail thru

Hello- Sorry if this is a noob question, but I cant seem to get my password_query to work with dovecot + mysql. Im using 'Password verification by SQL server' at: http://wiki2.dovecot.org/AuthDatabase/SQL trying to modify it to work with my encrypted passwords in the DB. Im using the following which isnt working: password_query = SELECT NULL AS password, \ 'Y' as

Hello, I use dovecot + postfix with postfix sasl authentication by dovecot auth service. I have one question. Is it possible to have separate password_query only for auth service. I have two fields in database, one permits login to imap pop, second I want to use to permit login to smtp. Please explain how to set this (if it is possible) or give me some direction and sorry my English. --

Hello, I am using the mail_crypt plugin with Dovecot 2.3 and have issues trying to use a mail crypt private password which contains a percent "%" character as you can see below: $ doveadm -o plugin/mail_crypt_private_password=SomethingWith\%Percent mailbox cryptokey generate -u email at domain.tld -URf doveadm(email at domain.tld): Error: Failed to expand plugin setting

> > > Hello, > > I am using the mail_crypt plugin with Dovecot 2.3 and have issues trying to use a mail crypt private password which contains a percent "%" character as you can see below: > > $ doveadm -o plugin/mail_crypt_private_password=SomethingWith\%Percent mailbox cryptokey generate -u email at domain.tld -URf > > doveadm(email at domain.tld):

??????? Original Message ??????? On Tuesday, July 2, 2019 6:21 PM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > Hi, you need to escape % with %%. We are aware of a bug affecting when % comes in from some field via userdb, and we are looking into how to fix this. Hi Aki, Thank you very much for your very fast answer. I will then simply double the percent character as workaround

> > > ??????? Original Message ??????? > On Tuesday, July 2, 2019 6:21 PM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > Hi, you need to escape % with %%. We are aware of a bug affecting when % comes in from some field via userdb, and we are looking into how to fix this. > > Hi Aki, > > Thank you very much for your very fast answer. I will then

??????? Original Message ??????? On Tuesday, July 2, 2019 6:21 PM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > Hi, you need to escape % with %%. We are aware of a bug affecting when % comes in from some field via userdb, and we are looking into how to fix this. Aki, I was wondering, does this bug also affect the changing of a cryptokey password using this command: $ doveadm

On 2.7.2019 23.27, mabi wrote: > ??????? Original Message ??????? > On Tuesday, July 2, 2019 6:32 PM, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > >> I don't actually recommend using password directly from user as password for private keys, I recommend running them thru some hash / pkcs5 before that. > That's a great idea and makes things even safer. I

On 4.7.2019 16.05, mabi via dovecot wrote: > ??????? Original Message ??????? > On Thursday, July 4, 2019 11:18 AM, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > >> It depends. You can use either one, seehttps://wiki2.dovecot.org/Variables >> >> I think the safest option would be setup LDAP so that the private >> password would be only readable by

??????? Original Message ??????? On Tuesday, July 2, 2019 6:32 PM, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > I don't actually recommend using password directly from user as password for private keys, I recommend running them thru some hash / pkcs5 before that. That's a great idea and makes things even safer. I don't know much about PKCS5 but would SHA512 also

??????? Original Message ??????? On Thursday, July 4, 2019 11:18 AM, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > It depends. You can use either one, seehttps://wiki2.dovecot.org/Variables > > I think the safest option would be setup LDAP so that the private > password would be only readable by self, and have dovecot use bind > authentication. This way you can

This patch updates dbomatic, taskomatic and host-register to use the new C++ wrapped ruby QMF bindings. It also fixes a couple of bugs along the way including the 0 cpu bug for host-register. This is a compilation of work done by myself and Arjun Roy. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 111 ++++++-------