Exactly! I agree with you! I used to have webmail connect locally via unencrypted IMAP on port 143, but the problem occurred even more frequently. So I thought that it could be dovecot not being able to work out both protocols... I had it like this: protocol imap { listen = 127.0.0.1:143 ssl_listen = *:[another port] } Then I commented the listen line, and things got better, but not good enough yet. Strange, uh?
I know I should not be using webmail locally via SSL. But I got less errors like that. Altough, I know once I get the problem solved, I can go back to the correct solution. Just for the record: My mail server is running super fast! The problem happens only at specific moments, twice a day, only. Otherwise, what's the other configuration that could be eating up resources? BTW, I got plenty of CPU (2xQuadCore 3.0) and memory (32GB). On Fri, Jan 8, 2010 at 5:07 AM, Stan Hoeppner <s...@hardwarefreak.com>wrote: > > On Thu, 7 Jan 2010 11:08:54 -0200, Mario Gomide <mariogom...@gmail.com> > wrote: > > > Webmail is in localhost and connects locally also with SSL. > > > > The problem starts when webmail takes long to authenticate and show > folders > > and stuff. After a while it times out and doesn't connect. > > Any ideas? > > It may be unrelated to your current problem, but, why in the world are you > having a local process connect to another local process via SSL? That's > akin to encrypting the traffic between the left and right hemispheres of > your brain for fear someone might be listening in to the unencrypted > traffic occurring within you skull. Silly isn't it? > > One thing your configuration will certainly do is suck CPU horsepower, eat > up memory unnecessarily, and make things slower than they should/could be. > > -- > Stan >