ZenMail serves as an SMTP server that you can bind to a specific TCP port. You can then configure your embedded system to send mail to the Zenoss server explicitly by using the Zenoss's server's IP address as the relay. Alternatively, ZenPop allows you to retrieve event emails from a POP server.

ZenMail supports the following configuration directives:

${ZENHOME}/bin/zenmail (no arguments): default operation. Binds to port 25 on all ports and listens for email messags to arrive. Ignores the TO field in the email and uses the FROM address as the device IP address.

${ZENHOME}/bin/zenmail --listenPort: Bind to the port provided. Useful in situations where an smtp server is already running on the Zenoss server and you don't wish to interfere with the existing mail delivery system. Semantics are the same as the no-argument version (FROM address used as the device IP).

ZenPOP supports the following configuration directives:

--usessl: Issue the STARTTLS command to the POP server and attempt to transfer email messages using SSL encryption. This is required if retrieving mail from Google.

--nodelete: Do not issue the DELE command after retrieving all messages. This is typically used during initial testing so that you don't have to resend test messages to the POP account. Note that some email systems (most notably Google) do not actually delete messages when the DELE command is issued.

--pophost: The hostname or IP address of the POP server to retrieve messages from.

--popport: The tcp port the POP server listens on. Defaults to 110. Used in situations where the POP provider listens on another port (e.g. Google on port 995)

--popuser: The username that contains email messages to retrieve

--poppass: The password to use for the username provided

--cycletime: The time to sleep between polls. All emails are retrieved and then ZenPOP sleeps for this amount of time before waking up and attempting to pull new emails.