- dovecot - dovecot.org

Domain quota
by Evgeny Basov 02 Feb '15

02 Feb '15

Hello. I'm tried to use domain quota: plugin { quota = dict:Domain quota:%d:redis:host=127.0.0.1:prefix=domain/ quota_rule = *:storage=0 quota2 = dict:User quota::redis:host=127.0.0.1:prefix=user/ quota2_rule = *:storage=0 quota3_rule = Trash:storage=+5%% } but got next problem with it. Init state: # doveadm quota get -u "testacc(a)m.tld" Quota name Type Value Limit % Domain quota STORAGE 27070 204800 13 Domain quota MESSAGE 21 - 0 User quota STORAGE 27068 - 0 User quota MESSAGE 18 - 0 # doveadm quota get -u "testacc2(a)m.tld" Quota name Type Value Limit % Domain quota STORAGE 27070 204800 13 Domain quota MESSAGE 21 - 0 User quota STORAGE 2 - 0 User quota MESSAGE 3 - 0 Make recalc: # doveadm quota recalc -u "testacc2(a)m.tld" and got: # doveadm quota get -u "testacc2(a)m.tld" Quota name Type Value Limit % Domain quota STORAGE 2 204800 0 Domain quota MESSAGE 3 - 0 User quota STORAGE 2 - 0 User quota MESSAGE 3 - 0 # doveadm quota get -u "testacc(a)m.tld" Quota name Type Value Limit % Domain quota STORAGE 2 204800 0 Domain quota MESSAGE 3 - 0 User quota STORAGE 27068 - 0 User quota MESSAGE 18 - 0 All values of all domain quota are equals. Execute recalc one more time: # doveadm quota recalc -u "testacc(a)m.tld" # doveadm quota get -u "testacc(a)m.tld" Quota name Type Value Limit % Domain quota STORAGE 27068 204800 13 Domain quota MESSAGE 18 - 0 User quota STORAGE 27068 - 0 User quota MESSAGE 18 - 0 # doveadm quota get -u "testacc2(a)m.tld" Quota name Type Value Limit % Domain quota STORAGE 27068 204800 13 Domain quota MESSAGE 18 - 0 User quota STORAGE 2 - 0 User quota MESSAGE 3 - 0 How can I get fast realtime changed domain quota? Used dovecot 2.2.13.

2 1

auth: Error: auth worker: Aborted request: Lookup timed out
by ML mail 01 Feb '15

01 Feb '15

Hello, I was checking the errors on my mailbox server using "doveadm log errors" and found that around 2-3 times a day I get the following error: Jan 29 22:14:43 auth: Error: auth worker: Aborted request: Lookup timed out Any ideas if this is a bad sign? For example some timeout on my side which is too low or is it just an aborted connection from the side of the IMAP client? The configuration on my Dovecot mailbox server can be found here: http://article.gmane.org/gmane.mail.imap.dovecot/80823 It is a Debian 7 box with standard debian packages. Best regards ML

4 6

[Bug ?] IMAP keywords are not preserved during mailbox conversion
by Alexander Moisseev 01 Feb '15

01 Feb '15

IMAP keywords (Thunderbird Tags) are not preserved during Maildir to mdbox conversion. For mailbox conversion I am using the command: # doveadm -o mail_location=maildir:~/Maildir sync -u user(a)example.com mdbox:~/mdbox After conversion all Thunderbird Tags are lost. Is it a bug or expected behavior? -- Alexander

1 0

LDAP Quota Limits & Warnings
by Leander Schäfer 30 Jan '15

30 Jan '15

