- dovecot - dovecot.org

[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 16 Dec '04

16 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

[Dovecot] Verbose logging
by Daniel 15 Dec '04

15 Dec '04

Hi How can I make dovecot have very verbose logging? Regards Daniel

2 1

[Dovecot] Internal login failure
by Jaeson Schultz 15 Dec '04

15 Dec '04

Hello, I am fairly new to Dovecot, so please forgive me if I am missing something obvious here. I have checked the archived dovecot mailing list messages and have Googled for everything I can think of, and I still have not found anything to help me solve this problem. I am running Postfix+Postgresql+Dovecot on my Fedora FC2 box. I have compiled both Postfix and Dovecot from source. I believe I have postfix running properly. No error messages show up in my logs when starting Postfix or Dovecot. Messages are being delivered by Postfix just fine: Dec 12 11:45:42 co-nundrum postfix/virtual[15759]: 15E82F8EF0: to=<jaeson(a)domain.name>, relay=virtual, delay=1, status=sent (delivered to maildir) However, when I try to login to Dovecot over IMAP I get an "Internal login failure" error: [jaeson@localhost jaeson]$ telnet co-nundrum imap Trying 207.7.137.6... Connected to co-nundrum. Escape character is '^]'. * OK dovecot ready. 1 LOGIN jaeson secret 1 OK Logged in. * BYE Internal login failure. Error report written to server log. Connection closed by foreign host. When I check the dovecot log file I see the following entries: dovecot-auth: Dec 12 01:15:59 Info: PGSQL: Performing query: SELECT password FROM user_accounts WHERE username='jaeson' imap-login: Dec 12 01:15:59 Info: Internal login failure: jaeson [66.159.231.21] dovecot: Dec 12 01:15:59 Error: child 9845 (auth) killed with signal 11 Here are the entries from my dovecot.conf file. As you can see, I have set both auth_verbose and auth_debug = yes, but I don't seem to be getting any log messages with enough verbosity to indicate just what the problem is. base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s imap_listen = * pop3_listen = * ssl_parameters_regenerate = 24 disable_plaintext_auth = no log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log login_dir = /var/run/dovecot-login login = imap login_executable = /usr/libexec/dovecot/imap-login login_user = dovecot login_process_size = 16 login_process_per_connection = yes login_processes_count = 3 login_max_processes_count = 128 login_max_logging_users = 256 max_mail_processes = 1024 verbose_proctitle = yes verbose_ssl = yes first_valid_uid = 5000 last_valid_uid = 65535 first_valid_gid = 5000 last_valid_gid = 65535 default_mail_env = maildir:/mail/%d/%u mail_save_crlf = yes maildir_copy_with_hardlinks = no maildir_check_content_changes = no mbox_locks = fcntl umask = 0077 imap_executable = /usr/libexec/dovecot/imap imap_process_size = 256 auth = default auth_mechanisms = plain auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_passdb = pgsql /etc/dovecot-pgsql.conf auth_executable = /usr/libexec/dovecot/dovecot-auth auth_user = root auth_count = 1 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_verbose = yes auth_debug = yes Additionally, here are the entries in my dovecot-pgsql.conf file: connect = host=localhost dbname=mail_DB user=mailreader password=secret default_pass_scheme = PLAIN password_query = SELECT password FROM user_accounts WHERE username='%u' user_query = SELECT '/mail/'||mailbox AS home, uid, gid FROM user_accounts WHERE username='%u' Finally, here is the configure command I used when building Dovecot from source: ./configure --prefix=/usr --enable-debug --with-pgsql --with-cyrus-sasl2 --with-ssl=openssl --sysconfdir=/etc At this point, I think that the connections to my postgresql tables are all working properly, and the initial authentication with Dovecot appears to be working. Dovecot *does* accept my password and gives me the "OK Logged in." response message, but somewhere before it kicks off the IMAP process it dies with a SIGSEGV. Perhaps I have some file permissions out of whack? Has anyone else encountered this problem, or perhaps has any insight into what might be going wrong or how to find out more information? Thanks, Jaeson Schultz jaeson at jaeson dot net

3 4

Re: Re: [Dovecot] login pam and mysql
by Marin Florian 15 Dec '04

15 Dec '04

I try 1.0 vresion, but seems to be a problem at mysql login. I'll look again at this version. Regards, > Hi Marin, > Try the 1.0 test versions, they allow as many login type as you want. > > Regards > Andrew > > > Marin Florian wrote: > > Hy, > > > > I use dovecot 0.99.12 on a FC2 and i try to obtain dual login pam and mysql, but > > seems that it's impossible. I must use or pam or mysql. Do you have any ideea > > how to obtain dual login. Thanks in advance. > > > > > > > > _________________________________ > > Noile abonamente Astral OnLine > > 256 kbps ; 12 USD/luna > > http://www.astral.ro > > > > -- > Andrew Hutchings > Systems Operator / Developer / Linux Guru > Netserve Consultants Ltd. > http://www.domaincity.co.uk/ > _________________________________ Noile abonamente Astral OnLine 256 kbps ; 12 USD/luna http://www.astral.ro

1 0

[Dovecot] login pam and mysql
by Marin Florian 15 Dec '04

15 Dec '04

Hy, I use dovecot 0.99.12 on a FC2 and i try to obtain dual login pam and mysql, but seems that it's impossible. I must use or pam or mysql. Do you have any ideea how to obtain dual login. Thanks in advance. _________________________________ Noile abonamente Astral OnLine 256 kbps ; 12 USD/luna http://www.astral.ro

2 1

[Dovecot] latest debs
by Paul 14 Dec '04

14 Dec '04

Just wondering: Has anyone, or is anyone planning to, build debs for 0.99.12? Jaldhar Vyas, are you still around and doing such things? Paul

2 1

[Dovecot] Re: Corrupted index files in 0.99.12.1
by Brady Wetherington 14 Dec '04

14 Dec '04

--- dovecot-request(a)dovecot.org Wrote: > From: Timo Sirainen <tss(a)iki.fi> > On 13.12.2004, at 21:26, Brady Wetherington wrote: > > > A solution I already tried was having Dovecot run by being invoked from > > a copy of tcpserver, which used a .cdb 'rules' database which set > > certain environment variables based upon the users IP address. I > > patched > > my copy of Dovecot to listen for those environment variables and pay > > attention/ignore NO_IMAP based upon those environment variables, but it > > looks like environment variables get clobbered when dovecot invokes the > > authenticator process from within imap-login (And the code seems to say > > that it blows out the environment, too). And I'm willing to bet that it > > would only work on first invoke of dovecot from imap-login, too, even > > if > > it didn't blow out the environment (because the authentication process > > stays running). > > You could do this by first getting the remote IP address transferred to > dovecot-auth (http://dovecot.org/patches/pam-rhost.patch) then checking > the IP in vpopmail code to see if you want to check NO_IMAP with the > IP. That sounds like that's the direction I want to go - I will definitely take a look into that, and possibly tweak it if I can. The way I was thinking about doing it was either respecting one or the other of NO_IMAP or NO_WEBMAIL depending on if you're coming from a local address or a remote one. I might stick with tcpserver using a tcprules.cdb to set environment variables and modify the patch to pass those environment variable(s) onward...we'll see. Or I might just suffer with my many dovecots. > > > I also _think_ I found out the problem, what was corrupting my indexes, > > though I'm not sure. I think one of the messages in my Maildir was > > 'unreadable' by Dovecot (well, that's what the logs say). Which seems > > to > > completely blow out the index. I got rid of the file, so lets keep > > fingers crossed that that solves it... > > If there's a repeateable way to break Dovecot with some specific > message even after indexes have been recreated, I'd like to see the > message. > > Unless, of course, you meant that 'unreadable' was because there was no > file system permissions to read it? Yes, unfortunately, the file was unreadable because there was no file system permissions to read it. That actually made dovecot make indices which imply there's nothing in the mailbox. How a file with no FS perms got into my maildir is rather embarassing and I'll skip unless it's important, but it was there and it did hose my indexes.

1 0

Re: [Dovecot] Ximian Evolution Issue
by Adam Todorski 14 Dec '04

14 Dec '04

Thanks for your swift replies, I really appreciate it. I looked at my mail logs and couldn't find anything awry. Also, if I use Mozilla Thuderbird from any remote platform or Squirrelmail hosted on the mail server itself I have no problems, regardless of the number of messages in a folder. I realize that I should probably ask on Evolution forums, but I think you guys may be better equiped to answer. Thanks again, Adam

2 1

[Dovecot] RE: Internal login failure
by Jaeson Schultz 13 Dec '04

13 Dec '04

Hello, I should have sent my first message in plain text instead of HTML so it would show up better in the list archives. Anyhow, I am using the latest release of Dovecot, v0.99.12.1. Seeing as how I don't need the cyrus-sasl2 to be compiled in, I have just rebuilt dovecot without it. Unfortunately I am still getting the same results... [jaeson@shell01 ~]$ telnet co-nundrum imap Trying 207.7.137.6... Connected to co-nundrum. Escape character is '^]'. * OK dovecot ready. 1 LOGIN jaeson secret 1 OK Logged in. * BYE Internal login failure. Error report written to server log. Connection closed by foreign host. The dovecot logs still indicate an "Internal login failure", but offers no extra explanation as to why. dovecot-auth: Dec 13 11:43:04 Info: PGSQL: Performing query: SELECT password FROM user_accounts WHERE username='jaeson' imap-login: Dec 13 11:43:04 Info: Internal login failure: jaeson [216.39.112.19] dovecot: Dec 13 11:43:04 Error: child 25784 (auth) killed with signal 11 I am wondering that since I see the auth_passdb query, shouldn't I also be seeing a log entry for the auth_userdb query as well, or does this happen once the imap process is started? Any advice for how to track down the source of the problem is appreciated. ~Jaeson [This E-mail scanned for viruses]

1 0

[Dovecot] Re: Corrupted index files in 0.99.12.1
by Brady Wetherington 13 Dec '04

13 Dec '04

--- dovecot-request(a)dovecot.org Wrote: > From: Matthias Andree <matthias.andree(a)gmx.de> > Brady Wetherington <brady(a)netservnyc.com> writes: > > > Would my old, corrupted index files be of any use to anyone? I still > > have that directory sitting somewhere. Is it perhaps 'bad' to run two > > copies of Dovecot? I don't know exactly what I was doing, but I can > > easily imagine accessing one of my Dovecots using my webmail setup, and > > one using straight IMAP - is that an unsupported setup? > > I'd think the way to go is to use one Dovecot installation for both IMAP > logins by remote clients as well as the webmail system. > > -- > Matthias Andree I would think the exact same thing, and I would _love_ to run only one copy of Dovecot. But I run vpopmail, and I need to make IMAP available only to users who have IMAP 'enabled' (the guys who pay more money). But I need webmail available for _all_ users (even the cheapskates), and my webmail of course uses IMAP behind the scenes. So my solution is one copy of regular Dovecot on port 143, which respects the NO_IMAP flag from vpopmail, and one copy of modified Dovecot, which I patched to ignore the NO_IMAP flag, on port 144 - and then I configured my webmail software to talk to port 144. That copy of Dovecot will eventually only listen to the local network for connections, though currently it listens for anyone. A solution I already tried was having Dovecot run by being invoked from a copy of tcpserver, which used a .cdb 'rules' database which set certain environment variables based upon the users IP address. I patched my copy of Dovecot to listen for those environment variables and pay attention/ignore NO_IMAP based upon those environment variables, but it looks like environment variables get clobbered when dovecot invokes the authenticator process from within imap-login (And the code seems to say that it blows out the environment, too). And I'm willing to bet that it would only work on first invoke of dovecot from imap-login, too, even if it didn't blow out the environment (because the authentication process stays running). All this stuff is, I'm sure, a thousand times easier in something like courier-imap, but I like Dovecot, so I'd rather run two copies of Dovecot than one of courier-imap. So if anyone has any possible direction to go on a solution that lets me run only one Dovecot, I'd love that. Until then, I'm stuck with my hack-ey two-Dovecot solution. I also _think_ I found out the problem, what was corrupting my indexes, though I'm not sure. I think one of the messages in my Maildir was 'unreadable' by Dovecot (well, that's what the logs say). Which seems to completely blow out the index. I got rid of the file, so lets keep fingers crossed that that solves it...

