- dovecot - dovecot.org

[Dovecot] Remove From Server When Deleted From Deleted Items
by Matt 21 Dec '09

21 Dec '09

In Windows Live Mail I have this setting enabled: "Remove From Server When Deleted From Deleted Items". It does not seem to remove them even when the trash is emptied though. Am using POP3 access. Anyone else see this? Matt

1 0

[Dovecot] Dovecot v2.0 wiki
by Timo Sirainen 21 Dec '09

21 Dec '09

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior everywhere and get rid of all the old v1.x specific settings. The wiki1 is already annoyingly bloated and confusing with information about v1.0 and then v1.1 and maybe even how it's still different in v1.2.. Now would be a good time to do any other larger changes, if anyone has suggestions. :) (Oh, and I haven't yet done any actual changes to wiki2..)

3 5

Re: [Dovecot] [exim] Exim + Dovecot deliver overquota problems
by Nikita Koshikov 21 Dec '09

21 Dec '09

On Mon, 21 Dec 2009 13:44:42 +0100 Joan <aseques(a)gmail.com> wrote: > > > > You need to check user's quota on routing stage, not transport. > > > It'd be much better, because I would allow me to mix overquota and > no-overquota recipients. > But the problem in my case is that I am using some hashing to > distribute the users' mailboxes, dovecot can handle this easily > because it supports some interesting stuff > (http://wiki.dovecot.org/Variables) Exim have much more variables and functions http://exim.org/exim-html-4.69/doc/html/spec_html/ch11.html#SECTexpvar, so if you don't use any special dovecot variable data, than it shouldn't be a problem. > With a perl script I could also do that, I would like only if it's the > last resort (too much overhead I would think) > > Parsing file and counting quota value - is trivial stuff. The main disadvantage of this way is executing external aplication on every RCPT TO command. If you'll decide to use perl consider using option perl_at_start to minimize aplication starting time.

1 0

[Dovecot] Released Pigeonhole Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.9
by Stephan Bosch 21 Dec '09

21 Dec '09

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change, but also fixes quite a few small problems. The ManageSieve release is necessary to match Sieve API changes. Changelog Sieve v0.1.14: * Made the imposed limits on the number of redirects and the number of actions configurable. The settings are called sieve_max_actions and sieve_max_redirects. * Did a major rework of extension handling, making sure that no global state is maintained. This change was triggered by problems that global state info would cause for Dovecot v2.0, but it is also important for v1.2 as it significantly cleans up the library implementation. + Made LDA Sieve plugin recognize the deliver_log_format setting. + Message headers produced from user-supplied data are now RFC2047-encoded if necessary for outgoing messages. This is for example important for the :subject argument of the vacation action. + Added support for the $text$ substitution in the deprecated notify extension. + The subaddress extension now also accepts recipient_delimiter setting as an alias for sieve_subaddress_sep setting. This anticipates the recipient_delimiter setting in v2.0. - Fixed logging of mailbox names. It logged the converted mUTF7 version in stead of the original UTF8 version supplied by the user. - Fixed a minor memory leak in the multiscript support. - Fixed a bug in the recompilation of Sieve scripts. Made sure that scripts are only recompiled when the script file - or the symlink pointing to it - is strictly newer. Changelog ManageSieve v0.11.10: * This release contains adjustments to match changes in the Sieve API. This means that this release will only compile against Pigeonhole Sieve v0.1.14. - Fixed compilation of ManageSieve against CMUSieve. The releases are available as follows: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14.tar.gz.sig ManageSieve (package + patch): http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10.tar.gz.… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.9-managesieve-0.11.10.diff.… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.9-managesieve-0.11.10.diff.… Refer to http://pigeonhole.dovecot.org for more information. Have fun testing the new releases and don't hesitate to notify me when there are problems. Releases for Dovecot v2.0 are still under development... Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 4

[Dovecot] Dovecot vs Exim file locking
by Daniel Campos 21 Dec '09

21 Dec '09

Hi all: We're planning to deploy a large e-mail system storing maildirs in a NAS system through NFS. One of the options we're thinking on is using Dovecot+EXIM. As far as I've read in both project's documentation, both services implement locking allowing multiple servers to access the same maildirs in order to distribute the service load. However, I can't find any information explaining whether both locking mechanisms are compatible, whether any additional configuration is needed both in Dovecot and/or EXIM, or even whether any locking synchronization between both services is needed/recommendable at all. The only remote clue I've found is that, according to Dovecot docs: "Because Dovecot uses its own non-standard locking (dovecot-uidlist.lock dotlock file), other MUAs accessing the maildir don't support it." (but EXIM is not a MUA, anyway) Anyhow theoretically MailDir could even be considered free of locking problems, but I'm not sure of the real implications of putting together several Exim and Dovecot installations pointing to the same NFS filesystem. Any knowledge/experience/link/clue on this would be greatly appreciated. Thanks in advance, Daniel Campos

