Bug#635133: closed by Mathieu Parent math.par...@gmail.com (Re: [pkg-kolab] Bug#635133: Bug#635133: More info)
Mathieu, You are correct. /etc/horde/horde3/conf.xml was not involved. The problem was just with the type in my port forward. I'm still not sure why I need to have the port forwarded on my router at this location and not at my other locations. I'm wondering in the FQDN resolves to the localhost on the other boxes and the external IP on this machine. I didn't do anything special to make that happen, but it would explain the symptoms. Soren -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635133: [pkg-kolab] Bug#635133: More info
Mathieu, Thank you. The problem was in /etc/horde/horde3/conf.xml. I also fixed a typo in my port forwarding for 4190, so I can now telnet to sieve using the FQDN. This was also an issue. I'm not sure why it works on the other boxes without 4190 forwarded correctly, but I'm guessing it is using localhost instead of the FQDN. Soren -- Soren Stoutner Small Business Tech Solutions so...@smallbusinesstech.net 623-262-6169 On 21.11.2011 13:31, Mathieu Parent wrote: 2011/11/21 Soren Stoutner : I thought I had successfully reverted all those changes, but I'm guessing that one of my customizations still remains. I just don't know where to look to find it. You can maybe try a big grep -r 2000 /etc /usr? -- Mathieu Links: -- [1] mailto:so...@smallbusinesstech.net
Bug#635133: More info
Mathieu, In both the case of the functioning and the non-functioning servers, the FQDN resolves to the WAN port of the router, which then forwards the information to the Kolab server on the inside of the network. (Interestingly, forwarding sieve doesn't seem to be necessary on the working server. I'm guessing that the web admin connects to sieve via localhost instead of the FQDN.) I setup the Kolab server on the system that isn't working during Debian's transition in testing from port 2000 to port 4190 for sieve. Some packages in testing had transitioned and others had not. I remember that I had to tweak a bunch of settings. I thought I had successfully reverted all those changes, but I'm guessing that one of my customizations still remains. I just don't know where to look to find it. Soren On Saturday, November 19, 2011 12:18:00 PM Mathieu Parent wrote: (Sorry for being so slow to respond) Does the fqdn resolve to the Ip you tested with telnet? Regards -- Soren Stoutner Small Business Tech Solutions 623-262-6169 so...@smallbusinesstech.net www.smallbusinesstech.net signature.asc Description: This is a digitally signed message part.
Bug#635133: [pkg-kolab] Bug#635133: More info
2011/11/21 Soren Stoutner so...@smallbusinesstech.net: I thought I had successfully reverted all those changes, but I'm guessing that one of my customizations still remains. I just don't know where to look to find it. You can maybe try a big grep -r 2000 /etc /usr? -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635133: More info
(Sorry for being so slow to respond) Does the fqdn resolve to the Ip you tested with telnet? Regards -- Mathieu Parent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