2 1

[Dovecot] 1.0-test57 LDAP dovecot-auth SIGABRT
by Thomas Hummel 13 Dec '04

13 Dec '04

Hi, I'm experiencing the following problem when runnig dovecot-1.0-test set up to authenticate users against openldap, while the corresponding setup with dovecot-0.99.11 works fine : . my platform : FreeBSD 5.3-RELEASE-p1 . dovecot version : dovecot-1.0-test57 . openldap version : openldap-2.1.27 - Description : When I talk IMAP to the dovecot server, I can connect on port 143 and receive the 'Dovecot ready' greeting message, but when I issue the command 'x LOGIN username userpass', the following message is written to the log file : ---------------------------------------------------------------------- 'dovecot: Dec 13 16:40:26 Error: auth(default): dovecot-auth in free(): error: chunk is already free dovecot: Dec 13 16:40:26 Error: child 17260 (auth) killed with signal 6' ---------------------------------------------------------------------- - here's a gdb backtrace of the dovecot-auth running process as it happens : (gdb) continue Continuing. Program received signal SIGABRT, Aborted. 0x1826e1d7 in kill () from /lib/libc.so.5 (gdb) bt full #0 0x1826e1d7 in kill () from /lib/libc.so.5 No symbol table info available. #1 0x1826327e in raise () from /lib/libc.so.5 No symbol table info available. #2 0x182d5627 in abort () from /lib/libc.so.5 No symbol table info available. #3 0x18279389 in ldexp () from /lib/libc.so.5 No symbol table info available. #4 0x182793cd in ldexp () from /lib/libc.so.5 No symbol table info available. #5 0x1827a2c1 in ldexp () from /lib/libc.so.5 No symbol table info available. #6 0x1827a513 in ldexp () from /lib/libc.so.5 No symbol table info available. #7 0x1827a644 in free () from /lib/libc.so.5 No symbol table info available. #8 0x080502c7 in ldap_input (context=0x2c) at db-ldap.c:172 request = (struct ldap_request *) 0x806a580 timeout = {tv_sec = 0, tv_usec = 0} res = (LDAPMessage *) 0x806a5a0 ret = 0 msgid = 405650150 #9 0x0805cea8 in io_loop_handler_run (ioloop=0x8075340) at ioloop-poll.c:184 data = (struct ioloop_handler_data *) 0x806a160 pollfd = (struct pollfd *) 0x2 tv = {tv_sec = 0, tv_usec = 268537} io = (struct io *) 0x806a300 t_id = 2 msecs = 0 ret = 0 call = 1 #10 0x0805c8e5 in io_loop_run (ioloop=0x8075340) at ioloop.c:218 No locals. #11 0x08051174 in main (argc=1, argv=0x0) at main.c:296 master = (struct auth_master_connection *) 0x8075500 i = 1 env = 0x4598 <Error reading address 0x4598: Bad address> pid = 0 master_p = (struct auth_master_connection **) 0x8075400 size = 1 (gdb) detach Detaching from program: /usr/local/dovecot-1.0-test57/libexec/dovecot/dovecot-auth, process 17804 (gdb) - here are the configure options I passed when compiling openldap and dovecot : - dovecot ./configure --prefix=/usr/local/dovecot-1.0-test57 --with-ldap --with-cyrus-sasl2 --with-rawlog --with-ssl=openssl --with-storages=mbox,maildir - openldap ./configure --prefix=/usr/local/openldap-2.1.27 --with-threads --with-tls=openssl --enable-dynamic --with-cyrus-sasl --enable-ldbm --enable-crypt --enable-lmpasswd --enable-ldap --enable-meta --enable-rewrite --enable-null --enable-monitor --enable-bdb --with-ldbm-api=berkeley --enable-spasswd --enable-wrappers -- Thomas Hummel <hummel(a)pasteur.fr>

1 0

[Dovecot] Problem with LDAP and Dovecot
by Peter Clark 13 Dec '04

13 Dec '04

I am trying to set up Dovecot so that it uses LDAP, but I keep getting this error message in /var/log/syslog: Dec 12 03:38:17 mydomain dovecot-auth: LDAP: ldap_search() failed (filter user_filter = (mail=user(a)mydomain.tld)) Bad search filter Relevant configuration files: /etc/dovecot-ldap.conf: hosts = localhost dn = cn=dovecot,ou=sysAccounts,dc=mydomain,dc=tld dnpass = password ldap_version = 3 base = ou=mailAccounts,dc=mydomain,dc=tld deref = never scope = subtree user_attrs = mail,,,,, user_filter = (mail=%u) pass_attrs = mail,userPassword pass_filter = user_filter = (mail=%u) default_pass_scheme = CRYPT user_global_uid = 5000 user_global_gid = 5000 /etc/dovecot.conf: protocols = imap imaps pop3s imap_listen = 127.0.0.1 imaps_listen = * pop3s_listen = * ssl_cert_file = /etc/ssl/mydomain.tld/Cert.pem ssl_key_file = /etc/ssl/mydomain.tld/PrivateKey.pem disable_plaintext_auth = yes login = imap login_user = dovecot login = pop3 verbose_proctitle = yes first_valid_uid = 5000 last_valid_uid = 5000 first_valid_gid = 5000 last_valid_gid = 5000 mail_extra_groups = mail valid_chroot_dirs = /var/mail/virtualmail default_mail_env = maildir:/var/mail/virtualmail/%n/Maildir auth = default auth_mechanisms = plain auth_userdb = ldap /etc/dovecot-ldap.conf auth_passdb = ldap /etc/dovecot-ldap.conf auth_user = dovecot auth_verbose = yes auth_debug = no In /etc/ldap/slapd.conf: access to attribute=userPassword by dn="cn=admin,dc=mydomain,dc=tld" write by dn="cn=dovecot,ou=sysAccounts,dc=mydomain,dc=tld" read by anonymous auth by self write by * none Output of 'slapcat | grep dovecot': dn: cn=dovecot,ou=sysAccounts,dc=mydomain,dc=tld cn: dovecot sn: dovecot I've even tried changing the dn to admin, but I still get the same error. What am I doing wrong? :Peter

3 3

[Dovecot] Ximian Evolution Issue
by Adam Todorski 13 Dec '04

13 Dec '04

Hi This may be a problem with Dovecot and it may be a problem with Evolution, I'm trying to narrow it down. I'm using Evolution 2.0.2 on Fedora Core 3 x86_64 to connect over SSL to Dovecot 0.99.11 on Debian testing (Sarge) on an i686 using Maildir for the mail store. Specifically, when I open a folder with more than a few dozen messages in it I get the following error (with the carroted fields populated): Error while Opening folder imap://<username>@<mailserver>/<folder>. Incomplete server response: no information provided for message <message number>. Thanks for any leads on this! Adam

2 1

[Dovecot] Corrupted index files in 0.99.12.1
by Brady Wetherington 12 Dec '04

12 Dec '04

Hi - I've got two copies of Dovecot installed on my server (don't worry, talking to two different sockets for authentication, with two different sets of filenames using options in configure), and I found at least one instance where the index file for my INBOX (on my own account, in fact) got corrupted. So badly so that when I connected via IMAP and selected my INBOX, it said there were no messages there - but if I logged in via sqWebMail (ugh), it said all my messages were there. Note that it didn't give the 'NO can't use index file' message. I moved the .INBOX directory to another filename, and then re-logged in and found that all was well (it regenerated the index files correctly). Would my old, corrupted index files be of any use to anyone? I still have that directory sitting somewhere. Is it perhaps 'bad' to run two copies of Dovecot? I don't know exactly what I was doing, but I can easily imagine accessing one of my Dovecots using my webmail setup, and one using straight IMAP - is that an unsupported setup? I'd also be happy to discuss why I'm using two copies of Dovecot, but that's a whole other discussion :)

2 1

Re: [Dovecot] Timeouts with outlook express
by Daniel 11 Dec '04

11 Dec '04

Hi Yes I have all the outlook workarounds enabled. Interestingly the progress bar dose not move until the whole email has been downloaded. Normally this moves bit by bit as the mail downloads. But as I said the email is downloading, there is network traffic. Any ideas? Regards Daniel On Thu, 2004-12-09 at 07:45 +0000, Andrew Hutchings wrote: > Hi Daniel, > > Have you tried turning on th outlook-no-nuls workaround in dovecot? > > Regards > Andrew > > On Thu, 2004-12-09 at 15:22 +0800, Daniel wrote: > > Hi > > > > I am using Dovecot 0.99.12.1 (just upgraded) on a site with about 1500 > > mailboxes. One thing I have noticed is when the client outlook express > > is receiving a large mail via pop3 it gets a time out. There is traffic. > > If you click on the "wait" button in the dialogue the mail continues to > > download. > > > > This seem to relate to the "Server Timeouts" setting under mail account > > Properties/advance. If this setting is set higher the dialogue come only > > after this time has passed. > > > > If the mail take a long time to download if say is very big the user may > > have to click "Wait" a number of time even if the time out setting is > > set to the largest amount. > > > > It funny because the mail is downloading, So the pop3 server has not > > stopped responding as outlook express say it has. Strange. > > > > What is happening here? and is there a work around for it. Do I have a > > setting wrong. > > > > Regards > > Daniel ROwe > > > >

2 1

[Dovecot] SQL + AUTH command bug?
by Andrew Hutchings 10 Dec '04

10 Dec '04

