- dovecot - dovecot.org

[Dovecot] PLAIN-MD5 passwords?
by Peter Clark 03 Jan '05

03 Jan '05

After I found out that {CRYPT} doesn't support passwords longer than 8 characters, I decided to switch over to MD5 for user passwords in my LDAP database. However, while I have no problem with Postfix + SASL, Dovecot fails to authenticate. Relevant bits from /etc/dovecot-ldap.conf: user_attrs = mailAddress,,,,, # The search string is identical to what's found in /etc/saslauthd.conf: user_filter = (&(|(uid=%u)(mailAddress=%u))(status=active)) pass_attrs = mailAddress,userPassword pass_filter = (&(|(uid=%u)(mailAddress=%u))(status=active)) default_pass_scheme = PLAIN-MD5 When I try to connect using either KMail or SquirrelMail (which worked just fine before I switched schemes), the following error appears in /var/log/syslog: ldap(user(a)mydomain.tld): password mismatch But when I try 'testsaslauthd -u user(a)mydomain.tld -p longpassword' it authenticates just fine. I have the line 'password-hash {MD5}' in /etc/ldap/slapd.conf, and I used 'slappasswd -h {MD5}' to create the MD5 versions of the passwords. Dovecot is v. 0.99.11. If I can't figure out how to get it to work with MD5, I guess I'll have to go back to CRYPT, but it would be nice to have longer passwords... :Peter

5 5

[Dovecot] Wanted: gnutls11 support
by Jaldhar H. Vyas 03 Jan '05

03 Jan '05

I talked to Timo about this before and even provided the beginnings of a patch but don't have enough time to really do a proper job. Anyway, dovecot doesn't work with recent versions of the GNU TLS library. As a result, I compile the Debian package with OpenSSL. However some of the other libraries used, such as OpenLDAP are linked against GNU TLS so Dovecot is linked against both. And it is suspected this is leading to bugs. So could some kind soul provide Timo with a patch he can include in 0.99.13? -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 0

Re: [Dovecot] Maildir owner importance
by Roi Efrati 02 Jan '05

02 Jan '05

That last line actually made it possible for me to be able to log into the server :) I am still getting errors from PAM but it starting to look good. Is there a good HowTo on setting Dovecot to comunicate directly to MySql without using PAM in the middle ? Also, Since Postfix is still not working on my server, I can't actually recive Emails. Is there somewere an example of the files that need to be in the maildir that I can put them in there and test that the email client get's the mail out ? On Wed, 29 Dec 2004 18:36:34 +0200, Timo Sirainen <tss(a)iki.fi> wrote: > > If you have passwords in Mysql, you probably don't want to use > passwd-file as your auth_userdb. Rather just use: > > auth_userdb = static uid=100 gid=101 home=/var/local/virtualdir/%d/%u >

4 7

[Dovecot] SASL AUTH
by Tom Allison 01 Jan '05

01 Jan '05

I'm reading through the dovecot wiki pages for virtual hosting with postgresql/postfix/dovecot/debian and it looks pretty nice but I think I'm going to skip the SASL authentication since I'm in a trusted network. I think all I need to do is skip section 5 entirely and bypass all the sasl references in the postfix section. Technically, I don't think any of the SASL has much to do with the dovecot configuration.

2 1

[Dovecot] random pool depletion
by Johannes Berg 31 Dec '04

31 Dec '04

I'm facing a problem with dovecot 1.0 test-59; ever since I installed it and use it my random pool is always depleted whenever someone opens an imap connection. This wouldn't be too bad if the machine was used interactively, but since it is not and other services read directly from /dev/random those are sometimes blocked due to dovecot depleting the pool by reading /dev/urandom. Thus my question: is it really necessary to use random numbers from /dev/urandom for temporary filenames? And even if, couldn't it use less? It apparently uses 8 bytes every time. johannes

2 3

[Dovecot] delivery agent in 1.0?
by "Branko F. Gračnar" 31 Dec '04

31 Dec '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi :) Is there any plan to include delivery agent in 1.x? I would be very happy, if there would be lmtp delivery agent included with dovecot 1.x... This would make creating large mailsystem cluster creation very simple + indexes would be always up2date. Brane -----BEGIN PGP SIGNATURE----- iD8DBQFBytD9N7LHXgqRB4IRAi67AKCn/A1t3tCsMX0nhL8l4sgzTfDhlACgj1j5 NdgMzA3v0dLx6Bnui62rLRc= =4UGm -----END PGP SIGNATURE-----

9 18

[Dovecot] Authentication difficulties
by Timo Sirainen 30 Dec '04

30 Dec '04

There are constantly pretty basic questions in this list (and in my inbox) about how to get user authentication work correctly. This means that the documentation how it all works is either bad, or people don't find it easily. Any ideas how to improve it? I did this now: - Documentation link in dovecot.org now points directly to Wiki, so people don't go read the outdated documents - Upcoming 1.0-tests and 0.99.13 will contain doc/USE-WIKI-INSTEAD file pointing to Wiki: http://dovecot.org/list/dovecot-cvs/2004-December/003928.html - Updated comments in dovecot-example.conf: http://dovecot.org/list/dovecot-cvs/2004-December/003924.html - Added pointers to Wiki in dovecot-example.conf: http://dovecot.org/list/dovecot-cvs/2004-December/003927.html How good are the Wiki documents about user authentication in general? The content should probably be split somehow to "getting started" vs. "everything there is to know about it" and "system users" vs. "virtual users". I'm not really sure how to best do that though. I think the Wiki in general could be better organized. Wish I knew how.

3 2

[Dovecot] Maildir owner importance
by Roi Efrati 29 Dec '04

29 Dec '04

I have set up a directory (/var/local/virtualdir/) as the maildir with a special user/group (virtualmail) and in it I create directories for each domain (example1.tld, example2.tld etc) and sub dir's for each mailbox). Only at the moment, apart from the first one, they are all created as with user root as the owner. How important is to have all the directory tree owned by the same user group (virtualmail:virtualmail) ?

4 11

[Dovecot] bug in 99.13-rc2 in ldap md5 patch
by Farkas Levente 29 Dec '04

29 Dec '04

