email

Mailchimp Campaigns is a sub module of the Drupal 7 Mailchimp module that allows creating and sending campaigns, and viewing statistics from within a Drupal website.

Installation

The install file adds one table to list campaigns and one input filter format named MailChimp campaign. There is one entity added with the name MailChimp Campaign.

Add a Campaign

Add a list and a template first then switch on the campaign module then select Administration » Configuration » Web services » MailChimp then the Campaigns tab and add a campaign.

Enter a Title, Subject, and select a List. The From Email and From Name default to the site settings.

Now you select a Template from a list. The template has to exist before you add the campaign. The page appears to let you edit the template. I have not tested edits. There is no way to create a new template and no link to the MailChimp template creation page.

Creating Campaigns

1. Click Add a Campaign in the overview
2. Fill out the required fields
   • Title: An internal name to identify the campaign
   • Subject: Message subject

MailChimp Lists is a sub module of the Drupal 7 MailChimp module. It allows synchronizing Drupal users with MailChimp lists and it allows users to subscribe, unsubscribe, and update member information.

Note: this module does not automatically load lists from MailChimp.

Install

Install the parent module MailChimp
Install the module MailChimp Lists and the required module Entity in the usual way.

Add, edit, remove lists

Manage MailChimp lists at Administration > Configuration > Web services > MailChimp (http://example.com/admin/config/services/mailchimp/lists).

Add a list

You enter a Label, a Description, a Type of list, the Type of list, Settings that vary based on the type of list, the Roles that can subscribe to the list, and the MailChimp List you want to connect to. You have to have the list defined in Mailchimp before selecting it here. You cannot save your list definition until you select the Mailchimp list.

Settings

setup token

use the token custom module to create a new custom token with name "nodeemail" of TYPE: custom

and use php filter with following code

now wherever you have tokens available you can use [custom:nodeemail]

NOTE1: assuming that email field has machine name field_email and is not translatable ('und') otherwise change accordingly

NOTE2: to get more node fields use echo print_r($node); in the custom token or look at http://drupal.org/node/49768

Who needs this custom token ?

webform 4.x adds support for tokens but if webform is attached to node using "webform block" the tokens are not populating the webform fields as reported in #1544044: Attach webform to node, email to field from node and #1617086: Webform > E-mails: Add "Content values" (ie: node field) support so custom token is needed

This custom token might not be needed after this issue is resolved #919760: Add a [current-page:object:?] dynamic token

Commerce Email Documentation

This is the documentation page for the Commerce Email module.

Dependencies

The 2.x version is still not completely stable, but it should work if you have:

• commerce
• Variable in its DEV version
• Variable Email
• htmlmail

Please make sure you have those modules in their required versions and it should work...
(derived from http://drupal.org/node/1433822#comment-5579468 )

Basic installation and usage guide

• Download the latest 7.x-2.x version of Commerce Email
• Download the latest variable-7.x-1.x-dev

(So you won't run into #1451680: Notice: Undefined index: module en variable_type_include())

• Download rules, variable_email, entity, htmlmail, mailsystem, token
• Enable commerce_email
• Go to admin/commerce/config/email and configure your emails (it has Token support, so enable Token)

Introduction

If you use the Mailhandler module and you want different user accounts to have their own mailbox to send content to a site, you are required to configuring multiple Mailhandler mailboxes for each account as well as multiple feeds to process each mailbox. The provisioning of mailboxes on a mail server and configuration of so many Mailhandler mailboxes and the associated feeds could be automated, but it would be pretty gnarly.

The solution we came up with was to have a single mailbox on the mail server, and have a single mailhandler and single feed processor for the a site. Instead of each user getting their own inbox, we have a single inbox that collects email from any number of addresses. This can be done by either configuring the mail server to have a single ‘catch all’ address or, if available, a plus addressing scheme (think GMail).

What does this module do?

The module exposes the 'Send content by mail' permission.
The module provides a user interface to generate unique 'email addresses' for each user on the site with the 'Send content by mail' permission.

Why is that useful?

Note: more documentation for the Drupal 7 version of the MailChimp module is also available in the README files of the submodules.

About

The MailChimp module integrates with MailChimp, the popular email delivery service.

Features

• Embed subscription forms for any MailChimp list with custom meta data and a block for each list.
• Enables end users to manage their subscriptions from their account page.
• Allows end users to subscribe to lists during registration.
• Lets you map user tokens to MailChimp merge fields.
• Provides required, optional, and freeform lists. Required lists are automatically synchronized with the sites users. Optional lists provide a checkbox allowing users to subscribe during registration or when updating their account. Free form lists present a signup form with all MailChimp merge fields displayed.
• Allows subscriptions to be maintained via a batch process during cron or in real time.
• Allows the option of also enabling list "interest group" subscriptions, for more fine grained mailing list control.

Install

(Versions 7.x-2.8 and higher).