March 2007 - dovecot - dovecot.org

[Dovecot] mail archive
by T. Horsnell 09 Mar '07

09 Mar '07

I'd like to download a complete mail archive so that I can browse for problems concerning Mulberry. Is this possible, or can I only get them in monthly gulps? Cheers, Terry. --

5 7

[Dovecot] Bug: mbox-sync-parse.c: line 228
by Dean Quanne 09 Mar '07

09 Mar '07

[root@mail postfix]# dovecot --version 1.0.rc25 [root@mail postfix]# dovecot -n # /usr/local/etc/dovecot.conf ssl_cert_file: /usr/share/ssl/certs/dovecot.pem ssl_key_file: /usr/share/ssl/private/dovecot.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mbox_write_locks: fcntl auth default: passdb: driver: pam userdb: driver: passwd Attempting to delete an email yields ... (from Thunderbird, Becky and Squirrel WebMail) Mar 5 23:58:30 localhost dovecot: imap-login: Login: user=<dean>, method=PLAIN, rip=192.168.0.81, lip=81.235.169.182, TLS Mar 5 23:58:30 localhost dovecot: IMAP(dean): file mbox-sync-parse.c: line 228 (parse_x_imap_base): assertion failed: (ctx->sync_ctx->next_uid > ctx->sync_ctx->prev_msg_uid) Mar 5 23:58:30 localhost dovecot: IMAP(dean): Raw backtrace: imap [0x80a8265] -> imap [0x80a7de7] -> imap [0x8070a04] -> imap [0x8070a17] -> imap(mbox_sync_parse_next_mail+0x200) [0x807101c] -> imap(mbox_sync_rewrite+0x94f) [0x8077813] -> imap [0x80724bc] -> imap(mbox_sync+0x3e2) [0x807447a] -> imap [0x806cd9a] -> imap(cmd_copy+0x23d) [0x8057599] -> imap(cmd_uid+0x76) [0x805a60a] -> imap [0x805afb6] -> imap [0x805af4a] -> imap(_client_input+0x78) [0x805b0fc] -> imap(io_loop_handler_run+0x131) [0x80ad9e1] -> imap(io_loop_run+0x21) [0x80acf79] -> imap(main+0x458) [0x8061fc4] -> /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x467e23] -> imap [0x8056799] Mar 5 23:58:30 localhost dovecot: child 4221 (imap) killed with signal 6 -- Dean Quanne

3 3

[Dovecot] Dovecot vs Couir-IMAP
by Erdenebat Gantomor 09 Mar '07

09 Mar '07

I'm the beginner for IMAP/POP3 servers. I'm starting to use Dovecot. But I'm confusing between Courier-IMAP and Dovecot. Anyone tell me some quick tips regarding this issue. What's the better and what's the worst thing comparing these two IMAP/POP3 servers? I think the Dovecot is good enough for security and performance issue over Courier. Is it right? And how about the feature comparision? -- Best regards, Erdenebat Guntomor/ /mailto:RkLogin@gmail.com

9 11

[Dovecot] Dovecot's Sieve Support
by Robb Beal 09 Mar '07

09 Mar '07

Hi Folks, I'm looking for details of Dovecot's Sieve support. Specifically, Support for Sieve scripts (RFC 3028) and the protocol for remotely managing Sieve scripts, including: -- draft-martin-managesieve-06.txt -- draft-ietf-sieve-imapflags-05.txt And the following Sieve actions: -- fileinto -- redirect -- imapflags Thanks, Robb Beal -- www.laszlosystems.com --

2 1

[Dovecot] Dovecot Stable Version
by Erdenebat Gantomor 09 Mar '07

09 Mar '07

Dovecot is now in release candidate. When will release stable? Is it safe to use in production? I mean now the Dovecot is stable enough to use in production? -- Best regards, Erdenebat Guntomor/ /mailto:RkLogin@gmail.com

4 3

[Dovecot] global_script_path and virtual users
by Joan 09 Mar '07

09 Mar '07

We have a big installation with postfix + dovecot + sieve. Now we would like to create a "junk" folder in every customer inbox so they can discard the spam by they own. We are planning to user global_script_path = /etc/dovecot/dovecot.sieve Where /etc/dovecot/dovecot.sieve is: require "fileinto"; if exists "X-Spam-Flag" { fileinto "Junk"; } My question is, will the script find the users in our database? And how, will it be using the lda configuration? I have been for weeks looking for this in the wiki and couldn't find it anywhere. I promise I'll put it in there if I find the clue :)

2 1

Re: [Dovecot] Problems with different mail clients
by Nuno Miguel Neves 09 Mar '07

09 Mar '07

Hello, all. I thing I solved my problem... I just changed dovecot.conf to include the default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u which is disabled by default. Now, apparently, I can access my inbox from both my pocket and my Vista Mail. Than you all and hope this helps someone else. :) ----- Original Message ----- From: Nuno Miguel da Cruz Neves To: dovecot(a)dovecot.org Sent: Thursday, March 08, 2007 7:23 PM Subject: Problems with different mail clients I use dovecot as my imap server, and everything is ok. I used an IMAP client from Windows XP (Outlook Express) as well as Pocket PC (Windows Mobile 5) and webmail. The problem is that I recently used Windows Vista and its imap client (Windows Mail), and problems began. From the Windows XP machine, all is ok, but from the Pocket PC a weird thing happens: When I first configure the client, in the Received Items, it shows all items correctly, but then, when starting to donwload, they simply disappear. All other folders are OK. Problem is just in inbox. I thing (although my tests were not exaustive) that deleting the .imap folder solves the problem, but I just can't understand why, because it is recreated again... Any help? Thank you, ------------------------------------------------------------- Tel +351 21 3182720 | Fax +351 213146114 Email Nuno.Miguel.Neves(a)pkf.pt | www.pkf.pt PKF | Av. António Augusto de Aguiar, 108, 4º | 1050-019 Lisboa | Portugal

