[Dovecot] master user and ACL's
Hi, Quick question...I read in the docs that: "Master user is still subject to ACLs just like any other user, which means that by default the master user has no access to any mailboxes of the user." ... and that the standard workaround is to return master_user=%u from the userdb. But why is the master_user authn-id used in the ACLs and not the authz-id (requested-login-user) ? Isn't the whole point of SASL authz-id semantics to have authorization resolved based on the authz-id? /Peter
[Dovecot] Dsync crash (v2.2.10, sdbox+sis → mbox)
Hi, I'm trying to use dsync to convert sdbox + sis mailboxes to mbox (mbox is chosen here to "re-attach" the attachments to their original place) # dsync -Dv -u $LOGIN -o "mail_location=sdbox:/zfspool/clone_srv_mail/$LOGIN" -o "mail_attachment_dir=/zfspool/clone_srv_attachments" backup "mbox:/zfspool/restore/$LOGIN/mbox:DIRNAME=mBoX-MeSsAgEs:INDEX=/zfspool/restore/$LOGIN/indexes:CONTROL=/zfspool/restore/$LOGIN/control" For 5 users out of a sample of 24, here is what's happening: dsync(user1): Error: read(/zfspool/clone_srv_attachments/cb/0a/cb0aad465a4ff95bf6fa6ece0fba94b43e8892cf-19dc51309fc2f3527e3144c1c7e7-b55eb9176ca1b350e56594b229f9-30810[base64:19 b/l]) failed: Stream is larger than expected (163244 > 163243, eof=1) dsync(user1): Error: copy: i_stream_read() failed: Invalid argument dsync(user1): Panic: file mail-index-transaction-update.c: line 19 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) dsync(user1): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x6889a) [0x7f58a95a189a] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7f58a95a19a2] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f58a955b1cf] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xc0287) [0x7f58a98ca287] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xc3145) [0x7f58a98cd145] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_cache_decision_state_update+0xb6) [0x7f58a98bcb06] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_cache_lookup_headers+0x91) [0x7f58a98be5e1] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xa0ac3) [0x7f58a98aaac3] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0x4a) [0x7f58a98ab04a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x9c021) [0x7f58a98a6021] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x9c151) [0x7f58a98a6151] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_mail_close+0xf5) [0x7f58a98a6295] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_save_cancel+0x48) [0x7f58a98867c8] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x92) [0x7f58a9880e32] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5f) [0x7f58a9886c2f] -> dsync() [0x42f750] -> dsync(dsync_brain_sync_mails+0x459) [0x42e9c9] -> dsync(dsync_brain_run+0x2a1) [0x42ac51] -> dsync() [0x42876f] -> dsync() [0x411c97] -> dsync(doveadm_mail_try_run+0x238) [0x4120a8] -> dsync(main+0x3d1) [0x41aaa1] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f58a91c3d1d] -> dsync() [0x411419] dsync(user2): Error: read(/zfspool/clone_srv_attachments/ad/0c/ad0cef35cc6f0b2dae2197c4ff2b61a2bd58070d-9e8345192ccbf352c21044c1c7e7-6efa5f2e522db350ed3d94b229f9-15470[base64:18 b/l]) failed: Stream is larger than expected (194476 > 194475, eof=1) dsync(user2): Error: copy: i_stream_read() failed: Invalid argument dsync(user2): Panic: file mail-index-transaction-update.c: line 19 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) dsync(user2): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x6889a) [0x7f2e2248d89a] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7f2e2248d9a2] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f2e224471cf] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xc0287) [0x7f2e227b6287] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xc3145) [0x7f2e227b9145] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_cache_decision_state_update+0xb6) [0x7f2e227a8b06] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_cache_lookup_headers+0x91) [0x7f2e227aa5e1] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xa0ac3) [0x7f2e22796ac3] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0x4a) [0x7f2e2279704a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x9c021) [0x7f2e22792021] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x9c151) [0x7f2e22792151] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_mail_close+0xf5) [0x7f2e22792295] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_save_cancel+0x48) [0x7f2e227727c8] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x92) [0x7f2e2276ce32] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5f) [0x7f2e22772c2f] -> dsync() [0x42f750] -> dsync(dsync_brain_sync_mails+0x459) [0x42e9c9] -> dsync(dsync_brain_run+0x2a1) [0x42ac51] -> dsync() [0x42876f] -> dsync() [0x411c97] -> dsync(doveadm_mail_try_run+0x238) [0x4120a8] -> dsync(main+0x3d1) [0x41aaa1] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f2e220afd1d] -> dsync() [0x411419] dsync(user3): Error: read(/zfspool/clone_srv_attachments/23/8a/238a781b53bb4d1b1bee989a5ff38636b616d5c5-41ba47152912f4522c6f44c1c7e7-f3b06c2f5aa1b350d56594b229f9-38650[base64:19 b/l]) failed: Stream is larger than expected (33191 > 33190, eof=1)
Re: [Dovecot] possible quota bug ?
Hi Timo, I'm posting more info about this issue: Sent a message from gmail, delivered via lmtp/lda/sieve -rw--- 1 vmail vmail 1187 Feb 9 15:14 1391966051.M730051P32575.LAB-STO-V-01,S=2392,W=2440 The message was compressed (gz) Maildirsize: 1073741824S 51505 31 2392 1 Move message from INBOX to TRASH Feb 9 15:15:45 LAB-LMB-V-01 dovecot: imap(xxx): copy from INBOX: box=INBOX.Trash, uid=27, msgid=, size=1187 Feb 9 15:15:45 LAB-LMB-V-01 dovecot: imap(xxx): expunge: box=INBOX, uid=32, msgid=, size=2392 Maildirsize: 1073741824S 51505 31 2392 1 1187 1 -2392 -1 De: t...@iki.fi Enviada: Sexta-feira, 7 de Fevereiro de 2014 15:07 Para: dovecot@dovecot.org Assunto: [Dovecot] possible quota bug ? On 30.1.2014, at 16.30, fernando.fig...@uol.com.br wrote: > I was researching deeper this issue, activated debug logs and when I move a > message from one folder to another the message size is different > > Jan 30 18:48:07 imap(xxx@xxx): Info: copy from INBOX: box=INBOX.Sent, uid=17, > msgid=<5520ed0fedee4e3386d08c98d249a...@lab.imap>, size=1048 > Jan 30 18:48:07 imap(xxx@xxx): Info: expunge: box=INBOX, uid=3, > msgid=<5520ed0fedee4e3386d08c98d249a...@lab.imap>, size=1898 > > This is exactly the sizes I see in the maildirsize. But I think these values > should be equals. Yes, they should be equal. I don't know why they wouldn't be. Do your Maildir filenames contain the S=1898 (i.e. the uncompressed size)? Are you delivering mails via Dovecot LDA/LMTP? > > 1073741824S > 2136 1 > 1048 1 > -1898 -1 > > Att > Fernando > > > De: fernando.fig...@uol.com.br > Enviada: Quarta-feira, 15 de Janeiro de 2014 15:11 > Para: dovecot@dovecot.org > Assunto: [Dovecot] possible quota bug ? > > Hi, > > I'm using dovecot 2.2.5 with quota (maildir backend), zlib and expunge > plugins. > > When I list maildirsize file, I get: > > 1073741824S > 17952 16 > > If I receive a new message (example: 1204 bytes compressed and 2524 bytes > plain text), the quota file is write correctly (2524 1 entry). When I move > the message to trash folder (or between user custom folders) the file have > wrong entries: > > 1073741824S > 17952 16 > 2524 1 > 1204 1 (this is the size of the compressed message) > -2524 -1 > > I coudn't find any relation with the config settings causing this problem and > checked the changelog since 2.2.5. Had someone had this same problem? > > Thanks, > Fernando >
Re: [Dovecot] New global ACL mailbox pattern feature in HG
On 7.2.2014, at 17.21, Thomas Leuxner wrote: > * Timo Sirainen 2014.02.07 21:37: > >>> $ doveadm mailbox create -u t...@leuxner.net "Shops/Test" >>> doveadm(t...@leuxner.net): Panic: file acl-global-file.c: line 163 >>> (acl_global_file_find_rights): assertion failed: (file->last_refresh_time >>> != 0) >> >> Fixed: http://hg.dovecot.org/dovecot-2.2/rev/c69ca1f5bc34 > > Crash is gone. Thanks. > > Public/* group=PublicMailboxAdmins lrwsik > > yields an error (Public/ Namespace) while 'Public*' works: > $ doveadm mailbox create -u t...@leuxner.net "Public/Test" > $ doveadm(t...@leuxner.net): Error: Can't create mailbox Public/Test: > Permission denied I think that's correct behavior? The "k" right needs to be for the parent "Public", while Public/* only matches its children.
[Dovecot] Sieve - Not showing new emails in Thunderbird?
Hi, Issue: Sieve works perfectly and does deliver the mail to the correct mail directories. However Thunderbird doesn't detect the new email, until the user clicks on the folder and then all of a sudden it shows the newly detected emails. Perhaps this is a task for the Thunderbird forums? (Thunderbird 24.2.0) Server Side: * CentOS release 6.3 (Final) * dovecot-2.0.9-7.el6.x86_64 * dovecot-pigeonhole-2.0.9-7.el6.x86_64 * postfix-2.6.6-2.2.el6_1.x86_64 * Server Sieve Settings: mail_location = maildir:~/Maildir plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_vacation_default_period = 10d sieve_vacation_max_period = 30d sieve_vacation_min_period = 1h } * Client App: - Thunderbird 24.2.0 * Userlevel config; File: ~/.dovecot.sieve require "fileinto"; if address :is "to" "sysad...@example.com" { fileinto "sysadmin"; } elsif address :is "to" "root@" { fileinto "sysadmin"; } elsif address :is "from" "root@" { fileinto "sysadmin"; } cya Craig
Re: [Dovecot] Sieve - Not showing new emails in Thunderbird?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Feb 2014, craig.dove...@noboost.org wrote: mail directories. However Thunderbird doesn't detect the new email, until the user clicks on the folder and then all of a sudden it shows the newly detected emails. Perhaps this is a task for the Thunderbird Is Thunderbird configured to detect changes in those folders? - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUvht0HD1/YhP6VMHAQLrDAf+OML7afu7LXzTZoLET6dN7k4T2cSw7kYz dykSVuE5rbLOmr+LkYMmTad2aXUY4orPeRI6181TVnWAFAhVImpjgQdpKI0hQwjj ge6tjIQq3p+DWq8c3l1mO+tBOK2VU8e/CQ1OfvK8FmWlj5DQCZj3PxspZ7a/O1u/ YegxWzzcxjj7LjKX5vsKHpCm68degk/jTNTD46AMubb63m+1MZQcCrZeNnu23//h BcciTNBN7UDXGyFzqNUyJqOzR57xeOZ+2JkFdQY+MviBaWEyb7c2m6vXdbh3to3q jNX76EyDEZL7aBSzzNb933o5+G9ED7yBNWgn4fqsg5p/jLMi10pO7g== =KQCA -END PGP SIGNATURE-
Re: [Dovecot] New global ACL mailbox pattern feature in HG
* Timo Sirainen 2014.02.10 00:25: > > Public/* group=PublicMailboxAdmins lrwsik > > > > yields an error (Public/ Namespace) while 'Public*' works: > > $ doveadm mailbox create -u t...@leuxner.net "Public/Test" > > $ doveadm(t...@leuxner.net): Error: Can't create mailbox Public/Test: > > Permission denied > > I think that's correct behavior? The "k" right needs to be for the parent > "Public", while Public/* only matches its children. I see. Wouldn't "Public" also let's say undesirably apply to mailboxes in the user context then, e.g. someone creates a "Public" folder in his INBOX? I'm asking as I only want to apply the ACL to a namespace. Regards Thomas signature.asc Description: Digital signature