- dovecot - dovecot.org

[Dovecot] starting with daemontools
by Jens Gutzeit 23 Jun '03

23 Jun '03

Hi all, I want to start dovecot through DJBs Daemontools-supervise, is there a configuration option that lets dovecot stay in foreground? best regards, Jens

3 3

[Dovecot] newbie question: alias addresses
by R.Charles Sweeten 23 Jun '03

23 Jun '03

Hello! I looked through the mail archives but did not see how to set up alias addresses. Could someone please put me on the right road. How do I create/implement aliases? and group aliases? Thanks! ~rick........... "There is no spoon. .....<gun-shot>...."

3 3

[Dovecot] new pkgsrc on NetBSD
by tom 23 Jun '03

23 Jun '03

hi all, just updated the pkgsrc to build dovecot-0.99.10-rc2, see http://news.gw.com/netbsd.pkgsrc.changes/27698 for reference. best regards, TOM

1 0

[Dovecot] strange problem
by tom hensel 23 Jun '03

23 Jun '03

hi, running dovecot-0.99.10-rc2 on NetBSD, client is Entourage on MacOS 9.2. sylpheed on NetBSD does not show this behaviour. --snip-- Jun 23 16:28:15 host imap(user): file mail-index.c: line 619 (mail_index_lookup_uid_range): assertion failed: (first_uid > 0 && last_uid > 0) --snap-- any hints? thanks, TOM

2 1

[Dovecot] RFC: PAM service name change?
by Jeremy Katz 23 Jun '03

23 Jun '03

It would be nice for the sake of not conflicting to have the PAM service name not be imap. Especially as the same service name is used for pop as well :) My recommendation would be to use dovecot instead. Any other opinions? Jeremy

3 3

[Dovecot] 0.99.10-rc1
by Timo Sirainen 23 Jun '03

23 Jun '03

Home again. Fixed SSL checking for Redhat 9, I hope. Could someone test if it actually works now? Also fixed a few compiler warnings. If this thing works, I'll just update the NEWS file and call it 0.99.10. http://dovecot.procontrol.fi/rc/ Near future plans include rewriting parts of index handling. At least .tree file will go, I've a _much_ better idea how to replace it. .data file is also too bloaty and it's a bit difficult to add new fields into it. I'd have to figure out some better API to access it. I've also been worrying about locking.. If we want to share indexes between many clients, lock contention will become a problem. For example a "FETCH 1:* BODY[]" could take a long time and index can't be modified while it's being done. I'm not really sure what to do about this.. Probably some more fine graned locking and maybe some kind of transaction log where changes are written if you couldn't get exclusive lock.

3 5

[Dovecot] Dovecot and LDAP problems
by Spectron International, Inc. 22 Jun '03

22 Jun '03

I'm having problems with dovecot and OpenLDAP. I installed both, and configured both. /etc/dovecot-ldap.conf exists and I modified dovecot.conf to have... auth_userdb = ldap /etc/dovecot-ldap.conf auth_passdb = ldap /etc/dovecot-ldap.conf ...but the log displays the following: Jun 19 13:59:15 backup dovecot-auth: Unknown userdb type 'ldap' Jun 19 13:59:15 backup dovecot: Auth process died too early - shutting down Jun 19 13:59:15 backup dovecot: child 4187 (auth) returned error 89 the auth_userdb and auth_passdb seem to be ok, so what am I missing? Faw

4 5

[Dovecot] Bug?
by Steve Gare 20 Jun '03

20 Jun '03

