March 2014 - dovecot - dovecot.org

[Dovecot] possible quota bug ?
by fernando.figaro＠uol.com.br 31 Mar '14

31 Mar '14

Hi, I'm using dovecot 2.2.5 with quota (maildir backend), zlib and expunge plugins. When I list maildirsize file, I get: 1073741824S 17952 16 If I receive a new message (example: 1204 bytes compressed and 2524 bytes plain text), the quota file is write correctly (2524 1 entry). When I move the message to trash folder (or between user custom folders) the file have wrong entries: 1073741824S 17952 16 2524 1 1204 1 (this is the size of the compressed message) -2524 -1 I coudn't find any relation with the config settings causing this problem and checked the changelog since 2.2.5. Had someone had this same problem? Thanks, Fernando

4 6

Re: [Dovecot] Connection refused userdb lookup ..dovecot/auth-userdb
by Simon 31 Mar '14

31 Mar '14

On Thursday, March 13, 2014, Steffen Kaiser <skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 13 Mar 2014, Simon wrote: > > Ive taken a look at this and cant quite figure out what is going on here. >> I have tested all the SQL permissions, and also changed the unix_listener >> auth-userdb mode to 0666 (as instructed elsewhere to try and solve this >> issue), but cannot seem to work out what the issue is. >> > > what happens if you connect to that socket manually, e.g.: > > # sudo -u <lda-user> socat - UNIX:/usr/local/dovecot/var/ > run/dovecot/auth-userdb > VERSION 1 1 > SPID 1746 > > Maybe first try as root, then with the partucular users. > Thanks for the reply! I tried this as root and got the following: [root@vmail1 ~]# socat - UNIX:/usr/local/dovecot/var/run/dovecot/auth-userdb 2014/03/16 20:57:05 socat[24404] E connect(3, AF=1 "/usr/local/dovecot/var/run/dovecot/auth-userdb", 48): Connection refused Seems a bit wierd that I can't connect as root? Simon

4 12

[Dovecot] still issues with metadata support
by Mihai Badici 31 Mar '14

31 Mar '14

