- dovecot - dovecot.org

[Dovecot] v1.1.alpha5 crashes with segmentation fault
by arvids 15 Sep '07

15 Sep '07

Hello, dovecot process crashes on startup with segmentation fault. Here is backtrace: (gdb) r Starting program: /usr/local/dovecot/sbin/dovecot Program received signal SIGSEGV, Segmentation fault. settings_is_active (set=0x0) at master-settings.c:505 505 if (*set->protocols == '\0') { (gdb) bt full #0 settings_is_active (set=0x0) at master-settings.c:505 No locals. #1 0x080535d5 in master_settings_read (path=<value optimized out>, nochecks=false, nofixes=false) at master-settings.c:1397 ctx = {type = SETTINGS_TYPE_ROOT, parent_type = SETTINGS_TYPE_ROOT, protocol = MAIL_PROTOCOL_ANY, root = 0x80721d0, server = 0x80721d0, auth = 0x80727c8, socket = 0x807293c, auth_socket = 0x8072930, auth_passdb = 0x8072878, auth_userdb = 0x80728e0, namespace = 0x0, level = 0} server = <value optimized out> prev = (struct server_settings *) 0x80721d0 auth = <value optimized out> ns = <value optimized out> temp = <value optimized out> #2 0x08051407 in main (argc=1, argv=0xbfdf9524) at main.c:445 exec_protocol = 0x0 exec_section = 0x0 foreground = false ask_key_pass = false log_error = false dump_config = false dump_config_nondefaults = false i = -1208668172 (gdb) dovecot -n also crashes, but here is dovecot -n output taken with previous version: # 1.1.alpha4: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ syslog_facility: local0 protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/pop3-login login_greeting: Server. login_process_per_connection: no login_process_size: 64 verbose_proctitle: yes first_valid_uid: 95 first_valid_gid: 95 mail_uid: 95 mail_gid: 95 mail_location: maildir:~/Maildir mail_debug: yes fsync_disable: yes mail_executable: /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins: quota mail_plugin_dir: /usr/local/dovecot/lib/dovecot/pop3 pop3_enable_last: yes pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 apop cache_size: 2048 cache_ttl: 28800 cache_negative_ttl: 60 user: doveauth verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: dict:::proxy:/var/run/dovecot/dict-server:quotadict dict: quotadict: mysql:/usr/local/dovecot/etc/dovecot-sql-dict-quota.conf Regards, Arvids

2 1

[Dovecot] mailbox_idle_check_interval in minutes or seconds?
by Rupert Kolb 15 Sep '07

15 Sep '07

Hi, sorry for this question, but I didn't find the information in the documentation or wiki: Is mailbox_idle_check_interval (in dovecot.conf) in seconds or minutes? I think it's minutes. But ... It would be nice, if this will be in the docu of the dovecot.conf. Thanks Rupert

2 1

[Dovecot] v1.0.5 released
by Timo Sirainen 15 Sep '07

15 Sep '07

http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz.sig v1.0.4 was a bit bad release. - deliver: v1.0.4 broke home directory handling - maildir: Creating mailboxes didn't use dovecot-shared's group for cur/new/tmp directories.

3 4

[Dovecot] v1.1.alpha5 released
by Timo Sirainen 15 Sep '07

15 Sep '07

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha5.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha5.tar.gz.sig I think we're finally close to v1.1.betas. - Fixed "messages_count too large" index errors. - deliver was crashing. - Saving messages with maildir accessed freed memory, which might have caused crashes. - Index files are now never marked as "corrupted". Instead fsck is run which preserves as much of the original index as possible. This is important with dbox at least since index files are the only place where the latest flag/keyword changes are. Recent alphas were also modifying process's fd limits. The current behavior is: - If current fd limit is less than login_max_processes_count (imap +pop3) + max_mail_processes, log a warning at startup: "fd limit 1024 is lower than what Dovecot can use under full load (more than 1234). Either grow the limit or change login_max_processes_count and max_mail_processes settings" - Since 1024 is a common default limit, I dropped max_mail_processes default to 512. - Login processes drop their fd limit to the maximum number of fds needed, plus a few more just in case.

1 0

[Dovecot] Proxy problems with 1.0.5 !
by Ed W 15 Sep '07

15 Sep '07

Hi I am trying to do a staged migration over to dovecot, but having troubles at the first hurdle. I setup the proxy feature to redirect most of our users back to the current Courier imap/pop server, and it's partly working, but I'm getting some serious errors using Thunderbird and IMAP. Now, I had expected the proxying to be fairly transparent and basically just dovecot doing an auth and then passing the stream on to the other server? My problem is that using Thunderbird I can read all my folders OK, but I can't save anything in my Sent Items or Drafts folders... Basically I get errors every time I try and send an email, or try to save to the draft folder. Curiously, directly browsing into those folders works fine, as does deleting emails, and apparently copying them works fine also... Why is the saving of sent messages failing...? The setup is basically taking a working Thunderbird install, changing the server name from pointing at the Courier server to point at the dovecot server - dovecot in turn is told to proxy back to the original server. All I'm getting from Thunderbird is an "Invalid Command" response. Is there an easy way to get a look inside the imap stream to try and see what's failing? Any suggestions on why this is happening at all? One idea is that I have setup completely different namespaces in Dovecot, (with a hidden namespace which should be courier compatible), but I wouldn't have expected this to affect the Proxy stuff at all?! Grateful for any pointers to debug this - it's a fairly major hurdle for my rollout Thanks Ed W

4 8

[Dovecot] Quota problem
by Osvaldo Alvarez Pozo 15 Sep '07

15 Sep '07

Hi alI I install dovecot using the DovecotLDAPostfixAdminMySQL HOWTO but I have a problem with quota. Quota it is not taken into account by deliver I also tried a compiled dovecot version from sorces and the resault is the same. dovecot version from debian distribution 1.0.rc15-2 dovecot from sources dovecot-1.0.5.tar.gz Thanks in advance Osvaldo Those are my files File /etc/dovecot/dovecot.conf ssl_cert_file = /etc/apache2/ssl/server.crt ssl_key_file = /etc/apache2/ssl/server.key #ssl_ca_file = /etc/pki/dovecot/certs/ca-bundle.crt protocols = imap pop3 imaps pop3s log_timestamp = "%Y-%m-%d %H:%M:%S " #mail_location = maildir:/export/mail/%d/%u mail_location = maildir:/var/vmail/%d/%u/Maildir mail_extra_groups = mail first_valid_uid = 5000 last_valid_uid = 5000 maildir_copy_with_hardlinks = yes disable_plaintext_auth = no protocol imap { mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh protocol lda { postmaster_address = postmaster(a)example.com mail_plugins = quota log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log mail_plugins = cmusieve # sieve_global_dir = /etc/dovecot/sieve/ global_script_path =/etc/dovecot/sieve/dovecot.sieve } auth default { # Having "login" also as a mechanism make sure outlook can use the auth smtpd as well # http://wiki.dovecot.org/Authentication/Mechanisms mechanisms = plain login passdb sql { args = /etc/dovecot/sql.conf } userdb sql { args = /etc/dovecot/sql.conf } userdb prefetch { } user = nobody socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } dict { } plugin { quota = maildir:storage=10240:messages=1000 acl = vfile:/etc/dovecot/acls trash = /etc/dovecot/trash.conf } File /etc/dovecot/sql.conf driver = mysql default_pass_scheme = MD5 connect = host=localhost dbname=postfix user=postfix password=password user_query = SELECT concat('/var/vmail/', maildir, 'Maildir') as home, concat('maildir:/var/vmail/', maildir, 'Maildir') as mail, 5000 AS uid, 8 AS gid, concat('maildir:storage=', floor(quota/1024)) AS quota FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, concat('/var/vmail/', maildir, 'Maildir') as userdb_home, concat('maildir:/var/vmail/', maildir, 'Maildir') as userdb_mail, 5000 as userdb_uid, 12 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1'

2 1

[Dovecot] auth_default_realm for different listeners
by John Morrissey 15 Sep '07

15 Sep '07

We provide POP3 service for several realms, each of which has a substantial number of users logging in with no realm (bare username). We would like to use Dovecot, but I haven't been able to findout how to vary auth_default_realm for each listener. My most recent attempt was to set up one auth {} block for each realm with a different auth_default_realm and socket master path. I then set up one protocol pop3 {} block for each realm, listening on different IP addresses and with a auth_socket_path corresponding to the auth block for that listener. I'm not sure if I'm on the right track here, but I'm seeing two problems: 1. When dovecot starts, I get: Sep 5 18:32:21 pop01 dovecot: auth(otherdomain): Socket already exists: /var/run/dovecot/auth-otherdomain for each additional auth {} block. 2. dovecot won't start with auth_socket_path specified in a protocl pop3 {} block: Error in configuration file /etc/dovecot/dovecot.conf line 654: Unknown setting: socket_path Is there a way to vary auth_default_realm for each listener, so I can have multiple realms log in with bare usernames? thanks, john -- John Morrissey _o /\ ---- __o jwm(a)horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__

2 3

[Dovecot] namespace prefix issue with avelsieve
by it-dovecot＠ml.epigenomics.com 15 Sep '07

15 Sep '07

Hi! I am currently testing a setup with dovecot's lda, the cmusieve plugin, pysieved and the avelsieve plugin for squirrelmail. The issue I am stumbling upon is that avelsieve is generating folder names including the namespace prefix when creating "fileinto" rules. E.g.: A rule: If the header "Precedence" contains "bulk", then file it into the folder INBOX.bulk. Also keep a copy in INBOX, marked as deleted. translates into sieve: require ["fileinto","reject","vacation","imapflags","relational","comparator-i;ascii-numeric","regex","notify"]; if header :contains "Precedence" "bulk" { fileinto "INBOX.bulk"; addflag "\\Deleted"; keep; } But what happens when a matching email is delivered is that a new mailbox ".INBOX.bulk" in the user's Maildir is created. I.e. the email is not delivered to ~/.Maildir/.bulk as intended, but into ~/.Maildir/.INBOX.bulk, creating the new folder on the fly. The same happens when trying to fileinto folders from other namespaces. It seems that either avelsieve is generating "too much" and should remove the prefix (at least for INBOX) or dovecot's deliver is not able to use the namespaces definition in dovecot.conf correctly when interpreting sieve's fileinto directive. Did I miss something? This is the dovecot.conf in use: # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S listen: *:143 ssl_listen: *:993 ssl_cert_file: /etc/courier/imapd.pem ssl_key_file: /etc/courier/imapd.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 512 verbose_proctitle: yes mail_location: maildir:~/.Maildir:INDEX=/var/cache/dovecot/INBOX.%u:CONTROL=/var/cache/dovecot/INBOX.%u mail_full_filesystem_access: yes maildir_stat_dirs: yes maildir_copy_with_hardlinks: yes namespace: type: private separator: . prefix: INBOX. inbox: yes namespace: type: public separator: . prefix: shared. location: maildir:~/.Maildir/shared:INDEX=/var/cache/dovecot/shared.%u:CONTROL=/var/cache/dovecot/shared.%u namespace: type: private separator: . prefix: archive. location: maildir:/mnt/nfs/imap_archive.hm/%u:INDEX=/var/cache/dovecot/archive.%u:CONTROL=/var/cache/dovecot/archive.%u auth default: verbose: yes passdb: driver: passwd userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 Greetings -- Robert Sander Senior Manager Information Systems Epigenomics AG Kleine Praesidentenstr. 1 10178 Berlin, Germany phone:+49-30-24345-0 fax:+49-30-24345-555 http://www.epigenomics.com robert.sander(a)epigenomics.com

2 1

[Dovecot] Broken Pipe
by Joseph D. Wagner 15 Sep '07

15 Sep '07

Since upgrading to dovecot 1.0.5, I started to see the following error in maillog: dovecot: IMAP(username): Connection closed: Broken pipe Any insight that anyone can offer would be greatly appreciated. I've attached a complete list of all dovecot log entries in maillog in the hope that it will help you identify the issue. Thanks in advance. Joseph D. Wagner

3 2

[Dovecot] Error: imap-login: Can't connect to auth server atdefault: Resource temporarily unavailable
by David Gitman 15 Sep '07

15 Sep '07

Did you ever solve this? I'm having the same problem. David Gitman david(a)gitman.net http://gitman.net Yahoo Messenger: gitmand AIM: gitmand Skype: davidgitman

1 0