Author Topic: Getting it to work  (Read 3908 times)

Offline bret.miller

  • Newbie
  • *
  • Posts: 4
Getting it to work
« on: September 07, 2007, 05:58:24 PM »
I downloaded and installed RoundCube today on DreamHost (apache/mysql) and configured it to connect to my CommuniGate Pro server. When I try to log into RoundCube, it sits there for a very, very long time and then comes back with a 500 error. Renaming .htaccess didn't solve this. On my mail server, I can see it connect, but it doesn't get beyond that.

I did a chmod 777 on the logs directory, but it's still empty.

The mail server log says:

14:46:45.715 5 IMAP [0.0.0.0]:143 <- [208.97.171.15]:56986 connection request. socket=5172
14:46:45.715 4 IMAP-001907([208.97.171.15]) got connection on [10.99.3.100]:143(wcg.org) from [208.97.171.15]:56986
14:46:45.715 5 IMAP-001907([208.97.171.15]) out: * OK CommuniGate Pro IMAP Server 5.1.12 at mail.wcg.org ready\r\n
14:48:30.793 3 IMAP-001907([208.97.171.15]) read failed. Error Code=connection reset by peer
14:48:30.793 4 IMAP-001907([208.97.171.15]) closing connection
14:48:30.793 4 IMAP-001907([208.97.171.15]) releasing stream

So, RoundCube connected, but didn't actually ever try to log in.

Any ideas?
Bret

Offline bret.miller

  • Newbie
  • *
  • Posts: 4
Re: Getting it to work
« Reply #1 on: September 18, 2007, 06:31:29 PM »
OK... so no help..

This appears to be a problem with my firewall (I think). I was able to get it working by pointing it at other servers besides this one. So, I guess if I get that issue fixed, RoundCube will likely work for me.

Offline tekone

  • Jr. Member
  • **
  • Posts: 27
Re: Getting it to work
« Reply #2 on: September 19, 2007, 10:28:47 PM »
i'm confused?

don't you have your server set as localhost? or are you trying to access IMAP on another host?

Offline bret.miller

  • Newbie
  • *
  • Posts: 4
Re: Getting it to work
« Reply #3 on: September 24, 2007, 10:15:42 AM »
Yes, I don't have a web server installed on the mail server and wanted to IMAP to a remote host. The actual goal was to provide a webmail interface that is transferrable to a different environment as we look at the probability of outsourcing our email infrastructure.

So the connection was being made to the remote IMAP server, but it was unable to actually talk over the connection. What made the problem so hard to track down is that it only affected a handful of connections, including the one from this web server. It was consistent in that it always affected those specific IP addresses and never affected others. Still, generally, you don't generally suspect the firewall if most people can connect through it.

Bret