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.
