- dovecot - dovecot.org

Re: [Dovecot] quota and postfix virtual users
by gbotero＠emailforall.no-ip.org 01 Jun '10

01 Jun '10

hi, Simone Caruso, thanks for your answer but i have some questions i test the script in the console and he works he read the quota pased by mysql and then quota_rule ok but he update the maildirsize file??? and this script have to be called from postfix or dovecot?? thanks for all, sorry for my english ;) Guillermo Botero Leticia, Amazonas - Colombia gbospina(a)gmail.com

2 1

[Dovecot] Error: file_dotlock_open() failed with file $FILE ENOENT
by Pascal Volk 31 May '10

31 May '10

I've deleted some empty IMAP folders, using Thunderbird. But before deleting them, I had a look into Trash directory on the filesystem: /home/pvo/mdbox/mailboxes/Trash/ ├── dbox-Mails │ ├── dovecot.index │ ├── dovecot.index.backup │ ├── dovecot.index.cache │ └── dovecot.index.log ├── Dev │ └── dbox-Mails │ └── dovecot.index.log ├── S4 │ └── dbox-Mails │ └── dovecot.index.log └── Server4 └── dbox-Mails └── dovecot.index.log (Yeah, looks good, no dbox-GUID file.) After deleting all IMAP folders from Trash I found this lines in the log file: Apr 06 05:44:36 imap(pvo): Error: file_dotlock_open() failed with file /home/pvo/mdbox/mailboxes/Trash/S4/dbox-Mails/dovecot.index.log: No such file or directory Apr 06 05:44:36 imap(pvo): Error: file_dotlock_open() failed with file /home/pvo/mdbox/mailboxes/Trash/S4/dbox-Mails/dovecot.index.log: No such file or directory Regards, Pascal -- The trapper recommends today: fabaceae.1009606(a)localdomain.org

2 1

[Dovecot] dovecot-2.0-pigeonhole/ManageSieve: wrong service name
by Pascal Volk 31 May '10

31 May '10

Hi Stephan, ManageSieve uses the wrong™ service name for the authdb lookup. With dovecot-1.2-managesieve the service name was changed from 'managesieve' to 'sieve'. So I altered my table layout in order to make the query "SELECT userid AS "user", password FROM dovecotpassword('%Ln', '%Ld') WHERE %Ls" work again. When I try to login on the sieve port 4190/tcp, I find this in my dovecot.log: auth: Error: pgsql: Query failed, retrying: ERROR: column "managesieve" does not exist auth: Error: LINE 1: ...", password FROM dovecotpassword('user', 'example.org') WHERE managesiev... Regards, Pascal -- The trapper recommends today: defaced.1015004(a)localdomain.org

3 4

[Dovecot] Permanent flags not announced and public mailbox with per-user index
by Julien Danjou 31 May '10

31 May '10

Hi, I've a set of public mailboxes that all users can access. The index is stored per user, so each user can mark the message as read for themselves. This is with dovecot 1.2.10. However, when selecting the mailbox, system flags are not announced as permanent but only as session flags: 3619 SELECT "public.Admin" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 324 EXISTS * 0 RECENT * OK [UNSEEN 171] First unseen. * OK [UIDVALIDITY 1254326934] UIDs valid * OK [UIDNEXT 1102] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest 3445 OK [READ-ONLY] Select completed. I think (reading the RFC, but I bet you know it better than me) that FLAGS should also been set in PERMANENTFLAGS since they can be permanent. The relevant code seems to be in commands-util.c (dovecot 1.2.11): void client_send_mailbox_flags(struct client *client, bool selecting) { […] if (mailbox_is_readonly(client->mailbox)) { client_send_line(client, "* OK [PERMANENTFLAGS ()] " "Read-only mailbox."); } else { […] } } Even if it's true that the Maildir is read-only, it's still possible to store \Seen permanently. Am I getting things wrong, or is this a bug? If I'm correct, a simple fix MAY be not to send the PERMANENTFLAGS at all since the RFC says: OK [PERMANENTFLAGS (<list of flags>)] A list of message flags that the client can change permanently. If this is missing, the client should assume that all flags can be changed permanently. Thanks, -- Julien Danjou // ᐰ <julien(a)danjou.info> http://julien.danjou.info

2 6

[Dovecot] Dovecot 2.0beta4 HG 11189: dovecot-uidvalidity warning with mdbox mailboxes
by Thomas Leuxner 31 May '10

31 May '10

