similar to: Avoiding logging password when dict lookup fails

logging some error,dict process is not dead. hfh at cndns.com From: Aki Tuomi via dovecot Date: 2019-05-09 14:21 To: hfh at cndns.com; dovecot Subject: Re: dict lookup too long time On 9.5.2019 8.00, hfh--- via dovecot wrote: hi, The following error message sometimes appears on my server log,it causes the mailbox to exceed the disk capacity limit. May 9 09:54:11 imap dovecot: imap(hfh at

hi, The following error message sometimes appears on my server log,it causes the mailbox to exceed the disk capacity limit. May 9 09:54:11 imap dovecot: imap(hfh at cndns.com): Error: dict-client: Lookup 'priv/quota/storage' failed: Connection closed: read(size=8192) failed: Connection reset by peer (reply took 2.728 secs (2.729 in dict wait, 0.000 in other ioloops, 0.000 in locks))

Hello, I get last_login_dict: Failed to write value: dict-server returned failure: sql dict: commit failed randomly in the logs: --- ???????1 mailserver dovecot: imap(test-email-bb at exemple.com) <NtiT9H2SFIVcuGID> [xxx.xxx.xxx.xxx]: Error: last_login_dict: Failed to write value: dict-server returned failure: sql dict: commit failed: INSERT, UPDATE command denied to user

I am having trouble with using a custom daemon listening on a socket together with the quota plugin. My configuration is: quota = dict:User quota::dict:/tmp/dovecot-proxy-dict:: The problem is that dovecot sends keys without usernames, for example: priv/quota/storage Is it possible to get around this limitation without code modification? Also, is it planned to support the

All I did was ??? - create a sqlite database with: # sqlite3 /tmp/storage.db (/run only to test for perm issues in other folders) ??? - change it's owner to mail (that's the user owning the mail files): # chown mail:mail /tmp/storage.db ??? - point dovecot to the file in "dovecot-dict-sql.conf.ext" with "connect = /tmp/storage.db" ??? - enable quota in

...and then I found the commit I was looking for. It's fixed in https://github.com/dovecot/core/commit/ab80122c68bfe5c3dbae2b4d782f4181122710a1.patch Aki > On 03 February 2019 at 20:06 Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > Can you try out the attached patch? > > Aki > > > On 03 February 2019 at 17:17 Marcel Menzel <mail at mcl.gg>

Good day to everyone Currently, I'm trying to implement the sieve "vacation" plugin with the sieve "Extdata" plugin to lookup information from a MySQL remote server. I'm following the instructions in the documentation: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Extdata ===== I have the following error === Apr 09 13:46:51 mail dovecot[5512]: dict: Error:

Is there a way to change the lookup string (correct me if I am wrong here) regarding the schema attribute Samba uses for AD authentication? Not if this is accurate but it seems the AD lookup queries the CN attribute within an active directory user account. My problem is I have legacy user accounts which under the CN attribute have not just their login name but their last name as well: ex.

Dear all, Is it possible to perform dict lookups with a SQL backend, without specifying the username_field in the SQL query? I am using the dict to retrieve a Sieve script. My dict configuration looks like this: map { pattern = priv/sieve/data/$id table = sieve_scripts username_field = email value_field = data fields { id = $id } } I don't want to specify the username

Hi, How difficult would it be to try to hack some extension to the Dovecot dict mechanism for someone unfamiliar with the code? I'm using SQL as a backend and am looking for, at a minimum, the ability to specify a WHERE clause in addition to the built-in one that feeds the current username. The field name to test the additional value against would be necessary as well of course.

Hi, I am beginning to see many entries like: Sep 10 21:32:06 mail1 dovecot: imap(user1 at example1.com): Warning: read(/var/run/dovecot/dict): dict lookup took 20 seconds Sep 10 21:32:11 mail1 dovecot: imap(user2 at example2.com): Warning: read(/var/run/dovecot/dict): dict lookup took 25 seconds Sep 10 21:32:16 mail1 dovecot: imap(user3 at example3.com): Warning: read(/var/run/dovecot/dict):

Can you try out the attached patch? Aki > On 03 February 2019 at 17:17 Marcel Menzel <mail at mcl.gg> wrote: > > > All I did was > > ??? - create a sqlite database with: # sqlite3 /tmp/storage.db (/run > only to test for perm issues in other folders) > > ??? - change it's owner to mail (that's the user owning the mail files): > # chown mail:mail

PCI CARD: Model 3C095C - TX - M MBA v4.32 Result: DHCP ok TFTP ok (pxelinux.0 transfer correct) But nothing happens more, no SAY messages, no PROMPT, no DISPLAY, no KERNEL loading Thanx Peter, see you _________________________________________________________________ Recibe ofertas de empleo adaptadas a tu perfil. [1]Introduce tu CV en MSN Empleo.

When I run the following "net lookup sid" command, I get: # net lookup sid S-1-5-21-1908027396-2059629336-315576832-12220 S-1-5-21-1908027396-2059629336-315576832-12220 1 (User) \fhess This is wrong in that "\fhess" should be "NIST\fhess". The other direction works fine: # net lookup name "NIST\fhess" S-1-5-21-1908027396-2059629336-315576832-12220 1

>>>> Set >>>> >>>> ssl_client_ca_file=/path/to/cacert.pem to validate the certificate >>> >>> Can this be the Lets Encrypt cert that we already have? In other words we have: >>> ssl_cert = </etc/pki/dovecot/certs/dovecot.pem >>> ssl_key = </etc/pki/dovecot/private/dovecot.pem >>> >>> Can those be

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Can you provide steps on how to reproduce this? Tracked as DOP-899 </div> <blockquote type="cite"> <div> On 03 February 2019 at 16:50 Aki Tuomi < <a

On 28.3.2019 22.34, Robert Kudyba via dovecot wrote: >>>>> Set >>>>> >>>>> ssl_client_ca_file=/path/to/cacert.pem to validate the certificate? >>>> >>>> Can this be the Lets Encrypt cert that we already have? In other >>>> words we have: >>>> ssl_cert = </etc/pki/dovecot/certs/dovecot.pem

Looks like the dict-proxy code doesn't currently do escaping newlines properly, but it still accidentally happens to work, because the data is stored in the escaped form. I'm thinking about fixing this, but this might break somebody's existing dict usage. But then again maybe nobody is actually using it now, especially because it hasn't been working exactly as expected. So, can

On 29 Oct 2015, at 12:15, Christian Kivalo <ml+dovecot at valo.at> wrote: > > Hi, > > I configured shared mailboxes and get an error when i use SQL as the acl_shared_dict. It works when i use a file instead. With SQL as the shared_dict, dict crashes. > > Oct 29 10:12:13 uschi dovecot: dict(27421): Panic: file dict-sql.c: line 670 (sql_dict_iterate): assertion failed:

Hi, after upgrading my database I kept on getting those errors. It seems like later versions of databases have strict mode enabled by default and it must either be disabled or change the dovecot database schema. Besides the password, would anyone know what other fields must be changed to the dovecot schema and have a default value? Is there any other dovecot schema for strict mode? Lefteris