- dovecot - dovecot.org

[Dovecot] qpopper to dovecot migration
by Jernej Porenta 23 Dec '09

23 Dec '09

Heya, We are in the process of migrating from qpopper to dovecot as POP3 server (and IMAP as well) and we hit the UIDL issue with dovecot. Qpopper uses its own algorithm to create UIDL values and if you set it up to write them down in the mbox file as X-UIDL, then dovecot can use them (pop_uidl_reuse = yes). But if you don't use that feature from qpopper, than X-UIDLs are missing and there is no way to create the same UIDL values. So, I was wondering if anyone else hit that issue and maybe knows how to address it (writing an extension or something)? Thanks in advance, regards, Jernej

2 1

[Dovecot] Dovecot Deliver CPU usage
by Aravind Divakaran 23 Dec '09

23 Dec '09

Hi All, We have upgraded the dovecot from 1.0 to 1.2.8. After upgradation we have noticed that dovecot deliver process is utilizing a lot of CPU. As a result the mailsystem will stop working. When we limit the no of procs in postfix for dovecot deliver the CPU usage will come down. But we are not facing this problem with the previous version. Below is the log files for dovecot when the error occurs write_full(/home/vmail/dhanbank.co.in/vinukumarvm/temp.server.be3e5a849a909847) failed: No space left on device dovecot: deliver(user(a)example.com): stat(/tmp/Dovecot Delivery Mail) failed: No space left on device But my system has 54gb of free space for root filesystem where tmp residing. Can anyone help me to solve this issue. Rgds, Aravind

5 17

[Dovecot] Panic: file maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): assertion failed
by Anton Dollmaier 23 Dec '09

23 Dec '09

Hi all, after inserting another sieve-rule, I get the following backtrace on deliver. The mail gets delivered into the Mailbox, but as deliver does not exit with 0, postfix bounces the mail. The additional rule is the same as all others in my .dovecot-sieve: > require ["fileinto", "include"]; > > if header :contains ["From"] ["@terra.a1a-server.de"] { > fileinto "Server.ADITSystems.terra"; > (...) > } elsif header :contains ["From"] ["@neon.a1a-server.de"] { > fileinto "Server.ADITSystems.neon"; > } else { > include :global "shared.sieve"; > fileinto "Server.Serveradmin"; > } > Dec 23 11:23:37 deliver(serveradmin(a)aditsystems.de): Panic: file > maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): > assertion failed: (recs[i]->uid < rec->uid) > Dec 23 11:23:37 deliver(serveradmin(a)aditsystems.de): Error: Raw backtrace: > /usr/lib/dovecot/deliver [0x80e52a1] -> > /usr/lib/dovecot/deliver(default_fatal_handler+0x3a) [0x80e53ca] -> > /usr/lib/dovecot/deliver [0x80e4c79] -> /usr/lib/dovecot/deliver > [0x807e097] -> > /usr/lib/dovecot/deliver(maildir_uidlist_sync_finish+0x29f) > [0x807f10f] -> > /usr/lib/dovecot/deliver(maildir_uidlist_sync_deinit+0xa8) > [0x807f458] -> > /usr/lib/dovecot/deliver(maildir_transaction_save_commit_pre+0x399) > [0x80820c9] -> /usr/lib/dovecot/deliver [0x807bbb2] -> > /usr/lib/dovecot/deliver(index_transaction_commit+0x4e) [0x80a472e] > -> /usr/lib/dovecot/deliver(mailbox_transaction_commit+0x26) > [0x80a9716] -> /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so > [0xb7d30b84] -> > /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_result_execute+0x244) > [0xb7d2a024] -> > /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_execute+0x87) > [0xb7d37fa7] -> /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so > [0xb7d1bcde] -> /usr/lib/dovecot/deliver(main+0x1108) [0x8061618] -> > /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7d8a455] -> > /usr/lib/dovecot/deliver [0x805f3c1] Following output of "dovecot -n": > # 1.2.8: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.26-2-686-bigmem i686 Debian 5.0.3 > protocols: imap imaps managesieve pop3 pop3s > listen: [::], * > ssl_cert_file: /etc/dovecot/dovecot.pem > ssl_key_file: /etc/dovecot/dovecot.pem > disable_plaintext_auth: no > 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 > login_processes_count: 5 > mail_privileged_group: vmail > 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_plugins(default): autocreate expire quota imap_quota > mail_plugins(imap): autocreate expire quota imap_quota > mail_plugins(pop3): > mail_plugins(managesieve): > 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/modules/pop3 > mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve > imap_client_workarounds(default): delay-newmail tb-extra-mailbox-sep > imap_client_workarounds(imap): delay-newmail tb-extra-mailbox-sep > imap_client_workarounds(pop3): > imap_client_workarounds(managesieve): > pop3_save_uidl(default): no > pop3_save_uidl(imap): no > pop3_save_uidl(pop3): yes > pop3_save_uidl(managesieve): no > pop3_uidl_format(default): %08Xu%08Xv > pop3_uidl_format(imap): %08Xu%08Xv > pop3_uidl_format(pop3): UID%u-%v > pop3_uidl_format(managesieve): %08Xu%08Xv > pop3_client_workarounds(default): > pop3_client_workarounds(imap): > pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh > pop3_client_workarounds(managesieve): > managesieve_implementation_string(default): dovecot > managesieve_implementation_string(imap): dovecot > managesieve_implementation_string(pop3): dovecot > managesieve_implementation_string(managesieve): Cyrus timsieved v2.2.13 > namespace: > type: private > separator: . > prefix: INBOX. > inbox: yes > list: yes > subscriptions: yes > namespace: > type: public > separator: . > prefix: Server. > location: maildir:/var/mail/vmail/%d/shared/Server:INDEX=~/indexes/Server > list: yes > subscriptions: yes > lda: > postmaster_address: postmaster(a)terra.a1a-server.de > mail_plugins: quota sieve autocreate > deliver_log_format: %m:%$:%f:%s > log_path: /var/log/dovecot-deliver.log > info_log_path: /var/log/dovecot-deliver.log > auth default: > mechanisms: plain login > passdb: > driver: sql > args: /etc/dovecot/dovecot-sql.conf > passdb: > driver: sql > args: /etc/dovecot/dovecot-sql-master.conf > userdb: > driver: sql > args: /etc/dovecot/dovecot-sql.conf > socket: > type: listen > client: > path: /var/spool/postfix/private/auth > mode: 432 > user: postfix > group: postfix > master: > path: /var/run/dovecot/auth-master > mode: 438 > plugin: > sieve: ~/.dovecot.sieve > sieve_global_dir: /etc/dovecot/sieve/ > sieve_dir: %h/sieve > autocreate: INBOX.Trash > autocreate2: INBOX.Spam > autocreate3: INBOX.Sent > autosubscribe: INBOX.Trash > autosubscribe2: INBOX.Spam > autosubscribe3: INBOX.Sent Best regards & merry christmas! Anton Dollmaier