1 0

[Dovecot] "ldap_result() failed: Can't contact LDAP server" log messages
by Mike Brudenell 09 Mar '07

09 Mar '07

Greetings - I', continuing to build a test system that, at present, only I have access to. It is running Dovecot 1.0rc24. Here's the output of a "dovecot-n"... # /usr/local/etc/dovecot.conf log_path: /logfiles/mail/live/dovecot protocols: imap ssl_cert_file: /usr/local/etc/ssl/certs/imapservice-bundle.crt ssl_key_file: /usr/local/etc/ssl/private/imapservice-private.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_process_per_connection: no login_greeting_capability: yes mail_location: maildir:/mailstore/%1u/%u/Maildir:INDEX=/var/dovecot/ index/%1u/%u:CONTROL=/var/dovecot/control/%1u/%u mail_debug: yes mmap_disable: yes maildir_copy_with_hardlinks: yes mail_log_prefix: %Us(%u)[%p]: imap_client_workarounds: delay-newmail outlook-idle namespace: type: private separator: / inbox: yes auth default: mechanisms: plain login cache_size: 1024 cache_ttl: 600 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 username_format: %Lu passdb: driver: ldap args: /usr/local/etc/dovecot-ldap-passdb.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap-userdb.conf We are using LDAP for the passdb and userdb. The oddity is that even on a quiescent system (Dovecot started from scratch, but no connections being made to it) we are seeing these messages being logged, apparently every 5 minutes: dovecot: Mar 09 11:09:44 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:09:44 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:14:45 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:14:45 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:19:45 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Mar 09 11:19:45 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server I'm guessing there are two log entries each time because of separate connections being used for the passdb and userdb. The LDAP server *is* available throughout. I'm wondering if Dovecot is trying to hold the connection open but, after a timeout of 5 minutes of inactivity, the LDAP server is closing it and causing Dovecot to log this message. If this is indeed the case then I guess on a production server these message will be rarely if ever seen. Obviously I'd prefer not to have such worrying-sounding log entries appearing. (And if my guess is right then they're slightly misleading: the LDAP server *can* be contacted!) Any thoughts? Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

3 3

[Dovecot] deliver(redacted): Mar 08 10:13:03 Fatal: postmaster_address setting not given
by Larry Vaden 09 Mar '07

09 Mar '07

Hi, We're new to dovecot and like what we see so far, but Google doesn't seem to have much on this error message. What are the likely causes? Kind regards, Larry Vaden, CoFounder and CEO Internet Texoma, Inc. We Care About Your Connection The Market Leader In Texomaland Since 1995

3 2

Re: [Dovecot] 1.0rc26: ssl_verify_client=yes ?
by Apostolis Papagiannakis 09 Mar '07

09 Mar '07

> > Date: Thu, 08 Mar 2007 18:13:48 +0200 > From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] 1.0rc26: ssl_verify_client=yes ? > > On Thu, 2007-03-08 at 16:40 +0100, Steffen Kaiser wrote: > >> >> > On Thu, 8 Mar 2007, Timo Sirainen wrote: >> > >> >>>> > >> Q2) >>>> > >> The next step, if dovecot blocks the client because >>>> > >> of the verify_client_cert, how to create certs for OE, >>>> > >> Evolution and Thunderbird? >>>> >>> > > >>> > > I don't think most clients support SSL client certificates at all, >>> > > although I know some people are using them with some clients.. Maybe >>> > > someone could add a list of the clients supporting them into wiki. >>> >> > >> > Er, a dummy question, I guess: >> > Can you use client certs to login into Dovecot? >> > Aka can use the certs as "passdb"? >> > > Yes. It will still need some passdb, but you could use null password and > ssl_username_from_cert=yes settings in which case it doesn't matter what > user/password is used to log in. > > But it circumvents Dovecot's login/auth process security model, so I > don't recommend it that much. Maybe some day I'll make login process > forward the client cert to dovecot-auth which does the actual > verification. > I have successfully tested ssl_username_from_cert and found no real problem, apart from the fact that dovecot "username" takes the value of the certificate "CN" attribute , instead of the email attribute (in my case "Apostolos Papayanakis" instead of apap/ at /ccf.auth.gr). Everything else works as expected (eg, further userdb lookups based on certificate CN). Our University has issued a few thousand certificates with subjects such as "/C=GR/O=Aristotle University of Thessaloniki/OU=Network Operations Center/CN=Apostolos Papayanakis/emailAddress=apap/ at /ccf.auth.gr", that are used for administrative purposes. We would be very happy to use them as an alternative method of IMAP/POP3 authentication. However certificate CNs are not unique (e.g. "John Smith") and we would like to avoid constantly patching dovecot to use the email (or other) attribute from the certificate. I think replacing NID_commonName with NID_pkcs9_emailAddress ( or NID_subject_key_identifier, or NID_subject_alt_name) in login-common/ssl-proxy-openssl.c, line 527 would suffice. (X509_NAME_get_text_by_NID(X509_get_subject_name(x509), NID_commonName, buf, sizeof(buf)) < 0). Maybe I should post a complete patch if Timo is interested. Apostolis

3 2