- dovecot - dovecot.org

[Dovecot] 2.1.rc5 Cannot delete folders from trash
by Mike Constabel 14 Feb '12

14 Feb '12

Hi, If I delete a folder "foo" in Thunderbird, it is moved to trash. [root@dovecot1][tmp:exec](~) # ll /mailspool1/xxxx.de/test1/mdbox/mailboxes/Trash/ insgesamt 16K drwx------ 4 vmail vmail 4,0K 31. Jan 22:16 . drwx------ 8 vmail vmail 4,0K 31. Jan 22:16 .. drwx------ 2 vmail vmail 4,0K 12. Feb 11:51 dbox-Mails drwx------ 3 vmail vmail 4,0K 31. Jan 22:16 foo [root@dovecot1][tmp:exec](~) # [root@dovecot1][tmp:exec](~) # [root@dovecot1][tmp:exec](~) # ll /mailspool1/xxx.de/test1/mdbox/mailboxes/Trash/foo/ insgesamt 12K drwx------ 3 vmail vmail 4,0K 31. Jan 22:16 . drwx------ 4 vmail vmail 4,0K 31. Jan 22:16 .. drwx------ 2 vmail vmail 4,0K 12. Feb 11:52 dbox-Mails [root@dovecot1][tmp:exec](~) # ll /mailspool1/xxxx.de/test1/mdbox/mailboxes/Trash/foo/dbox-Mails/ insgesamt 12K drwx------ 2 vmail vmail 4,0K 12. Feb 11:52 . drwx------ 3 vmail vmail 4,0K 31. Jan 22:16 .. -rw------- 1 vmail vmail 224 12. Feb 11:52 dovecot.index.log [root@dovecot1][tmp:exec](~) # If I delete foo from trash, thunderbird removed it from view, but if I restart thunderbird, the folder is still in trash. No error in dovecot log, no error in thunderbird. tcpdump: 156 45.101512 192.168.10.1 192.168.10.117 TCP 54094 > imap [ACK] Seq=353 Ack=1617 Win=10144 Len=0 TSV=2414467591 TSER=251091441 157 45.349600 192.168.10.1 192.168.10.117 IMAP Request: 16 list "" "Trash/*" 158 45.349717 192.168.10.117 192.168.10.1 IMAP Response: * LIST (\HasNoChildren) "/" "Trash/foo" 159 45.349756 192.168.10.1 192.168.10.117 TCP 54094 > imap [ACK] Seq=375 Ack=1727 Win=10144 Len=0 TSV=2414467653 TSER=251091503 160 45.395546 192.168.10.1 192.168.10.117 IMAP Request: 17 list "" "Trash/foo/*" 161 45.395624 192.168.10.117 192.168.10.1 IMAP Response: * LIST (\Noselect \HasNoChildren) "/" "Trash/foo/" 162 45.395662 192.168.10.1 192.168.10.117 TCP 54094 > imap [ACK] Seq=401 Ack=1802 Win=10144 Len=0 TSV=2414467665 TSER=251091515 163 45.439998 192.168.10.1 192.168.10.117 IMAP Request: 18 delete "Trash/foo/" 164 45.440067 192.168.10.117 192.168.10.1 IMAP Response: 18 NO [CANNOT] Invalid mailbox name 165 45.440104 192.168.10.1 192.168.10.117 TCP 54094 > imap [ACK] Seq=425 Ack=1839 Win=10144 Len=0 TSV=2414467676 TSER=251091526 166 45.493978 192.168.10.1 192.168.10.117 IMAP Request: 19 IDLE with dovecot 1.2 and Maildir I can delete folders from trash. Something wrong in my config? Thunderbird-Bug? # 2.1.rc5 (b9e74767cd39): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.4 auth_cache_size = 1 M auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot/dovecot-debug.log dict { expire = sqlite:/etc/dovecot/dovecot-dict-expire.conf.ext } disable_plaintext_auth = no hostname = mx4.xxxx.de info_log_path = /var/log/dovecot/dovecot-info.log log_path = /var/log/dovecot/dovecot.log mail_debug = yes mail_location = mdbox:~/mdbox mail_plugins = quota notify mail_log expire mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Archive/2011 { auto = subscribe } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = scheme=PLAIN username_format=%u /etc/imap.userdb driver = passwd-file } plugin { expire = Trash expire2 = Trash/* expire3 = Spam expire_dict = proxy::expire quota = dict:User quota::file:/mailspool1/%d/%n/dovecot-quota quota_rule = *:storage=9000M:messages=1000000 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster@localhost protocols = " imap lmtp sieve pop3" ssl_ca = </etc/postfix/psw-ssl/ssl.ca-bundle ssl_cert = </etc/postfix/psw-ssl/ssl.crt ssl_key = </etc/postfix/psw-ssl/ssl.key userdb { args = username_format=%Lu /etc/imap.userdb driver = passwd-file } protocol lmtp { mail_plugins = quota notify mail_log expire sieve } protocol lda { mail_plugins = quota notify mail_log expire } protocol imap { imap_logout_format = bytes=%i/%o mail_plugins = quota notify mail_log expire imap_quota } protocol pop3 { mail_plugins = quota notify mail_log expire }