hi, it takes me another hour do debug it again, although i already report it for both joshua and timo. the original patch for openldap's md5 crypt has a small bug. in passdb-ldap.c the schema is already PLAIN-MD5 since that was set in the other part of the original patch in password-scheme.c. do anybody use dovecot with ldap and md5 password? i don't think so:-( this patch would be useful to apply before the final 0.99.13. anyway in the current 1.0 series the PLAIN-MD5 and LDAP-MD5 schema are different. at least plain_md5_verify and plain_md5_generate differ from ldap_md5_verify and ldap_md5_generate. why? -- Levente "Si vis pacem para bellum!" --- dovecot-0.99.13/src/auth/passdb-ldap.c.lfarkas 2004-12-22 17:06:25.000000000 +0100 +++ dovecot-0.99.13/src/auth/passdb-ldap.c 2004-12-22 17:06:56.000000000 +0100 @@ -109,12 +109,11 @@ } /* Special case for OpenLDAP's MD5 type */ - if (strcasecmp(scheme, "MD5") == 0) { + if (strcasecmp(scheme, "PLAIN-MD5") == 0) { buf = buffer_create_static(data_stack_pool, 16); if (base64_decode(password, strlen(password), NULL, buf) == 1 && buffer_get_used_size(buf) == 16) { password = binary_to_hex(buffer_get_data(buf, NULL), 16); - scheme = "PLAIN-MD5"; } }

2 4

[Dovecot] 0.99.13-rc3
by Timo Sirainen 29 Dec '04

29 Dec '04

http://dovecot.org/rc/ One more. Added LDAP-MD5 password scheme and changed non-$1$-MD5 passwords to use it. This is how it's done in 1.0-tests.

1 0

[Dovecot] dovecot_auth / pam_mysql login errors
by Roi Efrati 29 Dec '04

29 Dec '04

I am getting this errors at the maillog file : Dec 29 12:22:10 websrv dovecot-auth: pam_sm_authenticate called. Dec 29 12:22:10 websrv dovecot-auth: host changed. Dec 29 12:22:10 websrv dovecot-auth: database changed. Dec 29 12:22:10 websrv dovecot-auth: dbuser changed. Dec 29 12:22:10 websrv dovecot-auth: dbpasswd changed. Dec 29 12:22:10 websrv dovecot-auth: table changed. Dec 29 12:22:10 websrv dovecot-auth: usercolumn changed. Dec 29 12:22:10 websrv dovecot-auth: passwdcolumn changed. Dec 29 12:22:10 websrv dovecot-auth: crypt changed. Dec 29 12:22:10 websrv dovecot-auth: sqllog changed. Dec 29 12:22:10 websrv dovecot-auth: db_connect called. Dec 29 12:22:10 websrv dovecot-auth: returning 0 . Dec 29 12:22:10 websrv dovecot-auth: db_checkpasswd called. Dec 29 12:22:10 websrv dovecot-auth: pam_mysql: where clause = Dec 29 12:22:10 websrv dovecot-auth: SELECT password FROM email_users WHERE log in='myname' Dec 29 12:22:10 websrv dovecot-auth: sqlLog called. Dec 29 12:22:10 websrv dovecot-auth: returning 0 . Dec 29 12:22:10 websrv dovecot-auth: returning 0. ## And then: Dec 29 12:22:10 websrv dovecot-auth: pam_mysql: setcred called but not implemen ted. Dec 29 12:22:10 websrv dovecot-auth: pam_mysql: acct_mgmt called but not implem ented. Dont panic though :) Dec 29 12:22:10 websrv pop3-login: Internal login failure: myname [xxx.xxx.xxx.xxx] As much as I was trying to find reading material on them I have not maneged to find something that will help me. If anybody can shed some light on how to fix my server...

1 0

[Dovecot] Deleting a message through IMAP
by Doug Eubanks 28 Dec '04

28 Dec '04

I have been having a problem with the test releases...I am now using Test 59. When I delete a message using SquirrelMail (IMAP) the message stays in the message list....but you can't open it anymore because it can't be found, if I logout and log back in...the message is gone from the list. I thought it could be a problem with the cache, so I added mail_never_cache_fields = MessagePart Envelope Body only to recieve Dec 24 09:23:34 news dovecot: IMAP(admin): mail_never_cache_fields: Invalid cache field name 'Body', ignoring Any ideas? This problem has plagued me for a while and I always go back to using the and older test like 22 and the problem isn't there... Doug

3 2

[Dovecot] Moving existing MD5 passwords to LDAP?
by Ben Beuchler 28 Dec '04

28 Dec '04

I have a dovecot installing working quite well for around 1000 users using passwd-file authentication. I'm moving to LDAP and would sure love to be able to migrate the existing MD5 passwords. I've tried using ldapmodify to set "userPassword" to {CRYPT}$1$H8JE0k5X$y.ptShgYbOgWF.99lX88N1 and {MD5}$1$H8JE0k5X$y.ptShgYbOgWF.99lX88N1 In both cases, ldapmodify exits without errors but I cannot bind using the new password. Any ideas? -Ben -- Ben Beuchler There is no spoon. insyte(a)emt-p.org -- The Matrix

2 1

[Dovecot] bidirectional synchronization of dovecot-managed maildirs
by James Leifer 28 Dec '04

28 Dec '04

Hello and happy holidays, I've been thinking about high performance bidirectional synchronizing the mail on my laptop (which is frequently disconnected) and my workstation at work (which is always on and receives all inbound mail). Both run dovecot on top of maildir. I've been playing with offlineimap, unison (which I already use for all my non-mail files), as well as the gnus agent (in IMAP "disconnected mode"). None of these solutions is really satisfactory: * offlineimap treats a message refile between folders as a delete-plus-resend; * unison doesn't understand the semantics of flag changes at the end of files in maildirs; it also has to stat all the files (which can become slow) to detect changes; * gnus agent can't refile messages between folders when in disconnected mode. Perhaps there are better disconnected IMAP modes available for other MUAs, but, it seems like a more general solution would be appropriate. In particular, the "uniq" field of a maildir filename is an easy way of tracking the identity of a message as it gets refiled. My question: would it be difficult to patch dovecot so that it maintained the *same* uniq when copying messages between folders? What about adding hooks that get triggered whenever dovecot copies or deletes messages? These hooks could log the changes. Later, when one tries to sync, one merges the changes from both replicas and then applies them. I'm aware that dovecot has an option to do copies as hardlinks, which is a good start, but still requires one to stat the files to discover which have the same inode. This is *much* slower than simply listing the directories and comparing maildir "uniq" fields. I'm aware that this invariant wouldn't be maintained if other programs modified the maildirs under dovecot's nose, but I'm willing to exclude this possibility. Suggestions? Best regards, -James Leifer

3 4

[Dovecot] dspam plugin
by Johannes Berg 27 Dec '04

27 Dec '04

The first version is available at http://johannes.sipsolutions.net/edit/Projects/dovecot-dspam-integration/co… I'm calling dspam for every message, that seemed easier for now. I will probably integrate Tom's idea about storing the messages until a cron-job picks them up at night by just storing signatures into mysql, in which case its easy to do with a single query: INSERT INTO new_spam (user, signature, isspam) VALUES (<user>, <signature>, <isspam>) ON DUPLICATE KEY UPDATE isspam = <isspam> with given values for <user>, <signature> and <isspam> and a key on (user, signature). For now, however, calling dspam for every message works good enough for me, and seems to work. Regards, Johannes

1 0

[Dovecot] Worthwile to use quotas?
by Peter Clark 24 Dec '04

24 Dec '04

I'm aware that dovecot doesn't support Maildir++ quotas yet (pity). However, is it still worthwhile to set up something like Postfix + Maildrop to use quotas, or is dovecot's lack of support just going to throw a wrench in the works? Thanks, :Peter

4 6

[Dovecot] Lots of SIG11 with test57
by Nicolas STRANSKY 24 Dec '04

24 Dec '04

Hi, Here is the backtrace. -- Nico Que de tout inconnu le sage se méfie. -+- Jean de La Fontaine (1621-1695), Le Renard, le Loup et le Cheval (Fables XII.17) -+- Here is the full backtrace : GNU gdb 6.1-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1". Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. warning: current_sos: Can't read pathname for load map: Erreur d'entrée/sortie Reading symbols from /lib/tls/libdl.so.2...done. Loaded symbols for /lib/tls/libdl.so.2 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 mail_index_sync_init_expunge_handlers (ctx=0xbffff8b0) at mail-index-sync-ext.c:36 36 mail-index-sync-ext.c: Aucun fichier ou répertoire de ce type. in mail-index-sync-ext.c (gdb) bt full #0 mail_index_sync_init_expunge_handlers (ctx=0xbffff8b0) at mail-index-sync-ext.c:36 handlers = (const mail_index_expunge_handler_t * const *) 0x80cae68 extensions = (const struct mail_index_ext *) 0x6738 id_map = (const uint32_t *) 0x1 eh = {handler = 0, context = 0x0, record_offset = 0} handlers_count = 1 id_map_size = 1860 size = 3082539416 idx_ext_id = 3082539384 map_ext_id = 0 #1 0x080831ec in sync_expunge (e=0xb7bbd178, ctx=0xbffff8b0) at mail-index-sync-update.c:113 view = (struct mail_index_view *) 0x80caac8 map = (struct mail_index_map *) 0x80cd5b0 count = 3082539384 seq = 3082539384 seq1 = 1862 seq2 = 1862 expunge_handlers = (struct mail_index_expunge_handler *) 0xb7bbd178 i = 0 expunge_handlers_count = 3082539376 #2 0x08083a90 in mail_index_sync_record (ctx=0xbffff8b0, hdr=0x80cd4f4, data=0xb7bbd178) at mail-index-sync-update.c:400 rec = (const struct mail_transaction_expunge *) 0xb7bbd178 end = (const struct mail_transaction_expunge *) 0xb7bbd198 ret = 0 #3 0x08083f47 in mail_index_sync_update_index (sync_ctx=0x0, sync_only_external=1) at mail-index-sync-update.c:628 index = (struct mail_index *) 0x80c6e68 view = (struct mail_index_view *) 0x80caac8 map = (struct mail_index_map *) 0xf148 sync_map_ctx = {view = 0x80caac8, cur_ext_id = 4294967295, expunge_handlers = 0x80d3da0, extra_context_buf = 0x0, extra_context = 0x0, type = MAIL_INDEX_SYNC_HANDLER_INDEX, sync_handlers_initialized = 0, expunge_handlers_set = 0, expunge_handlers_used = 0, cur_ext_ignore = 0} thdr = (const struct mail_transaction_header *) 0x80cd4f4 data = (const void *) 0xb7bbd178 old_lock_id = 61768 seq = 135033704 i = 0 first_append_uid = 0 offset = 4430000952 ret = 1 skipped = 0 check_ext_offsets = 0 #4 0x080824e8 in mail_index_sync_commit_external (ctx=0x80caa80, seq=0, offset=61864) at mail-index-sync.c:287 ret = 0 #5 0x080826af in mail_index_sync_begin (index=0x80c6e68, ctx_r=0x0, view_r=0x0, log_file_seq=0, log_file_offset=18446744073709551615, sync_recent=0, sync_dirty=0) at mail-index-sync.c:367 ctx = (struct mail_index_sync_ctx *) 0x80caa80 seq = 1 offset = 61864 lock_id = 8 seen_external = 135042384 #6 0x08062f1f in maildir_sync_index_begin (ibox=0x80c9550) at maildir-sync.c:579 sync_ctx = (struct maildir_index_sync_context *) 0x80caa30 #7 0x08063616 in maildir_sync_context (ctx=0x80b2240, forced=0) at maildir-sync.c:912 ret = 0 new_changed = 1 cur_changed = 1 #8 0x080637cb in maildir_storage_sync_init (box=0x80c9550, flags=0) at maildir-sync.c:975 ctx = (struct maildir_sync_context *) 0x80b2240 ret = 0 #9 0x0808b876 in mailbox_sync_init (box=0x0, flags=0) at mail-storage.c:329 No locals. #10 0x0805e97d in imap_sync_nonselected (box=0x0, flags=0) at imap-sync.c:153 ctx = (struct mailbox_sync_context *) 0x80c9550 sync_rec = {seq1 = 134986640, seq2 = 134987528, type = 7} status = {messages = 1102598494, recent = 513357221, unseen = 131740, uidvalidity = 0, uidnext = 134984600, first_unseen_seq = 134987528, diskspace_full = 0, keywords_count = 134987528, keywords = 0x7} #11 0x08057943 in get_mailbox_status (client=0x80bbc68, storage=0x0, mailbox=0x80c9550 "š\226\f\b\220»\v\b \203\a\b@\203\a\b", items=0, status=0x0) at cmd-status.c:68 box = (struct mailbox *) 0x80c9550 failed = 1 #12 0x08057a7b in cmd_status (client=0x80bbc68) at cmd-status.c:110 args = (struct imap_arg *) 0x80bbe58 status = {messages = 135003808, recent = 134895249, unseen = 434, uidvalidity = 22, uidnext = 134987168, first_unseen_seq = 134982184, diskspace_full = 0, keywords_count = 134582362, keywords = 0x80bfea0} items = 23 storage = (struct mail_storage *) 0x80bbb90 mailbox = 0x80bbf08 "Crans.All-bureau" str = (string_t *) 0x80bbb90 #13 0x08058b75 in client_handle_input (client=0x80bbc68) at client.c:324 No locals. #14 0x08058c48 in _client_input (context=0x80bbc68) at client.c:368 client = (struct client *) 0x80bbc68 #15 0x0809d2d8 in io_loop_handler_run (ioloop=0x80ba9e8) at ioloop-poll.c:184 data = (struct ioloop_handler_data *) 0x80baa10 pollfd = (struct pollfd *) 0x80baa28 tv = {tv_sec = 0, tv_usec = 801471} io = (struct io *) 0x80bbda0 t_id = 2 msecs = 0 ret = 0 call = 1 #16 0x0809c858 in io_loop_run (ioloop=0x80ba9e8) at ioloop.c:218 No locals. #17 0x080605f9 in main (argc=1, argv=0x0, envp=0x0) at main.c:224 No locals.

2 2

[Dovecot] Purging /var/mail/username ?
by Michael Hipp 23 Dec '04

23 Dec '04

Dovecot is delivering mail to my ~/.mail directory wonderfully. But /var/mail/michael is growing steadily. Is it the job of Dovecot to purge this file regularly? Is there a setting somewhere for this? Thanks, Michael

7 9

Re: [Dovecot] Purging /var/mail/username ?
by Jonas Smedegaard 23 Dec '04

23 Dec '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23-12-2004 18:48, Michael Hipp wrote: > From reading http://www.dovecot.org/doc/mail-storages.txt it appears > maildir stores everything in ~/Maildir. That's another good reason to > switch to it - so everything is in one place. There's good reasons to use Maildir, and there's good reasons to stay with mbox, but avoiding /var/mail is not one of them. mbox is the "classical" format, and Timo (I assume) chose to setup dovecot to use the "classical" location scheme as well, which is to store incoming mail below /var/mail and let users pull it from there and store it however they want at their personal folder below /home. If you are new to all this, actually there is probably a good point in staying close to the "classical" way of doing things, so that you can get help from more sources. I suggest keep receiving mail below /var/mail as mbox files, and play around with mbox and Maildir storage for different (test-)users below /home. Good luck, whatever you choose. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFByw6+n7DbMsAkQLgRAuj3AJ9QuWo3RD3NXCQV+tq0PH4+K4o4FgCeLTCE 2WASXMMup7CbMQwWn8+btjQ= =rF9V -----END PGP SIGNATURE-----

1 0

[Dovecot] error when popping mail over DSL
by Jeff Ramsey 23 Dec '04

23 Dec '04

Hi, I have a user who is getting a strange error when popping his mail over a DSL line. The error in my log file is as follows: file client.c: line 237 (client_send_line): assertion failed: ((size_t)ret == str_len(str)) I can POP his mail just find here locally connected to the server via 100bT, but over his DSL link, he gets this error. His mailbox size is 24MB, and he is using outlook w/ the option 'leave a copy of messages on the server'. He has Outlook 2003 and we use Dovecot 1.0 test 42. Is there a timeout limit on the pop3 server? -- Jeff Ramsey MIS Administrator Tubafor Mill, Inc.

2 1

[Dovecot] Need subfolders - convert to Maildir & how?
by Michael Hipp 22 Dec '04

22 Dec '04

I just installed Dovecot and it is working great. But I need subfolders. Does this mean I need to convert to Maildir format? I found several tools to do the conversion, but is there anything that needs to be changed in Dovecot to make the switch? Any advice appreciated. Thank you, Michael Hipp Heber Springs, AR, USA

4 6

[Dovecot] Mixing mbox and maildir
by Kenneth Porter 22 Dec '04

22 Dec '04

Is there some way to add a maildir folder to a mbox hierarchy? My folders are all mbox, but I want to migrate some client-side mail from a client (PMMail2000) that stores messages as individual files, and it might be easiest just to dump all the files into a maildir directory with suitable naming.

5 4

[Dovecot] moving messages with bash
by Todd Slater 22 Dec '04

22 Dec '04

I use bogofilter and a script or two to manage junk mail on my home box (fetchmail from POP3, postfix and procmail to local maildirs, mutt for MUA). Since these mails are just files I figured it never mattered that I moved them from one folder to another via a bash script, but some posts on this list make me think I shouldn't do that on a server running dovecot (IMAP). What I currently have is a MakeJunk folder (maildir) that I drop spam that was missed into, then a cron job runs mail in that folder through bogofilter and moves it to a Junk folder. Is it sane to do that with simple mv, or do I need to use some special imap command? Confused, Todd

1 0

[Dovecot] 0.99.13-rc2
by Timo Sirainen 21 Dec '04

21 Dec '04

http://dovecot.org/rc/ Another one. Unless there are some bugs this will be the final version in a few days. * GNUTLS support hasn't been working for a while, so it's not even tried to be used anymore unless explicitly wanted. + Added CRAM-MD5 authentication mechanism. Patch by Joshua Goodall + Added SMD5 password scheme support and changed MD5 scheme with LDAP to act as PLAIN-MD5 rather than as MD5crypt. Patch by Joshua Goodall + Workaround for some POP3 client bugs: if message doesn't contain the "end of headers" empty line, add it automatically. - SQL and LDAP authentication was broken - SEARCH UNKEYWORD wasn't working

2 1

[Dovecot] Stalled Authentication, Great Clues
by Richard Petty 21 Dec '04

21 Dec '04

I've just installed Dovecot 0.99.12.1 onto a White Box EL 3 server. I'm mostly following the email server setup instructions at http://www.wanderingbarque.com/mailserver.html and getting Dovecot to work is the last task to complete. I've compiled Dovecot with LDAP support. I'm authenticating Postfix via SASL to the LDAP database just fine, and I also authenticate and manipulate LDAP info from JAMM very well, too. However, Dovecot authentication seem to hang up when a correct password is submitted (POP or IMAP... it doesn't matter). Here's an example of the problem: [root@kayak /etc] telnet localhost 110 Trying 127.0.0.1... Connected to localhost.bramble.com (127.0.0.1). Escape character is '^]'. +OK dovecot ready. user repetty(a)bizzy.mine.nu +OK pass bogeybogey sadf hello? ^] telnet> q Connection closed. As you can see, once I hit the return key to submit the password I do not get another prompt. In fact, Dovecot doesn't respond at all although it seems to respond to the escape character just fine. Additionally, dovecot-auth starts soaking up CPU time... until I kill the process (dovecot-auth must be killed manually.) 22:15:32 up 32 days, 21:40, 5 users, load average: 1.05, 1.02, 0.98 121 processes: 119 sleeping, 2 running, 0 zombie, 0 stopped CPU states: cpu user nice system irq softirq iowait idle total 50.5% 0.0% 0.5% 0.0% 0.0% 0.0% 48.8% cpu00 66.7% 0.0% 0.0% 0.0% 0.0% 0.0% 33.2% cpu01 34.4% 0.0% 1.1% 0.0% 0.0% 0.0% 64.3% Mem: 318260k av, 300740k used, 17520k free, 0k shrd, 24380k buff 141540k actv, 28364k in_d, 3864k in_c Swap: 655352k av, 80868k used, 574484k free 94736k cached PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 23846 dovecot 25 0 1928 1928 1352 R 49.7 0.6 27:30 0 dovecot-auth 23847 dovecot 15 0 1072 1072 868 S 0.0 0.3 0:00 1 imap-login 23848 dovecot 15 0 1072 1072 868 S 0.0 0.3 0:00 1 imap-login 23849 dovecot 15 0 1160 1160 936 S 0.0 0.3 0:00 1 imap-login 23850 dovecot 15 0 1136 1136 928 S 0.0 0.3 0:00 0 pop3-login 23851 dovecot 15 0 1140 1140 928 S 0.0 0.3 0:00 1 pop3-login 23852 dovecot 15 0 1140 1140 928 S 0.0 0.3 0:00 0 pop3-login 23858 dovecot 15 0 1068 1068 868 S 0.0 0.3 0:00 0 imap-login 23870 dovecot 15 0 1064 1064 864 S 0.0 0.3 0:00 1 pop3-login 23886 dovecot 15 0 1060 1060 864 S 0.0 0.3 0:00 1 pop3-login 23916 dovecot 15 0 1064 1064 864 S 0.0 0.3 0:00 0 pop3-login From the client's point of view, the server never seems to come back after the account password is submitted. Dovecot's log shows that it eventually times out the client, although the client never seems to get wind of this: pop3-login: Dec 19 22:13:08 Info: Disconnected: Inactivity [192.168.0.6] I know that Dovecot is connecting to the LDAP server because if I mess up the Dovecot LDAP password in the dovecot.conf file I get an authentication error (as I should): dovecot-auth: Dec 19 20:52:19 Error: LDAP: ldap_simple_bind_s() failed (dn cn=dovecot,dc=dillo,dc=info): Invalid credentials Again, if client submits an incorrect email account password everything works as it should: Dovecot tells the client that the password is incorrect, over and over, if necessary. However, if the password is entered correctly then Dovecot hangs up for good. --Richard

2 2

[Dovecot] Postfix + dovecot-auth
by Timo Sirainen 20 Dec '04

20 Dec '04

I wrote a patch to Postfix which now supports SMTP AUTH using dovecot-auth. This time it doesn't need any Dovecot libraries and it's backwards compatible with Cyrus SASL by default. You'll just need to set one variable in Postfix config file to enable it. Patches and instructions in: http://dovecot.org/patches/postfix/ Not very well tested yet though. And it doesn't work with 1.0-test59, you'll need to have at least today's nightly snapshot.

1 0

[Dovecot] 1.0-test59 on OpenBSD: Undefined symbol `_strtoull' referenced
by Wouter Van Hemel 20 Dec '04

20 Dec '04

Hello, dovecot-1.0-test59 compilation fails on an old OpenBSD version with: var-expand.c:19: Undefined symbol `_strtoull' referenced from text segment collect2: ld returned 1 exit status *** Error code 1 Stop in /root/dovecot-1.0-test59/src/auth (line 392 of Makefile). [...] OpenBSD should have strtoull starting from about version 3.2.

3 4

[Dovecot] Just delete that index
by Doug Luce 20 Dec '04

20 Dec '04

I get a few messages of this ilk each day: Dec 16 01:56:31 aurora dovecot: IMAP(doug): Corrupted index cache file /home/doug/Maildir/.users.joe/dovecot.index.cache: indexid changed I usually address this by deleting dovecot.* in the directory of issue. I was thinking that I could instead just have the server delete these files and attempt to recreate them, and skipping that error message unless the re-created files are also corrupted. Any problems with this approach? Thanks, Doug

2 2

[Dovecot] panic with search
by Kazuo Moriwaka 20 Dec '04

20 Dec '04

Hello, My imap daemon get SIGABRT with following message. "pool_data_stack_realloc(): stack frame changed" This is caused with cvs head sources.(and or not with my last 2 patches.) This causes while doing search command. This is IMAP command log: --------------------------------------------------------------------------- * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as mailtest * select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 135 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1102574212] UIDs valid * OK [UIDNEXT 139] Predicted next UID * OK [READ-WRITE] Select completed. * search body "hoge" imap(mailtest): Panic: pool_data_stack_realloc(): stack frame changed Aborted --------------------------------------------------------------------------- I'll attach backtrace just before print panic messages. If maildir and messages are need for debug, please request to me. thanks, -- Kazuo Moriwaka moriwaka(a)valinux.co.jp (gdb) bt #0 printf_string_upper_bound (format_p=0xbffff848, args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at printf-upper-bound.c:78 #1 0x080a7640 in default_handler (prefix=0x80c226a "Panic: ", f=0x41149fe0, format=0x80c3300 "pool_data_stack_realloc(): stack frame changed", args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at failures.c:99 #2 0x080a76b8 in default_panic_handler (format=0x80c3300 "pool_data_stack_realloc(): stack frame changed", args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at failures.c:115 #3 0x080a786a in i_panic (format=0x80c3300 "pool_data_stack_realloc(): stack frame changed") at failures.c:173 #4 0x080afd33 in pool_data_stack_realloc (pool=0x80c7788, mem=0x80c77d0, old_size=256, new_size=8192) at mempool-datastack.c:110 #5 0x080a650f in buffer_alloc (buf=0x80c77b0, size=8192) at buffer.c:32 #6 0x080a6c74 in buffer_check_limits (buf=0x80c77b0, pos=1, data_size=4096) at buffer.c:57 #7 0x080a6a49 in buffer_copy (_dest=0x80c77b0, dest_pos=1, _src=0x80c7950, src_pos=0, copy_size=4096) at buffer.c:227 #8 0x080a6acd in buffer_append_buf (dest=0x80c77b0, src=0x80c7950, src_pos=0, copy_size=4096) at buffer.c:240 #9 0x080a0a71 in message_search_body_block (ctx=0xbffffa00, block=0x80c7950) at message-body-search.c:229 #10 0x080a0e4e in message_search_body (ctx=0xbffffa00, input=0x80de170, part=0x80dede0) at message-body-search.c:336 #11 0x080a1135 in message_body_search_ctx (ctx=0xbffffa60, input=0x80ddf08, part=0x80dede0) at message-body-search.c:408 #12 0x080a11ff in message_body_search (key=0x80d4f60 "hoge", charset=0x0, unknown_charset=0xbffffabc, input=0x80ddf08, part=0x80dede0, search_header=0) at message-body-search.c:433 #13 0x0807f58a in search_body (arg=0x80d4f38, context=0xbffffb40) at index-search.c:467 #14 0x08098278 in search_arg_foreach (arg=0x80d4f38, callback=0x807f4f0 <search_body>, context=0xbffffb40) at mail-search.c:81 #15 0x080982a8 in mail_search_args_foreach (args=0x80d4f38, callback=0x807f4f0 <search_body>, context=0xbffffb40) at mail-search.c:93 #16 0x0807f82b in search_arg_match_text (args=0x80d4f38, ctx=0x80dec88) at index-search.c:545 #17 0x08080011 in search_match_next (ctx=0x80dec88) at index-search.c:813 #18 0x080800bf in index_storage_search_next (_ctx=0x80dec88) at index-search.c:837 #19 0x08098e38 in mailbox_search_next (ctx=0x80dec88) at mail-storage.c:397 #20 0x0805787c in imap_search (client=0x80d0cf8, charset=0x0, sargs=0x80d4f38) at cmd-search.c:32 #21 0x08057baf in cmd_search (client=0x80d0cf8) at cmd-search.c:97 #22 0x08059c2e in client_handle_input (client=0x80d0cf8) at client.c:324 #23 0x08059d2e in _client_input (context=0x80d0cf8) at client.c:368 #24 0x080ae2f8 in io_loop_handler_run (ioloop=0x80cfa58) at ioloop-poll.c:184 #25 0x080ad4c1 in io_loop_run (ioloop=0x80cfa58) at ioloop.c:218 #26 0x080637d0 in main (argc=1, argv=0xbffffdd4, envp=0xbffffddc) at main.c:224 (gdb) up #1 0x080a7640 in default_handler (prefix=0x80c226a "Panic: ", f=0x41149fe0, format=0x80c3300 "pool_data_stack_realloc(): stack frame changed", args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at failures.c:99 99 (void)printf_string_upper_bound(&format, args); (gdb) up #2 0x080a76b8 in default_panic_handler (format=0x80c3300 "pool_data_stack_realloc(): stack frame changed", args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at failures.c:115 115 (void)default_handler("Panic: ", log_fd, format, args); (gdb) up #3 0x080a786a in i_panic (format=0x80c3300 "pool_data_stack_realloc(): stack frame changed") at failures.c:173 173 panic_handler(format, args); (gdb) up #4 0x080afd33 in pool_data_stack_realloc (pool=0x80c7788, mem=0x80c77d0, old_size=256, new_size=8192) at mempool-datastack.c:110 110 i_panic("pool_data_stack_realloc(): stack frame changed"); (gdb) list 105 /* @UNSAFE */ 106 if (new_size == 0 || new_size > SSIZE_T_MAX) 107 i_panic("Trying to allocate %"PRIuSIZE_T" bytes", new_size); 108 109 if (dpool->data_stack_frame != data_stack_frame) 110 i_panic("pool_data_stack_realloc(): stack frame changed"); 111 112 if (mem == NULL) 113 return pool_data_stack_malloc(pool, new_size); 114 (gdb) p dpool $18 = (struct datastack_pool *) 0x80c7788 (gdb) p *dpool $19 = {pool = {get_name = 0x80afbd5 <pool_data_stack_get_name>, ref = 0x80afbdf <pool_data_stack_ref>, unref = 0x80afc0d <pool_data_stack_unref>, malloc = 0x80afc70 <pool_data_stack_malloc>, free = 0x80afcc4 <pool_data_stack_free>, realloc = 0x80afcec <pool_data_stack_realloc>, clear = 0x80afdd0 <pool_data_stack_clear>, alloconly_pool = 1, datastack_pool = 1}, refcount = 1, data_stack_frame = 5} (gdb) p *dpool->data_stack_frame Cannot access memory at address 0x5 (gdb) p dpool->data_stack_frame $20 = 5 (gdb) p data_stack_frame $21 = 7

