Skip to content

HOWTO: Install & Configure

Derek Battams edited this page Jan 18, 2015 · 1 revision

Types of deployment

WAR file

You can run psmtp as an app within your favourite J2EE container. In a development/QA environment, you'd probably ask your IT/DevOps/etc. team to simply deploy psmtp within an available container and then make it available within the environment.

Standalone

The standalone version provides a self contained application that leverages an embedded Jetty 8 container. You can launch a psmtp instance via command line. This may be suitable for embedding a psmtp instance within unit tests or it can be deployed within a QA environment that doesn't have an accessible J2EE container.

WAR deployment

Prereqs

  • JRE 7
  • J2EE container that provides support for Servlet 3.0 API

Instructions

The war file build is simply deployed in your favourite J2EE container. Details on exact installation procedures vary by container. Consult your container's documentation for specifics.

Once successfully deployed, simply visit:

http://<host>:<port>/<context>/config.groovy

The default id and password are both admin. On that page you can configure the settings for the SMTP server, logging, etc.

In my environment, I have a Tomcat 7 installation that I use to test the war file.

Standalone deployment

Prereqs

  • JRE 7

Instructions

From the bin directory of the distribution, run pseudosmtp -h and it will respond with all of the supported command line arguments. None are required and the help output will show you the defaults that will be used when an option isn't specified. After the app is started, configuration is the same as described in the war instructions above.