Where to go from here

by Hans-Peter Locher — last modified Feb 04, 2009 03:06 AM

Mailtoplone makes heavy usage of the component architecture, and therefore, like plone itself encourages you to extend it's functionality.

Extending mailtoplone

Mailtoplone makes heavy usage of the component architecture, and therefore, like plone
itself encourages you to extend it's functionality. Here are some approaches:

define more conditions to check the mail for
define more actions ( deliver to foreign urls e.g. )
create more sophisticated adapters (e.g. create content types for addon products)
maybe there's more than just content creation, for example reporting
Create more ways emails get to the plone instance ( e.g. fetching from a mailserver via pop or imap)
*

Check out the project page,

try out mailtoplone, post to the tracker,
or contact me on irc (#plone, mr_savage)

« Previous: Example: Create a blog

Knowledge Base: The Knowledge Base is a place for free-form, community-mantained documentation. If you want to contribute, ask for collective access here.

About

You are reading:

from mailtoplone: Integrate emails with plone.

Mailtoplone's main purpose is to create plone content from emails. The emails are delivered to plone as plaintext containing the entire email including the envelope. Mailtoplone makes heavy use of the zope 3 component architecture and plone's content rules. The tutorial explains the approach and shows an example usecase.

All content on a single page

Use with: Plone 3
Relevant for:

This document was contributed by Hans-Peter Locher, and last modified 1101 days ago.

Visit our chat rooms or support forums if you have more specific questions.

You can also learn how to design, build, and deploy a website in Plone through one of the numerous Plone training sessions around the world.

Report errors, omissions, etc., to the documentation by emailing plone-docs@lists.sourceforge.net