- dovecot - dovecot.org

[Dovecot] SSL setup ?
by Marius Stan 01 Oct '04

01 Oct '04

Hello, I'm having treuble setting up a ssl dovecot; here's some info: /etc/xinetd.d/pop3s: service pop3s { disable = no flags = REUSE socket_type = stream wait = no user = root group = root instances = UNLIMITED server = /usr/libexec/dovecot/pop3-login log_type = SYSLOG daemon info } I've setup the certificates, ssl_disable = no, protocols = imap pop3 pop3s ,but if I telnet on my server's port 995, I get the dovecot banner in clear-text. I'm for sure missing something here... Marius

2 1

[Dovecot] [PATCH] NTLM2 support
by Andrey Panin 30 Sep '04

30 Sep '04

Hello, as pointed by Andrew Bartlett NTLM2 authentication support is missing in dovecot. Attached patch adds it. Tested and works for me. Please consider applying. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 1

[Dovecot] Dovecot on Cygwin
by espino＠infomed.sld.cu 30 Sep '04

30 Sep '04

Sorry, guys for the second message. But I forgot something that may be useful. The first dialog, the one who says "cygcrypt-0.dll" is missing, has "dovecot-auth.exe" as title. And the second one, which says "cygwin1.dll" is missing, has "imap-login.exe" as title. Sorry again. ------------------------------------------------- Este mensaje fue enviado usando el servicio de correo en web de Infomed http://webmail.sld.cu

2 1

[Dovecot] dovecot not working with some vpopmail passwords
by radus＠smartpost.ro 30 Sep '04

30 Sep '04

Hello. I tried installing dovecot on a server that relies on vpopmail authentication using $1$ MD5 algorithm and it didn't work. Please fix this for the next release. Attached is a patch, please be carefull with the line wrapping. Radu --- passdb-vpopmail.c.old Thu Feb 20 00:46:51 2003 +++ passdb-vpopmail.c Thu Sep 30 18:58:56 2004 @@ -1,4 +1,4 @@ -/* Copyright (C) 2002-2003 Timo Sirainen */ +/* Copyright (C) 2002-2003 cTimo Sirainen */ /* Thanks to Courier-IMAP for showing how the vpopmail API should be used */ @@ -20,6 +20,7 @@ { char vpop_user[VPOPMAIL_LIMIT], vpop_domain[VPOPMAIL_LIMIT]; struct vqpasswd *vpw; + char *password_crypt; int result; vpw = vpopmail_lookup_vqp(request->user, @@ -44,7 +45,12 @@ } /* verify password */ - result = strcmp(mycrypt(password, vpw->pw_passwd), vpw->pw_passwd) == 0; + + if (strncmp(vpw->pw_passwd, "$1$", 3) == 0) + password_crypt = md5_crypt(password, vpw->pw_passwd); + else password_crypt = crypt(password, vpw->pw_passwd); + + result = strcmp(password_crypt, vpw->pw_passwd) == 0; safe_memset(vpw->pw_passwd, 0, strlen(vpw->pw_passwd)); if (!result) {

1 0

[Dovecot] Dovecot on Cygwin
by espino＠infomed.sld.cu 30 Sep '04

30 Sep '04

I'mt trying to make Dovecot run on Cygwin. I managed to make it compile and register as a service on Windows XP. I had a problem with setrlimit, but I disabled the process size limitation in the config file. Now, when I start the process, either by clicking the start button on the MS Managemente Console or by cygrunsrv -S dovecot, i get to error dialogs saying that the program needs cygcrypt-0.dll and cygwin1.dll. I have both of those libraries on the system but the program doesn't seem to see them. Do any of you have a clue about this? Thanks. ------------------------------------------------- Este mensaje fue enviado usando el servicio de correo en web de Infomed http://webmail.sld.cu

1 0

[Dovecot] Documentation
by Timo Sirainen 30 Sep '04

30 Sep '04

I just wrote two "new user documentation" pages to wiki: http://wiki.dovecot.org/moin.cgi/CompilingSource http://wiki.dovecot.org/moin.cgi/BasicInstall Do you think they are easy enough to understand? Did I miss something? Feel free to edit them directly :) Next should probably come: - Mailbox formats fully explained - Performance tuning

1 0

Re: [Dovecot] Concerned about Dovecot's new NTLM code
by Andrey Panin 30 Sep '04

30 Sep '04

