- dovecot - dovecot.org

[Dovecot] Authors wanted for Linux Magazine
by Markus Feilner 25 Jun '07

25 Jun '07

Hello list, as an editor at the german linux magazine I am looking for an author who would like to write about 5-6 pages on dovecot clustering (as a workshop or presenting a detail of special interest) If you are interested, please send me an email to: <mfeilner(a)linuxnewmedia.de> Mit freundlichen Gruessen - Best Regards, Markus Feilner -- Linux New Media AG, Sueskindstr. 4, 81929 Muenchen, Germany Phone: +49 89 9934 1122, Fax: +49 89 9934 1199 mfeilner(a)linuxnewmedia.de - http://www.linuxnewmedia.de Linux New Media - The Pulse of Linux Lawrence - Malaga - Manchester - Muenchen - Sao Paulo - Timisoara - Warszawa --------------------------------------------------- Sitz der Gesellschaft: Sueskindstrasse 4, 81929 Muenchen Amtsgericht Muenchen: HRB 129161 Vorstand: Rosemarie Schuster, Hermann Plank Aufsichtsratsvorsitzender: Rudolf Strobl

1 0

[Dovecot] Dovecot and Sendmail Working Together . . .
by Eddie Johnson Jr 24 Jun '07

24 Jun '07

I am new to this, I was just given the responsibility Thursday to get Sendmail/SquirrelMail/Dovecot to work in sync. How do I start? iloadmin

2 1

Re: [Dovecot] Dovecot won't stay running
by Gunter Ohrner 22 Jun '07

22 Jun '07

Am Freitag, 22. Juni 2007 schrieb Jon Slater: > You are AWESOME!!! Thank you!!! Mh, I think this is one of the few times I read that someone was actually greatful for a "RTFM" he got... ;) > Jun 22 01:27:56 servername dovecot: Time just moved backwards by 37 > seconds. This might cause a lot of problems, so I'll just kill myself That's bad and may cause a lot of other (and more subtle) troubles than Dovecot committing suicide. I'f your' using something like "ntpdate" to periodically step the time, do not do that but run an ntp server instead which will gradually skew the clock to keep the system's time accurate. Greetings, Gunter -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I would actually distinguish between problems with compiling the kernel, and problems with the kernel after compiling. -- Karol 'sziwan' Kozimor auf der swsusp-Mailingliste +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + PGP-verschlüsselte Mails bevorzugt! + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

1 0

Re: [Dovecot] test program #2: mmaping
by Bill Boebel 22 Jun '07

22 Jun '07

On Wed, June 20, 2007 9:28 pm, Timo Sirainen <tss(a)iki.fi> said: > Attached another test program. I don't expect it to print any errors > with any OS, but I'd like to confirm it for non-Linux SMP kernels. # ./concurrency writing, page size = 4096 4: reading, page size = 4096 3: reading, page size = 4096 2: reading, page size = 4096 1: reading, page size = 4096 0: reading, page size = 4096 Red Hat ES3 (2.4.21-32.0.1.EL) athlon i386

1 0

Re: [Dovecot] Dovecot won't stay running
by Jochen Schulz 22 Jun '07

22 Jun '07

Jon Slater schrieb: > > So I got the same suggestion several times, and I upgraded to Dovecot 1.0.1. > > At 1:27am and again at 5:23am Dovecot stopped running. My cron was able to > restart the service in both instances, but how do I debug why this is > happening? Take a look at http://wiki.dovecot.org. It contains useful instructions for debugging. J.

2 1

Re: [Dovecot] Dovecot won't stay running
by Jon Slater 22 Jun '07

22 Jun '07

So I got the same suggestion several times, and I upgraded to Dovecot 1.0.1. At 1:27am and again at 5:23am Dovecot stopped running. My cron was able to restart the service in both instances, but how do I debug why this is happening? Thanks!!! Jon > -----Original Message----- > From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] > On Behalf Of Jon Slater > Sent: Thursday, June 21, 2007 5:19 PM > To: dovecot(a)dovecot.org > Subject: [Dovecot] Dovecot won't stay running > > This weekend I upgraded my OS from FC4 to FC6. At the same time I > updated > Dovecot from 0.99 to 1.0.0. > > Now, dovecot periodically shuts off. > > It will run fine for several hours then just dies. > > Right now my solution is to run a cron every 5 minutes to see if it’s > still > running, and if not, re-start it. > > I’m also having trouble finding any sort of meaningful logs to tell me > what’s going on. > > Where should I start? > > Thanks in advance! > > Jon > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.9.2/858 - Release Date: > 6/21/2007 > 1:46 PM > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.9.2/858 - Release Date: > 6/21/2007 1:46 PM > No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.4/860 - Release Date: 6/21/2007 5:53 PM