6 7

[Dovecot] R: Re: R: Re: LMTP : Can't handle mixed proxy/non-proxy destinations
by cinzia.delcoiro＠libero.it 14 Feb '12

14 Feb '12

Charles I need to accept mail also for nonexistent users because I'm delivering a particular service (Certified Mail). Regards Cinzia >----Messaggio originale---- >Da: CMarcus(a)Media-Brokers.com >Data: 14-feb-2012 16.42 >A: "Dovecot Mailing List"<dovecot(a)dovecot.org> >Ogg: Re: [Dovecot] R: Re: LMTP : Can't handle mixed proxy/non-proxy destinations > >On 2012-02-14 10:02 AM, cinzia.delcoiro(a)libero.it ><cinzia.delcoiro(a)libero.it> wrote: >> I'm writing to alert you that even in version 2.1. we have the error: "Can't >> handle mixed proxy/non-proxy destinations" when we write to two users: one >> existent and one not. > >why are you accepting mail for non existing users? > >Catch-alls are a very very bad idea in 99.999% of cases, and usually >when someone thinks they need a catchall, they are mistaken. > >-- > >Best regards, > >Charles >

1 0

[Dovecot] Boehm
by Daniel L. Miller 13 Feb '12

13 Feb '12

As the Boehm GC is an available option, do I take that to mean it's beneficial for some users but not most? -- Daniel

2 1

[Dovecot] Synchronization error in NFS
by Andy YB Hu 13 Feb '12

13 Feb '12

Hi there, Not sure whether it's a bug or env setting issue. I am running some concurrent testings under NFS. The dovecot (version 2.0.13) are deployed in 2 servers (same setup), whose maildir are on the file server via NFS. Here are the output of dovecot -n: [root@MyMachine src]$dovecot -n # 2.0.13: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-274.3.1.el5 i686 Red Hat Enterprise Linux Server release 5.7 (Tikanga) nfs auth_anonymous_username = andy auth_debug = yes auth_debug_passwords = yes auth_mechanisms = anonymous plain auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no lock_method = dotlock log_path = /tmp/log mail_debug = yes mail_fsync = always mail_gid = andy mail_location = maildir:/tmp/NFS mail_nfs_index = yes mail_nfs_storage = yes mail_uid = andy mmap_disable = yes passdb { driver = pam } ssl = no userdb { driver = passwd } Here are what I am doing: One session running loop of COPY commands (while(1) COPY...) connects to one dovecot server; The other session running loop of SELECT commands (while(1) SELECT...) connects to the other dovecot server. Both are accessing the same mail box (/tmp/NFS); After some while (not accurate duration, maybe 2 seconds, or 1 min), I found the number of EXISTS returned from SELECT command is not correct(less than the real number). Then I stop the both sessions. In the /tmp/log: Feb 07 03:44:59 imap(andy): Error: Corrupted transaction log file /tmp/NFS/dovecot.index.log seq 2: Unexpected garbage at EOF (sync_offset=2204) Feb 07 03:44:59 imap(andy): Error: Index /tmp/NFS/dovecot.index: Lost log for seq=2 offset=2204 Feb 07 03:44:59 imap(andy): Warning: fscking index file /tmp/NFS/dovecot.index Then I tried to dump the index, sometime it's failed because of the index corruption. If not, it says: [root@MyMachine src]$doveadm dump /tmp/NFS > /tmp/dump ; vi /tmp/dump doveadm(root): Error: Log synchronization error at seq=2,offset=744 for /tmp/NFS/dovecot.index: Broken extension introduction: Headersize too large (2273345664) doveadm(root): Warning: fscking index file /tmp/NFS/dovecot.index doveadm(root): Error: fcntl(write-lock) locking failed for file /tmp/NFS/dovecot.index.log: Bad file descriptor doveadm(root): Error: mail_index_wait_lock_fd() failed with file /tmp/NFS/dovecot.index.log: Bad file descriptor doveadm(root): Error: Log synchronization error at seq=2,offset=744 for /tmp/NFS/dovecot.index: Broken extension introduction: Headersize too large (2273345664) doveadm(root): Warning: fscking index file /tmp/NFS/dovecot.index doveadm(root): Error: fcntl(write-lock) locking failed for file /tmp/NFS/dovecot.index.log: Bad file descriptor doveadm(root): Error: mail_index_wait_lock_fd() failed with file /tmp/NFS/dovecot.index.log: Bad file descriptor And sometime from the dump output, in the RECORD part: -- RECORDS: 5 RECORD: seq=1, uid=1, flags=0x00 RECORD: seq=2, uid=2, flags=0x00 RECORD: seq=3, uid=3, flags=0x00 RECORD: seq=4, uid=4, flags=0x00 RECORD: seq=5, uid=6, flags=0x00 The uid 5 is missed. but in uidlist file, it's there.. Here are all what I found. If you need additional information, pls let me know. The clock on the 3 machines are synchronized. You can also reproduce it if the 2 sessions are APPEND and SELECT. If both sessions are running towards the same dovecot server, even the maildir are on the NFS, it works very well without any error.

