Products.MailHost 2.13.4

zope.sendmail integration for Zope 2.

Overview

The MailHost product provides support for sending email from within the Zope environment using MailHost objects.

An optional character set can be specified to automatically encode unicode input, and perform appropriate RFC 2822 header and body encoding for the specified character set. Full python email.Message.Message objects may be sent.

Email can optionally be encoded using Base64, Quoted-Printable or UUEncode encoding (though automatic body encoding will be applied if a character set is specified).

Usage

MailHost provides integration with the Zope transaction system and optional support for asynchronous mail delivery. Asynchronous mail delivery is implemented using a queue and a dedicated thread processing the queue. The thread is (re)-started automatically when sending an email. The thread can be started manually (in case of restart) by calling its manage_restartQueueThread?action=start method through HTTP. There is currently no possibility to start the thread at Zope startup time.

Supports TLS/SSL encryption (requires Python compiled with SSL support).

Configuration

To force MailHost to only queue mails without sending them, activate queuing in the ZMI and set the environment variable MAILHOST_QUEUE_ONLY=1. This could be helpful in a staging environment where mails should not be sent.

Changelog

2.13.4 (2019-06-03)

• Do not start QueueProcessorThread on configuration update. (#14)

2.13.3 (2019-04-03)

• Add ability to disable sending of queued mails. Details see README.txt. (#14)

2.13.2 (2014-11-02)

• Adjust tests to pass with latest zope.sendmail versions.

• Specify detailed distribution dependencies.

2.13.1 (2010-09-25)

• LP #642728: Fixed TypeError on nested multi part messages in MailHost.

2.13.0 (2010-07-13)

• Released as separate package.