On dovecot 2.2.12 compiled from source I use ActiveSync with kolab-syncroton. When running a test i have this imap log: [29-Mar-2014 22:58:25 +0200]: [F658] S: A0004 OK Getmetadata completed. [29-Mar-2014 22:58:25 +0200]: [F658] C: A0005 SETMETADATA INBOX (/private/vendor/kolab/activesync "{\"DEVICE\":{\"601099122\":{\"ID\": \"a5daac4806642a1cfeceb53aea32e86218c4d512\",\"TYPE\": \"TestActiveSyncConnectivity\",\"ALIAS\":null}},\"FOLDER\":{\"601099122\": {\"S\":1}}}") [29-Mar-2014 22:58:26 +0200]: [F658] S: A0005 OK Setmetadata completed. [29-Mar-2014 22:58:26 +0200]: [F658] C: A0006 GETMETADATA "*" (/private/vendor/kolab/activesync) [29-Mar-2014 22:58:26 +0200]: [F658] S: A0006 NO Mailbox doesn't exist: * [29-Mar-2014 22:58:26 +0200]: [F658] C: A0007 GETMETADATA "*" (/private/vendor/kolab/folder-type /shared/vendor/kolab/folder-type) [29-Mar-2014 22:58:26 +0200]: [F658] S: A0007 NO Mailbox doesn't exist: * [29-Mar-2014 22:58:26 +0200]: [F658] C: A0008 GETMETADATA "*" (/private/vendor/kolab/folder-type /shared/vendor/kolab/folder-type) [29-Mar-2014 22:58:26 +0200]: [F658] S: A0008 NO Mailbox doesn't exist: * [29-Mar-2014 22:58:26 +0200]: [F658] C: A0009 GETMETADATA "*" (/private/vendor/kolab/folder-type /shared/vendor/kolab/folder-type) [29-Mar-2014 22:58:26 +0200]: [F658] S: A0009 NO Mailbox doesn't exist: * [29-Mar-2014 22:58:26 +0200]: [F658] C: A0010 GETMETADATA "*" (/private/vendor/kolab/folder-type /shared/vendor/kolab/folder-type) [29-Mar-2014 22:58:26 +0200]: [F658] S: A0010 NO Mailbox doesn't exist: * [29-Mar-2014 22:58:26 +0200]: [F658] C: A0011 GETMETADATA "*" (/private/vendor/kolab/folder-type /shared/vendor/kolab/folder-type) [29-Mar-2014 22:58:26 +0200]: [F658] S: A0011 NO Mailbox doesn't exist: * It looks like GETMETADATA "*" is still not expanded , even we have this part of code in cmd-getmetadata.c: else if (strchr(mailbox, '*') == NULL && strchr(mailbox, '%') == NULL) { ns = client_find_namespace(cmd, &mailbox); if (ns == NULL) return TRUE; return cmd_getmetadata_mailbox(ctx, ns, mailbox); } else { /* wildcards in mailbox name. this isn't supported by RFC 5464, but it was in the earlier drafts and is already used by some software (Horde). */ const char *patterns[2]; patterns[0] = mailbox; patterns[1] = NULL; -- Mihai Bădici http://mihai.badici.ro

2 3

[Dovecot] pop3 mailbox mirroring issues using dsync
by Nikolaos Milas 30 Mar '14

30 Mar '14

Hello, I have setup v2.2.12 to mirror mailboxes between our main mail server (vmail.example.com) and a failover server (vmail1.example.com) The problem I have is the behavior of mailboxes used on the main server (*vmail*) over POP3. I have setup an IMAP account on the failover server (*vmail1*) on such a mailbox: the mailbox is used on vmail using POP3 and the same is monitored on vmail1 using IMAP. It's mailbox *userx*(in Maildir format). I notice that all mail coming in userx mailbox on vmail, is correctly replicated on vmail1, but when it is downloaded from vmail over POP3 (and the mailbox there remains empty), the same mailbox on vmail1 is not updated to be emptied (automatically) as well, but it is accumulating mail forever (which is real problem on the mirror server). Is there a setting to enable correct mirroring of a POP3 mailbox (to empty the respective mailbox on the failover server) when mail is downloaded from it or something else should be done in this respect? Please explain. I quote below the full current config on the main server. Thanks in advance, Nick ====================================================================== # 2.2.12: dovecot.conf protocols = imap pop3 login_greeting = Org POP/IMAP Srv XAPITI XPICTOY mail_location = maildir:~/Maildir/ mail_gid = 500 mail_uid = 500 auth_mechanisms = plain login auth_username_format = %Lu auth_verbose = yes auth_debug = no disable_plaintext_auth = no mail_plugins = quota notify replication protocol imap { imap_client_workarounds = "delay-newmail" mail_plugins = quota imap_quota notify replication } protocol pop3 { mail_max_userip_connections = 3 mail_plugins = quota notify replication pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master info_log_path = log_path = mail_plugins = quota notify replication postmaster_address = sysadmin(a)example.com sendmail_path = /usr/lib/sendmail } userdb { args = /etc/dovecot/dovecot-usrdb-ldap.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-passdb-ldap.conf driver = ldap } dsync_remote_cmd = ssh -l root vmail1.example.com doveadm dsync-server -u%u plugin { mail_replica = remote:vmail@vmail1.example.com } plugin { quota = maildir:User quota quota_rule = *:storage=4G quota_rule2 = Trash:storage=+3%% quota_warning = storage=75%% quota-warning 75 %u quota_warning2 = storage=90%% quota-warning 90 %u } service quota-warning { executable = script /opt/mail1.sh user = vmail unix_listener quota-warning { user = vmail } } service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service replicator { unix_listener replicator-doveadm { mode = 0600 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } user = root } service imap-login { service_count = 1 vsz_limit = 64 M } service pop3-login { service_count = 1 vsz_limit = 64 M } service replicator { process_min_avail = 1 } ssl_ca = </etc/pki/tls/certs/chain-1552.pem ssl_cert = </etc/pki/tls/certs/cert-1552.pem ssl_key = </etc/pki/tls/private/key-1552.pem syslog_facility = local1 ======================================================================

1 1

[Dovecot] basic dsync wrapper for migration from another server
by Alan McGinlay 29 Mar '14

29 Mar '14

Hi, I cobbled together this somewhat shoddy Bash script to migrate email accounts from our Cyrus server to a new dovecot system. Feel free to use, or laugh at it as you wish :) #!/bin/bash ## # Migrate email accounts via IMAP from one server to another ## trap "kill 0" SIGINT workdir=/root/migrate # Load list of users into array. The file "migration_map" should contain one user(a)domain.tld per line. mapfile userList < $workdir/migration_map # Number of symultanious migrations num=10 index=0 # Loop over the array of user accounts function process_userlist { procs=$(ps aux | grep "dsync" | grep -v "grep" | wc -l) # Perform $num operations at a time for the length of the userList while [[ $procs -lt $num ]] && [[ ${#userList[@]} -gt $index ]]; do procs=$(ps aux | grep "dsync" | grep -v "grep" | wc -l) dsync -o mail_fsync=never mirror -f -R -u ${userList[$index]} imapc:& echo "procs: $procs user: ${userList[$index]} index: $index" let index++ done } # Until the userList is empty, keep going until [ ${#userList[@]} -eq $index ]; do process_userlist done exit 0

