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 localho
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 u
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
--
To UNSUBSCRIBE, email to debi
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 serv
(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
5 matches
Mail list logo
