- dovecot - dovecot.org

pigeonhole: upgrade 0.4.3 -> 0.4.6 broke script storage
by Petar Bogdanovic 12 Jan '15

12 Jan '15

Hi, I ran into some troubles while upgrading pigeonhole: crane dovecot: lda(petar): Error: sieve: Failed to access user storage (temporary failure) crane dovecot: lda(petar): Error: sieve: file storage: Could not find storage root directory; path was left unconfigured and autodetection failed After reading through the changelog, I noticed that there have been some changes in the script storage location syntax but that old prefix-less paths should still work fine. My lda-configuration is very simple: # lda protocol lda { mail_plugins = sieve postmaster_address = <snip> } plugin { sieve = /data/dovecot/user/%u.sieve sieve_extensions = +editheader sieve_max_redirects = 50 } And even if I change $sieve to: sieve = file:/data/dovecot/user/%u.sieve the error messages disappear but based on the sudden unfiltered wave of mails in my INBOX that I usually store somewhere else, I guess the path still doesn't work. Any ideas? Thanks, Petar Bogdanovic

2 3

Dovecot replication over TCP/SSL, certificate error
by Jonas Plitt 12 Jan '15

12 Jan '15

Hi All, I'm running TCP-based dsync replication on two dovecot nodes. Nowdays i tried to enable SSL (TCPS). I changed mail_replica prefix from tcp:* to tcps:* and added ssl=yes to the inet_listener. Then on running *doveadm sync* i'm getting the following message: " *doveadm(example(a)example.com <example(a)example.com>): Error: Couldn't initialize SSL context: Can't load CA certs from directory /etc/ssl/certs: error:02001024:system library:fopen:File name too longdoveadm: Error: Failed to iterate through some users*" this is my config (part): *ssl_cert = </etc/ssl/certs/alpha-servers.pemssl_key = </etc/ssl/private/alpha-servers.keyssl_ca = </etc/ssl/certs/startcom-ca-bundle.pemssl_client_ca_dir = /etc/ssl/certsssl_client_ca_file = </etc/ssl/certs/startcom-ca.pemssl_protocols = !SSLv2 !SSLv3* The file startcom-ba-bundle contains the complete chain. The file startcom-ca contains only the ca certificate. Can anybody help, please? -- with kind regards, Jonas

2 2

Solaris 10 make check core dumps
by Brian Eliassen 12 Jan '15

12 Jan '15

