Setting it up

1. Install the mailtoplone packages

Mailtoplone consist of three eggs:

mailtoplone.policy:

 Installs mailtoplone.base and mailtoplone.contentrules.

mailtoplone.base:

 Contains the custom types InBox and Email, also the adapters used when generating content out of emails and the dropemail script.

mailtoplone.contentrules:

Contains definitions of content rules actions and conditions to be used with mailtoplone

You can get these eggs and also a buildout from the collective

mailtoplone.base and mailtoplone.contentrules are also on pypi.

2. Create your global InBox

Add an InBox to the portal.

3. Mark existing content to be used together with mailtoplone

Mailtoplone finds possible dropboxes by their markerinterface, following Markerinterfaces are currently (version 0.1) defined:
 

IMailDropBoxMarker(Interface):

 """ marker interface for mail drop boxes """ 

IBlogMailDropBoxMarker(IMailDropBoxMarker):

""" marker interface for blog mail drop boxes """   

IEventMailDropBoxMarker(IMailDropBoxMarker):

""" marker interface for event mail drop boxes """ 

Remember to reindex the object after marking it.

4. Create Content Rules and assign them to your InBox

You can use each of the standard triggers, conditions and actions and combine them, with the one's defined
by mailtoplone. A common rule may consist of following components:

• Event trigger: Object added to this container
• Condition: Email Header
• Action: Deliver
• Action: Delete Object

Assigning such a rule to the InBox would enable to delivier emails to another destination in your portal and create content
there based on the context (by using the provided markerinterfaces different implementations of the drop method are
called, thank's to the component architecture).