search for: mailbox_id

Displaying 4 results from an estimated 4 matches for "mailbox_id".

2020 May 14
0
[Dovecot v2.3.9.3] HTTP API Endpoint for mailbox cryptokey operations
...ck user=<user> password=<pass> dbname=<db>" # User's private keys map { pattern = priv/$mailboxid/vendor/vendor.dovecot/pvt/crypt/privkeys/$digest table = virtual_users_cryptokeys_priv_dict username_field = email value_field = key_contents fields { mailbox_id = $mailboxid key_digest = $digest } } map { pattern = priv/$mailboxid/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/pvt/crypt/privkeys/$digest table = virtual_users_cryptokeys_priv_server_dict username_field = email value_field = key_contents fields { mailbox...
2006 Jul 24
0
Dynamic Scope plugin
...gt; Post.with_scope({ :find => { :conditions => [ ''user_id = ?'', params[:user_id] ]}, :create => { :user_id => params[:user_id] } }) { yield } scope_messages_to_mailbox { yield } #=> Message.with_scope({ :find => { :conditions => [ ''mailbox_id = ?'', params[:mailbox_id] ]}, :create => { :mailbox_id => params[:mailbox_id] } }) { yield } SVN: http://joshpeek.com/svn/plugins/dynamic_scope/ -- Posted via http://www.ruby-forum.com/.
2012 Oct 10
1
Clarifications on Pigeonhole and MySQL lookups
...ble (storing the domain info) and a mailbox table (storing the mailbox info, but the username is composed by the local part, stored in this table, and the domain part is a FK to the domain table, using an id). Do you think it's possible to run a join query on domain+mailbox to retrieve the mailbox_id needed to query the table for the filters? Or do we have to create the filter table and store the local at domain.ext info there ("relaxing" the integrity relationships between tables)? How do we specify which filters are enabled for any given user? We originally thought of an "E...
2012 Feb 13
6
Dovecot v2.2 plans
...he dict configuration to allow things like: - mixed backends for different hierarchies (e.g. priv/mailbox/* goes to a file, while the rest goes to sql) - allow sql dict to be used in more relational way, so that mail annotations could be stored with tables: mailbox (id, guid) and mail_annotation (mailbox_id, key, value), i.e. avoid duplicating the guid everywhere. Things to think through: - How to handle quota? Probably needs to be different from regular mail quota. Probably some per-user "metadata quota bytes" counter/limit. - Dict lookups should be done asynchronously and prefetched as...