2 1

[Dovecot] Error indexing mbox file /var/mail/seb: LF not found where expected
by Sebastian 20 Dec '04

20 Dec '04

Howdy all, Dec 19 14:24:53 dev imap(seb): Error indexing mbox file /var/mail/seb: LF not found where expected I just installed version dovecot-0.99.12.1 for the first time on FreeBSD 4.10 stable. This error occurs when I try to check my mail from a remote client and I have new messages. Here is my configuration: http://unf.be/dovecot.conf It's very close to the default install. In attempts to remedy the problem, I set "mail_read_mmaped = no", but the problem persists. I'm not sure if it's relevent, but I'm receiving mail with postfix and my mail file has lines that end with \r\n Thanks in advance for any help Sebastian -- ------------- buddhahead(a)gmail.com

1 1

[Dovecot] Auth Mechanism
by Tom Allison 19 Dec '04

19 Dec '04

Uh... I'm trying to debug an application and keep running into this: DEBUG: Sending: 1 AUTHENTICATE CRAM-MD5 DEBUG: Sent 25 bytes DEBUG: Read: 1 NO Authentication failed: Unsupported authentication mechanism DEBUG: Read: * BYE Disconnected for inactivity. So is this really asking for "digest-md5" or am I S.O.L? IIRC these are different protocols, but it's a bit early for my head to get this together.

