- dovecot - dovecot.org

[Dovecot] LDAP with Active Directory
by B Hatoum 16 Jun '06

16 Jun '06

Hello, I have successfully used dovecot 1.0 Beta 9 to do SASL authentication for postfix using the unix passwd/shadow files. I need to authenticate with a windows 2003 server using active directory. My system does not support PAM (I'm using slackware) so I cannot take that route. I do not need to use dovecot for POP or IMAP at the present time and so I would like to avoid modifying my active directory schema. Dovecot seems to be communicating with the active directory server, however it is sending an authentication failure to postfix: postfix/smtpd[24540]: warning: unknown[XXX.XXX.XXX.X]: SASL LOGIN authentication failed: UxxvcmxxQ6 I don't see any messages in the log from dovecot. Here is my dovecot-ldap.conf: hosts = 192.168.1.2:389 dn = "cn=dovecot,cn=Users,dc=DOM,dc=local" dnpass = "password" auth_bind = yes ldap_version = 3 base = cn=Users,dc=DOM,dc=local deref = never scope = subtree default_pass_scheme = CRYPT user_global_uid = 900 user_global_gid = 900 Can someone point out what I am missing? I can't find documentation on this type of setup. Thanks in advance. B Hatoum

4 3

[Dovecot] fedora directory server
by Alfonso Sparano 16 Jun '06

16 Jun '06

Hi all someone is successful to use fedora directory server as an ldap server for user/password and also with the LDA? I'm testing protocol smtp: sendmail + dovecot lda + fedora directory server and also: protocol pop3 and imap: dovecot + fedora directory server Thanks a lot folks Alfonso

1 0

[Dovecot] Dovecot-auth relicensing to BSD/MIT
by Timo Sirainen 15 Jun '06

15 Jun '06

Bcc'd to everyone who have sent me patches to dovecot-auth or related code. Once in a while people ask me if Dovecot's authentication server code could be relicensed to BSD so they could use it for their project. Usually they have been other BSD-licensed open source projects which just prefer not to use LGPL code. Now there's again this company asking me to give them a bit less restrictive license (they want to link it statically to a closed source program). They'd want to move the code to a separate SASL package and create a library out of it. They want SASL client code too, so they'd apparently write it for the package as well. I've been thinking about separating the dovecot-auth to be a separate package for a while too, although only around the time when Dovecot v2.0 is released (certainly not before v1.0). So, I think changing the Dovecot-auth's license from LGPL to BSD or MIT wouldn't really hurt and it could get it more widely used. Most of Dovecot's lib/ code is already MIT-licensed, so MIT would be more consistent. But I don't think there really is any real difference between BSD and MIT, so either one is fine for me. :) Now, this mail is mostly meant for asking people who have sent me patches to dovecot-auth if they allow the license change for their patch. If not, I'll either rewrite the part of the code, or for larger code parts (eg. NTLM auth) I'll just leave it LGPL licensed but so that it can be compiled out optionally. So, bcc'd people, please reply to me which one of these you're okay with: 1) I allow license change to either BSD or MIT 2) I allow license change to BSD 3) I allow license change to MIT 4) I don't allow license change

2 2

[Dovecot] SASL AUTH LOGIN mechanism problems
by Anders Karlsson 15 Jun '06

15 Jun '06

Hi all, Have anyone had problems with Exhange 2003 servers trying to use sasl against Postfix+Dovecot SASL using the AUTH LOGIN Mechanism ? I've done some smtp debugging, and it seems that Exchange sends the usename at the same time as AUTH LOGIN i.e: AUTH LOGIN <base64_username> It then expects to be able to send the password. mech-login.c silently discards all data after AUTH LOGIN and just prompts the username prompt whetever the username has already been supplied during initial AUTH LOGIN request. I've attached a patch to make mech-login.c check if additional data has been sent along with AUTH LOGIN, and in this case skip ahead directly to the Password: prompt. Cheers Anders

2 1

[Dovecot] nfs, dovecot, and maildirs
by bofh list 15 Jun '06

15 Jun '06

Hello - I know I am not the only one that will be trying, or has tried this before. Here are my questions! NFS Clients, multiple servers running dovecot - linux with 2.6 kernel with relevant patches (utime, etc) Backend - netapp filer End users - various clients all running IMAP It looks like 1.0.beta8 is definately the way to go. I have a few questions with regards to setup. Is it now possible to reliably store index files over nfs? If not, the alternative is keeping index files in memory, or on local disk - on each server. How big of a performance hit is this if imap connections are round-robined between imap servers? I've seen various people using different actimeo settings, some set at 0, some slightly higher - as much as 30. Can anyone speak on experience they have had with netapps on this subject? The following sound like they are required: mmap_disable=yes lock_method=dotlock Has anyone been successful with fnctl() on netapps with dovecot? Thanks in advance!

3 2

[Dovecot] How to open only these dovecot ports?
by M. Fioretti 15 Jun '06

15 Jun '06