Hello everyone, I'm doing a standard build on Solaris 10 with Dovecot 2.2.15 without anything fancy: ./configure make make check make install Configure output looks like this: *** Install prefix . : /usr/local File offsets ... : 64bit I/O polling .... : poll I/O notifys .... : none SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : static passwd passwd-file shadow pam checkpassword : -bsdauth -sia -ldap -sql -vpopmail userdbs ........ : static prefetch passwd passwd-file checkpassword : -ldap -sql -vpopmail -nss SQL drivers .... : : -pgsql -mysql -sqlite Full text search : squat : -lucene -solr *** Everything works properly including the "make" until I try a "make check" at which time I receive the following failure. It would appear that something in test-http-auth is most unhappy. http auth challenges valid [0]: parse `Basic realm="WallyWorld"' ..... : ok http auth challenges valid [0]: [0]->scheme = Basic .................. : ok /bin/bash: line 1: 28057 Segmentation Fault (core dumped) ./$bin make[2]: *** [check-test] Error 1 make[2]: Leaving directory `/export/home/brian/software/dovecot-2.2.15/ src/lib-http' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/export/home/brian/software/dovecot-2.2.15/ src' make: *** [check-recursive] Error 1 This creates: -rw------- 1 root 1000 3523871 Jan 7 10:43 core Can this be safely ignored and I can proceed to "make install" or should I look somewhere else for the problem? Here is the mdb backtrace: $ mdb test-http-auth core Loading modules: [ libc.so.1 ld.so.1 ] > ::stack libc.so.1`strlen+0x50(29487, ffbffb00, ffbff43d, 0, 0, 0) libc.so.1`vsnprintf+0x70(4f2c0, 10f, 29478, ffbffaf8, 10, ff1c7078) t_noalloc_strdup_vprintf+0x3c(4f2c0, ffbffaf8, ffbffa2c, 1, 19, 0) p_strdup_vprintf+0xc(4cb90, 29478, ffbffaf8, ff1c759c, 4cc38, 4cb8c) t_strdup_printf+0x38(29478, 0, 0, 61fefeff, 80808080, 1010101) test_http_auth_challenges_valid+0x150(29000, 29400, 0, 4f250, 4cbb8, 0) test_run_funcs+0x24(4ca74, 1c00, ff1c7940, 4, ff312a00, ff13866c) test_run+0xc(4ca74, ffbffc7c, ffbffc84, 4f030, ff310140, 0) _start+0x5c(0, 0, 0, 0, 0, 0) Any help would be greatly appreciated. Brian

2 2

Dovecot on Fedora 20 or 21
by David Mehler 10 Jan '15

10 Jan '15

Hello, Is anyone running Dovecot on either a Fedora 20 or 21 system? I'm having an issue, on a system reboot, which I admit does not happen often, Dovecot fails to start in the systemctl list, output is status failed. The issue seems to be Dovecot can not bind to the ipv6 address. Now later if I manually log in to the box and start dovecot it works just fine no problems. I've googled and seen similar issues to this. Does anyone have a solution? Thanks. Dave.

4 3

pop3 seen
by David Saez 10 Jan '15

10 Jan '15

Hi Is there a way to know if a message has been dowloaded via pop3 and not seen via imap ?

4 5

Re: dovecot on wheezy, best ssl configuration ?
by Joseph Tam 10 Jan '15

10 Jan '15

ml(a)ruggedinbox.com writes: > Our smtp server is postfix, can you please suggest a better > 'ssl_protocols' and 'ssl_cipher_list' configuration ? > We are running Debian 7 Wheezy A useful command to know is "openssl ciphers" run on the server that will tell you the ciphers available given a protocol and cipher list spec. If it comes out to empty, your client won't be able to negotiate any SSL sessions, and you'll have include more ciphers. For example, TLSv1 protocol minus any low-grade encryption or SSLv2 ciphers: $ openssl ciphers -tlsv1 'ALL:\!LOW:\!SSLv2' ADH-AES256-SHA:DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA:AES256-SHA:ADH-AES128-SHA:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA:AES128-SHA:ADH-DES-CBC3-SHA:EXP-ADH-DES-CBC-SHA:ADH-RC4-MD5:EXP-ADH-RC4-MD5:EDH-RSA-DES-CBC3-SHA:EXP-EDH-RSA-DES-CBC-SHA:EDH-DSS-DES-CBC3-SHA:EXP-EDH-DSS-DES-CBC-SHA:DES-CBC3-SHA:EXP-DES-CBC-SHA:IDEA-CBC-SHA:EXP-RC2-CBC-MD5:RC4-SHA:RC4-MD5:EXP-RC4-MD5 Joseph Tam <jtam.home(a)gmail.com>

1 0

dovecot on wheezy, best ssl configuration ?
by ml＠ruggedinbox.com 10 Jan '15

10 Jan '15

Hi all, when hardening dovecot against the POODLE vulnerability, we followed the advise to disable SSL2 and SSL3 but this is giving problems with some email clients (claws-mail). ssl_protocols = !SSLv2 !SSLv3 results in the following error: dovecot: pop3-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=XXX, lip=XXX, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher, session=<2C8jBjIMmQBVGNd1> Our smtp server is postfix, can you please suggest a better 'ssl_protocols' and 'ssl_cipher_list' configuration ? We are running Debian 7 Wheezy Thank you, RuggedInbox team

4 8

auth-deny : from file to LDAP
by hummel＠pasteur.fr 09 Jan '15

09 Jan '15

Hello Timo, I want to deny access to some users. For now I'm doing it using 2 passdb's and listing users in a text file. !include auth-deny.conf.ext -> passwd-file driver !include auth-ldap.conf.ext -> ldap driver I want to do the same using only LDAP. I'm not quite sure how to do it : a) should I . change the driver of the first passdb from passwd-file to ldap . for user to be rejected, add an LDAP attribute named "foo" with a value of "yes" and map it with something like this : pass_attrs = ....,foo=deny in dovecot-ldap.conf.ext ? b) or could I use only one ldap passdb by changing the pass_filter from pass_filter = (&(objectClass=posixAccount)(uid=%u)) to something like pass_filter = (&(objectClass=posixAccount)(uid=%u)(!foo=yes)) ? Thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Groupe Exploitation et Infrastructure

3 4

Corrupted index cache after migrating from maildir to mdbox
by Tim 09 Jan '15

09 Jan '15

Hi guys, I'm running dovecot/postfix on my Debian Jessie maschine: # dovecot --version 2.2.13 doveconf -n output: http://p.bastelfreak.de/HsVwS/ today I migrated from maildir(located at /var/vmail) to mdbox with these commands: rsync -av -f"+ */" -f"- *" /var/vmail/ /home/vmail/ rm /home/vmail/*/*/Maildir -rf for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i |cut -d@ -f2); dsync -v -u $i mirror mdbox:/home/vmail/$d/$u/mdbox; done Then I changed the mail_location to mdbox:/home/vmail/%d/%n/mdbox and did the following commands: service dovecot restart for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i |cut -d@ -f2); dsync -v -u $i mirror maildir:/var/vmail/$d/$u/Mail; done doveadm index -A all INBOX for i in $(doveadm user \*); do doveadm -Dv fts rescan -u $i;done unfortunately I'm getting the following two kinds of error messages for all mail boxes in my mail.log: Error: Corrupted index cache file /home/vmail/%domain/%user/mdbox/mailboxes/%maildir/dbox-Mails/dovecot.index.cache: Broken virtual size for mail UID 2564 and: Error: read(/home/vmail/%domain/%user/mdbox/storage/m.108 ): FETCH BODY[] for mailbox %maildir UID 2564 got too little data: 2417 vs 6319 please let me know if you have any suggestions for fixing this issue or if you need more information. kind regards, Tim

6 19

Quota, doveadm, postfixadmin
by Ricardo 09 Jan '15

09 Jan '15

Hello all and happy holidays. I have Postfix+Dovecot+MySQL+Postfixadmin with CentOS 6.6, a virtual machines for testing, and then pass it to servers in production, my problem is the next: I add 30 MB for domain.local, then cast 10 MB for test1(a)domain.local and 20 MB for test2(a)domain.local, so far so good. Sending an attachment from one account to another, the example of test1(a)domain.local to test2(a)domain.local, test2(a)domain.local receive the email with the attachment. If I write in the shell doveadm quota get -u test2(a)domain.local I get the following: Quota name Type Value Limit % user STORAGE 3391 20000 16 user MESSAGE 3 10000 0 Informs me that I this consuming 16% of the 20 MB assigned to this account, but if I delete the file and again write doveadm quota get -u test2(a)domain.local I release this: Quota name Type Value Limit % user STORAGE 6782 20000 33 user MESSAGE 4 10000 0 Normal serious you continue using 16%, not 33%, when you go into the trash, because that happens from one place to another, right? These statistics the Postfixadmin Dame them so much as writing in the shell doveadm quota get -u test2(a)domain.local. I delete the file in the trash and to again write doveadm quota get -u test2(a)domain.local still see me. Quota name Type Value Limit % user STORAGE 6782 20000 33 user MESSAGE 4 10000 0 But I realize that so that it resets to 0%, I have to close the mail client, if not would follow using 33% and is when is 0% as shown here. Quota name Type Value Limit % user STORAGE 1 20000 0 user MESSAGE 2 10000 0 Is this normal? The client to send emails and exceed quota will having to always close the mail client, so you reset and stays at 0%? Can anyone help me? I have looked online but I can't find information about this. Has happened to someone? Thanks so much. Best regards.

2 1