4 4

[Dovecot] deliver panics when handling mails bigger than some kByte
by Leon Meßner 19 Dec '09

19 Dec '09

Hi, i've just upgraded to dovecot-1.2.8 (from 1.2.4) and do now get the following errors when deliver gets hands on mails with some attachments. # tail -n 1 /var/log/messages Dec 14 19:00:36 mail3 dovecot: deliver(user): Panic: file istream.c: line 96 (i_stream_read): assertion failed: (stream->eof) The MTA is postfix running inside a FreeBSD 7.2-STABLE jail. The homes where deliver should put mails are mounted via NFS. As it works with small attachments perhaps this is related to the message size. However i don't get the "stale NFS file handle" error any more which i did under 1.2.4 (See thread that begins with: Message-ID: <20091016122519.GC6309(a)emmi.physik-pool.tu-berlin.de> ) Greetings, Leon

2 2

[Dovecot] "Filename keeps changing" issue
by Paul Ezvan 19 Dec '09

19 Dec '09

Hello, I have been experiencing a issue for a while with dovecot 1.2.8 : Dec 4 12:54:00 gen1 dovecot: IMAP(paul): maildir_file_do(/home/paul/Maildir/.Travail.Linux.Arch Linux/cur/1224250603.M73770P8724.gen0:2,): Filename keeps changing Dec 4 12:54:01 gen1 dovecot: IMAP(paul): Disconnected: Internal error occurred. Refer to server log for more information. [2009-12-04 12:53:59] bytes=4445/26986 So I can't get the messages in this directory neither with Evolution neither with Horde neither with Squirrelmail, but it works with roundcubemail. How can I debug this ? dovecot -n # 1.2.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31-ARCH i686 protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/ssl/certs/ezvan.fr.pem ssl_key_file: /etc/ssl/private/ezvan.fr.key login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_process_per_connection: no mail_location: maildir:~/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_process_size: 0 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): imap_client_workarounds(managesieve): lda: postmaster_address: postmaster(a)ezvan.fr mail_plugins: sieve sieve_global_path: /var/sieve/global auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: sieve: ~/.dovecot.sieve sieve_storage: ~/sieve Thanks for help ! Paul Ezvan

6 11

[Dovecot] dovecot: pipe() failed: Too many open files
by JW 19 Dec '09

19 Dec '09

In the past few months we've been having increasing problems with dovecot timing out pop3 logins. As best I can tell it gets to the point where it won't accept any new pop3 logins. The error in the mail log is: dovecot: pipe() failed: Too many open files I've researched this problem a number of times, usually I see suggestions to increase ulimit. I've done this a number of times, all the way up to: ulimit -n 8192 I've put that in the init script right above the daemon start line. So far it hasn't helped. In addition, when looking at lsof, it doesn't seem like we're anywhere near the actual limit. for example, last time dovecot only had 1032 files open. Does anyone have any idea what could be causing the error? Or what else I can try to figure this out? Thank you, JW -- ---------------------- System Administrator - Cedar Creek Software http://www.cedarcreeksoftware.com

5 7

[Dovecot] Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8
by Stephan Bosch 19 Dec '09

19 Dec '09

Hello Dovecot users, I am getting closer to new releases for Sieve and ManageSieve for Dovecot v1.2.8. However, the release for Sieve includes a large restructuring of the sources to improve extension handling and to remove global state. That is why I first provide a few pre-releases for you to check first: Sieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz.sig ManageSieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10pre.tar.… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10pre.tar.… Check the NEWS files in the respective repositories for other changes included in these releases: http://hg.rename-it.nl/dovecot-1.2-sieve/file/216f58aae5c1/NEWS http://hg.rename-it.nl/dovecot-1.2-managesieve/file/a44ca0d89875/NEWS Feel free to test these release candidates and please notify me when you incur any problems. The real releases will follow this weekend. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 5

[Dovecot] Maildir on NFS - attribute caching question
by Brandon Davidson 18 Dec '09

18 Dec '09

Hi Timo, We've been running Dovecot with Maildir on NFS for quite a while - since back in the 1.0 days I believe. I'm somewhat new here. Anyway... The Wiki article on NFS states that 1.1 and newer will flush attribute caches if necessary with mail_nfs_storage=yes. We're running 1.2.8 with that set, as well as mail_nfs_index=yes, mmap_disable=yes and fsync_disable=no. We have a pool of POP/IMAP and SMTP machines that are accessing the maildirs, and can't guarantee any sort of user session affinity to a particular host. We also mount our NFS shares with 'noac', which is what I'm writing to ask about. I'd like to stop doing that for performance reasons. Do you see any issues with taking that out of the mount options, given our environment? Thanks, -Brad

2 1