- dovecot - dovecot.org

[Dovecot] Dovecot 2.0 b13e01d82083
by Renaud Allard 18 Mar '10

18 Mar '10

Hello, I was trying to compile Dovecot 2.0 b13e01d82083, and I found this when doing make: Making all in lib test -f UnicodeData.txt || wget http://www.unicode.org/Public/UNIDATA/UnicodeData.txt /bin/sh: wget: not found I think it's probably not the best idea to assume everyone has wget installed. Perhaps it is installed by default on linux, but probably not on all other platforms. Why not just include the UnicodeData.txt file? Best Regards

2 1

[Dovecot] quota usage
by Papp Tamás 18 Mar '10

18 Mar '10

hi All! Dovecot's version is 1.2.11-0~auto+0 from http://xi.rename-it.nl/debian/ . dovecot.conf: dict { quota = mysql:/data/apps/dovecot/dict-sql.conf #expire = db:/var/lib/dovecot/expire.db } /data/apps/dovecot/dict-sql.conf: connect = host=127.0.0.1 dbname=db user=user password=pw map { pattern = priv/quota/storage table = quota username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota username_field = username value_field = messages } The problem is that the mailbox is almost empty: $ du -sh . 228K . But the quota usage show something else: mysql> select bytes,messages from quota where username='<user>'; +-----------+----------+ | bytes | messages | +-----------+----------+ | 217699358 | 987 | +-----------+----------+ What could be a problem, how can I fix this? Thank you very much, tamas

2 1

[Dovecot] .mailboxlist location
by Dave Brenner 18 Mar '10

18 Mar '10

Greetings. On our 1.2.9 setup, we are finding that .mailboxlist (we recompiled to use this name rather than .subscriptions) ends up in the user's ~/mail folder. We'd like this file to be stored in ~/ instead. Is this possible without changing namespaces (for UW compatibility) and/or userdb mail location? Thanks! -- Dave Brenner - david(a)toledotel.com The Toledo Telephone Company, Inc.

2 4

[Dovecot] v1.2.11 released
by Timo Sirainen 17 Mar '10

17 Mar '10

http://dovecot.org/releases/1.2/dovecot-1.2.11.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.11.tar.gz.sig mbox users really should upgrade, because by sending a message with a huge header you could basically cause a DoS (this problem exists only with v1.2.x, not with v1.0 or v1.1). - mbox: Message header reading was unnecessarily slow. Fetching a huge header could have resulted in Dovecot eating a lot of CPU. Also searching messages was much slower than necessary. - mbox, dbox, cydir: Mail root directory was created with 0770 permissions, instead of 0700. - maildir: Reading uidlist could have ended up in an infinite loop. - IMAP IDLE: v1.2.7+ caused extra load by checking changes every 0.5 seconds after a change had occurred in mailbox

2 2

Re: [Dovecot] I stream read - stale NFS file handle (reboot of server)
by Damon Atkins 17 Mar '10

17 Mar '10