1 0

[Dovecot] Dovecot won't stay running
by Jon Slater 22 Jun '07

22 Jun '07

This weekend I upgraded my OS from FC4 to FC6. At the same time I updated Dovecot from 0.99 to 1.0.0. Now, dovecot periodically shuts off. It will run fine for several hours then just dies. Right now my solution is to run a cron every 5 minutes to see if it’s still running, and if not, re-start it. I’m also having trouble finding any sort of meaningful logs to tell me what’s going on. Where should I start? Thanks in advance! Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.2/858 - Release Date: 6/21/2007 1:46 PM

1 0

Re: [Dovecot] Fwd: LDAP subtree search on AD
by Bruno Puga 22 Jun '07

22 Jun '07

Timo, I have sent this message below before but I didn't saw that it was delivered to you personal email instead to the list, I just see this now, sorry. Because I'm in a hurry I gave up using Dovecot + AD and start using Mysql as my userdb and passdb and things worked perfect until the moment. I have some doubts but I will open a new thread for this. Anyway, if you get some news about this issue I would appreciate to know, if not, that's OK. Many thanks for your help. Bruno. On 6/18/07, Bruno Puga <brpuga(a)gmail.com> wrote: > > Timo, I had set this in the dovecot.conf: > > auth_verbose = yes > auth_debug = yes > auth_debug_passwords = yes > > ########################################################### > ### My dovecot logs shows this using auth_bind = yes and userdn template > ### > > dovecot: 2007-06-17 12:35:52 Warning: Killed with signal 15 > dovecot: 2007-06-17 12:35:53 Info: Dovecot v1.0.0 starting up > dovecot: 2007-06-17 12:37:23 Info: auth(default): client in: AUTH > 1 PLAIN service=IMAP secured lip= 192.168.0.251 rip=192.168.0.251 > resp=AHRlc3RlAHRlc3Rl > dovecot: 2007-06-17 12:37:23 Info: auth(default): ldap(teste,192.168.0.251): > bind: dn=teste > dovecot: 2007-06-17 12:37:23 Info: auth(default): client out: OK > 1 user=teste > dovecot: 2007-06-17 12:37:23 Info: auth(default): master in: REQUEST > 1 31290 1 > dovecot: 2007-06-17 12:37:23 Info: auth(default): ldap(teste,192.168.0.251): > user search: base=DC=tecnicopias01,DC=com,DC=br scope=subtree > filter=(&(objectClass=organizationalPerson)(sAMAccountName=teste)) > fields=info > dovecot: 2007-06-17 12:40:23 Info: imap-login: Disconnected: Inactivity: > user=<teste>, method=PLAIN, rip=192.168.0.251 , lip=192.168.0.251, secured > > dovecot: 2007-06-17 12:52:46 Error: auth(default): ldap(teste, > 192.168.0.251): ldap_search() failed: Operations error > dovecot: 2007-06-17 12:52:46 Info: auth(default): master out: FAIL 1 > dovecot: 2007-06-17 12:52:46 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-17 13:07:46 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-17 13:22:47 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > > As we can see, first dovecot bind correct, but after it open a new > connection as showed in the ngrep output, and without bind try to make the > ldap_search, in that point AD blocks the search saying that for the new > connection opened is necessary a successful bind. > ########################################################### > > ### Now, changing for User database Lookups authenticating with krb5 ### > > dovecot: 2007-06-18 10:14:35 Info: auth(default): client in: AUTH > 1 PLAIN service=IMAP secured lip=192.168.0.251 rip= > 192.168.0.251 resp=AHRlc3RlAHRlc3Rl > dovecot: 2007-06-18 10:14:35 Info: auth(default): pam(teste,192.168.0.251): > lookup service=dovecot > dovecot: 2007-06-18 10:14:35 Info: auth(default): client out: OK > 1 user=teste > dovecot: 2007-06-18 10:14:35 Info: auth(default): master in: REQUEST > 1 32029 1 > dovecot: 2007-06-18 10:14:35 Info: auth(default): ldap(teste,192.168.0.251): > user search: base=DC=tecnicopias01,DC=com,DC=br scope=subtree > filter=(&(objectClass=organizationalPerson)(sAMAccountName=teste)) > fields=info > dovecot: 2007-06-18 10:17:35 Info: imap-login: Disconnected: Inactivity: > user=<teste>, method=PLAIN, rip=192.168.0.251 , lip=192.168.0.251, secured > > dovecot: 2007-06-18 10:29:25 Error: auth(default): ldap(teste, > 192.168.0.251): ldap_search() failed: Operations error > dovecot: 2007-06-18 10:29:25 Info: auth(default): master out: FAIL 1 > dovecot: 2007-06-18 10:29:25 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-18 10:44:26 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-18 10:59:26 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > > ########################################################### > > After some time, the dovecot logs starts logging this last 3 lines saying > it "Can't contact LDAP server", and ngrep shows this: > > ########################################################### > ############# > T 192.168.0.251:49043 -> 192.168.0.11:389 [AP] > 0E...`@....1CN=postfix,CN=Users,DC=tecnicopias01,DC=com,DC=br..post123! > # > T 192.168.0.11:389 -> 192.168.0.251:49043 [AP] > 0........a............ > ### > T 192.168.0.251:49043 -> 192.168.0.11:389 [AP] > 0....B. > ####### > T 192.168.0.251:42083 -> 192.168.0.11:389 [AP] > 0E...`@....1CN=postfix,CN=Users,DC=tecnicopias01,DC=com,DC=br..post123! > # > T 192.168.0.11:389 -> 192.168.0.251:42083 [AP] > 0........a............ > ### > T 192.168.0.251:42083 -> 192.168.0.11:389 [AP] > 0....B. > ####### > T 192.168.0.251:52084 -> 192.168.0.11:389 [AP] > 0E...`@....1CN=postfix,CN=Users,DC=tecnicopias01,DC=com,DC=br..post123! > # > T 192.168.0.11:389 -> 192.168.0.251:52084 [AP] > 0........a............ > # > > Dovecot after a while keep trying to connect to LDAP server without any > requests being sent to server. So it keep logging this line below forever: > > LDAP: ldap_result() failed: Can't contact LDAP server > ########################################################### > > If I change the base to the same location as the user being authenticating > is, the userdb lookup is successfully because he's find at a first > ldap_seach try, and no subtree search is necessary. So again I think dovecot > must not open other connections then that opened at the bind time to make > the subtree search, like postfix do. > > Timo, I'm waiting for your reply. > > Thanks in advance to spent your time to contribute with free software, > Bruno.