2 2

[Dovecot] Authentication problems
by Rory Campbell-Lange 19 Dec '04

19 Dec '04

Hi. I aim to provide pop3 and imap services to a few users. At the moment I only offer imap for squirrelmail users. However, I can't login successfully for pop3. It appears to be trying to auth against PAM, rather than directly using the passwd-file. Thoughts? Thanks, Rory Config: uthenticatprotocols = pop3 imap ssl_disable = yes login = imap login = pop3 mail_extra_groups = mail auth = default auth_mechanisms = plain auth_userdb = passwd-file /etc/dovecot.passwd.conf auth_user = root auth_verbose = yes Password file: # squirrelmail imap users user1:xe9l8sIMpcTsg:1008:1008::::chroot:Maildir:/home/cmp/Maildir/user1 user2:m7VKCgWVmZYMY:1008:1008::::chroot:Maildir:/home/cmp/Maildir/user2 user3:ELh9mthLVjEG2:1008:1008::::chroot:Maildir:/home/cmp/Maildir/user3 # normal users xyz1:QtR.iN1DbL/UM:1004:1004::::chroot:mbox:/var/mail/xyz1 xyz2:y38.qLIgrvYic:1002:1002::::~/Mail:mbox:/var/mail/xyz2:INDEX=/home/xyz2 ... Problem shown in log: Dec 19 16:45:30 localhost dovecot-auth: PAM: pam_authenticate(xyz2) failed: User not known to the underlying authentication module Dec 19 16:45:30 localhost pop3-login: Aborted login [ipaddress] -- Rory Campbell-Lange <rory(a)campbell-lange.net> <www.campbell-lange.net>