Hi, Been using Dovecot for a few weeks now, must say it's very good.. I've been looking for a 'drop in' replacement for UWImap for ages! :) but just recently It's been giving me a few problem, I haven't tracked down exactly what causes the problem yet (I'm using Apple Mail on OS X 10.2.6) but after a good mail session it keep trying to log in over and over again.. Looking the the log file I find this... Jun 20 15:38:02 neuron imap-login: Login: sgare [IP REMOVED] Jun 20 15:38:02 neuron imap(sgare): file imap-bodystructure.c: line 263 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Jun 20 15:38:02 neuron dovecot: child 6329 (imap) killed with signal 6 Jun 20 15:38:02 neuron imap-login: Login: sgare [IP REMOVED] Jun 20 15:38:02 neuron imap(sgare): file imap-bodystructure.c: line 263 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Jun 20 15:38:02 neuron dovecot: child 6331 (imap) killed with signal 6 Jun 20 15:38:02 neuron imap-login: Login: sgare [IP REMOVED] Jun 20 15:38:03 neuron imap(sgare): file imap-bodystructure.c: line 263 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Jun 20 15:38:03 neuron dovecot: child 6332 (imap) killed with signal 6 Jun 20 15:38:03 neuron imap-login: Login: sgare [IP REMOVED] Jun 20 15:38:03 neuron imap(sgare): file imap-bodystructure.c: line 263 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Jun 20 15:38:03 neuron dovecot: child 6333 (imap) killed with signal 6 Jun 20 15:38:03 neuron imap-login: Login: sgare [IP REMOVED] Cheers, Steve Gare - Xantara.Net -- 0845 123 5707

2 2

[Dovecot] NetBSD pkgsrc maintanance
by tom hensel 20 Jun '03

20 Jun '03

hi all, i've taken over the maintainership of dovecot's pkgsrc on NetBSD - please send me your ideas, questions and comments related to dovecot on NetBSD. FreeBSD's port has currently some more 'features' than the pkgsrc, i'm going to add some of them - any feedback is appreciated. bye, TOM

3 2

[Dovecot] Re: dovecot Digest, Vol 2, Issue 15
by ohp＠pyrenet.fr 19 Jun '03

19 Jun '03

> >Message: 2 >Date: Wed, 18 Jun 2003 13:21:08 +0200 (CEST) >From: Andreas Aardal Hanssen <dovecot(a)andreas.hanssen.name> >Subject: Re: [Dovecot] Multiple auth howto >To: Dovecot mailing list <dovecot(a)procontrol.fi> >Message-ID: > <Pine.LNX.4.44.0306181319060.29812-100000(a)shusaku.troll.no> >Content-Type: TEXT/PLAIN; charset=US-ASCII > >On Wed, 18 Jun 2003 ohp(a)pyrenet.fr wrote: >>> Well, short answer: You can't. Put them all to one place (eg. pgsql), >>> maybe using some automated scripts. I don't know if I should even >>> consider about supporting fallbacking.. >>Hi Timo, Thanks for your answer. >>The reason I came to dovcot is that I thought it was possible. I've benn >>researching this for weeks now. First thought that cyrus would do that, it >>does but though SASL and pam whitch I don't have. >>How difficult would it be to implement a fallback? > >Does this tool do what you want? (checkpassword only though, but I bet you >will find checkpassword compatible authenticators that suit your needs): > >http://www.andreas.hanssen.name/software/multichkpwds.c It surely is interesting bu I'd rather see modules inside the server, see below > >-- >Andreas Aardal Hanssen > > > >------------------------------ >Message: 4 >Date: 18 Jun 2003 15:31:36 +0300 >From: Timo Sirainen <tss(a)iki.fi> >Subject: Re: [Dovecot] Multiple auth howto >To: dovecot(a)procontrol.fi >Message-ID: <1055939496.10262.163.camel@hurina> >Content-Type: text/plain > >On Wed, 2003-06-18 at 14:05, ohp(a)pyrenet.fr wrote: >> > Well, short answer: You can't. Put them all to one place (eg. pgsql), >> > maybe using some automated scripts. I don't know if I should even >> > consider about supporting fallbacking.. >> > >> > >> Hi Timo, Thanks for your answer. >> The reason I came to dovcot is that I thought it was possible. I've benn >> researching this for weeks now. First thought that cyrus would do that, it >> does but though SASL and pam whitch I don't have. >> >> How difficult would it be to implement a fallback? > >Not very. I'm mostly concerned about what happens if the user exists in >both authenticators. I guess normally this shouldn't happen, but you >can't really guarantee that and mistakes happen.. Yes mistakes happen. Why could'nt you (we?) do like proftpd that has a parameter that give the order of authenticators first one wins. That way you could even have the same user as a real and virtual account with differents passwords > >If fallbacking happened only when user isn't found from first >authenticator, that could work a bit more safely, but I'm not sure if I >can know with PAM if check failed because user wasn't found or because >password didn't match. I don't know either. My idea is to get rid of PAM for that's although fantastic on the paper is a Linux thing that I can't even compile here. Regards -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

1 0