Quoting "Oleg D." <dzoleg@rsute.ru>:

Hello Chris,

Wednesday, May 24, 2006, 8:36:00 PM, you wrote:

CH> Quoting "Oleg D." <dzoleg@rsute.ru>:

...

...

MB> Hmmm... I was seeing a problem rather like this with 1.0beta8 under Solaris MB> with Sun's compiler: only it was with the IMAP protocol rather than POP.

MB> The problem there was an assumption Tio had made that everyone was using a MB> C99-compatible compiler. Apparently this handles some aspects of variable MB> initialisation differently from earlier C compilers.

MB> In my case adding a command-line option to the C compiler to flip it into MB> C99 mode seemed to solve the problem. The option for our compiler was MB> "-xc99" -- however if your compiler has such an option it may have a MB> different name. If you check the manual page for your C compiler you may MB> find an equivalent option to try.

MB> However another solution was provided by Timo in the form of a simple patch MB> that made changes to a couple of source files. I hope Timo doesn't mind: MB> I'm re-sending his patch as an attachment to this message as it is tiny. MB> You could try applying it and rebuilding Dovecot.

MB> Cheers, MB> Mike Brudenell

But I use FreeBSD 4.11-RELEASE-p15 with native compiler. Really nobody has this problem on freebsd?

And the main - Why I can't start dovecot without SSL :) Why I see in log "pop3-login: BUG: SSL initialization parameters not given while they should have been" even if I have "ssl_disable = yes" in dovecot.conf 1.0b3 works fine. This problem is main for me because I don't want to use SSL.

CH> I run FreeBSD here, and my hunch is that SSL (or some form) was CH> compiled it. Which would help explain the errors you describe. CH> What "knobs" did you use when you built it? Did you simply take CH> the default without examining the Makefile? My hunch is that if CH> you take a closer look at how it was built and installed; you'll CH> find some form of SSL/ encryption was built into it, and you'll CH> either have to: cd /usr/ports/mail/dovecot; make deinstall; CH> tweak the Makefile to your needs; make reinstall. Or figure out CH> how to utilize the security method that was built in by default. CH> Perhaps SASL2, or GSSAPI, as I see they're options in the Makefile.

CH> Best wishes. I hope this helps.

CH> --Chris H.

I have just delete section in src/login-common/main.c:

           if (net_getsockname(LOGIN_SSL_LISTEN_FD, NULL, NULL) == 0) {
                   if (!ssl_initialized) {
                           /* this shouldn't happen, master should have
                              disabled the ssl socket.. */
                           i_fatal("BUG: SSL initialization parameters "
                                   "not given while they should have "
                                   "been");
                   }

                   io_ssl_listen = io_add(LOGIN_SSL_LISTEN_FD, IO_READ,
                                          login_accept_ssl, NULL);
           }

set "ssl_disable = yes"

and dovecot start and work normal :)

Excellent. Thanks for taking the time to share the solution.

--Chris H.

just for testing probably it will help to discovering the bug.

-- Best regards, Oleg mailto:dzoleg@rsute.ru

-- Shameless self-promotion follows... ... or does it?

FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 /////////////////////////////////////////////////////////////////

On 30 May 2006, at 14:30, Timo Sirainen wrote:

On Wed, 2006-05-24 at 19:20 +0400, Oleg D. wrote:

...

MB> However another solution was provided by Timo in the form of a
simple patch MB> that made changes to a couple of source files. I hope Timo
doesn't mind: MB> I'm re-sending his patch as an attachment to this message as
it is tiny. MB> You could try applying it and rebuilding Dovecot.

But I use FreeBSD 4.11-RELEASE-p15 with native compiler. Really nobody has this problem on freebsd?

I think the patch could have solved your problem, since the error message really looks the same as what it was made to fix. Also the SSL error it causes could be explained by the same problem (ssl_listen_fd contains a random number which just happens to be a socket).

Maybe FreeBSD 4.11 has a bit older gcc which doesn't by default
compile with C99 enabled.

My 1.0.b8_1 update to the FreeBSD port was committed on the 27th of May. It includes a simple patch to resolve the C99 issue. It also contained a fix for a dlerror() reset issue; I hope the
originator has already reported this to you Timo? If not, details
here: http://www.freebsd.org/cgi/query-pr.cgi?pr=97671.

Regards, Robin