I found this on the dovecot wiki: The following limit names are supported: * *storage*: Quota limit in kilobytes, 0 means unlimited. * *bytes*: Quota limit in bytes, 0 means unlimited. * *messages*: Quota limit in number of messages, 0 means unlimited. This probably isn't very useful. * *backend*: Quota backend-specific limit configuration. * *ignore*: Don't include the specified mailbox in quota at all. As I understood it, all 5 limit categories are valid to use with maildir format while only "storage" and "messages" are valid to use with dmbox format, right? Also the "ignore" limit may appear more than one time for a user - like Trash:ignore and Spam:ignore, right? So I assumed following should work - and it does - except for "ignore" - even though LDAP does not hold multiple values for it - only a single one for each limit: user_attrs = [...] mailQuotaStorage=quota_rule=*:storage=%$, mailQuotaMessages=quota_rule2=*:messages=%$, mailQuotaIgnore=quota_rule3=*:ignore=%$ pass_attrs = [...] mailQuotaStorage=userdb_quota_rule=*:storage=%$, mailQuotaMessages=userdb_quota_rule2=*:messages=%$, mailQuotaIgnore=userdb_quota_rule3=*:ignore=%$ And unfortunately /var/log/maillog tells me: dovecot: imap(abuse(a)netocean.local): Error: user abuse(a)netocean.local: Initialization failed: Failed to initialize quota: Invalid quota root quota: Invalid rule *:ignore=Trash: Unknown rule limit name: ignore Yet /var/log/debug.log sounds a bit more promising ... but then again not really ... dovecot: imap: Debug: Added userdb setting: mail=maildir:/usr/local/www/default/mail/user@mydomain.tld dovecot: imap: Debug: Added userdb setting: plugin/quota_rule=*:storage=1048576 dovecot: imap: Debug: Added userdb setting: plugin/quota_rule2=*:messages=10 dovecot: imap: Debug: Added userdb setting: plugin/quota_rule3=*:ignore=Trash dovecot: imap(abuse(a)netocean.local): Debug: Effective uid=2110, gid=2110, home=/var/vmail/user(a)mydomain.tld/mail dovecot: imap(abuse(a)netocean.local): Debug: Quota root: name=User quota backend=maildir args= dovecot: imap(abuse(a)netocean.local): Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=0 dovecot: imap(abuse(a)netocean.local): Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=10 dovecot: imap(abuse(a)netocean.local): Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=10 Additionally, if one of the two working quotas (storage & messages) is exceeded than Dovecot sends out a warning from this setting: plugin { quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u # What message to send to IMAP clients (and SMTP senders) when quota is exceeded? quota_exceeded_message = Quota exceeded, please go to http://MyDomain.TLD for instructions on how to fix this. } No my question is how to provide two different warnings. One for storage like: Sorry, you're mail storage is full. Please delete some. And a second for messages like: Sorry, you've too many messages. Please delete some. Thanks & Best Regards Leander

1 0

Troubleshooting doveadm for Solr Configuration
by Kevin Laurie 30 Jan '15

30 Jan '15

Hey guys, I am trying to pinpoint where the problem with my dovecot-FTS installation . I am trying to rule out between the Dovecot and the Solr Module. I think if the output below looks OK then the dovecot is fine, and will focus more on the Solr. Appreciate if someone could check and confirm. Thanks root@mail:/etc/dovecot/conf.d# doveadm -D -v fts rescan -u admin(a)email.net doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib20_fts_plugin.so doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so doveadm(admin(a)email.net): Debug: auth input: admin(a)email.net master_user= admin(a)email.net home=/var/vmail/vmail1/ email.net/t/h/a/admin-2014.10.25.07.15.15/ quota_rule=*:bytes=26214400000 doveadm(admin(a)email.net): Debug: Added userdb setting: plugin/master_user= admin(a)email.net doveadm(admin(a)email.net): Debug: Added userdb setting: plugin/quota_rule=*:bytes=26214400000 doveadm(admin(a)email.net): Debug: Effective uid=2000, gid=2000, home=/var/vmail/vmail1/email.net/t/h/a/thai-2014.10.25.07.15.15/ doveadm(admin(a)email.net): Debug: Quota root: name=user backend=dict args=:proxy::quotadict doveadm(admin(a)email.net): Debug: Quota rule: root=user mailbox=* bytes=26214400000 messages=0 doveadm(admin(a)email.net): Debug: Quota warning: bytes=22282240000 (85%) messages=0 reverse=no command=quota-warning 85 admin(a)email.net doveadm(admin(a)email.net): Debug: Quota warning: bytes=23592960000 (90%) messages=0 reverse=no command=quota-warning 90 admin(a)email.net doveadm(admin(a)email.net): Debug: Quota warning: bytes=24903680000 (95%) messages=0 reverse=no command=quota-warning 95 admin(a)email.net doveadm(admin(a)email.net): Debug: Quota grace: root=user bytes=2621440000 (10%) doveadm(admin(a)email.net): Debug: dict quota: user=admin(a)email.net, uri=proxy::quotadict, noenforcing=0 doveadm(admin(a)email.net): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir://var/vmail/vmail1/ email.net/t/h/a/thai-admin.10.25.07.15.15//Maildir/:INDEX=//var/vmail/vmail… doveadm(admin(a)email.net): Debug: maildir++: root=//var/vmail/vmail1/ email.net/t/h/a/admin-2014.10.25.07.15.15//Maildir, index=, indexpvt=, control=, inbox=//var/vmail/vmail1/ sicl.net/t/h/a/thai-2014.10.25.07.15.15//Maildir, alt= doveadm(admin(a)email.net): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u doveadm(admin(a)email.net): Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= doveadm(admin(a)email.net): Debug: fts: Indexes disabled for namespace 'Shared/%u/'

2 1

Re: Uniqueness of dovecot mailbox-guids
by Christian Binder Stadt Freilassing 30 Jan '15

30 Jan '15

If mailbox guids should be unique systemwide, would it be safe to delete all 'dovecot-uidlist' files of the user's mailboxes and then do a doveadm force-resync after mailbox migration? Thanks! Christian ----------------ursprüngliche Nachricht----------------- Von: Christian Binder Stadt Freilassing [christian.binder(a)freilassing.de ] An: "dovecot dovecot.org" [dovecot(a)dovecot.org ] Datum: Thu, 29 Jan 2015 09:24:12 +0100 ------------------------------------------------- > Sorry if this is a duplicate message. I'm new in this mailing list and not sure if > the first message really got posted ... > > Dovecot version: 2.2.9 > > We're using doveadm backup to migrate user mailboxes from cyrus to dovecot. I > defined a master user for the old cyrus mailserver in imapc backend to get access > to all the mailboxes. Now I realized that after migration every user's "Inbox" or > "Trash" on the new dovecot server has the same mailbox-guid, e.g: > > User a: > inbox dd9456... > trash 5549cc... > > User b: > inbox dd9456... > trash 5549cc... > > Is this a wanted behaviour? If i do not migrate with doveadm backup and just > manually create mailboxes, the mailbox-guids are globally unique, e.g: > > User a: > inbox dd9456... > trash 5549cc... > > User b: > inbox c543fe... > trash t49ccc... > > Thanks! > Christian >

1 0

Re: Uniqueness of dovecot mailbox-guids
by Christian Binder Stadt Freilassing 30 Jan '15

30 Jan '15

Update: seems to me that the old cyrus mailserver already uses these non-unique mailbox guids. Is it necessary to have them unique over all private namespaces? Thanks Christian ----------------ursprüngliche Nachricht----------------- Von:Christian Binder Stadt Freilassing [christian.binder(a)freilassing.de ] An:"dovecot dovecot.org" [dovecot(a)dovecot.org ] Datum:Thu, 29 Jan 2015 09:24:12 +0100 ------------------------------------------------- > Sorry if this is a duplicate message. I'm new in this mailing list and not sure if > the first message really got posted ... > > Dovecot version:2.2.9 > > We're using doveadm backup to migrate user mailboxes from cyrus to dovecot. I > defined a master user for the old cyrus mailserver in imapc backend to get access > to all the mailboxes. Now I realized that after migration every user's "Inbox" or > "Trash" on the new dovecot server has the same mailbox-guid, e.g: > > User a: > inbox dd9456... > trash 5549cc... > > User b: > inbox dd9456... > trash 5549cc... > > Is this a wanted behaviour? If i do not migrate with doveadm backup and just > manually create mailboxes, the mailbox-guids are globally unique, e.g: > > User a: > inbox dd9456... > trash 5549cc... > > User b: > inbox c543fe... > trash t49ccc... > > Thanks! > Christian >

1 0

Info on shared folders
by Bobber 30 Jan '15

30 Jan '15

I'm interested in setting up shared folders in a small office environment.Â Can a folder be created and shared with other users from an IMAP client such as Thunderbird? -- *Bob Wooldridge* Blog: http://kc0dxf.net/blog/

2 1

Re: mdbox: Broken virtual size for mail UID ...
by Dennis Schridde 29 Jan '15

29 Jan '15

Hello everyone! I originally asked Timo for help in this case, but I understand he is very busy these days, so I am now posting my questions to this mailinglist. On Sunday 28 Dec 2014 10:02:08 Timo Sirainen wrote: > On 28 Dec 2014, at 07:06, Dennis Schridde <devurandom(a)gmx.net> wrote: > > My harddrives crashed, and now I get "Broken virtual size for mail UID …" > > messages in the dovecot logs from some mdbox folders. I assume the logged > > emails are destroyed forever, but I would like to restore as much as > > possible of them and keep them in their corrupted / incomplete state. How > > do I do that? > > > > I guess what I need is some kind of "doveadm fsck" command, that tries its > > best to limit the damage to a minimum: Inform me about the broken emails > > and then ask me whether they should be stored in truncated form, be > > deleted, etc. Is there such a thing? > > http://dovecot.org/tools/mdbox-recover.pl Thank you! >From what I read in the Wiki and how I understand the script, I should proceed like this: #!/bin/bash broken_storage=$PWD/storage recovered_storage=$PWD/storage-recovered cd ${recovered_storage} n=1 for f in ${broken_storage}/m.* ; do mdbox-recover.pl ${f} for f in msg.* ; do mv ${f} m.${n} $((n++)) done done mv ${broken_storage} storage-backup mv ${recovered_storage} storage exit 0 Afterwards dovecot will now automatically regenerate the dovecot.map.index files from the now bare m.* files, and as the dovecot.index files in the actual mailboxes reference the GUID, and the messages in the m.* files have the GUID embedded, nothing will be lost. Is that correct? To create proper assessment of the damage, I need to know a bit more: 1. In the script on line 43, the comment says: # end of metadata block missing, finish the previous mail That seems to be wrong, since idx2!=-1 and state==STATE_BODY on that line, while I understand it should be -1 and STATE_META if we were still reading the metadata block. I guess it should be something like: # still in data block, finish the previous mail 2. Line 47 reads: # truncated / broken data? just keep writing to previous file That is the only error which could be detected in that script, right? 3. A message could also be corrupted by loosing its complete data block from \001\003 to \001\002, which cannot be detected in the script, right? 4. The only case to detect this and find other unexpected oddities would be to compare each msg.* in size and offset with the messages referenced in the dovecot.map.index file, correct? How do I do that, if the dovecot.map.index does not contain the GUID of the message? Do I need to fuzzy match the file_id, offset and size with my current values, or is there a more reliable way to do this? 5. Metadata refers to the RFC822 mail headers? Or are they also included in the body, and the mentioned metadata is dovecot-only metadata? If the latter, do they also contain the size of the body and similar information? Best regards, Dennis

1 0

Dovecot antispam
by David Mehler 29 Jan '15

29 Jan '15

Hello, This is not specifically a dovecot issue, but to it's antispam plugin, that being the case if private responses are deemed so please do so. I've got a Postfix, amavisd-new, dovecot (delivery and sieve), setup with spamassassin. It's for the most part working fine, here's the problem, false positives and false negatives. The sieve moves spamassassin-tagged messages in to the Spam folder, sometimes it misses either a false positive or negative. What I'm wanting to do and this is where the dovecot-antispam plugin comes in is automatically retrain messages, a false positive or negative needs to be moved and reclassified accordingly. I've found a lot of google results indicating dspam, when I used this the results were terrible after three months of usage I gave up on it. I've thought about using spamc with dovecot-antispam to handle retraining or crm114, but not much on getting this going. If anyone has any information on this or any other non-dspam setup that would work I'd appreciate knowing about it. Thanks. Dave.

2 3