In the old days NFS Shared Path had a static handle (ie a number), normal based on some number pulled out of the file system/inode. To fix (well work around) a security issue, for about 10+ years now, when a NFS server reboots, it generates a new random handle for the NFS Share. (sever may generate a new random handle per mount request) The NFS Stale Handle happens when the client is still using the old NFS handle, the only fix is a remount Some NFSv3 server let you fix the handle id for NFS share so it does not change over reboots. (this is how NFS clustering works, sometimes you need to install cluster software if the exportfs/share command does not let you hard code the fsid by hand. The other option is to use NFSv4 which is design to handle reboots by servers.

4 6

[Dovecot] dovecot 2.0beta3 installation
by Renaud Allard 17 Mar '10

17 Mar '10

Hello, I tried to install dovecot 2.0 beta3 and deliver seems to look for its config file in unusual places. In my exim logs, I get: 010-03-17 13:39:24 [31257] 1NrsWt-0004T0-1K <email(a)example.com>: dovecot_delivery transport output: lda: Fatal: User lookup failed: net_connect_unix(/opt/dovecot/etc/dovecot/dovecot.conf) failed: No such file or directory 2010-03-17 13:39:24 [31257] 1NrsWt-0004T0-1K == email(a)example.com (email(a)example.com) <email(a)example.com> R=local_user T=dovecot_delivery defer (0): Child process of dovecot_delivery transport returned 75 (could mean temporary error) from command: /opt/dovecot/libexec/dovecot/deliver Dovecot have been started with the following command: /opt/dovecot/sbin/dovecot -F -c /etc/dovecot/dovecot2.conf Furthermore, it has been compiled with: --prefix=/opt/dovecot --sysconfdir=/etc I don't see why it searches for /opt/dovecot/etc/dovecot/dovecot.conf Also, I didn't really find out how to convert the v1.2 config snippet: auth default { mechanisms = digest-md5 cram-md5 ntlm login plain passdb passwd-file { args = /etc/cram.pwd } userdb passwd { } userdb passwd-file { args = /etc/passwd } socket listen { client { path = /var/run/dovecot/auth-client mode = 0666 } } user = exim } I tried the following, but it does not seem to work as I get an authentication socket protocol error service auth { unix_listener /var/run/dovecot/auth-client { mode = 0666 } } Thanks for you help

2 6

[Dovecot] Testing EXTERNAL AUTHENTICATION
by Stephen Feyrer 17 Mar '10

17 Mar '10

Hi. I'm trying to test EXTERNAL AUTHENTICATION in Dovecot. To do this I first configured Thunderbird and Opera to use my server, neither of them were successful. As a result I contacted both organisations to enquire if they supported EXTERNAL AUTHENTICATION in their products. Thunderbird responded and said yes. However, on closer inspection my contact at Thunderbird identified that support for EXTERNAL AUTHENTICATION was poor at best and then only in SMTP. From that point on, my contact has been trying to implement support in Thunderbird. I've also try to test using openssl s_client which is detailed below. As far as I can tell my problems appear after the authentication. I don't know what the problem is only that there is one. [~] # dovecot -n # 1.2.10: /opt/etc/dovecot/dovecot.conf # OS: Linux 2.6.12.6-arm1 armv5tejl ext3 base_dir: /opt/var/run/dovecot/ log_path: /opt/var/log/dovecot/messages info_log_path: /opt/var/log/dovecot/info protocols: imaps listen: [::] ssl_ca_file: /opt/etc/domain.ca/cacrl.pem ssl_cert_file: /opt/etc/domain.ca/newcerts/mail.cer ssl_key_file: /opt/etc/domain.ca/private/mail.key ssl_cipher_list: ALL:!LOW:!SSLv2 ssl_verify_client_cert: yes verbose_ssl: yes login_dir: /opt/var/run/dovecot//login login_executable: /opt/libexec/dovecot/imap-login login_process_size: 32 mail_location: dbox:/share/MD0_DATA/mail/%u mail_debug: yes dbox_rotate_days: 0 imap_id_send: * imap_id_log: * lda: postmaster_address: postmaster(a)ksudra.net auth default: mechanisms: EXTERNAL realms: ksudra.net default_realm: ksudra.net user: admin verbose: yes debug: yes ssl_require_client_cert: yes ssl_username_from_cert: yes passdb: driver: passwd-file args: /opt/etc/dovecot/passwd userdb: driver: passwd [~] # openssl s_client -cert Stephen.pem -connect 10.1.1.245:993 <-- snip --> SSL handshake has read 4460 bytes and written 2451 bytes --- New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA Server public key is 4096 bit Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher : DHE-RSA-AES256-SHA Session-ID: [...] Session-ID-ctx: Master-Key: [...] Key-Arg : None Krb5 Principal: None Start Time: 1268756439 Timeout : 300 (sec) Verify return code: 19 (self signed certificate in certificate chain) --- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=EXTERNAL] Dovecot ready. 01 AUTHENTICATE EXTERNAL + 01 list "" * 01 NO [ALERT] Invalid base64 data in continued response 01 select inbox 01 BAD Error in IMAP command received by server. 02 select inbox 02 BAD Error in IMAP command received by server. DONE [~] # tail -f /opt/var/log/dovecot/info Mar 16 16:51:14 auth(default): Info: new auth connection: pid=9176 Mar 16 16:51:16 imap-login: Info: Valid certificate: /O=ksudra.net/OU=Ksudra CA/emailAddress=certs(a)ksudra.net/L=Wilmslow/ST=Cheshire/C=GB/CN=ksudra.net Mar 16 16:51:16 imap-login: Info: Valid certificate: /C=GB/ST=Cheshire/O=ksudra.net/OU=Stephen Feyrer/CN=Stephen Mar 16 16:52:06 auth(default): Info: client in: AUTH 1 EXTERNAL service=imap secured valid-client-cert cert_username=Stephen lip=10.1.1.245 rip=10.1.1.4 lport=993 rport=45379 Mar 16 16:52:06 auth(default): Info: client out: CONT 1 Mar 16 16:52:42 imap-login: Info: Valid certificate: /O=ksudra.net/OU=Ksudra CA/emailAddress=certs(a)ksudra.net/L=Wilmslow/ST=Cheshire/C=GB/CN=ksudra.net Mar 16 16:52:42 imap-login: Info: Valid certificate: /C=GB/ST=Cheshire/O=ksudra.net/OU=Stephen Feyrer/CN=Stephen Mar 16 16:52:42 auth(default): Info: client in: AUTH 1 EXTERNAL service=imap secured valid-client-cert cert_username=Stephen lip=10.1.1.245 rip=10.1.1.4 lport=993 rport=45381 Mar 16 16:52:42 auth(default): Info: client out: CONT 1 Mar 16 16:52:42 auth(default): Info: client in: CONT<hidden> Mar 16 16:52:42 auth(default): Info: EXTERNAL(Stephen,10.1.1.4): Invalid base64 data in continued response Mar 16 16:52:42 auth(default): Info: client out: FAIL 1 reason=Invalid base64 data in continued response Mar 16 16:52:42 auth(default): Info: new auth connection: pid=9182 Mar 16 16:52:45 auth(default): Info: client in: CONT<hidden> Mar 16 16:52:45 auth(default): Info: EXTERNAL(Stephen,10.1.1.4): Invalid base64 data in continued response Mar 16 16:52:45 auth(default): Info: client out: FAIL 1 reason=Invalid base64 data in continued response Mar 16 16:52:47 imap-login: Info: Aborted login (cert required, client didn't start TLS): method=EXTERNAL, rip=10.1.1.4, lip=10.1.1.245, TLS Mar 16 16:54:36 imap-login: Info: Valid certificate: /C=GB/ST=Cheshire/O=ksudra.net/OU=Stephen Feyrer/CN=Stephen Mar 16 16:54:36 auth(default): Info: new auth connection: pid=9188 Mar 16 16:54:37 auth(default): Info: client in: AUTH 1 EXTERNAL service=imap secured valid-client-cert cert_username=Stephen lip=10.1.1.245 rip=10.1.1.4 lport=993 rport=49113 Mar 16 16:54:37 auth(default): Info: client out: CONT 1 Mar 16 16:54:37 auth(default): Info: client in: CONT<hidden> Mar 16 16:54:37 auth(default): Info: EXTERNAL(Stephen,10.1.1.4): Invalid base64 data in continued response Mar 16 16:54:37 auth(default): Info: client out: FAIL 1 reason=Invalid base64 data in continued response Mar 16 16:54:42 imap-login: Info: Aborted login (cert required, client didn't start TLS): method=EXTERNAL, rip=10.1.1.4, lip=10.1.1.245, TLS Mar 16 16:54:49 imap-login: Info: Valid certificate: /O=ksudra.net/OU=Ksudra CA/emailAddress=certs(a)ksudra.net/L=Wilmslow/ST=Cheshire/C=GB/CN=ksudra.net Mar 16 16:54:49 imap-login: Info: Valid certificate: /C=GB/ST=Cheshire/O=ksudra.net/OU=Stephen Feyrer/CN=Stephen -- kind regards Stephen Feyrer.

3 12

[Dovecot] sieve fileinto rule (pigeonhole)
by Oliver Eales 17 Mar '10

17 Mar '10

Hello, i discovered that when a sieve rule "fileinto drawer;" tries to deliver a mail into a non existent drawer, the drawer gets created. This is neat, but is there also a way to automatically subcribe to the created folder ? Regards, Oliver Eales

2 4

[Dovecot] qmail-secretary plugin for dovecot deliver
by Rajkumar S 17 Mar '10

17 Mar '10

Hi, I have been using qmail-ldap for quite some time and now moved to postfix/dovecot. One feature that I miss is that provided by qmail-secretary. qmail-secretary basically is a mail list manager with following features: 1 no limit, just explode to all members 2 members only, as the name says; only members are allowed (based on envelope sender, so not very secure, everybody can fake that) 3 sender confirm, sender has to confirm submission and return address like DJBs qmail-secretary 4 moderated, moderator(s) have to accept every message; there are DN and RFC822 moderators All configuration (name, members, moderated etc...) are taken from LDAP. I had gone through the code and from what I understand for each 4 delivery types it works as follows: 1. Just deliver to all recipients (say, inject it via sendmail). 2. verify if envelope sender is in allowed list and proceed as above. 3. 1. create a random hash 2. save the mail in new/ with hash as filename 3. create a new mail with listname-confirm-hash(a)domain.com and send 4. If that mail comes back, deliver the mail to all recipients. 4. 1. as above but using listname-approve-hash and list-name-reject-hash 2. move the msg to cur/ 3. if appropriate reply comes retrieve the mail from cur/ and send to all recipient. qmail-secretary is invoked by qmail-local and thus this is a nice candidate for a deliver plugin. Before I start coding I just want to check if there is any gotchas that I am missing? I assume all these operations can be performed as a deliver plugin and that deliver plugin is the correct place for such functionality. It goes without saying that I would be contributing this plugin back to dovecot. with regards, raj

4 9

Re: [Dovecot] [xmail] XMail + Dovecot
by Sabahattin Gucukoglu 17 Mar '10

17 Mar '10

What, exactly, is the problem? How do you want Dovecot and XMail to work together? I am setting up Dovecot to read from standard Maildirs in user home directories, because I am using a separate delivery agent (TMDA but would work for maildrop, Dovecot's deliver program and others) to deliver mails using mailproc.tab. So, even while XMail runs as root, Dovecot need not and there is no problem getting it to work just like with other MTAs. XMail can't help with delivery to Maildir because it runs as root, and unless you mess about with packet filters to non-root it you'll still end up using for instance XACLs to allow Dovecot to read the mails. For authentication of XMail to Dovecot you would have to write external authentication helpers that use Dovecot's protocol. Or, you can use checkpassword or PAM-POP3 or something else to try getting Dovecot to authenticate against the active XMail list of users. Or you can just do what I do, maintain two databases and keep them in sync. Cheers, Sabahattin

1 0