2 1

[Dovecot] 1.0-test59
by Timo Sirainen 19 Dec '04

19 Dec '04

http://dovecot.org/test/ No-one had been testing 1.0-tests with Evolution? It was pretty much completely broken with messages having attachments. - test58's output stream code change were entirely wrong and caused bad breakages with mbox. - Named pipes are now treated as write-only mboxes (blocks if no-one is reading, perhaps it should timeout in a few seconds?) - FETCH BODY[n.xxx] replies were all wrong - LDAP authentication was crashing - pop3_uidl_format=%f from Andrey test60 will probably have keyword support. Its index file code is already working, with ability to set over 500k different keywords per mailbox (because message record size is limited to 65535 bytes - should be enough for everyone :). Code is still missing to notify other session about keyword changes, and storing the keywords into mbox/maildir. For mbox I can use X-Keywords header. There should probably be some configurable limit to how many keywords to set per mailbox.. Dovecot shouldn't mind if the X-Keywords header is huge, but other programs might. For maildir then.. I think I'll just implement it backwards compatible with 0.99.x, ie. store in maildir filename with a-z letters. That would make max. 26 keywords per mailbox. Except maybe I shouldn't limit it to that. The rest could be stored only in indexes. That however would make it necessary to keep indexes backwards compatible forever so data is not lost.

3 2

[Dovecot] 0.99.13-rc1
by Timo Sirainen 19 Dec '04

19 Dec '04

http://dovecot.org/rc/ I guess the RCing in 0.99.12 didn't help that much. SQL/LDAP authentication crashed because memory was freed wrong. Please test so it would actually work in 0.99.13. Also fixed SEARCH UNKEYWORD which wasn't working. Also added 1.0-test's oe-ns-eoh POP3 workaround built-in.

2 1

[Dovecot] Cygwin and index code
by Johannes Berg 19 Dec '04

19 Dec '04

As I can currently only work with windows (eek) I thought I'd try dovecot there. I already sent a patch to make dovecot compile under cygwin, but it still doesn't really work, here's part of a session that I started while my maildir was totally empty (only cur/new/tmp in ~/Maildir) $ ./imap.exe * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as jmberg A01 SELECT INBOX imap(jmberg): Warning: Compressing cache file /home/jmberg/Maildir/dovecot.index.cache imap(jmberg): Error: open() failed with file /home/jmberg/Maildir/dovecot.index.tmp: Permission denied A01 NO Internal error occured. Refer to server log for more information. [2004-12-17 15:51:06] A02 LOGOUT * BYE Logging out A02 OK Logout completed. A second session (some files were created by the first) yields this: $ ./imap.exe * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as jmberg A01 SELECT INBOX imap(jmberg): Error: open() failed with file /home/jmberg/Maildir/dovecot.index.tmp: Permission denied imap(jmberg): Error: rename(/home/jmberg/Maildir/dovecot.index.tmp, /home/jmberg/Maildir/dovecot.index) failed: Permission denied A01 NO Internal error occured. Refer to server log for more information. [2004-12-17 15:52:25] A02 LOGOUT * BYE Logging out A02 OK Logout completed. I think this is probably due to the indexing code opening the .tmp file and then unlinking it and trying to re-create it while the first is still open. Or something, I really am not sure. *Maybe* the index code might be made work if it creates a new temporary file-name every time it re-creates the file, but I don't understand the code well enough (yet) to give a better analysis of the problem. However, I do not think that this is really important. I certainly don't want to run dovecot on windows (I only saw cygwin compile in the todo and since I have a cygwin setup anyway I thought I'd try). The whole thing doesn't work anyway: [after correcting users, making directories, make install...] $ /usr/local/sbin/dovecot.exe dovecot: Dec 17 16:03:17 Info: Dovecot v1.0-test58 starting up dovecot: Dec 17 16:03:18 Error: login: fd_read() failed: Function not implemented dovecot: Dec 17 16:03:18 Error: close(mail client) failed: Bad file descriptor dovecot: Dec 17 16:03:18 Error: Login process died too early - shutting down dovecot: Dec 17 16:03:18 Error: imap-login: dovecot: Dec 17 16:03:18 Fatal: setrlimit(RLIMIT_DATA, 32): Invalid argument dovecot: Dec 17 16:03:18 Error: login: fd_read() failed: Function not implemented dovecot: Dec 17 16:03:18 Error: close(mail client) failed: Bad file descriptor dovecot: Dec 17 16:03:18 Error: imap-login: dovecot: Dec 17 16:03:18 Fatal: setrlimit(RLIMIT_DATA, 32): Invalid argument dovecot: Dec 17 16:03:18 Error: login: fd_read() failed: Function not implemented dovecot: Dec 17 16:03:18 Error: close(mail client) failed: Bad file descriptor dovecot: Dec 17 16:03:18 Error: imap-login: dovecot: Dec 17 16:03:18 Fatal: setrlimit(RLIMIT_DATA, 32): Invalid argument dovecot: Dec 17 16:03:18 Error: auth(default): dovecot: Dec 17 16:03:18 Fatal: setrlimit(RLIMIT_DATA, 256): Invalid argument dovecot: Dec 17 16:03:18 Error: child 2176 (auth) returned error 89 dovecot: Dec 17 16:03:18 Error: child 2192 (login) returned error 89 dovecot: Dec 17 16:03:18 Error: child 2212 (login) returned error 89 dovecot: Dec 17 16:03:18 Error: child 2232 (login) returned error 89 Maybe someone cares. If not, well, I had a less boring train ride ;) johannes

2 1

[Dovecot] building on cygwin
by Johannes Berg 19 Dec '04

19 Dec '04

