Difference between revisions of "Tomcat mail configuration"
From OpenKM Documentation
Line 1: | Line 1: | ||
OpenKM is a J2EE application deployed in a Tomcat. Some parameters have a default configuration that fit common user requirements but others depend on specific user configuration. | OpenKM is a J2EE application deployed in a Tomcat. Some parameters have a default configuration that fit common user requirements but others depend on specific user configuration. | ||
− | |||
− | |||
OpenKM sometimes sends emails to users (because they have subscribed a document or folder, for example) and you have to check that this email configuration is correct. If you edit the file ''$TOMCAT_HOME/conf/server.xml'': | OpenKM sometimes sends emails to users (because they have subscribed a document or folder, for example) and you have to check that this email configuration is correct. If you edit the file ''$TOMCAT_HOME/conf/server.xml'': |
Revision as of 18:47, 1 December 2012
OpenKM is a J2EE application deployed in a Tomcat. Some parameters have a default configuration that fit common user requirements but others depend on specific user configuration.
OpenKM sometimes sends emails to users (because they have subscribed a document or folder, for example) and you have to check that this email configuration is correct. If you edit the file $TOMCAT_HOME/conf/server.xml:
$ vim $$TOMCAT_HOME/conf/server.xml
You will see something like this:
<Resource name="mail/OpenKM" type="javax.mail.Session"
mail.transport.protocol="smtp"
mail.smtp.auth="true"
mail.smtp.host="your smtp server"
mail.smtp.user="<username>"
password="<password>"
mail.port="25"
mail.debug="true"
/>
Optional can be used mail.user="<username>" and mail.password="<password>" parameters |
Gmail example
<Resource name="mail/OpenKM" auth="Container" type="javax.mail.Session"
mail.transport.protocol="smtp"
mail.smtp.auth="true"
mail.smtp.host="smtp.gmail.com"
mail.smtp.port="465"
mail.smtp.user="<username>"
password="<password>"
mail.smtp.from="<sender email>"
mail.smtp.quitwait="false"
mail.smtp.starttls.enable="true"
mail.smtp.socketFactory.class="javax.net.ssl.SSLSocketFactory"
mail.debug="true"
/>
Use parameter mail.smtp.quitwait="false" if you got some stuck problems during tomcat startup |