Hi, the latest HG of Dovecot 2.0 throws a warning when creating a new mailbox inside an INBOX with 'mdbox' format. It does however create the mailbox correctly. ==> /var/log/dovecot.log <== Apr 24 14:35:09 spectre dovecot: imap(tlx(a)leuxner.net): rename(/var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity, /var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity) failed: No such file or directory $ ls -al /var/vmail/leuxner.net/tlx/mdbox total 36 drwx--S--- 4 vmail vmail 4096 2010-04-24 14:37 . drwx--S--- 4 vmail vmail 4096 2010-04-19 10:23 .. -rw------- 1 vmail vmail 386 2010-03-25 19:58 dovecot-acl-list -rw------- 1 vmail vmail 2952 2010-04-24 14:35 dovecot.mailbox.log -rw------- 1 vmail vmail 53 2010-04-24 14:37 dovecot-quota -rw------- 1 vmail vmail 8 2010-04-24 14:35 dovecot-uidvalidity -r--r--r-- 1 vmail vmail 0 2010-04-24 14:35 dovecot-uidvalidity.4bd2e57d drwx--S--- 15 vmail vmail 4096 2010-03-17 19:57 mailboxes drwx--S--- 2 vmail vmail 4096 2010-04-24 14:37 storage -rw------- 1 vmail vmail 1639 2010-04-24 14:35 subscriptions # 2.0.beta4 (6a3eaad2bae6): /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4 auth_verbose = yes mail_location = mdbox:~/mdbox mail_plugins = acl quota namespace { hidden = no inbox = yes location = prefix = separator = / type = private } namespace { list = yes location = maildir:/var/vmail/public:LAYOUT=fs:INDEX=~/public prefix = Public/ separator = / subscriptions = no type = public } passdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } plugin { acl = vfile:/var/vmail/conf.d/%d/acls:cache_secs=300 mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename quota = dict:user::file:%h/mdbox/dovecot-quota quota_rule = *:storage=1GB quota_rule2 = Trash:storage=10%% sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/vmail/conf.d/%d/sieve } protocols = imap lmtp service auth-worker { user = doveauth } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = doveauth } service imap-login { inet_listener imap { address = 1.2.3.4 port = 143 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/host_domain.crt ssl_key = </etc/ssl/private/host_domain_2010.key syslog_facility = local1 userdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } verbose_proctitle = yes protocol imap { mail_plugins = $mail_plugins imap_acl imap_quota mail_log notify } protocol lmtp { mail_plugins = $mail_plugins sieve } Regards Thomas

2 1

[Dovecot] Dovecot 2.0.beta5: dovecot-uidlist: Duplicate file entry at line X
by Chris Laif 31 May '10

31 May '10

Hi, I'm using dovecot 2.0.beta5 (IMAP and LMTP+sieve) and I'm getting lots of errors like this: Warning: /data/mail/4567/Maildir/dovecot-uidlist: Duplicate file entry at line 3: 1274182284.M635158P16414.mail,S=767,W=785:2,S (uid 5 -> 16) All data is stored on local disk (ext3, no NFS!). As this is a fresh installation of dovecot I do not know if older versions work better. One user complained about loosing email from inbox but I guess that's probably a user error :) I think that the error might be related to deliveries via LMTP as this (new) functionality has not been tested extensivly (?) Regards, Chris ./configure \ --with-pgsql \ --with-ioloop=best \ --without-shadow \ --without-pam \ --without-nss \ --with-storages=maildir \ --without-vpopmail # 2.0.beta5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4 auth_cache_negative_ttl = 60 s auth_cache_size = 10485760 auth_mechanisms = plain login cram-md5 disable_plaintext_auth = no first_valid_gid = 1234 first_valid_uid = 1234 info_log_path = /dev/stderr last_valid_gid = 1234 last_valid_uid = 1234 mail_location = maildir:~/Maildir passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = squat sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = -reject -vacation -enotify -notify } protocols = imap lmtp managesieve service lmtp { inet_listener { port = 24 } } service managesieve-login { inet_listener sieve { address = 10.2.3.4 } } ssl_cert = </etc/dovecot/ssl.crt ssl_key = </etc/dovecot/ssl.key userdb { args = uid=1234 gid=1234 home=/data/mail/%u driver = static } verbose_proctitle = yes protocol lda { mail_plugins = sieve } protocol imap { mail_max_userip_connections = 10 mail_plugins = fts fts_squat } protocol lmtp { mail_plugins = sieve

2 2

[Dovecot] cur folder e-mails are not shown...
by Gonzalo Aguilar Delgado 31 May '10

31 May '10