Hi, attached patch makes dovecot build on cygwin (only have a windows computer at the moment :-/ ) It spews a lot of warnings, for example "unsigned int format but uint32_t argument". johannes Only in dovecot-1.0-test58.mod/: Makefile Only in dovecot-1.0-test58.mod/: config.h Only in dovecot-1.0-test58.mod/: config.log Only in dovecot-1.0-test58.mod/: config.status Only in dovecot-1.0-test58.mod/doc: Makefile Only in dovecot-1.0-test58.mod/: libtool Only in dovecot-1.0-test58.mod/src: Makefile Only in dovecot-1.0-test58.mod/src/auth: .deps Only in dovecot-1.0-test58.mod/src/auth: Makefile Only in dovecot-1.0-test58.mod/src/imap: .deps Only in dovecot-1.0-test58.mod/src/imap: Makefile Only in dovecot-1.0-test58.mod/src/imap-login: .deps Only in dovecot-1.0-test58.mod/src/imap-login: Makefile Only in dovecot-1.0-test58.mod/src/lib: .deps Only in dovecot-1.0-test58.mod/src/lib: Makefile Only in dovecot-1.0-test58.mod/src/lib-auth: .deps Only in dovecot-1.0-test58.mod/src/lib-auth: Makefile Only in dovecot-1.0-test58.mod/src/lib-charset: .deps Only in dovecot-1.0-test58.mod/src/lib-charset: Makefile Only in dovecot-1.0-test58.mod/src/lib-imap: .deps Only in dovecot-1.0-test58.mod/src/lib-imap: Makefile Only in dovecot-1.0-test58.mod/src/lib-index: .deps Only in dovecot-1.0-test58.mod/src/lib-index: Makefile diff -ur --strip-trailing-cr dovecot-1.0-test58/src/lib-index/mail-cache-decisions.c dovecot-1.0-test58.mod/src/lib-index/mail-cache-decisions.c --- dovecot-1.0-test58/src/lib-index/mail-cache-decisions.c 2004-11-24 19:40:17.000000000 +0100 +++ dovecot-1.0-test58.mod/src/lib-index/mail-cache-decisions.c 2004-12-16 15:31:24.659497600 +0100 @@ -71,7 +71,7 @@ #include "mail-cache-private.h" void mail_cache_decision_lookup(struct mail_cache_view *view, uint32_t seq, - unsigned int field) + uint32_t field) { struct mail_cache *cache = view->cache; const struct mail_index_header *hdr; @@ -115,7 +115,7 @@ } void mail_cache_decision_add(struct mail_cache_view *view, uint32_t seq, - unsigned int field) + uint32_t field) { struct mail_cache *cache = view->cache; uint32_t uid; Only in dovecot-1.0-test58.mod/src/lib-mail: .deps Only in dovecot-1.0-test58.mod/src/lib-mail: Makefile Only in dovecot-1.0-test58.mod/src/lib-ntlm: .deps Only in dovecot-1.0-test58.mod/src/lib-ntlm: Makefile Only in dovecot-1.0-test58.mod/src/lib-settings: .deps Only in dovecot-1.0-test58.mod/src/lib-settings: Makefile Only in dovecot-1.0-test58.mod/src/lib-sql: .deps Only in dovecot-1.0-test58.mod/src/lib-sql: Makefile Only in dovecot-1.0-test58.mod/src/lib-storage: .deps Only in dovecot-1.0-test58.mod/src/lib-storage: Makefile Only in dovecot-1.0-test58.mod/src/lib-storage/index: .deps Only in dovecot-1.0-test58.mod/src/lib-storage/index: Makefile Only in dovecot-1.0-test58.mod/src/lib-storage/index/maildir: .deps Only in dovecot-1.0-test58.mod/src/lib-storage/index/maildir: Makefile Only in dovecot-1.0-test58.mod/src/lib-storage/index/mbox: .deps Only in dovecot-1.0-test58.mod/src/lib-storage/index/mbox: Makefile Only in dovecot-1.0-test58.mod/src/lib-storage/register: .deps Only in dovecot-1.0-test58.mod/src/lib-storage/register: Makefile Only in dovecot-1.0-test58.mod/src/lib-storage/register: mail-storage-register.c Only in dovecot-1.0-test58.mod/src/lib-storage/subscription-file: .deps Only in dovecot-1.0-test58.mod/src/lib-storage/subscription-file: Makefile Only in dovecot-1.0-test58.mod/src/login-common: .deps Only in dovecot-1.0-test58.mod/src/login-common: Makefile Only in dovecot-1.0-test58.mod/src/master: .deps Only in dovecot-1.0-test58.mod/src/master: Makefile Only in dovecot-1.0-test58.mod/src/pop3: .deps Only in dovecot-1.0-test58.mod/src/pop3: Makefile Only in dovecot-1.0-test58.mod/src/pop3-login: .deps Only in dovecot-1.0-test58.mod/src/pop3-login: Makefile Only in dovecot-1.0-test58.mod/src/util: .deps Only in dovecot-1.0-test58.mod/src/util: Makefile diff -ur --strip-trailing-cr dovecot-1.0-test58/src/util/dovecotpw.c dovecot-1.0-test58.mod/src/util/dovecotpw.c --- dovecot-1.0-test58/src/util/dovecotpw.c 2004-07-30 05:16:23.000000000 +0200 +++ dovecot-1.0-test58.mod/src/util/dovecotpw.c 2004-12-16 15:34:03.818356800 +0100 @@ -7,7 +7,6 @@ #include <ctype.h> #include <fcntl.h> -#include <libgen.h> #include <stdio.h> #include <stdlib.h> #include <unistd.h> Only in dovecot-1.0-test58.mod/: stamp-h1 Only in dovecot-1.0-test58.mod/: stamp.h

2 2

[Dovecot] spam plugin
by Johannes Berg 19 Dec '04

19 Dec '04

Here's a new version, it compiles (and appears to work) except the part in "copy_reclassified". Can anyone help me (probably only Timo knows how) with that? http://johannes.sipsolutions.net/edit/Projects/dovecot-dspam-integration/ps… johannes

2 1

[Dovecot] 1.0-test58
by Timo Sirainen 19 Dec '04

19 Dec '04

http://dovecot.org/test/ - Fixed APPEND hanging in some situations. Didn't happen with mail_save_crlf=yes. - Added pop3_uidl_format setting. No need to patch sources anymore if you don't want the default. Does anyone want pop3_uidl_xuidl_header yes/no setting, with fallbacking to pop3_uidl_format if X-UIDL header isn't found? Shouldn't be difficult to do.. - Added mbox_very_dirty_syncs setting which tries to avoid re-reading mbox as long as possible. - CREATE dir/ wasn't working - If login_process_per_connection=no and auth process count > 1, each auth process listens in different socket. Login processes then connect to all these sockets and send requests to them in round robin. - Multiple auth sections in config file work now a bit better. dovecot-auth might still complain about timeouts though.

6 9

[Dovecot] permissions and location of .subscriptions
by Tom 19 Dec '04

19 Dec '04

What is the correct set of permissions for the file .subscriptions and what is the correct directory location? Thanks, Tom

2 1

[Dovecot] deploying dspam
by Johannes Berg 17 Dec '04

17 Dec '04

Hi everyone, I've been thinking of phasing out my spamassassin installation (it's hardly doing me any good these days) in favour of dspam. Now since I'm working on this anyway, I thought I'd configure it so when users get any spam, it is delivered into a special folder. I figure I need the 1.0 test series for this, so I can make that folder fixed. But, I also want to allow them to move spam in and out of that folder and dspam can learn it. Anyway, I found a message dating back a while where Timo says this could easily be implemented in a plugin (in the 1.0 test series), but I can't put my finger on how to do it. Does anyone have an example plugin that can run commands when mail is moved in or out of a special folder? Or is there any plugin-writing documentation? Thanks, johannes

17 39

Re: [Dovecot] deploying dspam
by Gunter Ohrner 16 Dec '04

16 Dec '04

Am Donnerstag, 16. Dezember 2004 11:46 schrieben Sie: > > script. Even there you can optimize a lot by changing some of the > > queries to allow indizes to take effect. > Have you done that, Yes. > and if so would you share? Yes, of course. I already submitted it to the dspam author but did not get any reaction so I don't know if he considered to include it. In dspam 3.0 the rule to clean up dspam_token_data was terribly stressing my system, changing it to the equivalent (I hope ;) - delete from dspam_token_data where ((innocent_hits=0 and spam_hits < 5) - or (innocent_hits=1 and spam_hits < 3) or (innocent_hits=2 and - spam_hits = 0)) and @a-to_days(last_hit) > 30; reduced the queries run time by a factor of 10 to 50 easily. I simply "flattened" the atrithmetic expression within the "where" clause to allow the indices to support this query. > But this is getting too much OT, maybe we should move over to the dspam > mailing list :) I'm not subscribed there - maybe now everything is said and everyone will excuse this OT mail? ;) Greetings, Gunter -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + http://aachen.uni-dsl.de/ - Der direkte Draht in's Hochschulnetz! + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 362) BSI: Eine Art Ghostbuster-Truppe für Sicherheitsfragen (Spiegel Online) -- http://www.iks-jena.de/mitarb/lutz/usenet/Fachbegriffe.der.Informatik.htm l#362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + PGP-verschlüsselte Mails bevorzugt! + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

1 0

Re: [Dovecot] deploying dspam
by Johannes Berg 16 Dec '04

16 Dec '04

Tom Allison wrote: > Shared Folder? > Wouldn't you have to do something like this anyways? Something like this in a very broad sense: I have exactly _one_ special folder, supposed to always contain only spam. > If you don't like the folders idea, then tagged the SUBJECT lines and > deliver everything as per usual. I don't do this, I opt for the > multiple folders.. Oh, I like the folders idea! I just don't like having to put the maintenance burden on me as a user. Why shouldn't the system do all this /behind the scenes/ with a little special help from the IMAP server? > It's one option. Just to provide some ideas on how it can work. But then, what's wrong with my other suggestion about making that scale by implementing your NewXY folders behind the scenes? johannes

1 0

[Dovecot] IMAP Subdirectories
by Rory Campbell-Lange 16 Dec '04

16 Dec '04

Hi Using Apple Mail I cannot make subdirectories within new directories I have made on a Debian Dovecot-driven IMAP server (version 0.99.11-3). Some users, having used Exchange, expect to be able to do this. However I can't make it happen, even after doing some tests by chmod-ing the top-level directories to 777 and enabling the mail_full_filesystem_access = yes option on a test install. Views, comments and remarks much appreciated! Rory -- Rory Campbell-Lange <rory(a)campbell-lange.net> <www.campbell-lange.net>

3 5

[Dovecot] 1.0-test57
by Timo Sirainen 16 Dec '04

16 Dec '04