2 3

[Dovecot] Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
by Alan McGinlay 28 Mar '14

28 Mar '14

While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12 (compiled from source) dsync aborts with a backtrace on some (maybe 15 out of 800) mail accounts: (same error happens wiht or without -f flag) dsync -D -v -o mail_fsync=never mirror -f -R -u user@domain imapc: <snip> dsync(user(a)domain.com): Debug: brain M: in state=sync_mails dsync(user(a)domain.com): Debug: brain M: in box 'Privat/Jerry' recv_state=mails send_state=done dsync(user(a)domain.com): Debug: brain M: import mail uid 55 guid dsync(user(a)domain.com): Debug: brain M: Import Privat/Jerry: Import mail body for GUID= UID=55 dsync(user(a)domain.com): Panic: file ostream-lzma.c: line 147: unreached dsync(user(a)domain.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x68d4f) [0x7fb79ac26d4f] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fb79ac26e2a] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb79abe03b9] -> /usr/local/lib/dovecot/lib20_zlib_plugin.so(+0x5ca7) [0x7fb799fd0ca7] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_flush+0x4d) [0x7fb79ac4039d] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_nflush+0xf) [0x7fb79ac4085f] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_nfinish+0x9) [0x7fb79ac408a9] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(maildir_save_finish+0x2b1) [0x7fb79aedb771] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_save_finish+0x64) [0x7fb79af0ed44] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0xa2) [0x7fb79af06c72] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(maildir_copy+0x51) [0x7fb79aed7b81] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5e) [0x7fb79af0eeae] -> dsync() [0x430dc2] -> dsync(dsync_brain_sync_mails+0x276) [0x42f256] -> dsync(dsync_brain_run+0x353) [0x42b8c3] -> dsync() [0x4296b2] -> dsync() [0x411dc7] -> dsync(doveadm_mail_try_run+0x260) [0x412a90] -> dsync(main+0x3f0) [0x4119b0] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fb79a81f76d] -> dsync() [0x411bad] Aborted I tried reconstructing the users mailbox on the cyrus server but it made no difference to the sync Dovecot compiled with: ./configure --with-ssl --with-mysql --with-solr --with-zlib --with-bzlib --with-libcap --with-lzma --with-ldap --with-pam As you can see, I have made very few configuration changes to get this far: # 2.2.12: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-60-virtual x86_64 Ubuntu 12.04.4 LTS xfs imapc_features = rfc822.size fetch-headers imapc_host = oldmail.domain.com imapc_master_user = <adminuser> imapc_password = <password> imapc_user = %u mail_gid = vmail mail_location = maildir:/var/vmail/domains/%d/%1n/%n/Maildir mail_plugins = zlib mail_prefetch_count = 50 mail_uid = vmail mailbox_list_index = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { zlib_save = xz zlib_save_level = 6 } service auth-worker { user = $default_internal_user } ssl_cert = </etc/ssl/certs/<cert> ssl_key = </etc/ssl/private/<cert> userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } I have looked at the source code referenced in the error and my limited knowledge got me looking for LZMA compress error codes but I couldn't find anything really :( Please help!