Hello, I have not clear, due to the new syntax, how to configure dovecot 1.0 to listen only for the following combinations of ports and services: no pop3, from whatever host accept imap connections only if coming from localhost (since I understand this is secure _and_ the only way to make squirrelmail talk to dovecot) listen on the internet only for imaps and pop3s connections, accept them only if DIGEST-MD5 authentication succeeds. Thanks in advance for any explanation, Marco -- Marco Fioretti mfioretti, at the server mclink.it Fedora Core 3 for low memory http://www.rule-project.org/ We shall serve God, family and country, in that order, because without the one before it, each would perish.

2 2

[Dovecot] Error: socket() failed: Protocol not supported ERROR in dovecot-1.0.beta9
by Jeff Gardiner 14 Jun '06

14 Jun '06

I'm trying to get IMAPS working with dovecot-1.0.beta9. I'm building it on a Solaris 10 box, with openssl-0.9.8b installed. Here is the results of my ./configure: Install prefix ...................... : /usr/local/dovecot-1.0.beta9 File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : none Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with GSSAPI support ........ : no Building with user database modules . : static prefetch passwd passwd-file checkpassword (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword (modules) Building with SQL drivers ............: I've attached a copy of my dovecot.conf file (striped of comments). When I try running dovecot I get the following error: Error: socket() failed: Protocol not supported Fatal: listen(993) failed: Protocol not supported When I change ssl_disable = no to ssl_disable = yes, everything works. Anyone have any suggestions? Cheers Jeff protocols = imap imaps listen = * disable_plaintext_auth = no log_path = /var/log/dovecot ssl_disable = no ssl_cert_file = /usr/local/ssl/certs/Imaging_Dovecot_cert.pem ssl_key_file = /usr/local/ssl/private/Imaging_Dovecot_key.pem ssl_parameters_regenerate = 168 verbose_ssl = yes default_mail_env = maildir:%h/.email protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster(a)example.com } auth default { mechanisms = plain digest-md5 cram-md5 passdb pam { args = dovecot } userdb passwd { } user = root } plugin { }

5 5

[Dovecot] Problems with dovecot.beta9
by Adnae Mac Uthidir 14 Jun '06

14 Jun '06

Dear all :) I have been upgraded dovecot today and I get following errors: Jun 14 12:08:54 [dovecot] IMAP(adnae(a)xxxxxx.xxx): inotify_init() failed: Function not implemented Jun 14 12:08:54 [dovecot] IMAP(auftrag(a)xxxxxxx.xxx): inotify_init() failed: Function not implemented Jun 14 12:08:54 [dovecot] IMAP(swolf(a)xxxxxx.xxx): inotify_init() failed: Function not implemented I have a 64 bit system (Gentoo [amd64]) and I have enabled this function on my kernel: Kernel: 2.6.16-gentoo-r9: [*] Inotify file change notification support thx for your help :)

1 0

Re: [Dovecot] Quick thanks for wonderful ACLS!
by Gavin Henry 14 Jun '06

14 Jun '06

<quote who="Marc Perkel"> > Looks cute but - why do I want it? What's it good for? I must be missing > something .... > > Well, in a big company, you might not want users to delete any e-mails they have sent out of the company. Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

2 1

[Dovecot] 1.0 roadmap
by Timo Sirainen 14 Jun '06

14 Jun '06

I've read about one month back this list's messages. I've still 216 messages from this year marked as "unread" which I should look into more (+258 older ones). Also I've 180 "unread" messages in my INBOX also which might contain something useful. So those messages could still contain something that should be added to this list. Anyway looking at my current TODO, I think the following things should be fixed before v1.0. Additions, comments, patches and such welcome. :) Help would be welcome in checking if these bugs are still there: - Thunderbird+POP3 DELE error. Was this fixed already? Could someone try this? See http://www.dovecot.org/list/dovecot/2005-June/007497.html and the rest of the thread. Basically put thousands of messages into mailbox, start downloading them and see if error comes. - Solaris sendfile is broken? Is it? Can someone try? You can test it with maildir by setting mail_save_crlf=yes, saving a somewhat large mail and FETCHing it (and truss that it really uses sendfile) - passdb passwd + passdb shadow -> passdb_password isn't reset to NULL (ie. probably doesn't allow logging in if the shadow password is correct?) - maildir: rename foo foo.xyz -> infinite loop possible? (doesn't seem so? why did I think it could be? look at the code) Important: - dict-server should have some config file which lists the allowed dicts - LDA: empty mail gives an error. - deliver: delivering mail to box smaller than mbox_min_index_size give close() errors - mbox: CRLFs in headers break the mbox - index: when mailbox is deleted/renamed and someone else had it open, we get stat() error messages in log file. Handle at least the most common places where it happens. - lib-storage - limit folder hierarchy levels? user can now create eg. a/a/a/a/... and then start renaming them from end to beginning, which probably will at some point start causing syscall failures which will fill up logs. Probably should be done: - mbox: dirty mode should be stored to index - quota code should probably be always doing some quota_set_critical() instead of using mail_storage_set_critical(), so that quota_last_error() would work properly - rfc2557 support for BODYSTRUCTURE, as specified by RFC3501 - keywords: add some limits to how many there can be - don't return \* in PERMANENTFLAGS when we're full - mbox: how well does dirty sync + status work? it reads the last mail every time? not very good.. - maildir: we probably shouldn't do duplicate detection/fixing?.. or at least stat() the old file before trying, because we might have just previously seen the old file and then new file and then we try to fix it..

18 37