http://dovecot.org/test/ Two important fixes: - Fixes the recently reported dovecot-auth crashes with unexpected client input - Fixes mbox corruption in some not-so-common cases. Hopefully this is the last one. I added more asserts anyway which try to catch similiar mistakes and avoid losing data. Others: - Added oe-ns-eoh workaround for pop3. Fixes outlook/netscape problems with buggy mails. - lock_method = dotlock works now properly - Cache file compression crashed in some situations - auth_cache fixes from Andrey Also I have about 80% of the code written for keywords support. It's about the last major missing feature from v1.0, so naming should change into 1.0-alphas soon. From there on it should be mostly about stabilization, cleaning up the code and maybe some optimization.

5 8

[Dovecot] Dovecot SQL auth problem? (1.0-test52-56)
by Andrew Hutchings 16 Dec '04

16 Dec '04

Hi there, We are living dangerously and using the test versions on our production servers which are migrated from 3 different older servers (about 5000 accounts) therefore we have 3 different MySQL auths. All seems to be ok, but a guy in the office is using Thunderbird as pop3 access. The auth is saying: auth(sql): plain(?,xx.xxx.xx.xxx): invalid input I have hidden his IP for security reasons. The login should be user(a)domain.co.uk and his account works fine with outlook. With test 52 this killed the auth child with signal 6 and 11. Anyone have any ideas? Unrelated to this (I hope) we are also getting quite a few child xxxx (pop3) killed with signal 11 several times a minute. -- Andrew Hutchings Systems Operator / Developer / Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

2 1

[Dovecot] KMail + dovecot
by Timothy Murphy 16 Dec '04

16 Dec '04

Is anyone running docecot on a home LAN. to give an IMAP feed to other machines on the LAN? I am running dovecot on my desktop, alfred. I want to collect email on my laptop, william, using KMail. As far as I can tell, dovecot is running perfectly. I can bring email from /var/spool/mail/tim on alfred to the same directory on william by running "fetchmail alfred" on william. I can then read it with KMail on william, so there is not real problem. However, KMail does not seem to be able to collect email directly from alfred, even though I have added an entry in KMail=>Settings=>Configure KMail=>Network=>Receiving giving type imap, Name (dovecot), Login, Password, Host (alfred), Port (143). and Prefix to Folders "/var/spool/mail". I don't see any error message anywhere, but when I click on File=>Check mail in dovecot it says "Checking account dovecot for new mail". but nothing appears to happen. Any suggestions or advice gratefully received. -- Timothy Murphy e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

3 2

[Dovecot] Dovecot and PHP
by Don 15 Dec '04

15 Dec '04

Has anyone successfully compiled PHP 5 with the -imap option using Dovecot server? I get the error: "Cannot find rfc822.h. Please check your IMAP installation". It seems that Dovecot has no development libraries so I am stuck? Will I have to scrap Dovecot and use another server like Cyrus? Thanks, Don --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.813 / Virus Database: 553 - Release Date: 12/13/2004

4 3

[Dovecot] dovecot/openldap auth problems?
by Lee 15 Dec '04

15 Dec '04

Hi folks. New to both dovecot and openldap. Trying to set up virtual domains using the wanderingbarque howto: http://www.wanderingbarque.com/mailserver.html Platform is RH enterprise 3. Only difference is I'm trying to use phamm instead of jamm: http://phamm.rhx.it/ dovecot doesn't seem to want to play nice with my openldap; everything else (postfix, etc) seems to work alright. So I'm looking for some hints as to what I'm doing wrong. thanks in advance! When I do an /sbin/service dovecot restart, here's the error from /var/log/ldap.log: <snip> Dec 11 13:59:22 salcha slapd[15734]: => access_allowed: auth access to "cn=dovecot,dc=akforecast" "u serPassword" requested Dec 11 13:59:22 salcha slapd[15734]: => dnpat: [1] .*,jvd=([^,]+),o=hosting,dc=akforecast nsub: 1 Dec 11 13:59:22 salcha slapd[15734]: => dnpat: [2] .*,jvd=([^,]+),o=hosting,dc=akforecast nsub: 1 Dec 11 13:59:22 salcha slapd[15734]: => dnpat: [3] .*,jvd=([^,]+),o=hosting,dc=akforecast nsub: 1 Dec 11 13:59:22 salcha slapd[15734]: => dnpat: [4] o=hosting,dc=akforecast nsub: 0 Dec 11 13:59:22 salcha slapd[15734]: => acl_get: [5] check attr userPassword Dec 11 13:59:22 salcha slapd[15734]: <= acl_get: [5] acl cn=dovecot,dc=akforecast attr: userPassword Dec 11 13:59:22 salcha slapd[15734]: => acl_mask: access to entry "cn=dovecot,dc=akforecast", attr " userPassword" requested Dec 11 13:59:22 salcha slapd[15734]: => acl_mask: to all values by "", (=n) Dec 11 13:59:22 salcha slapd[15734]: <= check a_dn_pat: * Dec 11 13:59:22 salcha slapd[15734]: <= acl_mask: [1] applying none (=n) (stop) Dec 11 13:59:22 salcha slapd[15734]: <= acl_mask: [1] mask: none (=n) Dec 11 13:59:22 salcha slapd[15734]: => access_allowed: auth access denied by none (=n) Anyone see any big,glaring 'yewidiut' errors? Or just hints as to what could be wrong? slapd.conf: # $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.8.8.7 2001/09/27 20:00:31 kurt Exp $ # # See slapd.conf(5) for details on configuration options. # This file should NOT be world readable. # include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/redhat/autofs.schema include /etc/openldap/schema/redhat/kerberosobject.schema # include /etc/openldap/schema/jamm.schema include /etc/openldap/schema/phamm.schema include /etc/openldap/schema/ISPEnv2.schema include /etc/openldap/schema/amavisd-new.schema password-hash {CRYPT} # Define global ACLs to disable default read access. # Do not enable referrals until AFTER you have a working directory # service AND an understanding of referrals. #referral ldap://root.openldap.org # Create a replication log in /var/lib/ldap for use by slurpd. #replogfile /var/lib/ldap/master-slapd.replog schemacheck on pidfile /var/run/openldap/slapd.pid argsfile /var/run/openldap/slapd.args loglevel 128 lastmod on database ldbm directory /var/lib/ldap suffix "dc=akforecast" rootdn "cn=manager,dc=akforecast" rootpw x index objectClass eq index cn,mail eq,subinitial # include /etc/openldap/slapd-phamm.acl access to dn=".*,jvd=([^,]+),o=hosting,dc=akforecast" attr=userPassword by self write by group/jammPostmaster/roleOccupant="cn=postmaster,jvd=$1,o=hosting,dc=akforecast" write by dn="cn=dovecot,dc=akforecast" read by anonymous auth by * none access to dn=".*,jvd=([^,]+),o=hosting,dc=akforecast" attr=quota by group/jammPostmaster/roleOccupant="cn=postmaster,jvd=$1,o=hosting,dc=akforecast" write by dn="cn=phamm,o=hosting,dc=akforecast" read by self read by * none access to dn=".*,jvd=([^,]+),o=hosting,dc=akforecast" by self write by group/jammPostmaster/roleOccupant="cn=postmaster,jvd=$1,o=hosting,dc=akforecast" write by dn="cn=phamm,o=hosting,dc=akforecast" read by * none access to dn="o=hosting,dc=akforecast" by self write by dn="cn=phamm,o=hosting,dc=akforecast" read by anonymous auth by * none access to * by * none ----------------------------------------------------------- /etc/dovecot/dovecot-ldap.conf: [root@salcha openldap]# cat /etc/dovecot/dovecot-ldap.conf # NOTE: We don't support "authentication binds", so you'll have to give # dovecot-auth read access to userPassword field in LDAP server. With OpenLDAP # this is done by modifying /etc/ldap/slapd.conf. There should already be # something like this: # access to attribute=userPassword # by dn="<dovecot's dn>" read # add this # by anonymous auth # by self write # by * none # Space separated list of LDAP hosts to use. host:port is allowed too. #hosts = localhost hosts = localhost # Distinguished Name - the username used to login to the LDAP server #dn = dn = "cn=dovecot,dc=akforecast" # Password for LDAP server #dnpass = dnpass = dovecot # LDAP protocol version to use. Likely 2 or 3. ldap_version = 2 #ldap_version = 3 # LDAP base #base = uid=someone, dc=foo, dc=bar, dc=org base = o=hosting,dc=akforecast # Dereference: never, searching, finding, always deref = never # Search scope: base, onelevel, subtree scope = subtree # User attributes in order: # Virtual user name (user@domain) # Home directory # MAIL environment # System user name (for getting user's groups from /etc/group) # - For virtual users you don't want to use this, so this defaults to none. # System UID # System GID #user_attrs = uid,homeDirectory,,,uidNumber,gidNumber user_attrs = mail,homeDirectory,,,, # Filter for user lookup. Some variables can be used: # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain #user_filter = (&(objectClass=posixAccount)(uid=%u)) user_filter = (&(objectClass=JammMailAccount)(mail=%u)(accountActive=TRUE)(delete=FALSE)) # Password checking attributes in order: # Virtual user name (user@domain) # Password, may optionally start with {type}, eg. {crypt} #pass_attrs = uid,userPassword pass_attrs = mail,userPassword # Filter for password lookups #pass_filter = (&(objectClass=posixAccount)(uid=%u)) pass_filter = (&(objectClass=JammMailAccount)(mail=%u)(accountActive=TRUE)(delete=FALSE)) # Default password scheme. "{scheme}" before password overrides this. # Currently supported schemes include PLAIN, PLAIN-MD5, DIGEST-MD5, CRYPT #default_pass_scheme = CRYPT default_pass_scheme = PLAIN # You can use same UID and GID for all user accounts if you really want to. # If the UID/GID is still found from LDAP reply, it overrides these values. user_global_uid = 1051 user_global_gid = 1051 ---------------------------------------------------- /etc/dovecot/dovecot.conf: [root@salcha openldap]# cat /etc/dovecot/dovecot.conf ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap imaps #protocols = imap # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". #imap_listen = * #pop3_listen = * #imap_listen = 127.0.0.1 imap_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. imaps_listen = * #pop3s_listen = # Disable SSL/TLS support. ssl_disable = no #ssl_disable = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem ssl_cert_file = /usr/share/ssl/hosting.example/climate_cert.pem ssl_key_file = /usr/share/ssl/hosting.example/climate_private_key.pem # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. #disable_plaintext_auth = yes disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. #login_chroot = yes ## ## IMAP login process ## login = imap # Executable location. #login_executable = /usr/libexec/dovecot/imap-login # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/libexec/dovecot/pop3-login ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 first_valid_uid = 1051 last_valid_uid = 1051 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 first_valid_gid = 1051 last_valid_gid = 1051 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = valid_chroot_dirs = /vhosts/vmail # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = default_mail_env = maildir:/vhosts/vmail/%d/%n # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # outlook-pop3-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. #client_workarounds = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. #mail_read_mmaped = no # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. #mbox_locks = dotlock fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also be a small security risk if you use single UID # for multiple users, as the users could ptrace() each others processes then. #mail_drop_priv_before_exec = no ## ## IMAP process ## # Executable location #imap_executable = /usr/libexec/dovecot/imap # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no #imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/libexec/dovecot/pop3 # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules = no #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # An Authentication process is a child process used by Dovecot that # handles the authentication steps. The steps cover an authentication # mechanism (auth_mechanisms, how the client authenticates in the IMAP or # POP3 protocol), which password database should be queried (auth_passdb), # and which user database should be queried (auth_userdb, to obtain # UID, GID, and location of the user's mailbox/home directory). # # You can have multiple processes, though a typical configuration will # have only one. Each time "auth = xx" is seen, a new process # definition is started. The point of multiple processes is to be able # to set stricter permissions. (See auth_user below.) # # Just remember that only one Authentication process is asked for the # password, so you can't have different passwords accessible through # different process definitions (unless they have different # auth_mechanisms, and you're ok with having different password for # each mechanisms). # Authentication process name. auth = default # Specifies how the client authenticates in the IMAP protocol. # Space separated list of permitted authentication mechanisms: # anonymous plain digest-md5 cram-md5 # # anonymous - No authentication required. # plain - The password is sent as plain text. All IMAP/POP3 clients # support this, and the password can be encrypted by Dovecot to match # any of the encryption schemes used in password databases. # digest-md5 and cram-md5 - both encrypt the password so it is more # secure in transit, but are not well supported by clients, and # require that the password database use a matching encryption # scheme (or be in plaintext). # # See auth.txt for more details. # # If you are using SSL there is less benefit to digest-md5 and # cram-md5 as the communication is already encrypted. auth_mechanisms = plain # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # Where user database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf #auth_userdb = passwd auth_userdb = ldap /etc/dovecot/dovecot-ldap.conf # Where password database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf #auth_passdb = pgsql /usr/local/etc/dovecot-pgsql.conf #auth_passdb = passwd auth_passdb = ldap /etc/dovecot/dovecot-ldap.conf #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. #auth_user = root auth_user = dovecot # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. #auth_verbose = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_mechanisms = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5"