2 1

[Dovecot] Openbsd Postfix-Dovecot-SASL
by thekat 22 Dec '09

22 Dec '09

Greetings all, I have a OpenBSD /Dovecot server at home running and sending / receiving email "internally" without issue.. Recently, I set up the same at our Parish, but one of our users wants to get their email externally. The user can read their email but has to "send" via the local ISP server.. The problem After much searching I have not found an answer to my question. I would like the user to authenticate to be able to "send" email "through" the server.. OpenBSD uses bsdauth by default in Dovecot. After reading the Postfix http://www.postfix.org/SASL_README.html and the Dovecot Wiki http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL I have tried multiple configurations but I can't seem to get this to work.. It may be something very simple that I am missing.. All users on the Server have accounts in /etc/passwd (just no shell) Postfix - main.cf mailbox_command = /usr/local/libexec/dovecot/deliver mynetworks = 127.0.0.0/8 smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination dovecot --version 1.1.16 dovecot -n # OS: OpenBSD 4.6 i386 base_dir: /var/dovecot/ protocols: imaps listen: *, [::] ssl_cert_file: /etc/ssl/dovecotcert.pem disable_plaintext_auth: no login_dir: /var/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: _dovecot login_max_processes_count: 256 max_mail_processes: 32 mail_location: maildir:~/Maildir mbox_write_locks: fcntl imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: cache_size: 1024 passdb: driver: bsdauth args: cache_key=%u userdb: driver: passwd socket: type: listen client: path: /var/run/auth-client mode: 432 user: _postfix master: path: /var/run/auth-master mode: 384 user: _postfix Error using bsdauth Dec 21 15:07:09 aml000t3 dovecot: dovecot v1.1.16 starting up Dec 21 15:07:09 aml000t3 dovecot: Panic: auth(default): file passdb.c: line 190 (passdb_init): assertion failed: (passdb->passdb->default_pass_scheme != NULL || passdb->passdb->cache_key == NULL) Dec 21 15:07:09 aml000t3 dovecot: child 18954 (auth) killed with signal 6 (core not dumped) Dec 21 15:07:09 aml000t3 dovecot: Fatal: Auth process died too early - shutting down It looks like bsdauth has a bug and even though this thread "lists" a patch, I haven't been able to find it.. http://old.nabble.com/bsdauth-with-cache_key-failed-ts25800484.html#a258004… so I guess I am looking for an alternative to be able to allow users to "send through the server" Thx for any pointers tk -- View this message in context: http://old.nabble.com/Openbsd-Postfix-Dovecot-SASL-tp26890148p26890148.html Sent from the Dovecot mailing list archive at Nabble.com.

2 4

[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