Hi All! I realized that I have only e-mails from last 13 days. I see that I have lots more in the cur folder inside my Maildir folder. The problem is that I cannot see them. Permissions seems to be right: drwx------ 2 gaguilar gaguilar 1081344 2010-05-28 12:53 cur -rw------- 1 gaguilar gaguilar 4798145 2010-05-28 12:52 deliver.info -rw------- 1 gaguilar gaguilar 0 2010-04-17 21:17 deliver.log -rw------- 1 gaguilar gaguilar 191344 2010-05-28 12:51 dovecot.index -rw------- 1 gaguilar gaguilar 708608 2010-05-28 12:52 dovecot.index.cache -rw------- 1 gaguilar gaguilar 26356 2010-05-28 12:53 dovecot.index.log -rw------- 1 gaguilar gaguilar 35 2010-04-24 19:57 dovecot-keywords -rw------- 1 gaguilar gaguilar 746874 2010-05-28 12:52 dovecot-uidlist -rw------- 1 gaguilar gaguilar 8 2010-05-28 12:46 dovecot-uidvalidity -rw------- 1 gaguilar gaguilar 0 2010-04-17 00:45 dovecot-uidvalidity.4bc8e88d drwx------ 2 gaguilar gaguilar 32768 2010-05-28 12:52 new -rw------- 1 gaguilar gaguilar 2742243 2010-05-28 12:52 procmail.log -rw------- 1 gaguilar gaguilar 48 2010-05-28 12:46 subscriptions drwx------ 2 gaguilar gaguilar 4096 2010-05-28 12:52 tmp dovecot --version 1.1.11 What can be the problem? ____________________________________

3 5

[Dovecot] 1.2.11, mbox, new mail
by Stan Hoeppner 31 May '10

31 May '10

With 1.2.11 and mbox storage, the delay time in pulling new mail headers to the client from imap folders seems to be directly proportional to mailbox size, regardless of the number of new messages. At present, if the mailbox is large, pulling new headers is rather painfully slow. Is this expected behavior? Especially given that the client already has all the "old" mails in the folder cached, and thus wouldn't be asking for them? Is there a setting(s) I can change to optimize/fix this? -- Stan

4 8

[Dovecot] strange sieve situation
by Andy Dills 31 May '10

31 May '10

Hi there, I've been working on rolling out the "deliver" service so we can implement sieve. Dovecot 1.2.11, Postfix 2.6.6, FreeBSD 8, installed by ports. Clustered environment, NFS backend. Everything is working great for the most part, I'm using it to sort a copy of my personal email on a test server. However, I noticed two emails were not properly sorted. I had added a rule (using Ingo, nice little piece of software) to redirect the nightly FreeBSD security output emails into a folder "servers". However, nothing had triggered that rule, and the "Maildir/.servers" directory had not yet been created. Then, three of the "security outputs" came in at one time: May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070108.F2F0B7F5D4(a)mail-out04.xecu.net>: failed to store into mailbox 'servers': Mailbox already exists May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070109.D8F5E159913(a)mail-out01.xecu.net>: failed to store into mailbox 'servers': Mailbox already exists May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070109.D8F5E159913(a)mail-out01.xecu.net>: stored mail into mailbox 'INBOX' May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: execution of script /mail/var/mail2/xecunet/andytest.xecu.net//.dovecot.sieve failed, but implicit keep was successful May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070110.17A781B53B9(a)mail-out02.xecu.net>: stored mail into mailbox 'servers' May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070108.F2F0B7F5D4(a)mail-out04.xecu.net>: stored mail into mailbox 'INBOX' May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: execution of script /mail/var/mail2/xecunet/andytest.xecu.net//.dovecot.sieve failed, but implicit keep was successful That's the order they appeared in my logfile. I'm assuming they were all sent to deliver at the same time, they all thought they needed to make the directory, the one with msgid 20100529070110.17A781B53B9(a)mail-out02.xecu.net was able to make the directory and get delivered, whereas the other two freaked out because they couldn't make the directory they thought needed to be made, and just sent the mail to the inbox. That's a reasonable approach, although I wonder if deliver/sieve could be (or perhaps "has been in 2.0") adjusted to more intelligently handle that edge case. Also, I'm wondering about "dovecot_destination_recipient_limit = 1". I have that set in my main.cf, but I'm not 100% positive it's taking effect. # grep dovecot /usr/local/etc/postfix/main.cf dovecot_destination_recipient_limit = 1 virtual_transport = dovecot # grep dovecot /usr/local/etc/postfix/master.cf dovecot unix - n n - - pipe flags=DRhu user=mailman argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} # postconf | grep dovecot smtpd_sasl_type = dovecot virtual_transport = dovecot # postconf | grep destination_recipient_limit default_destination_recipient_limit = 50 lmtp_destination_recipient_limit = $default_destination_recipient_limit local_destination_recipient_limit = 1 relay_destination_recipient_limit = $default_destination_recipient_limit smtp_destination_recipient_limit = $default_destination_recipient_limit virtual_destination_recipient_limit = $default_destination_recipient_limit Is "dovecot_destination_recipient_limit" being converted into local_ ? Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---

2 1

[Dovecot] Unresolved client rejection
by Greg Pearson 31 May '10

31 May '10

Hi, would it be possible to prevent users who try to login from an unresolved IP from connecting to Dovecot IMAP? I have a suspicion that it should be done via the authentication module (ie PAM) but I am not sure (if this is the case could someone recommend a good resource or even a solution). For example sendmail has a relevant macro to achieve this, I was wondering if Dovecot can have similar behavior. Thanks

2 1