2 1

[Dovecot] IMAP crashes with signal 10 (SIGBUS)
by Joseph Tam 15 Dec '04

15 Dec '04

Any idea on what's causing this? Description: imap process crashed with SIGBUS. Versions: OS: Solaris 8, 9 Dovecot: 1.0-test57 Gcc: 3.2 Configure options: env CC=gcc CFLAGS="-O -g" ./configure \ --prefix=/var/dovecot \ --disable-ipv6 \ --with-ssl=openssl \ --with-ssldir=/etc/ssl \ --with-passwd-file \ --without-bsdauth \ --without-checkpassword \ --without-pam \ --without-passwd \ --without-shadow \ --without-vpopmail \ --without-static-userdb \ --without-libiconv-prefix \ --with-storages=mbox \ --with-pop3d Interestingly, eliminating optimisation seems to get rid of the problem, suggesting it might be a compiler problem. I've also tried gcc flags "-m32", "-m64", "-O3", "-O2", "-O1" and configure options "--with-file-offset-size=32 --with-mem-align=4" with no relief. IMAP dialogue: ... deleted cache, just in case ... >> 'MAIL=mbox:/nfs/ono/mail/:INBOX=/nfs/mail/ono:INDEX=/nfs/ono/dovecot/cache' imap << * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as ono >> x1 SELECT INBOX >> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) >> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. >> * 2 EXISTS >> * 2 RECENT >> * OK [UNSEEN 1] First unseen. >> * OK [UIDVALIDITY 1102645397] UIDs valid >> * OK [UIDNEXT 3] Predicted next UID >> x1 OK [READ-WRITE] Select completed. << x2 FETCH 1:2 (ENVELOPE) >> Bus Error - core dumped INBOX content: From abc(a)hushmail.com Thu Nov 18 18:04:46 2004 Received: from bogus.com ([221.15.172.119]) by mx.fake.com (8.12.10/8.12.10) with SMTP id iAJ24MIs000307; Thu, 18 Nov 2004 18:04:30 -0800 (PST) Message-ID: <81360434043.65276@abc@hushmail.com> From: <abc(a)hushmail.com> To: <fake(a)fakeu.edu> Subject: blah Date: Thu, 18 Nov 2004 19:00:26 -0700 X-UID: 1 blah blah From def(a)yahoo.com Thu Nov 18 18:48:37 2004 Received: from bogus.com (client-200.121.192.53.speedy.net.pe [200.121.192.53] (may be forged)) by mx.fake.com (8.12.10/8.12.10) with SMTP id iAJ2mCIs001481 for <somebody(a)fakeu.edu>; Thu, 18 Nov 2004 18:48:32 -0800 (PST) Message-Id: <200411190248.iAJ2mCIs001481(a)blah.ca> Date: Fri, 19 Nov 2004 02:39:36 +0000 From: <def(a)yahoo.com> To: somebody(a)fakeu.edu Subject: blah X-UID: 2 blah blah Backtrace: #0 mbox_file_seek (ibox=0x8d9b0, view=0x8dc38, seq=2, deleted_r=0xffbef40c) at mbox-file.c:119 #1 0x0002afbc in mbox_mail_seek (mail=0x935f0) at mbox-mail.c:48 #2 0x0002b1b0 in mbox_mail_get_stream (_mail=0x935f0, hdr_size=0x0, body_size=0x0) at mbox-mail.c:159 #3 0x00034894 in index_mail_get_headers (_mail=0x935f0, _headers=0x93d80) at index-mail-headers.c:540 #4 0x000343e4 in index_mail_headers_get_envelope (mail=0x935f0) at index-mail-headers.c:362 #5 0x000334cc in index_mail_get_special (_mail=0x935f0, field=MAIL_FETCH_IMAP_ENVELOPE) at index-mail.c:578 #6 0x0002b118 in mbox_mail_get_special (_mail=0x935f0, field=MAIL_FETCH_IMAP_ENVELOPE) at mbox-mail.c:128 #7 0x00020c80 in fetch_envelope (ctx=0x881d8, mail=0x935f0, context=0x0) at imap-fetch.c:347 #8 0x0002081c in imap_fetch (ctx=0x881d8) at imap-fetch.c:209 #9 0x0001c034 in cmd_fetch (client=0x83f50) at cmd-fetch.c:164 #10 0x0001f2a4 in client_handle_input (client=0x83f50) at client.c:324 #11 0x0001f370 in _client_input (context=0x83f50) at client.c:368 #12 0x000593b8 in io_loop_handler_run (ioloop=0x810c0) at ioloop-poll.c:184 #13 0x00058d34 in io_loop_run (ioloop=0x810c0) at ioloop.c:218 #14 0x000272c8 in main (argc=0, argv=0xffbefa4c, envp=0xffbefa5c) at main.c:224 Joseph Tam <tam(a)math.ubc.ca>

2 1

[Dovecot] Tricks to running as normal user?
by Ajaxster 15 Dec '04

15 Dec '04

Hi, I'm running on HPUX 11.11 and have installed dovecot 0.99.12 in my home directory. I've been running it at home on FC2 and had no problems. At work, on HPUX, when I modify the dovecot.conf file like is suggested in the wikki <http://wiki.dovecot.org/moin.cgi/Rootless>, it will detach and I can telnet to the port I've chosen, but I don't get any response back after I connect. Not other processes are getting launched when I connect. I can run the libexec/imap and get capability information echoed to the terminal. I tried the test builds and they seem to be hanging during the parsing of the .conf file. The the process never goes into the background. Does anyone have any suggestions on what I could try to get things running? Thanks very much. -- Jay

2 1