agentleFS
grasmashgrasmash/drupal-claude-skills/skills/drupal-mail/SKILL.md

drupal-mail

Skill81 starsChanged 42 days agoMITView on GitHub

Drupal mail system configuration for local testing (Mailpit) and production (Mailchimp Transactional). Covers HTML email rendering, Content-Type headers, sender/formatter plugins, and troubleshooting. Use when testing emails locally, debugging email issues, or configuring mail delivery.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Content-Type Header: Must be set to text/html for HTML rendering

    line 52
  2. Very specific:

    Use inline styles (email clients strip <style> tags)

    line 98
  3. Very specific:

    Check Headers tab: Content-Type: text/html.

    line 158
  4. Distinctive:

    Check HTML tab: Proper styled rendering

    line 159
  5. Distinctive:

    Check Text tab: Plain text fallback

    line 160

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Drupal Mail System Configuration

Quick Reference

Local Testing (DDEV Mailpit)

Working configuration for HTML emails in Mailpit:

# mailsystem.settings
defaults:
  sender: php_mail
  formatter: mailchimp_transactional_mail

Enable/disable notifications:

# Check if notifications are disabled
ddev drush state:get my_notifications.disabled

# Enable notifications (for local testing)
ddev drush state:set my_notifications.disabled 0

# Disable notifications (to stop local emails)
ddev drush state:set my_notifications.disabled 1

View Mailpit:

  • URL: https://<project>.ddev.site:8026
  • Or run: ddev mailpit

Production Configuration

Mailchimp Transactional (Mandrill) for sending:

# mailsystem.settings
defaults:
  sender: mailchimp_transactional_mail
  formatter: mailchimp_transactional_mail

Mail System Architecture

Key Concepts

  1. Sender: The plugin that actually sends the email (SMTP, PHP mail(), API)
  2. Formatter: The plugin that formats the email body (converts HTML, wraps content)
  3. Content-Type Header: Must be set to text/html for HTML rendering

Plugin Combinations

EnvironmentSenderFormatterHTML Works?Notes
Local (Mailpit)php_mailmailchimp_transactional_mailYesRecommended for local testing
Local (Mailpit)php_mailphp_mailNoStrips HTML to plain text
Productionmailchimp_transactional_mailmailchimp_transactional_mailYesUses Mandrill API
Productionsymfony_mailersymfony_mailerYesRequires SMTP config

HTML Email Requirements

Content-Type Header

Critical: Module must set Content-Type header in hook_mail_alter():

/**
 * Implements hook_mail_alter().
 */
function my_notifications_mail_alter(&$message) {
  if ($message['module'] === 'my_notifications') {
    $message['headers']['Content-Type'] = 'text/html; charset=UTF-8';
  }
}

Without this, HTML renders as plain text even with correct formatter.

Message Template Format

Config entity format (message.template.*.yml):

text:
  -
    value: |-
      Subject line with [tokens]

      <p style="margin: 0 0 16px 0; color: #333;">HTML body content</p>
    format: full_html

Key points:

  • First line = email subject (extracted, stripped of HTML)
  • Rest = HTML email body
  • Use inline styles (email clients strip <style> tags)
  • format: full_html enables HTML rendering

Configuration Commands

Check Current Config

# View mail system settings
ddev drush cget mailsystem.settings

# View notification plugin settings
ddev drush cget my_notifications.settings

# Check global disable state
ddev drush state:get my_notifications.disabled

Switch Between Local and Production

For local testing:

# Enable HTML email capture in Mailpit
ddev drush cset mailsystem.settings defaults.sender php_mail -y
ddev drush cset mailsystem.settings defaults.formatter mailchimp_transactional_mail -y
ddev drush state:set my_notifications.disabled 0
ddev drush cr

Reset to production:

ddev drush cset mailsystem.settings defaults.sender mailchimp_transactional_mail -y
ddev drush cset mailsystem.settings defaults.formatter mailchimp_transactional_mail -y
ddev drush state:set my_notifications.disabled 1
ddev drush cr

Testing Notifications

Test Commands

Give your notification module drush test commands so each template can be fired on demand, e.g.:

# Test entity deleted notification
ddev drush my-notifications:test-entity-deleted

# Test entity updated notification
ddev drush my-notifications:test-entity-updated

# Test comment notification
ddev drush my-notifications:test-comment

# Test group invitation
ddev drush my-notifications:test-invitation

Verify Email in Mailpit

  1. Open https://<project>.ddev.site:8026
  2. Check Headers tab: Content-Type: text/html; charset=UTF-8
  3. Check HTML tab: Proper styled rendering
  4. Check Text tab: Plain text fallback

Mailpit API

# List recent messages
curl -sk "https://<project>.ddev.site:8026/api/v1/messages" | jq '.messages[:3]'

# Get specific message with HTML
curl -sk "https://<project>.ddev.site:8026/api/v1/message/{ID}" | jq '{Subject, HTML}'

# Delete all messages
curl -sk -X DELETE "https://<project>.ddev.site:8026/api/v1/messages"

Troubleshooting

No Emails Appearing

  1. Check global disable state:
    ddev drush state:get my_notifications.disabled
    # If TRUE, run: ddev drush state:set my_notifications.disabled 0
  2. Check sender plugin:
    ddev drush cget mailsystem.settings defaults.sender
    # For Mailpit: should be php_mail
  3. Check DDEV is running:
    ddev describe | grep -i mail
  4. Test raw PHP mail:
    ddev exec "php -r \"mail('test@example.com', 'Test', 'Body');\""
    # Should appear in Mailpit immediately

HTML Not Rendering (Shows Raw Tags)

  1. Check formatter plugin:
    ddev drush cget mailsystem.settings defaults.formatter
    # Should be mailchimp_transactional_mail for HTML
  2. Check Content-Type header in hook_mail_alter():
    grep -r "Content-Type.*text/html" web/modules/custom/
  3. Check template format:
    grep "format:" config/default/message.template.*.yml
    # Should show: format: full_html

Emails Sending to Production

  1. Check sender plugin:
    ddev drush cget mailsystem.settings defaults.sender
    # If mailchimp_transactional_mail, emails go to real addresses!
  2. Switch to local capture:
    ddev drush cset mailsystem.settings defaults.sender php_mail -y

Module Dependencies

  • mailsystem: Routes mail through configured plugins
  • mailchimp_transactional: Provides Mandrill integration
  • message: Provides template-based message entities
  • my_notifications: Custom notification system

File Locations

  • Mail config: config/default/mailsystem.settings.yml
  • Notification settings: config/default/my_notifications.settings.yml
  • Message templates: config/default/message.template.*.yml
  • Notification processor: web/modules/custom/my_notifications/src/Plugin/QueueWorker/NotificationProcessor.php
  • Mail alter hook: web/modules/custom/my_notifications/my_notifications.module

Apply to Files

  • config/default/mailsystem.settings.yml
  • config/default/my_notifications.settings.yml
  • config/default/message.template.*.yml
  • web/modules/custom/my_notifications/**/*.php
  • web/modules/custom/my_notifications/*.module

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.