2 3

[Dovecot] How are messages send by sieve
by azurIt 28 Mar '14

28 Mar '14

Hi, i would like to ask how _exactly_ are messages send using sieve filters, for example vacation responses. Which SMTP server is used? Where can i find log files? How should i debug delivery problems? Thank you. azur

2 1

[Dovecot] struggling with dovecot v2.2
by Spyros Tsiolis 28 Mar '14

28 Mar '14

Hello all, Long time, no write :-) I am building a spanking, wonderful new mail server. I am very excited about this, since I am going to use the new dovecot v2.2.12 !! However, last time I did this (and documented it), I was working with v1.2. I consulted my notes and it seems there are huge differences between v1.2 and v2.2. So my question is, would anyone know if there's a "quick start" guide for v2.2 ? tia, s.

2 1

Re: [Dovecot] Help connecting from remote client (no auth attempts
by Joseph Tam 28 Mar '14

28 Mar '14

Blake McBride writes: > Thanks. The current version of Thunderbird auto-detects connection > parameters - presumably by trying every combination. All I give is an > email address and a password. They also have a manual configuration that I > spent a lot of time with. I was never able to do any better than their > auto-config. That's usually the cause of many problems I see with log entries like yours. It could happen when client and server disagree on using STARTTLS or SSL, so hardwiring your client to use whatever your server supports stops the client from fumbling around (and getting it wrong). > Given my experience with all this, I feel confident that Thunderbird is not > a factor in the problem. A network trace could clear that up, but auto-configure is problematic. > In terms of the config, I really don't know what I am doing. I think what > I want is clear text passwords sent over an SSL connection. Isn't that > secure? I don't know the difference between SSL and that TTSL thing. I > really don't care how it is setup. I just want it to be reasonably secure > and simple. You'll need to know these things in order to understand the problem. The essential difference, as far as your concerned, is that TLS (or STARTTLS or SSLv(some-number-I-forget)) starts out in plain text, then the client issues a command (STARTTLS) to commence the secure (encrypted) communication handshake, whereas SSL dives right in and expects the client to negotiate SSL parameters immediately. These two variations of SSL listen on two distinct ports. If you get these cross up, you'll get the above error log. In my experiments: SSL client -> TLS server port: Aborted login (no auth attempts) TLS client -> SSL server port: client hangs, Disconnected: Inactivity (no auth attempts in 180 secs) SSL/TLS + clear-text password is secure. If you do not use SSL/TLS, you'll have to use CRAM-MD5 or some challenge-response authentication to defeat password snooping. You could use both, but that's overkill. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Authentication woes, passwd standard install
by medicineme 28 Mar '14

28 Mar '14

I have two users working fine. Tried to add a third and it refuses to accept log on details. I've stripped everything back to default config, and still only the first two users are accepted! Can't understand it and it's driving me crazy. I've deleted and created the user a thousand times, and opened the config up as wide as possible. I'm obviously doing something stupid but what! # OS: Linux 3.2.0-4-686-pae i686 Debian 7.2 auth_mechanisms = plain login digest-md5 rpa base_dir = /var/run/dovecot/ disable_plaintext_auth = no login_trusted_networks = 10.0.0.0/8 passdb { driver = pam } protocols = imap service auth { user = root } ssl_cert = </etc/ssl/certs/server.pem ssl_key = </etc/ssl/private/mail.key userdb { driver = passwd } -- View this message in context: http://dovecot.2317879.n4.nabble.com/Authentication-woes-passwd-standard-in… Sent from the Dovecot mailing list archive at Nabble.com.

2 1