- dovecot - dovecot.org

[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

[Dovecot] b8 fails with ACL plugin on
by Fintec 14 Jun '06

14 Jun '06

After upgrading to b8 using the ATrpm with the ACL plugin on it fails: # /etc/init.d/dovecot start Starting Dovecot Imap: Edlopen(/usr/lib/dovecot/imap/lib01_acl_plugin.so) failed: /usr/lib/dovecot/imap/lib01_acl_plugin.so: cannot open shared object file: No such file or directory Error: imap dump-capability process returned 22784 [FAILED] Anyone able to help be troubleshoot this? Gavin

1 0

[Dovecot] question about upgrade
by Ivan Arteaga 14 Jun '06

14 Jun '06

HI, First time posting here. can someone do let me know if there is a specific upgrade procedure from 0.99x to 1.x? Any comment will be appreciated. --Ivan.

2 1

Re: [Dovecot] Error: socket() failed: Protocol not supported ERROR
by Marcus Rueckert 14 Jun '06

14 Jun '06

On 2006-06-13 17:20:11 -0700, Jack Bailey wrote: > The bug seems to be in dovecot.conf. Uncomment ssl_listen and set it to * works for me: SuSE Linux 10.0 i386 1.0.beta9 with imap and pop3 enabled with listen and ssl_listen set to either "*" or "[::]". maybe run the process under truss/strace to see which call exactly fails. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org

1 0

[Dovecot] Re: [Dovecot-news] 1.0.beta9 released
by Timo Sirainen 13 Jun '06

13 Jun '06

On Tue, 2006-06-13 at 18:49 +0200, Geert Hendrickx wrote: > On Tue, Jun 13, 2006 at 07:16:50PM +0300, Timo Sirainen wrote: > > Fixes a lot of bugs. The next release will be the first "release > > candidate" instead of a beta. > > Timo, > > thanks for another release. I noticed one thing though: ./configure now > checks for c++ and f77 compilers, even though dovecot doesn't seem to use > any C++ nor Fortran. Could this check be removed again? (unless it's > necessary, of course) I've no idea how to remove them. Autoconf for some reason just wants to add checks for them. I once tried looking into it how they could be removed but couldn't figure out anything. Cc'd the mailing list, maybe someone here knows how to do that?

2 1

[Dovecot] POP3 notice if password expired
by Vaidas Pilkauskas 13 Jun '06

13 Jun '06

Hi, We just migrated our IMAP service to Dovecot and it performs very well. We also want to migrate our POP3 service (qpopper) to Dovecot. The problem is that Dovecot and Qpopper differently act on expired passwords: Qpopper: -ERR "user": password expired. Dovecot: -ERR Authentication failed. Are there any way to tell Dovecot to report about expired passwords? We have about 30000 users and 84 days password lifecycle. "Password expired" notifications highly reduce the number of support calls from our users. Server setup info: Solaris 9 SPARC, PAM authentication. Thanks, Vaidas Pilkauskas Vilnius University

2 3

[Dovecot] ssl-proxy: client certificates and crl check
by HenkJan Wolthuis 13 Jun '06

13 Jun '06

Hi, I've attached a new version of my patch against ssl_proxy-openssl.c which: - disconnects when no clientcertificate is presented - checks the clientcertificate against the crl for our root cert. (so you can't use a revoked client cert.) - returns the CommonName from the client cert. in ssl_proxy_get_peer_name (this way it's easier to use dovecot as imap-proxy with a passwd-like userdb + ssl_require_client_cert + ssl_username_from_cert, it "binds" the emailuser to the clientcertificate, so a user / clientcert. can access only the account from the userdb) In order to use it, the CAfile must be a file which contains the CAcertificate (pem format) followed by the CRL (also in pem format). (servercert and the clientcerts are signed with a self-signed rootcert) changes in this version: - found the proper way to extract the CommonName from a certificate! - code cleanup there are some issues with the patch: - it needs openssl > 0.9.7. the way I do CRL loading/checking is new in 0.9.7. There are some examples on the openssl-devel list, but not much documentation. - ssl_verify_client_cert now returns 0 in case of an invalid cert. was there a reason why it always returned 1? - ssl_proxy_get_peer_name is changed, code depending on this function returning "X509_NAME_oneline" can break.. (at the moment it is only used for the ssl_username_from_cert config option, i think) I'd like comments / ideas etc. -- groeten, HenkJan Wolthuis --- ssl-proxy-openssl.c.orig 2006-04-04 10:32:58.000000000 +0200 +++ ssl-proxy-openssl.c 2006-06-01 09:24:57.000000000 +0200 @@ -498,7 +498,7 @@ const char *ssl_proxy_get_peer_name(struct ssl_proxy *proxy) { X509 *x509; - char buf[1024]; + char buf[256]; const char *name; if (!ssl_proxy_has_valid_client_cert(proxy)) @@ -508,10 +508,16 @@ if (x509 == NULL) return NULL; /* we should have had it.. */ - X509_NAME_oneline(X509_get_subject_name(x509), buf, sizeof(buf)); - name = t_strndup(buf, sizeof(buf)); + /* HJHJ */ + /* the X509_N_gtbN can return -1 without 0-terminating buf */ + /* if the call succeeds buf is 0-terminated (openssl 0.9.7e / 0.9.8b src) */ + buf[0] = '\0'; + if( X509_NAME_get_text_by_NID(X509_get_subject_name(x509),NID_commonName,buf,sizeof(buf)) < 0 ) + { buf[0] = '\0'; } + name = t_strndup(buf, sizeof(buf) ); X509_free(x509); - + /* HJHJ */ + return *name == '\0' ? NULL : name; } @@ -582,10 +588,22 @@ proxy = SSL_get_ex_data(ssl, extdata_index); proxy->cert_received = TRUE; + + /* HJHJ */ + char buf[1024]; + X509_NAME_oneline( X509_get_subject_name(ctx->current_cert),buf,sizeof(buf)); + if (!preverify_ok) + { proxy->cert_broken = TRUE; + i_warning("BAD CERT %s: %s",X509_verify_cert_error_string(ctx->error),buf); + } + else + { i_warning("CERT: %s",buf); } /* logging */ - return 1; + return preverify_ok; + /* HJHJ */ + } static int @@ -666,10 +684,20 @@ if (getenv("SSL_VERIFY_CLIENT_CERT") != NULL) { SSL_CTX_set_verify(ssl_ctx, SSL_VERIFY_PEER | - SSL_VERIFY_CLIENT_ONCE, + SSL_VERIFY_FAIL_IF_NO_PEER_CERT, ssl_verify_client_cert); } + /* HJHJ */ +#if OPENSSL_VERSION_NUMBER >= 0x00907000L + X509_STORE *store; + if( (store=SSL_CTX_get_cert_store(ssl_ctx)) != NULL ) + { X509_STORE_set_flags( store, X509_V_FLAG_CRL_CHECK | X509_V_FLAG_CRL_CHECK_ALL); } + else + { i_warning("X509 get cert store failed..."); } +#endif + /* HJHJ */ + /* PRNG initialization might want to use /dev/urandom, make sure it does it before chrooting. We might not have enough entropy at the first try, so this function may fail. It's still been

2 5