Installation
yawebmail minimal requires a JVM of Java-version 1.5 and a Servlet-Container conforming to the Servlet-Specification 2.4 / JSP-Specification 2.0
yawebmail is developed and tested under Tomcat 5.5, but these ones should do the job for you too (if you encounter problems, please report them):
- Tomcat since version 5.5
- JBoss since version 4.0.2 (Tomcat 5.5.x included)
- Apache Geronimo since version 1.0
- Bea Weblogic since version 9
Feel free to report others.
May it be that you downloaded the "yawebmail-n.n.n-src.zip"-file instead of the "yawebmail-n.n.n.zip"-file and deployed the directory "applications/yawebmail"?
If so, please download "yawebmail-n.n.n.zip" and deploy the yawebmail.war-file with your servlet-container.
Many problems with yawebmail are permission-problems. For Tomcat (especially if you don't find a logfile in /logs) try this:
/path/to/tomcat/bin/shutdown.sh
as root:
chown -R #insert-tomcat-user-here#:#insert-tomcat-user-group-here# /path/to/tomcat
as tomcat-user:
/path/to/tomcat/bin/startup.sh
If the exception occurs again, check:
/path/to/tomcat/logs/catalina.out
Check your path-settings and Java-version. Maybe there is a wrong path or version set for your Tomcat-user (and some Linux-installations deliver a broken java-link in /usr/bin/java):
your-machine:~# su - #insert-tomcat-user-here#
(Don't forget the "-" to load the environment of your Tomcat-user.)
tomcat@your-machine:~$ env
[...]
JAVA=/usr/local/java/current/bin/java
JAVA_HOME=/usr/local/java/current/
[...]
tomcat@your-machine:~$ java -version
Post your problem along with your OS, Java-version,
servlet-container-version and a stacktrace on the forum:
https://sourceforge.net/forum/forum.php?forum_id=444908
When a message is fetched to be displayed, it has to be loaded into the server-memory in whole. So if it is a message with a big attachment, it can exceed the size of memory that is allocated to your application-server. You can try to set the commandline-options
-Xms64m -Xmx1024m
in your application-server startscript (see "java -X" to get help on this options and adjust the values to your (hardware-)memory).
If you're able to connect with the yawebmail-"Test drive"
installation using the same login-data, the problem may be caused by
a javax.net.ssl.SSLException ("java.lang.RuntimeException:
Unexpected error: java.security.InvalidAlgorithmParameterException: the
trustAnchors parameter must be non-empty" (this can only be detected by
remote-debugging)).
Some Java-installations (like diablo-jdk1.6.0 on FreeBSD) have a kind of
broken "cacerts"-file in "JAVA_HOME/jre/lib/security". Replace this file
with a working version (the JRE- and JDK-Downloads from http://java.sun.com/
should all contain valid ones). Don't forget to backup the original one
(just in case you run into trouble with the replacement).
This is because of the needed JAR-files (for JSF (myFaces), Javamail, Jakarta-Commons, etc.). The actual yawebmail-classes only take about 5% of the WAR-filesize.