1 0

[Dovecot] test program #2: mmaping
by Timo Sirainen 21 Jun '07

21 Jun '07

Attached another test program. I don't expect it to print any errors with any OS, but I'd like to confirm it for non-Linux SMP kernels. (Except for OpenBSD, it doesn't work correctly in it anyway because it doesn't support mixing write()s and mmap())

8 8

[Dovecot] Status update
by Timo Sirainen 21 Jun '07

21 Jun '07

I'm leaving soon and I'll be away until sunday. Sorry about not replying to all mails yet, most of them are somewhat tricky and require some time to reply (other than "I don't know"). The new index code for v1.1 seems to be finally working pretty nicely. After 9 hours of running imaptest I haven't gotten a single error yet. I'll leave it running until I'm back. The new code makes the internal index file design a lot easier to understand. For v1.0 I just wanted to get it working and I didn't dare try to clean up the code, so it was kind of magic sometimes why it worked. :) All that magic is finally gone and I understand completely how everything is supposed to work (and hopefully also how it does work). Most important problem with the new code is that \Recent flags are completely broken. I think they're not completely correctly working in v1.0 either, or at least I'm not sure why they're working even as well as they are now.. Maildir syncing in v1.1 is also a bit bad. For example EXPUNGE command could have to be given twice to get it to work. Again it worked badly with v1.0 also but since the index code worked differently it wasn't visible. Cydir is a pretty nice format for stress testing index code. It's really lightweight so it's practically testing only the index code. Because of it I've found a couple of race conditions in the code that existed also in v1.0 tree (v1.0.2 will fix them). My earlier stress testing with maildir never saw those problems, probably because with maildir there was a lot of other code running as well so the race condition was really unlikely to hit.

1 0