similar to: A sqlite-based quota dict

Testing using the mysql dict for quota storage (dovecot-2.0.12-2_127.el5), and ran into a couple issues. First is a permissions issue: dovecot: lmtp(26786, dude at test.tld): Error: net_connect_unix(/var/run/dovecot/dict) failed: Permission denied (euid=5000(<unknown>) egid=5000(<unknown>) missing +r perm: /var/run/dovecot/dict, euid is not dir owner) The file

Hi, I have setup the latest Dovecot and Sieve with dict in order to read rules from MySQL and works fine: sieve_before = dict:proxy::sieve;name=activesql;bindir=~/.sieve-bin dict { sieve = mysql:/etc/dovecot/dovecot-dict-sieve-sql.conf.ext } # cat /etc/dovecot/dovecot-dict-sieve-sql.conf.ext connect = host=10.1.1.1 dbname=dovecot user=dovecot password=Ciao map { pattern =

Hello, i'm using dict quota stored in mysql (/etc/dovecot/dovecot-dict-quota.conf): connect = host=localhost dbname=vmail user=dovecot password= # CREATE TABLE quota ( # username varchar(100) not null, # bytes bigint not null default 0, # messages integer not null default 0, # primary key (username) # ); map { pattern = priv/quota/storage table = quota username_field =

Op 4/28/2017 om 10:58 AM schreef Alessio Cecchi: > Hi, > > I have setup the latest Dovecot and Sieve with dict in order to read > rules from MySQL and works fine: > > sieve_before = dict:proxy::sieve;name=activesql;bindir=~/.sieve-bin > > dict { > sieve = mysql:/etc/dovecot/dovecot-dict-sieve-sql.conf.ext > } > > # cat

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

Hello all, I'm sure this has been covered somewhere before, but my googlefu is not up to the challenge. Basically, I'm trying to configure quota plugin to use a dictionary service (specifically proxy with mysql) so that I can store the quota usage in a database and use that information in a lookup for postfix to reject mail if over quota. I'm doing this because postfix+avamis+dovecot

Hello, after upgrade my mailsystem to dovecot version 2.1.7, dovecot doesn't work properly. something went wrong in dict service connecting the postgres backend. that happens not on every connection. the db connection data are correct, no difference connecting via tcp or linux socket. dovecot log entries: Jun 23 23:19:10 mx dovecot: dict: Panic: file driver-pgsql.c: line 84

I've been mucking about, experimenting with the expire plugin and using a dictionary. I've got the iteration query working when I do a normal expunge using: doveadm expunge -A mailbox "INBOX.Trash" savedbefore 1w and expunging works as expected. However, I've got over 12,000 accounts on this server, so I was hoping using the expire plugin to could help out. I've

Hello everyone, I successfully set up the mail_crypt plugin using folder keys, and require user's key to be encrypted with a password using mail_crypt_require_encrypted_user_key = yes. As I'm trying to streamline the process of creating a user, and want to develop an application in PHP to help me in that process, I'm very interested in the doveadm HTTP API. Although the

Hello, I've set up user quota and domain quota for dict SQL and all seems OK. New mail for user increase the user quota and the domain quota. Deleting email count down user quota and domain quota. But in case of SQL failure, I'm trying to rebuild the user quota and domain quota with doveadm quota recalc. The problem is that the command : 'doveadm quota recalc -u foo at bar'

I spent an evening, again, reading up on quota. This time I think my search foo was strong enough. I found guidance and came up with the following: sed -i -e "s/#quota = /sqlquota = /w /dev/stdout" /etc/dovecot/dovecot.conf Sets up a dovecot dictionary of sqlquota to the default file of /etc/dovecot/dovecot-dict-sql.conf.ext cat

Thanks for your answer, Timo! :) I send to you my configoration for reproducing. Please, follow the link, because configuration is a very big, there will be more easy to read and understand My configuration Dovecot 2.2.19 <http://www.heypasteit.com/clip/28CW> Below the same my configuration Dovecot 2.2.19 here. BEGIN of configuration --------------------- # doveconf -n # 2.2.19:

Hi, I'm using dict quota with mysql for track them via SQL query instead of read maildirsize file. Primary quota and enforcing is provided via userdb and is "maildir" type. Since dovecot 2.1.10-13 (but perhaps even before) when a new user log in via POP/IMAP or receive an email for the first time dovecot created the entry for the users in the table "quota" of dovecot

Does dovecot compute that values for quota2 with each email it updates for the user?? Or only an incremental change? I ask because I am looking at migrating all the user mail from the old server to the new and building a new sql database.? All I see is: dovecot-dict-sql.conf.ext: connect = host=/var/lib/mysql/mysql.sock dbname=postfix user=postfix password=$Postfix_Database_Password map {

Keywords: dovecot, dict, quota, postgre sql, broken pipe, remote disconnected Having Dovecot 2.2.22 (fe789d2) with Postgre SQL 9.5 (9.5.5-0ubuntu0.16.04) as the backend. I do not understand why quota service is not working, not seeing it as a configuration error at least. My quotas are DICT/SQL based. OS: Ubuntu 16.0.4.1 32-bit (Linux XXX 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:36:54

On 2/12/19 12:38 PM, Aki Tuomi via dovecot wrote: >> On 12 February 2019 at 18:23 Robert Moskowitz via dovecot <dovecot at dovecot.org> wrote: >> >> >> Does dovecot compute that values for quota2 with each email it updates >> for the user?? Or only an incremental change? >> >> I ask because I am looking at migrating all the user mail from the old

Hi I just configure dovecot with the second dictionary for the domain quota dict { quotadict = mysql:/usr/local/etc/dovecot-quota.conf quota_domain = mysql:/usr/local/etc/dovecot-quota-domain.conf } plugin { quota = dict:user::proxy::quotadict quota2 = dict:domain:%d:proxy::quota_domain } and the dovecot-quota-domain.conf looks like this : connect = host=xxx dbname=xxx

Aki Tuomi wrote on Thu, 16 Aug 2018 21:03:44 +0300 (EEST): > Can you provide doveconf -n please? Thanks for the quick reply. I think I already provided the most relevant portions of config. I ran a doveconf -n and it doesn't reveal important information like sql setup. I'll do my best to sum up the relevant parts below, anyway. But first I would like to know how the

I have dovecot version 2.1.7 and I have quota configured as: ----------------------------------- dict { quota_domain = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } mail_plugins = quota protocol imap { mail_plugins = quota quota imap_quota } plugin { quota = dict:domain:%d:proxy::quota_domain quota_rule = *:storage=1M quota_rule2 = Trash:storage=+100M }

Hi, In our setup, we use two quota roots. One for user quota and one for domain quota. If a user has no quota, then the domain quota is applied. For a user with user quota this is how it looks: # doveadm quota get -u test at shellz.nl Quota name Type Value Limit % Domain quota STORAGE 1439155 2560000 56 Domain quota MESSAGE 21257 - 0 User quota STORAGE 0 102400 0