"Page not found" when accessing "webmail"

[les]

I had disabled SELinux, also...

Minor summary to this point...

- Apache default page displays (http://localhost)
- Subdirectories such as /webmail return 404, "page not found"
- Firewall disabled
- SELinux disabled
- Tomcat service verified running
- Scalix non-web (ie SMTP and POP) verfied running

- Cannot locate Tomcat "context" configuration which should describe the /webmail and /sax web directories

This is not the most elegant of comands but what output do you get from the following.....

netstat -apn |grep ":80" |grep LISTEN

You should see 3 java processes 8005, 8009, 8080 and then httpd running on 80.

also what tomcat based packages do you have?

# rpm -qa |grep tomcat
scalix-tomcat-5.5.25-415
scalix-tomcat-connector-11.4.1.905-1.rhel5

[les]

- Cannot locate Tomcat "context" configuration which should describe the /webmail and /sax web directories

All tomcat config files are in /var/opt/scalix/xx/tomcat (where xx is particular to your site). The conf subdirectory has server.xml.

Having said that though, in all my experiences tomcat needs no configuration post the installation. It is all handled by the installer. So you really don't need to do anything to get tomcat to work. The only issues i've ever come across have been dns related, virtual host config, selinux or having apache listening to port 8080 for another website, which breaks tomcat.

So, if you've only run the installer and not made any manual changes it should work.

i would re-run the installer and choose reconfigure all components. It won't hurt.

Hope this helps.

[les]

- Apache default page displays (http://localhost)
- Subdirectories such as /webmail return 404, "page not found"

Just one final note to be clear....

If you have <VirtualHost server.domainname:*.80> in the tomcat virtual host config files then http://localhost/webmail or http://localhost/sac will never work.
You could only use http://server.domainname/webmail etc.
Hence the use of *:80 to get localhost and or 127.0.0.1 to work. If you make those changes httpd and scalix-tomcat must be restarted.

[tonysu]

That did the trick...

Regardless whether configured for "all ports" or only on port 80, opening a webbrowser to "localhost" won't work... Only the website FQDN will work... no aliases, no alternative record names.

Would be nice if someone put that in the Install Documentation somewhere considering it's a critical thing to know.

I consider this quite possibly a minor architectural flaw/bug since I feel it's common to access a web resource by more than one FQDN. I can understand tying the FQDN to access for licensing purposes (if that is the case), but IMO in that case (again pure speculation that's the rationale) should be applied only to <providing> (serving) services but access should not be similarly restricted.

I commonly configure alternate FQDN to provide backdoor access when the main naming resolution is broken and to support portability (moving from one network to another), and initially it looks like this won't be available to me.

[jhinrichs]

I don't know whether this is correct. I can access my webmail/sac/m interface with full functionality from the intranet with:

webmail.domain.local and scalix.domain.local which are resolved to the same ip (192.168.x.x, but NOT 127.0.0.1)

from the internet via domain.dyndns.biz with port forwarding at the firewall.

Access from the internet via www.domain.local/webmail (the main intranet server) via ProxyPass/ProxyPassReverse directives also works fine, including calendars, appointments etc., but there are minor issues, so the mail headers cannot be shown completely.