Having gone in the opposite direction (Biology/Biochem/Biotech -> Computers) I can say without a doubt that biologists/biochemists can use more people with strong computer science skills. Many aspects of biochem and molecular biology are extremely computational intensive and in the past there was a large influx of computer programmers moving into the biotech arena.

Good luck and I hope you can find someone to help you manage Dovecot!

Stephen

On Thu, 2006-05-18 at 10:25, Jeff A. Earickson wrote:

Your acceptance into biochemistry would be a great loss for computer science. But I figure that you will find the cure for cancer. Good luck!

Jeff Earickson Colby College

On Thu, 18 May 2006, Timo Sirainen wrote:

...

Date: Thu, 18 May 2006 18:40:23 +0300 From: Timo Sirainen <tss@iki.fi> To: dovecot@dovecot.org Subject: [Dovecot] Busy, again

Just a note to people if you're wondering why I'm not replying to most of my mails:

I'm trying to get into university to start stydying cellular biology (so I'm applying to biochemistry and biotechnology). Their entrance exams are next wednesday, so I'm trying to use most of my time left to study for them (and also do some work..). I don't know much about the subject, so I really need to study for them. :)

Then again, if I don't pass, my fallback plan is to go in via computer science and try again next year. Hopefully they allow taking the same bio-classes even if it's not my major.

HELP! I can't start dovecot as a pop3 server after upgrade from 1.0b3 to b8 FreeBSD 4.11-RELEASE-p15

dovecot.conf is from 1.0b3 which worked fine.

(auth with MySQL)

After upgrade i have an error message in log: "pop3-login: BUG: SSL initialization parameters not given while they should have been" but I have not using SSL. I have "ssl_disable = yes" in dovecot.conf

OK. I have generates a keys by mkcert.sh set ssl_disable = no and.... nothing divecot started but not working after connections dovecot in not responding and in log i see:

dovecot: pop3-login: Unrecognized event: kevent {.ident = 0, .filter = 0xffffffff, .flags = 0x0001, .fflags = 0x00000000, .data = 0x00000001} dovecot: pop3-login: mode: 0x004x dovecot: child 353 (login) killed with signal 6

If I start dovecot compiled without kqueue i see in log: pop3-login: Disconnected: rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS and nothing else

Hi,

OD> If I start dovecot compiled without kqueue i see in log: OD> pop3-login: Disconnected: rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS OD> and nothing else

do you have "disable_plaintext_auth = no" in dovecot.conf? otherwise dovecot refuses plaintext logins with pop3 and imap without ssl.

what happens if you telnet to your dovecotserver?

you can use "auth_verbose = yes" and "auth_debug = yes" in dovecot.conf for more logging...

groeten, HenkJan Wolthuis

Oleg D. wrote:

Hello HenkJan,

Tuesday, May 23, 2006, 11:30:37 AM, you wrote:

...

do you have "disable_plaintext_auth = no" in dovecot.conf?

Yes.

...

"auth_verbose = yes" and "auth_debug = yes" in dovecot.conf for more logging

Yes.

...

what happens if you telnet to your dovecotserver?

I have already tried it many times.

And I don't see any prompt.

In log:

"dovecot: Dovecot v1.0.beta8 starting up

dovecot: Generating Diffie-Hellman parameters for the first time. This may take a while..

dovecot: auth-worker(default): mysql: Connected to /tmp/mysql.sock (mail)"

after telnet:

"dovecot: pop3-login: Waiting for SSL parameter file ssl-parameters.dat"

and nothing else

I found ssl-parameters.dat.tmp in /var/run/dovecot/login

After starting/stopping dovecot several times ssl-parameters.dat is appear in /var/run/dovecot/login

But nothing again

OK. I try all of this to start dovecot anyway.

But I don't want to use SSL!

THE MAIN QUESTION:

Why I see "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.

--

Best regards,

Oleg mailto:dzoleg@rsute.ru

What do you have as your "protocols" line? Make sure there's no "imaps" or "pop3s". Also, make sure you don't have any "ssl_listen" options set.

Also, do you ever get the "SSL parameters regeneration completed" line in your log file (it can take several minutes on a slow machine)? If it's decided (however wrongly) to do the SSL paramters generation, you won't be able to login until it's finished.

Chris

-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094