> I'm pleased to see another project increasing compatibility with windows > clients, by the addition of NTLM login support, but I'm a bit worried > about a few implementation details, and hope to offer an alternate > approach. > > I mean no disrespect to those who have implemented to the code so far, > but I feel that the idea of 'everybody re-implement NTLM' is prone to > failure. > > Firstly, to bugs I've noticed by casual inspection of your > implementation: > > - Unicode support is by 'null padding' - there is no real support for > non-ascii characters. Does it really matter ? Do you know many people who use non-ascii characters in their email addresses and passwords ? :) > - NTLM2 (a negotiated scheme to avoid sending the LM response) is > unsupported Did you RTFS ? Or may be I missed something ? > - NTLMSSP is NDR, not 'C struct pushed to the wire', it needs to be > correctly marshaled and unmarshaled. Yes, it's not a C struct, so what ? Where is the actual bug ? > There are other missing features, some of which are rumoured to become > mandatory flags in future, but more importantly, because the > implementation is standalone, it has no ability to integrate into an > NT/Win2k/Samba domain. It can be directly integrated with password backends using NTLM password scheme. > As part of the Samba team, I have worked with other projects - Squid in > particular, to deliver server-side (and client-side) NTLMSSP > authentication, without the need to re-implement the NTLMSSP protocol. > > This is done by a callout to 'ntlm_auth', a Samba 3.0 utility designed > for this purpose, which in turn can contact domain controllers, allowing > for seamless single sign on. > > http://samba.org/samba/docs/man/ntlm_auth.1.html So you'll need Samba to run POP3/IMAP server. Doesn't look convinent to me. Many people have no windows domain infrastructure, but want to provide secure authentication for poor MS Outlook users. > I have recently completed reworking mod_ntlm_winbind for a similar > purpose, and have patches for cyrus-sasl in my 'lorikeet' subversion > repository. These should serve as good examples for the simple > fork()/exec() modal that is used, and also show the support for > GSS-SPNEGO (aka HTTP Negotiate) that ntlm_auth also provides. > > http://download.samba.org/ftp/unpacked/lorikeet/trunk/ > > My hope is that I can tempt a Dovecot developer to take on the challenge > of modifying the dovecot to use ntlm_auth, and am most willing to answer > any questions (here, by private mail or on the samba-technical list) > that you may have on the issue.

7 16

Re: [Dovecot] Concerned about Dovecot's new NTLM code (Modified by Timo Sirainen)
by Timo Sirainen 29 Sep '04

29 Sep '04

(resend) On 29.9.2004, at 20:37, Jonas Smedegaard wrote: > Have you considered also separating the Mailbox access routines? They are more or less separated already, but I don't know how useful it would be to create a separate library distribution from them. That is what takes most of the space in Dovecot distribution anyway.. Oh, and after v1.0 I'll probably start fixing the mailbox APIs too. lib-index and lib-storage needs to have different kind of relationship. > It would be marvelous if at some point being able to replace c-client > library to your optimized one for PHP, mailsync, postman, aolserver and > others - even if it means loosing support for odd mailbox formats. I'm not sure what kind of API PHP provides for c-client. I know it's commonly used for building IMAP webmails, but Dovecot doesn't have any IMAP client code and maybe never will.

1 0

[Dovecot] pgsql and default_pass_scheme
by eL gino 29 Sep '04

29 Sep '04

Hello list, I am running Dovecot 1.0-test46 on FreeBSD with PostgreSQL as backend, runs _very_ nice, but i can not set "default_pass_scheme = CRYPT" (only PLAIN) for PostgreSQL Auth in dovecot-pgsql.conf. I have a valid entry in pg_hba.conf (and reloaded/restarted): "local mail mail crypt" If i replace crypt in pg_hba.conf with md5 it works also with plain in dovecot-pgsql.conf? -- Christian. PS: sorry for my poore english.

2 2

Re: [Dovecot] Any way to disable imap on all but localhost ?
by Kim Culhan 29 Sep '04

29 Sep '04

--- michael(a)crosscode.org wrote: > It's still there, just chagned (and probably for the better - > less > confusing and I'd venture less code) in 1.0. > > I had: > > protocols = imap imaps > imap_listen = 127.0.0.1 > imaps_listen = * > > Now I have: > > protocols = imap imaps > protocol imap { > listen = 127.0.0.1 > ssl_listen = * > } > > However, after encountering the same problem you did I moved my > 0.99 > configuration file out of place and put the 1.0 > dovecot-example.conf file > into place and modified it, since that seemed like the easier thing > to do > (not that the imap section already exists in the new example > config., > it's just empty). Ok, just did the same, running dovecot-1.0-test46 dovecot is still listening on port 143 It appears dovecot imap listens on all the interfaces regardless This is running on FreeBSD 5.3-BETA4 -kim __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail

1 0