- dovecot - dovecot.org

[Dovecot] 1.0.beta2 released
by Timo Sirainen 29 Jan '06

29 Jan '06

I had originally thought that I'd do a complete audit of the Dovecot's sources this weekend, but looks like I didn't. Hopefully I've been writing good enough code that the "1000 EUR for security hole" offer lasts for a long time. :) This release should fix the SSL parameter regeneration problem. There were two changes that were needed to fix it, but I had forgotten the other one. v1.0.beta2 2006-01-22 Timo Sirainen <tss(a)iki.fi> + Added SQLite support. Patch by Jakob Hirsch. + Added auth_debug_passwords setting. If it's not enabled, hide all password strings from logs. + Added mail_cache_min_mail_count and mbox_min_index_size settings which can be used to make Dovecot do less disk writes in small mailboxes where they don't benefit that much. + Added --build-ssl-parameters parameter to dovecot binary - SSL parameters were being regenerated every 10 minutes, although not with all systems. - Fixed dovecot-auth crashing at startup. Happened only with some specific compilers. - base_dir was supposed to be set world-readable, not world-writable

10 18

[Dovecot] Question concerning configuration
by Christopher R. Parr 29 Jan '06

29 Jan '06

Hi! I'm using dovecot and evim4 on a debian sarge system. Now I'd like to set up exim4 using vexim (http://www.debianhowto.de/de:howtos:sarge:exim4_vexim2_courier_mailman) My question: How do I have to configure dovecot? Thanks

1 0

[Dovecot] X-Status: D
by Gerhard Wiesinger 28 Jan '06

28 Jan '06

Hello! I've some folders where I deleted some messages. They are not really deleted, but have the X-Status: D header field set. How can I force a real delete in dovecot? Thank you for the answer. Ciao, Gerhard

2 3

[Dovecot] Invisible messages
by Anne Wilson 27 Jan '06

27 Jan '06

I have pulled in a couple of messages using fetchmail and put them through a procmail filter, which has resulted in the two messages being visible in a file manager in ~/Maildir/Design/new. However, using my Imap account on this box I can't see those messages. Any hints, please? Anne

3 9

[Dovecot] Upgrade to a new system
by Daniel Davidson 27 Jan '06

27 Jan '06

Hello, I have a system that I am preparing to update that currently uses dovecot for pop and imap (will have same ip as old system). In tests, I at times re-download data from the server if I have deleted or moved it in the client and the data is still on the server (just for pop). I am guessing the UIDs generated are different on the new system. Is there any way to check and see if they are the same on each system, and if they are not, how can I move that information over. thanks, Dan

1 0

[Dovecot] nfs and pop3
by Marten Lehmann 27 Jan '06

27 Jan '06

Hi, I'm working with dovecot 1.0.beta2 for pop3 only and have set index=memory, so no indizes are created on the disk. pop3_uidl_format is set to %f. The maildirs are located on an nfs-share. So generally, this setup is very similar to what qmail-popup and qmail-pop3d does. However, everytime I'm switching from qmail-pop3d to dovecot, the system load increases from less than 2 to more than 30 (and later up to 60 and more). The problem is I/O, probably caused by nfs-access. But what is causing this accesses? qmail-pop3d just takes filenames as UIDL, and moves the mails from new to cur, reads them to send them to the client or deletes them. This is working fine. But what is dovecot doing? There must be a lot more things that cause that high I/O load. Indizes are disabled, so they cannot be the cause any longer. Any ideas? I just want to switch to dovecot at some point finally without having qmail-pop3d as backup. Regards Marten

4 7

[Dovecot] gcc 2.95 compile errors
by Chris Wakelin 27 Jan '06

27 Jan '06

Timo, This is what I get when I compile 1.0-beta2 with gcc 2.95. It looks like I can then open my problem mbox even without your mbox-sync patch. It turns out I'd been using gcc 3.2.2 inadvertently, probably via some sort of shell bug - I'd accidentally set an environment variable called "PATH=/opt/RDGgcc3/bin:/usr/bin ..." and I guess some script had mistaken it for the real PATH environment variable (which didn't include the gcc3 location). Should I be worried? Chris ostream-file.c: In function `o_stream_writev': ostream-file.c:126: warning: `ret' might be used uninitialized in this function ostream-file.c: In function `_send_istream': ostream-file.c:671: warning: assignment from incompatible pointer type mail-cache.c: In function `mail_cache_lock': mail-cache.c:374: warning: `ret' might be used uninitialized in this function mail-index-transaction.c: In function `mail_index_update_header_ext': mail-index-transaction.c:710: warning: unused parameter `t' mail-index-transaction.c:711: warning: unused parameter `ext_id' mail-index-transaction.c:711: warning: unused parameter `offset' mail-index-transaction.c:712: warning: unused parameter `data' mail-index-transaction.c:712: warning: unused parameter `size' maildir-storage.c:891: warning: missing initializer maildir-storage.c:891: warning: (near initialization for `maildir_storage.pool') maildir-storage.c:926: warning: missing initializer maildir-storage.c:926: warning: (near initialization for `maildir_mailbox.pool') mbox-sync.c: In function `mbox_sync_seek_to_uid': mbox-sync.c:921: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_handle_eof_updates': mbox-sync.c:1228: warning: assignment from incompatible pointer type mbox-sync.c:1287: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_update_index_header': mbox-sync.c:1330: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_do': mbox-sync.c:1418: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_has_changed': mbox-sync.c:1496: warning: assignment from incompatible pointer type mbox-storage.c:1045: warning: missing initializer mbox-storage.c:1045: warning: (near initialization for `mbox_storage.pool') mbox-storage.c:1080: warning: missing initializer mbox-storage.c:1080: warning: (near initialization for `mbox_mailbox.pool') dbox-storage.c:630: warning: missing initializer dbox-storage.c:630: warning: (near initialization for `dbox_storage.pool') dbox-storage.c:665: warning: missing initializer dbox-storage.c:665: warning: (near initialization for `dbox_mailbox.pool') dbox-transaction.c: In function `dbox_transaction_commit': dbox-transaction.c:20: warning: unused parameter `flags' dbox-transaction.c: In function `dbox_transaction_rollback': dbox-transaction.c:77: warning: unused variable `dbox' auth-server-connection.c: In function `auth_server_connection_new': auth-server-connection.c:200: warning: `fd' might be used uninitialized in this function auth-master-connection.c: In function `master_input_die': auth-master-connection.c:145: warning: unused parameter `conn' main.c: In function `create_unix_listener': main.c:101: warning: `fd' might be used uninitialized in this function dict-process.c:96: warning: `dict_process_listen' defined but not used master-settings.c:360: warning: missing initializer master-settings.c:360: warning: (near initialization for `default_settings.listen_ip') quota-storage.c: In function `quota_save_init': quota-storage.c:165: warning: assignment from incompatible pointer type -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 1

[Dovecot] chained ssl cert not working
by harryp＠dmsnev.com 27 Jan '06

27 Jan '06

I am running a production server with 40 pop3 users using dovecot 0.99.14. I am trying to get a chained certificate installed that I purchased through godaddy.com. I need some clarification on how to do this. I found some really vague instructions on the dovecot wiki http://wiki.dovecot.org/ChainedSSLCertificates?highlight=%28chained%29 Unfortunately these instructions are very confusing for me. I also found someone else who asked a similar question http://dovecot.org/list/dovecot/2005-June/007528.html I have tried to get this to work, but have failed. Could someone please explain this better. I don't understand if all of these keys/certificates go into 1 file or what. I need an example if someone could be so kind as to take a moment of their time. Thanks for any help.

3 3

[Dovecot] out of memory error
by Pavel Volkovitskiy 27 Jan '06

27 Jan '06

Hello I have this errors in my dovecot.log every day or two: ============================================= ... dovecot: Jan 24 10:28:56 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:01 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:03 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:03 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:03 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:41 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:56 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:30:36 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:30:38 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:30:39 Error: auth-worker(default): Out of memory (Needed 52 bytes) dovecot: Jan 24 10:30:41 Error: auth-worker(default): pool_system_malloc(): Out of memory dovecot: Jan 24 10:30:41 Error: child 3576 (auth-worker) returned error 83 (Out of memory) ============================================= I use dovecot 1.0-beta1 login_process_size = 128 login_process_per_connection = no login_processes_count = 5 login_max_processes_count = 128 login_max_logging_users = 256 -- Pavel

3 6

[Dovecot] How to make pops
by mickael.choisnard＠free.fr 27 Jan '06

27 Jan '06

Hi, I use dovecot (pop) with gentoo but it's not securize. I would like to use pops but i don't how to do this. I think i have to use certificates... This my dovecot.conf : protocols = imap imaps pop3 pop3s imap_listen = * pop3_listen = * imaps_listen = * pop3s_listen = * ssl_disable = no login = imap login = pop3 default_mail_env = maildir:%h/.maildir mbox_locks = fcntl dotlock auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam dovecot auth_user = root auth_verbose = yes auth_debug = yes Thanks for your help

2 1