yab_email is a tiny Textpattern CMS-Plugin for obfuscating and defuscating email adresses to prevent harvesting email adresses.

This provides form field validation and spam prevention for zem_contact_reborn.

Specifically:

• submitted field combination check
• submitted field content validation
• anti-spam measures

Once installed, a collection of...

This plug-in adds an interface to the extensions tab to allow one to send plain text, HTML-only, or multipart (plain text & HTML, combined) emails from within the Textpattern admin interface.

When you publish a new post, this plugin will mail it to everywhere (email address of course :D) you want.

That means, you can publish the post onto other BSPs, which support email publish feature (like live space, or blogger), just as the same time you publish on textpattern.

This plugin helps two other plugins co-exist peacefully: the full-page caching of asy_jpcache and the powerful form processing of zem_contact_reborn (ZCR).

This plugin has been remade by the amazing Manfre. Get it here.

Reduces spam by using a hidden form field that only spammers will be tempted to fill out.

The companion plugin for zem_contact_reborn. Provides a language file which can be localised to any language you desire by editing the contents of this plugin once installed.

Zem_contact_reborn is a further developed fork of the zem_contact plugin. It is maintained by the Textpattern Community.

Add a little link to the email tagbuilder on the write page of the TXP interface.

Creates a simple profile page with Name, Age, Picture and Description

This plugin will generate a simple email feedback form, ideal for yoursite.com/contact.

zem_contact produces a flexible, customizable and secure email feedback form / email contact form for Textpattern.

This is a drop-in replacement for the txp:email tag which attempts to provide a more robust block against spam harvesters.

<txp:mrh_email_article_link /> generates a simple “mailto:” link using either a button image and/or text link that provides the URL for the current article in the message body (thus this should be used inside a single article form) and the title in the subject line.