Hi, While investigating the problem with Thunderbird auths I found the following happening: Escape character is '^]'. +OK Dovecot ready. CAPA +OK CAPA TOP USER UIDL RESP-CODES PIPELINING SASL PLAIN . AUTH PLAIN + + + -ERR Authentication failed. This is what is happening during a Thunderbird connection, when each '+' happens dovecot does an sql query on the sql server for user '?'. This was asserting mech.c until Timo did the bugfix last night. I currently have dovecot authing via 3 separate sql password tables as it is a migration from 3 old servers. If you try any other auth method (which shouldn't work anyway in my case) it doesn't talk to the SQL servers and just comes back as: -ERR Authentication failed. Regards Andrew -- Andrew Hutchings Systems Operator / Developer / Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

5 10

Re: [Dovecot] When the 1.0 release is planed?
by Kim Culhan 10 Dec '04

10 Dec '04

On Thu, December 9, 2004 15:07, Andrew Velikoredchanin said: > Wouter Van Hemel: > >>> >>> What part of 1.0-test now not fully tested? >>> >>> >>> >> >> For me, the latest test releases have been pretty stable. But if you're >> not going to offer imap, you might as well run a simple pop server such as popa3d >> (http://www.openwall.com/popa3d/) It's quite secure AFAIK -- >> at least, it's written by Solar Designer and uses a multiple-fork model. > > No. popa3d not support mysql userdb. :( > > >> But it probably would help dovecot if you would give the test releases a >> try, the last bugs (if any) are hardest to find. That way, you would have a stable dovecot >> sooner. > > Yes, of couse. FWIW, dovecot CVS (development version) has been running here for several weeks with pop3s users having no problems we can find. -kim' __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

4 4

[Dovecot] Exim4 authentication patch
by Andrey Panin 10 Dec '04

10 Dec '04

Hello all, attached patch makes possible to use dovecot as an authentication backend for Exim 4. Reasons beyond this patch are simple: exim's authenticators require use of plaintext passwords and NTLM code in exim is quite outdated and hairy. Patch generated against Exim 4.43, but should apply to earlier versions too. Patch adds new 'dovecot' authenticator, which can be used as such: ntlm: driver = dovecot public_name = NTLM server_socket = /var/authentication_socket_path server_set_id = $1 cram: driver = dovecot public_name = CRAM-MD5 ... Authenticator has only one parameter 'server_socket', it's value used as path for dovecot's authentication socket. Authenticator can be used for server authentication only. Hope it will be useful for someone. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 1

[Dovecot] mech-plain patch
by Andrew Hutchings 10 Dec '04

10 Dec '04

Hi Guys, Unoffical patch for mech-plain so the AUTH PLAIN command works with SQL (and possibly other DBs). Thunderbird should work again after this. --- mech-plain.c 2004-12-10 01:56:51.065987304 +0000 +++ mech-plain.c 2004-12-10 01:53:16.974534152 +0000 @@ -27,7 +27,10 @@ authid = (const char *) data; authenid = NULL; pass = ""; - count = 0; + if (data_size == 0) + return; + + count = 0; for (i = 0; i < data_size; i++) { if (data[i] == '\0') { if (++count == 1) Regards Andrew -- Andrew Hutchings Systems Operator / Developer / Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 1

[Dovecot] Help needed with debugging auth command
by Andrew Hutchings 10 Dec '04

10 Dec '04

Hi guys, OK, so I am trying to find out why the POP3 AUTH / IMAP AUTHORIZE command is not doing what it is supposed to (not sure if it just for me or what). I am getting as far as: sasl-server.c - line 123 - mech = auth_client_find_mech(auth_client, mech_name); auth_client_find_mech is in auth-client.c which is where I am getting lost. My guess is we are not returning back to sasl-server.c since we don't get an SASL auth or an 'Unsupported' error. If I try 'PLAIN' as the auth method as the parameter then it tries to login with no user or pass and fails. If I try anything else (I have configed to accept plain only) I get 'Authorization failed' and it doesn't even try to lookup the user/pass. Regards Andrew -- Andrew Hutchings Systems Operator / Developer / Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 1

[Dovecot] SHA1
by Marco Herrn 10 Dec '04

10 Dec '04

Hi, I am currently installing doveot as POP and IMAP server, but I a have a few difficulties configuring it correctly. I use postgresql to store the user information. The passwords are stored SHA1 encrypted. Now I have the problem that dovecot isn't accepting the user. In dovecot-pgsql.conf I defined default_pass_scheme = SHA1 I am not quite sure about whether this is corrents, since it is not mentioned in the documentation, but it is mentioned in the wiki (under the name SHA) and it doesn't produce an error (as specifying SHA does). So I assume this is correct. But when I log in with a user I always geht the following log output: dovecot-auth: Dec 08 22:18:20 Info: PGSQL: Performing query: SELECT passwd FROM mailbox WHERE localpart = érwin' AND domainname ='poiu.de' dovecot-auth: Dec 08 22:18:20 Info: pgsql(erwin(a)poiu.de): Password mismatch imap-login: Dec 08 22:18:20 Info: Aborted login [82.82.66.4] dovecot-auth: Dec 08 22:18:20 Info: Login process 9 disconnected dovecot-auth: Dec 08 22:18:20 Info: Login process 9 connected dovecot-auth: Dec 08 22:18:20 Info: Login process 9 sent handshake: PID 22222 Is there a way to get a more excessive debugging? I already set auth_verbose and auth_debug to yes. Or does anyone have an idea what the problem can be here? Regards Marco -- It's better to be wanted for murder that not to be wanted at all. -- Marco Herrn _ ___ o ' (_)< _ _ _>(__'> o 0 (_X % >(_`> O o _; _;'7^'_ \;\ % (GnuPG/PGP-encrypted mail preferred) _;\ _.\ _.';;) ;,;_/; Key ID: 0x94620736 _ _'./_$'))_; );/$}/`fsc

3 7

[Dovecot] When the 1.0 release is planed?
by Andrew Velikoredchanin 10 Dec '04

10 Dec '04

Hi! When the 1.0 release is planed?

5 7

[Dovecot] Timeouts with outlook express
by Daniel 09 Dec '04

09 Dec '04

Hi I am using Dovecot 0.99.12.1 (just upgraded) on a site with about 1500 mailboxes. One thing I have noticed is when the client outlook express is receiving a large mail via pop3 it gets a time out. There is traffic. If you click on the "wait" button in the dialogue the mail continues to download. This seem to relate to the "Server Timeouts" setting under mail account Properties/advance. If this setting is set higher the dialogue come only after this time has passed. If the mail take a long time to download if say is very big the user may have to click "Wait" a number of time even if the time out setting is set to the largest amount. It funny because the mail is downloading, So the pop3 server has not stopped responding as outlook express say it has. Strange. What is happening here? and is there a work around for it. Do I have a setting wrong. Regards Daniel ROwe

4 3

[Dovecot] SQL + POP3 AUTH command bug - test 57
by Andrew Hutchings 09 Dec '04

09 Dec '04

Hi guys, In addition to my previous message stating that POP3 'AUTH' command wasn't working correctly with SQL auths (making Thunderbird fail), the same is true of the AUTHENTICATE command in IMAP. Again I have created a temp fix by commenting out the lines that check for that command in imap-login/client.c If I get some time tonight I will write a patch to fix this properly. (Dovecot 1.0 test 57) Regards Andrew -- Andrew Hutchings Systems Operator / Developer / Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 0

[Dovecot] "correct" permissions for login dir
by Kirill Miazine 08 Dec '04

08 Dec '04

I'm in process of moving away from Cyrus to Dovecot. I have my own authentication daemon working fine. It sets up two sockets: drwxr-x--- 2 root dovecot 512 Dec 7 21:07 /var/state/dovecot/login srw-rw-rw- 1 krot krot 0 Dec 7 21:07 /var/state/dovecot/login/sock drwx------ 2 krot wheel 512 Dec 7 21:07 /var/state/dovecot/master srw-rw-rw- 1 krot wheel 0 Dec 7 21:07 /var/state/dovecot/master/sock When I fire up Dovecot, it warns me of "incorrect" permissons for login dir (/var/state/dovecot/login) and "fixes" the problem. I want /var/state/dovecot/login to be owned by user krot (which the main daemon is running as), not by root. I suggest that login directory is not touched if external authentication is used. Socket are not wiped out, why should permissions be fixed? (see in master/master-settings.c around line 560). I'm afraid that some day I will forget to make this tiny change to Dovecot and end up with a mail system which does not work at all, because the master daemon won't be able to create dovecot/login socket. 1.0-test "works pretty well". Does it mean well enough to replace Cyrus (which indeed works pretty well)? I have maildir-based folders. Most users have no idea what IMAP is (my sister uses IMAP because I set it up, others just say that they don't need IMAP...) and they just download everything using POP3. Sometimes they use SquirrelMail. Default usage pattern. Are the risks high? Currently I have test56 on my test installation (which is almost ready to take over). Timo, Dovecot has been a pleasure to work with so far! -- They make a desert and call it peace. -- Tacitus

2 1

[Dovecot] 0.99.12 released
by Timo Sirainen 08 Dec '04

08 Dec '04

One change since -rc1 (the last one below). - Fix memory leaks in LDAP, MySQL and PGSQL userdb/passdb - Fix hanging when parsing mails that have over 4096 bytes in one line (SMTP servers normally don't allow over 1000 bytes so it shouldn't be much of a problem) - FETCH BODYSTRUCTURE sometimes gave a wrong reply (eg. with FETCH (BODYSTRUCTURE RFC822.SIZE) if it wasn't cached) - Never return more than one INBOX in LIST even if there are such files. They don't work anyway and it just confuses clients. - mbox: Don't allow creating INBOX directory by creating/renaming mailboxes under it. They just wouldn't work. - POP3: Don't return PLAIN in SASL list. We don't support initial SASL responses, so it only breaks with most clients that try to use it. - IMAP and POP3 login processes may have sent each line in two IP packets, one with the data and another with CR+LF. Some clients didn't work because of this.

5 8

[Dovecot] problems with eudora
by Enrique Pedraza 08 Dec '04

08 Dec '04

Hi everyone, i just installed dovecot in Fedora Core release 1 (Yarrow). When accessing from a eudora 6.1 client, first it gave ssl authentication problems. I fixed disabling them in eudora, but now it authenticates ok and then it says that there is no inbox for that user. Any idea? Enrique Pedraza Valiente Formador en Lenguajes Avanzados y Nuevas Tecnologías cell: +34 678 51 75 19 http://epedraza.com

3 3

[Dovecot] (mail_index_sync_update_index): assertion failed
by Doug Luce 08 Dec '04

08 Dec '04

Anyone run into this one? I'm using test53... Dec 3 13:08:17 aurora dovecot: IMAP(doug): file mail-index-sync-update.c: line 1160 (mail_index_sync_update_index): assertion failed: (map->records_count == map->hdr.messages_count) Dec 3 13:08:17 aurora dovecot: child 65942 (imap) killed with signal 6 It doesn't seem to correlate with any particular action. The only change I make to the compilation is to comment out #define HAVE_FREEBSD_SENDFILE Thanks, Doug

4 8

[Dovecot] Non standart mbox path
by Andrew Velikoredchanin 08 Dec '04

08 Dec '04

Hi! I need set to dovecot non standart mbox path. For example, /var/service/mail/%u. How I can do it? I see default_mail_env parameter, but I don't undestend how it used. Thanks!

2 1

[Dovecot] dovecot 1.0-test-56 mail doesn't show up with Mac Entourage clients
by Will Bending 08 Dec '04

08 Dec '04

Hi. I'm seeing some issues where Entourage clients can see new mail, download it (or partially), but won't display the mail in the mailbox list. Mail shows up as having arrived, but never displays. These clients have worked in the past with versions of 0.99, but not in 1.0-test-56. I have dumped the connection traffic and it looks like Entourage aborts the IMAP session before it finishes fetching the mail. I have set up an IMAP server running test 56 and another running dovecot-0.99.11-1.1.fc3.rf and placed one email message in the inbox of a test account. The following is an error message I see in the 1.0 server's logs for some Entourage users experiencing this error, and is followed by a snippet of a tcpdump of the IMAP session on both machines showing where the Entourage client aborts the connection before completing the download of the message. Any help with or comments on this issue are greatly appreciated. Thanks, --will Error in dovecot.log from an Entourage client: dovecot: Dec 07 09:21:44 Error: IMAP(some_user): file mbox-lock.c: line 493 (mbox_lock): assertion failed: (lock_type == F_RDLCK || ibox->mbox_lock_type != F_RDLCK) dovecot: Dec 07 09:21:44 Error: child 16735 (imap) killed with signal 6 **************************************************************************** tcpdump snippets: 0.99 server with Entourage client: 14:43:17.997889 IP noctis.shsu.edu.61359 > ab1-1-41.shsu.edu.imap: P 52:128(76) ack 156 win 65535 <nop,nop,timestamp 519041503 335641251> 0x0000: 4500 0080 adf9 4000 4006 384b 9e87 0bfc E.....@.@.8K.... 0x0010: 9e87 0b29 efaf 008f a87e ee7c fc30 de0e ...).....~.|.0.. 0x0020: 8018 ffff c716 0000 0101 080a 1eef f1df ................ 0x0030: 1401 7aa3 4130 3237 2055 4944 2046 4554 ..z.A027.UID.FET 0x0040: 4348 2032 2028 5549 4420 464c 4147 5320 CH.2.(UID.FLAGS. 0x0050: 494e 5445 524e 414c 4441 5445 2052 4643 INTERNALDATE.RFC 0x0060: 3832 322e 5349 5a45 2042 4f44 592e 5045 822.SIZE.BODY.PE 0x0070: 454b 5b5d 3c30 2e32 3034 3830 3e29 0d0a EK[]<0.20480>).. 14:43:17.998229 IP ab1-1-41.shsu.edu.imap > noctis.shsu.edu.61359: . 156:1604(1448) ack 128 win 1448 <nop,nop,timestamp 335641262 519041503> 0x0000: 4500 05dc 73b9 4000 4006 6d2f 9e87 0b29 E...s.@.@.m/...) 0x0010: 9e87 0bfc 008f efaf fc30 de0e a87e eec8 .........0...~.. 0x0020: 8010 05a8 5a02 0000 0101 080a 1401 7aae ....Z.........z. 0x0030: 1eef f1df 2a20 3120 4645 5443 4820 2855 ....*.1.FETCH.(U 0x0040: 4944 2032 2046 4c41 4753 2028 5c52 6563 ID.2.FLAGS.(\Rec 0x0050: 656e 7429 2049 4e54 4552 4e41 4c44 4154 ent).INTERNALDAT 0x0060: 4520 2230 372d 4465 632d 3230 3034 2031 E."07-Dec-2004.1 0x0070: 343a 3432 3a34 3320 2d30 3630 3022 2052 4:42:43.-0600".R 0x0080: 4643 3832 322e 5349 5a45 2031 3836 3120 FC822.SIZE.1861. 0x0090: 424f 4459 5b5d 3c30 3e20 7b31 3836 317d BODY[]<0>.{1861} 0x00a0: 0d0a 5265 7475 726e 2d50 6174 683a 203c ..Return-Path:.< 0x00b0: 7563 735f 7768 6240 7368 7375 2e65 6475 ucs_whb(a)shsu.edu 0x00c0: 3e0d 0a52 6563 6569 7665 643a 2066 726f >..Received:.fro 0x00d0: 6d20 756e 786d 6169 6c2e 7368 7375 2e65 m.unxmail.shsu.e 0x00e0: 6475 2028 756e 786d 6169 6c2e 7368 7375 du.(unxmail.shsu 0x00f0: 2e65 6475 205b 3135 382e 3133 352e 312e .edu.[158.135.1. 0x0100: 3533 5d29 0d0a 0962 7920 6162 312d 312d 53])...by.ab1-1- 0x0110: 3431 2e73 6873 752e 6564 7520 2838 2e31 41.shsu.edu.(8.1 0x0120: 332e 312f 382e 3133 2e31 2920 7769 7468 3.1/8.13.1).with 0x0130: 2045 534d 5450 2069 6420 6942 374b 6768 .ESMTP.id.iB7Kgh 0x0140: 4246 3032 3632 3738 0d0a 0966 6f72 203c BF026278...for.< 0x0150: 7769 6c6c 7465 7374 4061 6231 2d31 2d34 willtest@ab1-1-4 0x0160: 312e 7368 7375 2e65 6475 3e3b 2054 7565 1.shsu.edu>;.Tue 0x0170: 2c20 3720 4465 6320 3230 3034 2031 343a ,.7.Dec.2004.14: 0x0180: 3432 3a34 3320 2d30 3630 300d 0a52 6563 42:43.-0600..Rec 0x0190: 6569 7665 643a 2066 726f 6d20 3135 382e eived:.from.158. 0x01a0: 3133 352e 302e 3734 2028 5b31 3538 2e31 135.0.74.([158.1 0x01b0: 3335 2e30 2e37 345d 290d 0a09 2861 7574 35.0.74])...(aut 0x01c0: 6865 6e74 6963 6174 6564 2062 6974 733d henticated.bits= 0x01d0: 3029 0d0a 0962 7920 756e 786d 6169 6c2e 0)...by.unxmail. 0x01e0: 7368 7375 2e65 6475 2028 382e 3132 2e31 shsu.edu.(8.12.1 0x01f0: 312f 382e 3132 2e31 3129 2077 6974 6820 1/8.12.11).with. 0x0200: 4553 4d54 5020 6964 2069 4237 4b67 7238 ESMTP.id.iB7Kgr8 0x0210: 7530 3032 3131 390d 0a09 2876 6572 7369 u002119...(versi 0x0220: 6f6e 3d54 4c53 7631 2f53 534c 7633 2063 on=TLSv1/SSLv3.c 0x0230: 6970 6865 723d 5243 342d 4d44 3520 6269 ipher=RC4-MD5.bi 0x0240: 7473 3d31 3238 2076 6572 6966 793d 4e4f ts=128.verify=NO 0x0250: 290d 0a09 666f 7220 3c77 696c 6c74 6573 )...for.<willtes 0x0260: 7440 7475 726e 6970 2e73 6873 752e 6564 t(a)turnip.shsu.ed 0x0270: 753e 3b20 5475 652c 2037 2044 6563 2032 u>;.Tue,.7.Dec.2 0x0280: 3030 3420 3134 3a34 323a 3533 202d 3036 004.14:42:53.-06 0x0290: 3030 0d0a 5375 626a 6563 743a 2074 6573 00..Subject:.tes 0x02a0: 740d 0a46 726f 6d3a 2057 696c 6c20 4265 t..From:.Will.Be 0x02b0: 6e64 696e 6720 3c75 6373 5f77 6862 4073 nding.<ucs_whb@s 0x02c0: 6873 752e 6564 753e 0d0a 5265 706c 792d hsu.edu>..Reply- 0x02d0: 546f 3a20 7563 735f 7768 6240 7368 7375 To:.ucs_whb@shsu 0x02e0: 2e65 6475 0d0a 546f 3a20 7769 6c6c 7465 .edu..To:.willte 0x02f0: 7374 4061 6231 2d31 2d34 312e 7368 7375 st(a)ab1-1-41.shsu 0x0300: 2e65 6475 0d0a 436f 6e74 656e 742d 5479 .edu..Content-Ty 0x0310: 7065 3a20 6d75 6c74 6970 6172 742f 7369 pe:.multipart/si 0x0320: 676e 6564 3b20 6d69 6361 6c67 3d70 6770 gned;.micalg=pgp 0x0330: 2d73 6861 313b 2070 726f 746f 636f 6c3d -sha1;.protocol= 0x0340: 2261 7070 6c69 6361 7469 6f6e 2f70 6770 "application/pgp 0x0350: 2d73 6967 6e61 7475 7265 223b 2062 6f75 -signature";.bou 0x0360: 6e64 6172 793d 223d 2d4e 684c 712f 622b ndary="=-NhLq/b+ 0x0370: 375a 6938 5247 5234 7355 706f 6722 0d0a 7Zi8RGR4sUpog".. 0x0380: 4f72 6761 6e69 7a61 7469 6f6e 3a20 5361 Organization:.Sa 0x0390: 6d20 486f 7573 746f 6e20 5374 6174 6520 m.Houston.State. 0x03a0: 556e 6976 6572 7369 7479 0d0a 4461 7465 University..Date 0x03b0: 3a20 5475 652c 2030 3720 4465 6320 3230 :.Tue,.07.Dec.20 0x03c0: 3034 2031 343a 3432 3a30 3720 2d30 3630 04.14:42:07.-060 0x03d0: 300d 0a4d 6573 7361 6765 2d49 643a 203c 0..Message-Id:.< 0x03e0: 3131 3032 3435 3231 3237 2e37 3435 332e 1102452127.7453. 0x03f0: 3131 2e63 616d 656c 406c 6f63 616c 686f 11.camel@localho 0x0400: 7374 2e6c 6f63 616c 646f 6d61 696e 3e0d st.localdomain>. 0x0410: 0a4d 696d 652d 5665 7273 696f 6e3a 2031 .Mime-Version:.1 0x0420: 2e30 0d0a 582d 4d61 696c 6572 3a20 4576 .0..X-Mailer:.Ev 0x0430: 6f6c 7574 696f 6e20 322e 302e 3220 2832 olution.2.0.2.(2 0x0440: 2e30 2e32 2d33 2920 0d0a 582d 5348 5355 .0.2-3)...X-SHSU 0x0450: 2d4d 6169 6c53 6361 6e6e 6572 2d49 6e66 -MailScanner-Inf 0x0460: 6f72 6d61 7469 6f6e 3a20 5361 6d20 486f ormation:.Sam.Ho 0x0470: 7573 746f 6e20 5374 6174 6520 556e 6976 uston.State.Univ 0x0480: 6572 7369 7479 0d0a 582d 5348 5355 2d4d ersity..X-SHSU-M 0x0490: 6169 6c53 6361 6e6e 6572 3a20 466f 756e ailScanner:.Foun 0x04a0: 6420 746f 2062 6520 636c 6561 6e0d 0a58 d.to.be.clean..X 0x04b0: 2d53 4853 552d 4d61 696c 5363 616e 6e65 -SHSU-MailScanne 0x04c0: 722d 5370 616d 4368 6563 6b3a 206e 6f74 r-SpamCheck:.not 0x04d0: 2073 7061 6d2c 2053 7061 6d41 7373 6173 .spam,.SpamAssas 0x04e0: 7369 6e20 2873 636f 7265 3d2d 302e 3030 sin.(score=-0.00 0x04f0: 312c 0d0a 0972 6571 7569 7265 6420 352e 1,...required.5. 0x0500: 352c 2061 7574 6f6c 6561 726e 3d6e 6f74 5,.autolearn=not 0x0510: 2073 7061 6d2c 2042 4159 4553 5f30 3020 .spam,.BAYES_00. 0x0520: 2d30 2e30 3029 0d0a 582d 4d61 696c 5363 -0.00)..X-MailSc 0x0530: 616e 6e65 722d 4672 6f6d 3a20 7563 735f anner-From:.ucs_ 0x0540: 7768 6240 7368 7375 2e65 6475 0d0a 582d whb@shsu.edu..X- 0x0550: 494d 4150 6261 7365 3a20 3131 3032 3433 IMAPbase:.110243 0x0560: 3936 3037 2032 0d0a 5374 6174 7573 3a20 9607.2..Status:. 0x0570: 4f0d 0a58 2d55 4944 3a20 320d 0a43 6f6e O..X-UID:.2..Con 0x0580: 7465 6e74 2d4c 656e 6774 683a 2034 3632 tent-Length:.462 0x0590: 0d0a 582d 4b65 7977 6f72 6473 3a20 2020 ..X-Keywords:... 0x05a0: 2020 2020 2020 2020 2020 2020 2020 2020 ................ 0x05b0: 2020 2020 2020 2020 2020 2020 2020 2020 ................ 0x05c0: 2020 2020 2020 2020 2020 2020 2020 2020 ................ 0x05d0: 2020 2020 2020 2020 2020 2020 ............ 14:43:17.998255 IP ab1-1-41.shsu.edu.imap > noctis.shsu.edu.61359: P 1604:2156(552) ack 128 win 1448 <nop,nop,timestamp 335641262 519041503> 0x0000: 4500 025c 73bb 4000 4006 70ad 9e87 0b29 E..\s.@.@.p....) 0x0010: 9e87 0bfc 008f efaf fc30 e3b6 a87e eec8 .........0...~.. 0x0020: 8018 05a8 5682 0000 0101 080a 1401 7aae ....V.........z. 0x0030: 1eef f1df 2020 2020 2020 2020 2020 2020 ................ 0x0040: 2020 2020 2020 2020 2020 2020 2020 2020 ................ 0x0050: 2020 2020 2020 2020 200d 0a0d 0a0d 0a2d ...............- 0x0060: 2d3d 2d4e 684c 712f 622b 375a 6938 5247 -=-NhLq/b+7Zi8RG 0x0070: 5234 7355 706f 670d 0a43 6f6e 7465 6e74 R4sUpog..Content 0x0080: 2d54 7970 653a 2074 6578 742f 706c 6169 -Type:.text/plai 0x0090: 6e0d 0a43 6f6e 7465 6e74 2d54 7261 6e73 n..Content-Trans 0x00a0: 6665 722d 456e 636f 6469 6e67 3a20 7175 fer-Encoding:.qu 0x00b0: 6f74 6564 2d70 7269 6e74 6162 6c65 0d0a oted-printable.. 0x00c0: 0d0a 0d0a 0d0a 2d2d 3d2d 4e68 4c71 2f62 ......--=-NhLq/b 0x00d0: 2b37 5a69 3852 4752 3473 5570 6f67 0d0a +7Zi8RGR4sUpog.. 0x00e0: 436f 6e74 656e 742d 5479 7065 3a20 6170 Content-Type:.ap 0x00f0: 706c 6963 6174 696f 6e2f 7067 702d 7369 plication/pgp-si 0x0100: 676e 6174 7572 653b 206e 616d 653d 7369 gnature;.name=si 0x0110: 676e 6174 7572 652e 6173 630d 0a43 6f6e gnature.asc..Con 0x0120: 7465 6e74 2d44 6573 6372 6970 7469 6f6e tent-Description 0x0130: 3a20 5468 6973 2069 7320 6120 6469 6769 :.This.is.a.digi 0x0140: 7461 6c6c 7920 7369 676e 6564 206d 6573 tally.signed.mes 0x0150: 7361 6765 2070 6172 740d 0a0d 0a2d 2d2d sage.part....--- 0x0160: 2d2d 4245 4749 4e20 5047 5020 5349 474e --BEGIN.PGP.SIGN 0x0170: 4154 5552 452d 2d2d 2d2d 0d0a 5665 7273 ATURE-----..Vers 0x0180: 696f 6e3a 2047 6e75 5047 2076 312e 322e ion:.GnuPG.v1.2. 0x0190: 3620 2847 4e55 2f4c 696e 7578 290d 0a0d 6.(GNU/Linux)... 0x01a0: 0a69 4438 4442 5142 4274 6857 6635 362b .iD8DBQBBthWf56+ 0x01b0: 5976 5377 624d 7277 5241 6a56 7941 4a30 YvSwbMrwRAjVyAJ0 0x01c0: 5472 446a 5466 3373 5846 7645 5430 4538 TrDjTf3sXFvET0E8 0x01d0: 4872 504f 4444 3742 6938 7743 6773 4955 HrPODD7Bi8wCgsIU 0x01e0: 420d 0a32 7469 4d62 4654 5245 3949 7261 B..2tiMbFTRE9Ira 0x01f0: 4436 4647 385a 6a77 6851 3d0d 0a3d 4455 D6FG8ZjwhQ=..=DU 0x0200: 7133 0d0a 2d2d 2d2d 2d45 4e44 2050 4750 q3..-----END.PGP 0x0210: 2053 4947 4e41 5455 5245 2d2d 2d2d 2d0d .SIGNATURE-----. 0x0220: 0a0d 0a2d 2d3d 2d4e 684c 712f 622b 375a ...--=-NhLq/b+7Z 0x0230: 6938 5247 5234 7355 706f 672d 2d0d 0a29 i8RGR4sUpog--..) 0x0240: 0d0a 4130 3237 204f 4b20 4665 7463 6820 ..A027.OK.Fetch. 0x0250: 636f 6d70 6c65 7465 642e 0d0a completed... 14:43:18.011006 IP noctis.shsu.edu.61359 > ab1-1-41.shsu.edu.imap: . ack 2156 win 65535 <nop,nop,timestamp 519041503 335641262> 0x0000: 4500 0034 adfa 4000 4006 3896 9e87 0bfc E..4..@.@.8..... 0x0010: 9e87 0b29 efaf 008f a87e eec8 fc30 e5de ...).....~...0.. 0x0020: 8010 ffff 1975 0000 0101 080a 1eef f1df .....u.......... 0x0030: 1401 7aae ..z. ********************************************************************************** Tcpdump from the 1.0-test-56 server of failed fetch request: 14:43:43.214921 IP noctis.shsu.edu.61362 > unxmail.shsu.edu.imap: P 177:253(76) ack 608 win 65535 <nop,nop,timestamp 519041530 438977827> 0x0000: 4500 0080 ae0c 4000 4006 422c 9e87 0bfc E.....@.@.B,.... 0x0010: 9e87 0135 efb2 008f 2fa2 46d7 61ef eaee ...5..../.F.a... 0x0020: 8018 ffff b026 0000 0101 080a 1eef f1fa .....&.......... 0x0030: 1a2a 4523 4130 3038 2055 4944 2046 4554 .*E#A008.UID.FET 0x0040: 4348 2032 2028 5549 4420 464c 4147 5320 CH.2.(UID.FLAGS. 0x0050: 494e 5445 524e 414c 4441 5445 2052 4643 INTERNALDATE.RFC 0x0060: 3832 322e 5349 5a45 2042 4f44 592e 5045 822.SIZE.BODY.PE 0x0070: 454b 5b5d 3c30 2e32 3034 3830 3e29 0d0a EK[]<0.20480>).. 14:43:43.228963 IP unxmail.shsu.edu.imap > noctis.shsu.edu.61362: . 608:2056(1448) ack 253 win 1448 <nop,nop,timestamp 438977889 519041530> 0x0000: 4500 05dc acf1 4000 4006 3deb 9e87 0135 E.....@.@.=....5 0x0010: 9e87 0bfc 008f efb2 61ef eaee 2fa2 4723 ........a.../.G# 0x0020: 8010 05a8 368c 0000 0101 080a 1a2a 4561 ....6........*Ea 0x0030: 1eef f1fa 2a20 3120 4645 5443 4820 2842 ....*.1.FETCH.(B 0x0040: 4f44 595b 5d3c 303e 207b 3134 3632 7d0d ODY[]<0>.{1462}. 0x0050: 0a52 6574 7572 6e2d 5061 7468 3a20 3c75 .Return-Path:.<u 0x0060: 6373 5f77 6862 4073 6873 752e 6564 753e cs_whb(a)shsu.edu> 0x0070: 0d0a 5265 6365 6976 6564 3a20 6672 6f6d ..Received:.from 0x0080: 2031 3538 2e31 3335 2e30 2e37 3420 285b .158.135.0.74.([ 0x0090: 3135 382e 3133 352e 302e 3734 5d29 0d0a 158.135.0.74]).. 0x00a0: 0928 6175 7468 656e 7469 6361 7465 6420 .(authenticated. 0x00b0: 6269 7473 3d30 290d 0a09 6279 2075 6e78 bits=0)...by.unx 0x00c0: 6d61 696c 2e73 6873 752e 6564 7520 2838 mail.shsu.edu.(8 0x00d0: 2e31 322e 3131 2f38 2e31 322e 3131 2920 .12.11/8.12.11). 0x00e0: 7769 7468 2045 534d 5450 2069 6420 6942 with.ESMTP.id.iB 0x00f0: 374b 6830 4f45 3030 3233 3736 0d0a 0928 7Kh0OE002376...( 0x0100: 7665 7273 696f 6e3d 544c 5376 312f 5353 version=TLSv1/SS 0x0110: 4c76 3320 6369 7068 6572 3d52 4334 2d4d Lv3.cipher=RC4-M 0x0120: 4435 2062 6974 733d 3132 3820 7665 7269 D5.bits=128.veri 0x0130: 6679 3d4e 4f29 0d0a 0966 6f72 203c 7769 fy=NO)...for.<wi 0x0140: 6c6c 7465 7374 4073 6873 752e 6564 753e lltest(a)shsu.edu> 0x0150: 3b20 5475 652c 2037 2044 6563 2032 3030 ;.Tue,.7.Dec.200 0x0160: 3420 3134 3a34 333a 3031 202d 3036 3030 4.14:43:01.-0600 0x0170: 0d0a 5375 626a 6563 743a 2074 6573 740d ..Subject:.test. 0x0180: 0a46 726f 6d3a 2057 696c 6c20 4265 6e64 .From:.Will.Bend 0x0190: 696e 6720 3c75 6373 5f77 6862 4073 6873 ing.<ucs_whb@shs 0x01a0: 752e 6564 753e 0d0a 5265 706c 792d 546f u.edu>..Reply-To 0x01b0: 3a20 7563 735f 7768 6240 7368 7375 2e65 :.ucs_whb@shsu.e 0x01c0: 6475 0d0a 546f 3a20 7769 6c6c 7465 7374 du..To:.willtest 0x01d0: 4073 6873 752e 6564 750d 0a43 6f6e 7465 @shsu.edu..Conte 0x01e0: 6e74 2d54 7970 653a 206d 756c 7469 7061 nt-Type:.multipa 0x01f0: 7274 2f73 6967 6e65 643b 206d 6963 616c rt/signed;.mical 0x0200: 673d 7067 702d 7368 6131 3b20 7072 6f74 g=pgp-sha1;.prot 0x0210: 6f63 6f6c 3d22 6170 706c 6963 6174 696f ocol="applicatio 0x0220: 6e2f 7067 702d 7369 676e 6174 7572 6522 n/pgp-signature" 0x0230: 3b20 626f 756e 6461 7279 3d22 3d2d 5844 ;.boundary="=-XD 0x0240: 5631 3663 3368 3745 5752 7169 4a33 654c V16c3h7EWRqiJ3eL 0x0250: 6e68 220d 0a4f 7267 616e 697a 6174 696f nh"..Organizatio 0x0260: 6e3a 2053 616d 2048 6f75 7374 6f6e 2053 n:.Sam.Houston.S 0x0270: 7461 7465 2055 6e69 7665 7273 6974 790d tate.University. 0x0280: 0a44 6174 653a 2054 7565 2c20 3037 2044 .Date:.Tue,.07.D 0x0290: 6563 2032 3030 3420 3134 3a34 323a 3134 ec.2004.14:42:14 0x02a0: 202d 3036 3030 0d0a 4d65 7373 6167 652d .-0600..Message- 0x02b0: 4964 3a20 3c31 3130 3234 3532 3133 342e Id:.<1102452134. 0x02c0: 3734 3533 2e31 332e 6361 6d65 6c40 6c6f 7453.13.camel@lo 0x02d0: 6361 6c68 6f73 742e 6c6f 6361 6c64 6f6d calhost.localdom 0x02e0: 6169 6e3e 0d0a 4d69 6d65 2d56 6572 7369 ain>..Mime-Versi 0x02f0: 6f6e 3a20 312e 300d 0a58 2d4d 6169 6c65 on:.1.0..X-Maile 0x0300: 723a 2045 766f 6c75 7469 6f6e 2032 2e30 r:.Evolution.2.0 0x0310: 2e32 2028 322e 302e 322d 3329 200d 0a58 .2.(2.0.2-3)...X 0x0320: 2d53 4853 552d 4d61 696c 5363 616e 6e65 -SHSU-MailScanne 0x0330: 722d 496e 666f 726d 6174 696f 6e3a 2053 r-Information:.S 0x0340: 616d 2048 6f75 7374 6f6e 2053 7461 7465 am.Houston.State 0x0350: 2055 6e69 7665 7273 6974 790d 0a58 2d53 .University..X-S 0x0360: 4853 552d 4d61 696c 5363 616e 6e65 723a HSU-MailScanner: 0x0370: 2046 6f75 6e64 2074 6f20 6265 2063 6c65 .Found.to.be.cle 0x0380: 616e 0d0a 582d 5348 5355 2d4d 6169 6c53 an..X-SHSU-MailS 0x0390: 6361 6e6e 6572 2d53 7061 6d43 6865 636b canner-SpamCheck 0x03a0: 3a20 6e6f 7420 7370 616d 2c20 5370 616d :.not.spam,.Spam 0x03b0: 4173 7361 7373 696e 2028 7363 6f72 653d Assassin.(score= 0x03c0: 2d30 2e30 3031 2c0d 0a09 7265 7175 6972 -0.001,...requir 0x03d0: 6564 2035 2e35 2c20 6175 746f 6c65 6172 ed.5.5,.autolear 0x03e0: 6e3d 6e6f 7420 7370 616d 2c20 4241 5945 n=not.spam,.BAYE 0x03f0: 535f 3030 202d 302e 3030 290d 0a58 2d4d S_00.-0.00)..X-M 0x0400: 6169 6c53 6361 6e6e 6572 2d46 726f 6d3a ailScanner-From: 0x0410: 2075 6373 5f77 6862 4073 6873 752e 6564 .ucs_whb(a)shsu.ed 0x0420: 750d 0a0d 0a0d 0a2d 2d3d 2d58 4456 3136 u......--=-XDV16 0x0430: 6333 6837 4557 5271 694a 3365 4c6e 680d c3h7EWRqiJ3eLnh. 0x0440: 0a43 6f6e 7465 6e74 2d54 7970 653a 2074 .Content-Type:.t 0x0450: 6578 742f 706c 6169 6e0d 0a43 6f6e 7465 ext/plain..Conte 0x0460: 6e74 2d54 7261 6e73 6665 722d 456e 636f nt-Transfer-Enco 0x0470: 6469 6e67 3a20 7175 6f74 6564 2d70 7269 ding:.quoted-pri 0x0480: 6e74 6162 6c65 0d0a 0d0a 0d0a 0d0a 2d2d ntable........-- 0x0490: 3d2d 5844 5631 3663 3368 3745 5752 7169 =-XDV16c3h7EWRqi 0x04a0: 4a33 654c 6e68 0d0a 436f 6e74 656e 742d J3eLnh..Content- 0x04b0: 5479 7065 3a20 6170 706c 6963 6174 696f Type:.applicatio 0x04c0: 6e2f 7067 702d 7369 676e 6174 7572 653b n/pgp-signature; 0x04d0: 206e 616d 653d 7369 676e 6174 7572 652e .name=signature. 0x04e0: 6173 630d 0a43 6f6e 7465 6e74 2d44 6573 asc..Content-Des 0x04f0: 6372 6970 7469 6f6e 3a20 5468 6973 2069 cription:.This.i 0x0500: 7320 6120 6469 6769 7461 6c6c 7920 7369 s.a.digitally.si 0x0510: 676e 6564 206d 6573 7361 6765 2070 6172 gned.message.par 0x0520: 740d 0a0d 0a2d 2d2d 2d2d 4245 4749 4e20 t....-----BEGIN. 0x0530: 5047 5020 5349 474e 4154 5552 452d 2d2d PGP.SIGNATURE--- 0x0540: 2d2d 0d0a 5665 7273 696f 6e3a 2047 6e75 --..Version:.Gnu 0x0550: 5047 2076 312e 322e 3620 2847 4e55 2f4c PG.v1.2.6.(GNU/L 0x0560: 696e 7578 290d 0a0d 0a69 4438 4442 5142 inux)....iD8DBQB 0x0570: 4274 6857 6d35 362b 5976 5377 624d 7277 BthWm56+YvSwbMrw 0x0580: 5241 6d38 6741 4b43 4d38 6239 6439 4734 RAm8gAKCM8b9d9G4 0x0590: 7a77 6945 5568 7468 516d 6b75 2b6e 7044 zwiEUhthQmku+npD 0x05a0: 4556 4143 6778 4933 590d 0a36 4961 4f45 EVACgxI3Y..6IaOE 0x05b0: 2f4f 5430 4d69 4374 464a 4f4e 4964 2b67 /OT0MiCtFJONId+g 0x05c0: 356f 3d0d 0a3d 456a 6755 0d0a 2d2d 2d2d 5o=..=EjgU..---- 0x05d0: 2d45 4e44 2050 4750 2053 4947 -END.PGP.SIG 14:43:43.228991 IP unxmail.shsu.edu.imap > noctis.shsu.edu.61362: P 2056:2209(153) ack 253 win 1448 <nop,nop,timestamp 438977889 519041530> 0x0000: 4500 00cd acf3 4000 4006 42f8 9e87 0135 E.....@.@.B....5 0x0010: 9e87 0bfc 008f efb2 61ef f096 2fa2 4723 ........a.../.G# 0x0020: 8018 05a8 2118 0000 0101 080a 1a2a 4561 ....!........*Ea 0x0030: 1eef f1fa 4e41 5455 5245 2d2d 2d2d 2d0d ....NATURE-----. 0x0040: 0a0d 0a2d 2d3d 2d58 4456 3136 6333 6837 ...--=-XDV16c3h7 0x0050: 4557 5271 694a 3365 4c6e 682d 2d0d 0a20 EWRqiJ3eLnh--... 0x0060: 5549 4420 3220 464c 4147 5320 285c 5265 UID.2.FLAGS.(\Re 0x0070: 6365 6e74 2920 494e 5445 524e 414c 4441 cent).INTERNALDA 0x0080: 5445 2022 3037 2d44 6563 2d32 3030 3420 TE."07-Dec-2004. 0x0090: 3134 3a34 333a 3032 202d 3036 3030 2220 14:43:02.-0600". 0x00a0: 5246 4338 3232 2e53 495a 4520 3134 3632 RFC822.SIZE.1462 0x00b0: 290d 0a41 3030 3820 4f4b 2046 6574 6368 )..A008.OK.Fetch 0x00c0: 2063 6f6d 706c 6574 6564 2e0d 0a .completed... 14:43:43.233988 IP noctis.shsu.edu.61362 > unxmail.shsu.edu.imap: P 253:266(13) ack 2209 win 65535 <nop,nop,timestamp 519041530 438977889> 0x0000: 4500 0041 ae0d 4000 4006 426a 9e87 0bfc E..A..@.@.Bj.... 0x0010: 9e87 0135 efb2 008f 2fa2 4723 61ef f12f ...5..../.G#a../ 0x0020: 8018 ffff 736d 0000 0101 080a 1eef f1fa ....sm.......... 0x0030: 1a2a 4561 4130 3039 204c 4f47 4f55 540d .*EaA009.LOGOUT. 0x0040: 0a . 14:43:43.242948 IP noctis.shsu.edu.61362 > unxmail.shsu.edu.imap: F 266:266(0) ack 2209 win 65535 <nop,nop,timestamp 519041530 438977889> 0x0000: 4500 0034 ae0e 4000 4006 4276 9e87 0bfc E..4..@.@.Bv.... 0x0010: 9e87 0135 efb2 008f 2fa2 4730 61ef f12f ...5..../.G0a../ 0x0020: 8011 ffff 01d4 0000 0101 080a 1eef f1fa ................ 0x0030: 1a2a 4561 .*Ea 14:43:43.251385 IP unxmail.shsu.edu.imap > noctis.shsu.edu.61362: P 2209:2255(46) ack 267 win 1448 <nop,nop,timestamp 438977911 519041530> 0x0000: 4500 0062 acf5 4000 4006 4361 9e87 0135 E..b..@.@.Ca...5 0x0010: 9e87 0bfc 008f efb2 61ef f12f 2fa2 4731 ........a..//.G1 0x0020: 8018 05a8 8954 0000 0101 080a 1a2a 4577 .....T.......*Ew 0x0030: 1eef f1fa 2a20 4259 4520 4c6f 6767 696e ....*.BYE.Loggin 0x0040: 6720 6f75 740d 0a41 3030 3920 4f4b 204c g.out..A009.OK.L 0x0050: 6f67 6f75 7420 636f 6d70 6c65 7465 642e ogout.completed. 0x0060: 0d0a .. 14:43:43.251720 IP noctis.shsu.edu.61362 > unxmail.shsu.edu.imap: R 799164209:799164209(0) win 0 0x0000: 4500 0028 ae0f 4000 4006 4281 9e87 0bfc E..(..@.@.B..... 0x0010: 9e87 0135 efb2 008f 2fa2 4731 0000 0000 ...5..../.G1.... 0x0020: 5004 0000 fe8b 0000 5555 5555 5555 P.......UUUUUU

1 0

[Dovecot] problems with eudora (2)
by Enrique Pedraza 08 Dec '04

08 Dec '04

ah, dovecot version is dovecot-0.99.12-1.1.fc2.rf. tx Enrique Pedraza Valiente Formador en Lenguajes Avanzados y Nuevas Tecnologías cell: +34 678 51 75 19 http://epedraza.com

1 0

[Dovecot] Lost BODY message
by Tom Allison 08 Dec '04

08 Dec '04

DEBIAN package information: ii dovecot-common 0.99.11-3 ii dovecot-imapd 0.99.11-3 ii bogofilter 0.93.1-1 Apologies for cross-posting, but I think the problem lies somewhere in here. Maybe someone can tell me something useful. Now, I've confirmed the following: I received a mail message that was not spam, of size 2132 originally. clamav scanned it and bumped the size up to 2356 (added headers) ls -l shows it at 1019. The message file (maildir) does not show any BODY. I didn't have my procmail logging on VERBOSE=yes at this time which is a real bummer. Nothing else shows up in the syslog or other logs. As near as I can tell, the following happened: postfix delivered the email to the procmail script in good shape. Now, either procmail or dovecot got goofy on this one. I'm also running bogofilter in the dovecot script, but there's nothing in the procmail log to indicate a problem (logging would have helped!). But the bogofilter database doesn't show any signs of corruption. Somewhere between the interplay of procmail, bogofilter, dovecot things went wrong. I've increased all the logging that I can to watch for the next event. BTW - how can I increase the verbosity of dovecot while staying in daemon mode?

2 1

Re: [Dovecot] Problem with dovecot on home LAN
by Timothy Murphy 08 Dec '04

08 Dec '04

On Tuesday 07 December 2004 15:28, David Sheryn wrote: > > With fetchmail I get the error message: > > ============================================ > > [tim@william ~]$ fetchmail alfred > > fetchmail: Server CommonName mismatch: localhost.localdomain != alfred > > fetchmail: Server CommonName mismatch: localhost.localdomain != alfred > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > This would appear to be you problem. You have an identity crisis > somewhere. Either your laptop or you dektop (or both) are confused as to > their (LAN, i.e. IP) network identity (note that this has nothing to do > with UUCP -- unless, of course, you are attempting to run UUCP over IP > which would be ill-advised.) > > It's not at all obvious where the misconfig lies, but I'd start with host > files / interface configs. I'm sure you are right that this is where the problem lies. Unfortunately I don't know what the solution is. There is no "identity crisis" normally, as I ssh from one machine to the other with no problem, and eg keep a yum repository on the desktop which I use to update Fedora-3 on the small number of machines on my two little LANs (Ethernet and WiFi). I googled for this error "Server CommonName mismatch" and found dozens fo hits, but none of them seemed to suggest a concrete solution. What slightly puzzles me is that dozens of people must be using dovecot for more or less the purpose I envisage - otherwise what are they using it for - so my little problem must have arisen many times before. -- 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] Problem with dovecot on home LAN
by Timothy Murphy 07 Dec '04

07 Dec '04

At present I get email directly on my laptop in /var/spool/mail/* through uucp. I'd like to get the email in the same directory on my desktop (alfred), and then run a mail server on the destop and collect the email on my laptop (william) (or on other computers on my two little home LANs, ethernet and WiFi). I was advised that dovecot was a good imap server for this purpose (I tried cyrus-imapd, but decided it was too complicated), so I'm running dovecot on alfred (my desktop), with the following /etc/dovecot.conf (minus comments): ============================================ imap_listen = * pop3_listen = * login_dir = /var/run/dovecot-login login = imap login = pop3 default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root auth_verbose = yes ============================================ I am able to access my desktop with telnet from my laptop: ============================================ [tim@william ~]$ telnet alfred 143 Trying 192.168.1.1... Connected to alfred. Escape character is '^]'. * OK dovecot ready. x login tim <password> x OK Logged in. ^] telnet> quit Connection closed. ============================================ Unfortunately, neither fetchmail not KMail on my laptop seem able to retrieve mail from my desktop. With fetchmail I get the error message: ============================================ [tim@william ~]$ fetchmail alfred fetchmail: Server CommonName mismatch: localhost.localdomain != alfred fetchmail: Server CommonName mismatch: localhost.localdomain != alfred 10 messages for tim at alfred. reading message tim@alfred.murphy.ie:1 of 10 (765 header octets) fetchmail: fetchmail: getaddrinfo(localhost.smtp) fetchmail: SMTP connect to localhost failed fetchmail: SMTP transaction error while fetching from alfred fetchmail: Query status=10 (SMTP) ============================================ My .fetchmailrc on william reads ============================================ poll alfred proto IMAP user "tim" password "whatever" ============================================ I have no better luck trying to retrieve mail with KMail on the laptop, after adding the following entry to KMail=>Settings=>Configure KMail=>Network=>Receiving ============================================== Name: dovecot Login: tim Password: <password> Host: alfred Port: 143 Prefix to folders: /var/spool/mail/ ============================================== (I also tried with "Prefix to folders:" empty.) When I start KMail on william I get the message "Checking account dovecot for new mail", but no mail comes over, and I see no error in the log files on either machine (although I may have missed something there). I should say that I am running Fedora-3 with all programs up-to-date. Apologies for the long message; any suggestions of 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

4 6

[Dovecot] Assert in mech.c
by Andrew Hutchings 07 Dec '04

07 Dec '04

Hi guys, Seems to be my week for mailing :) I am getting the following in my mail log: Dec 7 11:54:08 svr21 dovecot: auth(sql8): file mech.c: line 143 (mech_auth_finish): assertion failed: (*requests != request) Is this assert important or can I remove it from my copy of the code? Regards Andrew -- Andrew Hutchings Systems Operator / Developer / Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

2 1

[Dovecot] imaps, certificate and authentification
by jean-Noël Chardron 07 Dec '04

07 Dec '04

hello, first sorry for my poor english I'm doing the migration from UW-imap to Dovecot I have two question about the authentification in the imaps (port 993) process In dovecot .conf I can enable (or disable) the différent port (pop, pops, imap, imaps) and may be restrict the access to the serveur with the ip adresse. Can I configure dovecot in imaps so it permit the access if the certificate is knowing by the server? Actually, this is the process to authenticate in WU-imap on imaps : the client connect to the server through a tunnel SSL (stunnel) and only if stunnel know the certificate, then the client can connect. and more, Is it possible when the client (with a certificate) connect to the serveur with imaps to authenticate the user without prompting the password, so the authentication is throught the certificate ? These are similar functionnality in the apache server with the restriction access to location et authentification with certificate. thanks -- Jean-Noel

2 2

[Dovecot] 0.99.12.1 released
by Timo Sirainen 07 Dec '04

07 Dec '04

The only difference to 0.99.12 is that it now builds without GNU make. I didn't bother to change the version number so it's still 0.99.12 inside the tarball.

1 0

[Dovecot] 0.99.12-1.1.fc1.rf broken?
by alex＠amcms.org 06 Dec '04

06 Dec '04

Hi, I dont know if this is a dovecot problem, or the rpm build, me, or my computer ;) Was wondering if anyone else has been having problems using the 0.99.12-1.1.fc1.rf release from http://dag.wieers.com/packages/dovecot/ My specific problem is this. 1. Dovecot starts 2. You can login using telnet 3. You can issue a select inbox but nothing seems to happen By this stage dovecot is spiraling out of control, using up almost all my tiny cpu's processor, when usually it uses basically nothing. What appears to happen if you look at the logs is this. ======= Dovecot Log ======= dovecot: Dec 06 10:39:48 Error: login: Authentication process 5634 doesn't exist ======= Dovecot Info Log ======= imap-login: Dec 06 12:36:09 Info: Disconnected: Inactivity [127.0.0.1] Then, I noticed that if I tried to log in again I would have multiple dovecot-auth processes churning away at my processor.... I went thru the config file, and the new one with my changes, still the same. I also restarted dovecot several times, having to kill all the processes manually as service dovecot stop didnt seem to work. Is anyone else having this problem? And do they know how to fix it? Im running dovecot on fedora core 1, using mysql for authenticating. Thanks Alex

1 0

[Dovecot] 1.0 test 52 - test 56 upgrade
by Andrew Hutchings 06 Dec '04

06 Dec '04

Hi guys, I run a LVS cluster system which holds mail via a NFS server in Maildir format, and indexes on the local hard disks. When upgrading from 52-56 about half the index files failed to work correctly, many killing the server. Not really a problem, I just deleted them. Just thought the developer guys should know. Regards Andrew -- Andrew Hutchings Systems Operator / Developer / Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 0

[Dovecot] 1.0-test56
by Timo Sirainen 06 Dec '04

06 Dec '04

http://dovecot.org/test/ - Lots of fixes for mmap_disable = yes. It finally seems to be working pretty well. - POP3 idle timeouts changed to 10min I just wrote a simple stress test tool for IMAP and I've had one for POP3 for some months. The IMAP stress test was very helpful in finding out the bugs I fixed today. If anyone wants to try them, they're in: http://dovecot.org/tools/

3 7

[Dovecot] problem with test56
by Cor Bosman 06 Dec '04

06 Dec '04

Hi all, im doing some tests with the test56 release and im seeing some problems with APPEND (may be related to something else, I just see it with APPEND). When I ask someone to move some emails from one mailbox to another, after some messages (seemingly random), the client experiences a 'hang'. When tracing the process what seems to happen is that dovecot doesnt send a final OK after that specific email. It's kinda hard to attach a gdb at that point, so for now, maybe someone has seen this also? Cor

3 2

[Dovecot] [PATCH] passdb cache fixes
by Andrey Panin 06 Dec '04

06 Dec '04

Hello, attached patches fixes some bugs in passdb cache. First patch fixes bug which causes passdb cache always return empty scheme for cached passwords. Second patch fixes dovecot-auth crash with passdb cache enabled. I'm not sure that it is proper fix, though. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

1 0

[Dovecot] chained SSL certificates
by Cor Bosman 06 Dec '04

06 Dec '04

Hi all, anyone got dovecot to work with chained SSL certificates? Cor

1 0

[Dovecot] IMAP - many folders?
by piotr＠mallorn.ii.uj.edu.pl 05 Dec '04

05 Dec '04

Hi, I've been reading the list and it seems the answer to my (soon to be asked question) is no, at least with 0.99, but I'll ask to be sure. I have following setup: new mail goes to ~/Mail/Maildir, except for mailing lists which are moved by procmail to ~/Mail/mailing_lists/name, spam which goes to ~/Mail/spam. Read mail is moved by mutt to ~/Mail/read. Everything is in maildir format. Is it possibile to configure dovecot in such a way to allow user to access all those mail folders thorough imap/pop? User can access ~/Mail/Maildir by setting default_mail_env, but so far nothing else. -- Piotrek irc: #debian.pl Mors Drosophilis melanogastribus!

9 17

[Dovecot] (_send_istream): assertion failed:
by Kim Culhan 05 Dec '04

05 Dec '04

This is on FreeBSD 5.3, is this fixed in -test or CVS ? Log message is below.. dovecot: Dec 05 07:48:08 Error: IMAP(kimc): file ostream-file.c: line 643 (_send_istream): assertion failed: (instream->v_offset <= in_size) dovecot: Dec 05 07:48:08 Error: child 42086 (imap) killed with signal 6 -kim __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 3

[Dovecot] 0.99.12-rc1
by Timo Sirainen 05 Dec '04

05 Dec '04

http://dovecot.org/rc/ Just gathered the patches in dovecot.org/patches/ and a few more that I think have been sent to this list before. If there's anything missing, please tell. - Fix memory leaks in LDAP, MySQL and PGSQL userdb/passdb - Fix hanging when parsing mails that have over 4096 bytes in one line (SMTP servers normally don't allow over 1000 bytes so it shouldn't be much of a problem) - FETCH BODYSTRUCTURE sometimes giving a wrong reply (eg. with FETCH (BODYSTRUCTURE RFC822.SIZE) if it wasn't cached) - Never return more than one INBOX in LIST even if there are such files. They don't work anyway and it just confuses clients. - mbox: Don't allow creating INBOX directory by creating/renaming mailboxes under it. They just wouldn't work. - POP3: Don't return PLAIN in SASL list. We don't support initial SASL responses, so it only breaks with most clients that try to use it.

3 6

AW: [Dovecot] newbie question
by Grammes, Carsten 03 Dec '04

03 Dec '04

> If you really want to use maildir, you can have procmail deliver to > maildirs: > (in .procmailrc): > DEFAULT=$HOME/Maildir/ > > Note the trailing slash - that's the kicker. > > Then tell Dovecot to use maildir. > > If you want to mix and match mailbox formats per user, then you'll > need to use an auth database that allows setting this (passwd-file, or > maybe ldap or sql). Thanks, Jon! I think now I get the picture. I will start playing around with procmail and the with dovecot auth options. Carsten

1 0

[Dovecot] newbie question
by Grammes, Carsten 03 Dec '04

03 Dec '04

Hello all, just managed to install dovecot as imap server on a Suse Linux box. Now running fine with mbox format. A question regarding maildir or mbox. The MDA (in my case sendmail, Mlocal = procmail) stores mbox format. Do have to modify the local mailer to store maildir format or does dovecot convert automatically from mbox when I tell dovecot to use maildir format? Thanks, for any hint. Carsten

2 1

[Dovecot] Maildir/mbox on a per-user basis
by Jon Nathan 03 Dec '04

03 Dec '04

Hello, The Wiki indicates that Dovecot can do either mbox or Maildir on a per-user basis: default_mail_env can be overridden in userdb for each user. This works with userdbs supporting the "mail" attribute (eg. passwd-file, SQL, LDAP). How exactly does one do this for passwd-file? Thanks, -Jon -- Jon Nathan jon(a)rupture.net

9 8

[Dovecot] master or client
by Kirill Miazine 03 Dec '04

03 Dec '04

Hello, Dovecot auth protocol 1.0 defines differend command sets for client and master. How can a daemon distinguish a master connection from a client connection? Clients do send CPID and master does not. I have following auth configuration: auth external { socket connect { master { path = /var/state/dovecot/login/master-auth } } } I try to learn my authentication daemon to learn to speak with Dovecot. I fire up my master.py and try to login via pop3 as foo:bar. Below is what my master.py receives from Dovecot (master and client), VERSION commands are not shown: km@thinkpad:/home/km > ./krot/sbin/master.py CPID : ['11915'] CPID : ['11915'] CPID : ['16652'] CPID : ['11915'] AUTH : ['1', 'PLAIN', 'service=POP3', 'secured', 'lip=127.0.0.1', 'rip=127.0.0.1', 'resp=AGZvbwBiYXI='] REQUEST : ['9', '11915', '1'] CPID : ['16652'] (In the above output command and parameters are parsed.) The protocol specification is mentioning a separate SERVICE command in the client's greeting. I can't let my daemon die if the master issues DIE. Why should a server exit when it receives DIE? Can anybody provide an example dialog of an authentication request that is successful and a reques that fails because of a bad password. Thanks, Kirill -- They make a desert and call it peace. -- Tacitus

2 2

[Dovecot] pop3 with lmos results in multiple downloads
by Juerd 03 Dec '04

03 Dec '04

One of our users wants to use POP3 with leave-mail-on-server (LMOS). That's great and works well for most people. But for some reason, they MUA (outlook) downloads messages more than once. As the MUA asks for messages, I'm sure it's Outlook's fault, but I was wondering if there is anything that can be done about this on the servern side, or if anyone knows how to fix Outlook. I'm sending this here, because they report that with non-dovecot servers it does work correctly. They do not want IMAP, because they want to use Outlook, which cannot support both Exchange and IMAP simultaneously. This user has multiple accounts, and only for some of them things go wrong. A temporary fix is to remove the mail from the server once, but after a few more messages arrive, the problem starts all over again. Please help. Regards, Juerd

3 3

[Dovecot] imap: assertion failed
by Kim Culhan 03 Dec '04

03 Dec '04

This error is returned when reading a certain message using Squirrelmail. Any help on tracing the cause of this is greatly appreciated. >From the logs: dovecot: Nov 20 13:00:29 Error: IMAP(kimc): file ostream-file.c: line 643 (_send_istream): assertion failed: (instream->v_offset <= in_size) dovecot: Nov 20 13:00:29 Error: child 27873 (imap) killed with signal6 -kim __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com

2 1

[Dovecot] Problem getting incoming mail to IMAP inbox
by Jeff Sutherland 03 Dec '04

03 Dec '04

I have dovecot-0.99.10.5 on Fedora Core 2 installed and otherwise operating using Maildir format for the folders, Kmail as the email client. Got through all the ssl and other security configuration fine, but have one last problem: I can't read the incoming mail from /var/spool/mail/%u. Tried several 'default_mail_env' settings, including none at all, to no avail. When I try to check in new mail to the inbox, the only messages are "Transmission Complete, no new messages" Tried this setting for example: default_mail_env = maildir:~/Maildir/:INBOX=/var/spool/mail/%u but to no avail. Is something getting cocked up because the folders are all in maildir format and the incoming mail spool is in mbox format? I checked permissions, they seem ok. Kmail can pull the messages in just fine to its local folder inbox, it just seems that dovecot can't read the mail spool file for some reason. All the other maildir folders work fine. ????????? Regards, -Jeff -- Secure your email with Gnu Privacy Guard and Mozilla, the open source cross platform solution for Windows, Linux, and Mac OS X. See http://enigmail.mozdev.org/

2 1

[Dovecot] Cannot list mailbox
by Fawad Halim 03 Dec '04

03 Dec '04

Hi, I have dovecot 0.99.11 on a Linux machine running against a maildir based mailbox. I am getting the following errors in the maillog: Nov 27 23:08:14 fawad3 imap(fawad): file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Nov 27 23:08:14 fawad3 dovecot: child 14202 (imap) killed with signal 6 This happens when the mail reader tries to enumerate the messages in the INBOX. I am able to read the messages whose headers have already been cached by the mail reader. It is also able to read others folders without any problem. This problem has occured before, and I was able to get rid of it by identifying the junk mail message it was dying on. In this case, however, I'm not able to figure out which message is causing it to crash. I am able to read the same maildir in mutt, and Courier IMAP doesn't seem to have trouble with it either. I'd really appreciate if someone could tell me what I can do to get around this problem. Regards -fawad

2 1

[Dovecot] 1.0-test CVS HEAD index problems
by Jim Lawson 03 Dec '04

03 Dec '04

Running current CVS HEAD I get: dovecot: Dec 01 13:27:38 Info: Dovecot v1.0-test52 starting up dovecot: Dec 01 13:33:34 Info: imap-login: Login: jtl [69.162.177.245] dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:42:39 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:42:39 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:42:39 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:43:59 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:43:59 Error: IMAP(jtl): Corrupted index cache file /users/j/t/jtl/.i map/INBOX/dovecot.index.cache: indexid changed dovecot: Dec 01 13:47:24 Error: IMAP(jtl): file mbox-lock.c: line 493 (mbox_lock): asse rtion failed: (lock_type == F_RDLCK || ibox->mbox_lock_type != F_RDLCK) dovecot: Dec 01 13:47:25 Error: child 17528 (imap) killed with signal 6 dovecot: Dec 01 13:47:41 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:50:49 Error: IMAP(jtl): UIDVALIDITY changed (1101926435 -> 110192703 6) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:55:27 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:55:27 Error: IMAP(jtl): UIDVALIDITY changed (1101926435 -> 110192703 6) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:56:15 Info: imap-login: Login: jtl [69.x.x.x] dovecot: Dec 01 13:56:15 Error: IMAP(jtl): UIDVALIDITY changed (1101926435 -> 110192703 6) in mbox file /var/spool/mail/j/t/jtl Using Thunderbird-0.9. Dovecot is running on RHEL 3, on top of Redhat/Sistina GFS (clustered filesystem.) Currently I'm keeping it on one node to avoid possible GFS locking issues. I'm running with mmap_disabled=yes, mbox format. Most of the 1.0-test builds I have done eventually corrupt their index files, and show strange behavior (click on a message in the folder view, and an entirely different message opens... delete three or four messages and expunge, the messages instantly reappear as unseen.). I typically wipe the .imap directories between different builds of Dovecot. I've been following the -test code for a couple of months now, just to see how it does, because we're running UW IMAPd and are excited to have a way to increase the performance of our mail cluster (indexes) without having to move away from mbox. Let me know if there's more information I could provide that would be helpful. Jim

3 4

[Dovecot] Excessive imap_login processes
by Keith Edmunds 02 Dec '04

02 Dec '04

I'm running Dovecot on a very small mail server (never more than six users accessing IMAP, often fewer). I'm seeing the number of imap_login processes grow over time, and right now there are 23. All the "login_process_*" settings in dovecot.conf are commented (ie, at their defaults). Is this a known or expected issue? The version of Dovecot is 0.99.10.8, which I accept is perhaps a little old. Thanks, Keith

2 1

[Dovecot] 1.0-test55
by Timo Sirainen 30 Nov '04

30 Nov '04

http://dovecot.org/test/ Sorry :) The last fix I made a few minutes before test54 release didn't turn out to be exactly correct.

4 4