2 8

[Dovecot] Released Pigeonhole v0.2.6 for Dovecot v2.0.18
by Stephan Bosch 13 Feb '12

13 Feb '12

Hello Dovecot users, Pigeonhole v0.2.5 does not compile against the new Dovecot v2.0.18 release. That is why a release a new version now. Other changes are included as well, of which the one regarding the include extension requires special attention; Changelog v0.2.6: * This release fixes unintentional behavior of the include extension. Included script names with a name like "name.sieve" would implicitly map to a script file called "name.sieve" and not "name.sieve.sieve". Keep in mind that the .sieve file extension has no meaning from within the Sieve language. A Sieve script is always stored with an appended .sieve file extension, also when the name already ends with a .sieve suffix. IMPORTANT: Some installations have relied on this unintentional feature, so check your script includes for issues before upgrading. * Matched changes regarding auth_verbose setting in Dovecot. This means that this release will only compile against Dovecot v2.0.18. - Fixed problem in ManageSieve that caused it to omit a WARNINGS response code when the uploaded script compiled with warnings. - Made sure that locations of Sieve error never report `line 0'. - Fixed potential segfault occurring when interpreter initialization fails. The release is available as follows: http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.6.tar.gz http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.6.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.0 wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] Logging to messages instead of secure
by Cliff Hayes 13 Feb '12

13 Feb '12

I need to log to /var/log/messages instead of /var/log/secure on a fedora system. Is this the correct entry for dovecot.conf? syslog_facility = info

1 0

[Dovecot] Managesieve doesn't listen on 2000/4190
by Jacek Osiecki 13 Feb '12

13 Feb '12

Hi, Finally I decided to give a try to dovecot 2.0, after spending few years with 1.2. Unfortunately, it doesn't go smooth - finally I managed to cope with LMTP transport and exim, but failed to run managesieve. I have compiled pigeonhole, installed it, configured, everything seems to be done well - except the fact, that nothing is listening on port 2000 or 4190. Here is my doveconf -n. Any ideas? # 2.0.16: /etc/dovecot/dovecot.conf # OS: Linux 2.6.39.4-vs2.3.1-pre9.2-nfs41-nfsd x86_64 auth_debug = yes auth_debug_passwords = yes debug_log_path = /var/log/dovecot/debug.log dict { quota = mysql:/etc/dovecot/dovecot-dict-sql.conf } disable_plaintext_auth = no first_valid_uid = 79 info_log_path = /var/log/dovecot/info.log last_valid_uid = 79 log_path = /var/log/dovecot/main.log mail_debug = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = /var/mail/sieve/%d/%u.sieve sieve_dir = /var/mail/sieve/%d/%u sieve_global_path = /var/mail/sieve/%d/global.sieve } postmaster_address = postmaster(a)hybrid.pl service imap-login { inet_listener imap { address = 127.0.0.1 port = 143 } inet_listener imaps { address = 0.0.0.0 port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3 { address = 127.0.0.1 port = 110 } inet_listener pop3s { address = 0.0.0.0 port = 995 ssl = yes } } ssl = no userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " sieve quota" } protocol lda { mail_plugins = " sieve quota" } Best regards, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

2 2

Re: [Dovecot] Problems sending email direct into publich folders
by Kuran, Fabian 13 Feb '12

13 Feb '12

Hi, > Depends on how you want to do this.. For example all mails intended to be put to public namespace could be sent > to a "publicuser" named user, which has write permissions to the public namespace. Then you'll simply create a > sieve script for the publicuser which redirects the mails to the wanted folder (e.g. fileinto "public/hrztest"). I'm also migrating from cyrus-imapd to dovecot. But this solution isn't very good to me. With cyrus I could easily send an email to (for example) bb+shared/archive(a)mydomain.com. Then the mail will be putted to the public folder. Is there a comparable way to do this with Dovecot? FYI: I'm using dovecot in a clustered and multidomain setup. The Mails will be deliviered over LMTP. -- Bye, Fabian Kuran

2 1

[Dovecot] v2.1.0 status
by Timo Sirainen 13 Feb '12

13 Feb '12

I'll release v2.1.rc6 in maybe 16 hours or so. If no problems are reported in it after a few days I'll just change version to 2.1.0. So now's a great time to try the latest v2.1 hg version to see if there are any problems. I've gone through all of my old mails. Let me know if you think something is still missing / unfixed in v2.1 hg. Preferably today. Next up: Creating dovecot-2.2 tree with great new features. :)

4 8

[Dovecot] Dovecot 2.0.18 build error with pigeonhole
by Morten Stevens 13 Feb '12

13 Feb '12

Hi, It is probably a problem with pigeonhole 0.2.5. ... make[3]: *** [managesieve-proxy.o] Error 1 make[3]: *** Waiting for unfinished jobs.... Here is my build log: http://oss.imt-systems.com/mstevens/temp/build.log Someone an idea? Best regards, Morten

4 4