v16.1

Notifuse/notifusev16.1Nov 6, 2025by pierre-b

AI Summary

Notifuse 16.1 introduces SMTP Relay support, enabling users to connect SaaS applications that only provide SMTP integration (like Supabase Auth, Firebase, Auth0) to Notifuse. This allows full control over email designs and branding using Notifuse's MJML editor instead of default SaaS templates, with secure TLS encryption on port 587.

Key Highlights

  • Built-in SMTP Relay Server for connecting SaaS platforms with SMTP-only integration
  • Support for popular auth platforms: Supabase Auth, Firebase, Auth0, Keycloak, and more
  • TLS encryption with STARTTLS on port 587 for secure email transmission
  • Simple authentication using workspace API credentials
  • JSON payload format matching the Transactional API format for email content

New Features

  • SMTP Relay Server with configurable domain and port
  • TLS/STARTTLS encryption support with base64-encoded certificate configuration
  • JSON payload email body format with workspace_id, notification, contact, data, and email_options
  • Environment variable configuration (SMTP_RELAY_ENABLED, SMTP_RELAY_DOMAIN, SMTP_RELAY_PORT, SMTP_RELAY_TLS_CERT_BASE64, SMTP_RELAY_TLS_KEY_BASE64)
  • Full integration with existing transactional notification features including deduplication, template variables, and email options (reply_to, cc, bcc)

Full Release Notes

# Notifuse 16.1 - SMTP Relay for Transactional Emails

We're excited to announce **SMTP Relay support** for transactional emails! 🎉

This new feature allows you to connect SaaS applications that only provide SMTP integration to Notifuse, giving you full control over email designs and branding. Instead of being stuck with default email templates from your SaaS tools, use Notifuse's powerful MJML editor to create beautiful, custom-designed emails.

## 🚀 Key Features

### Built-in SMTP Relay Server

- **SaaS Integration**: Connect any SaaS platform that only offers SMTP integration (Supabase Auth, Firebase, Auth0, etc.)
- **Custom Email Designs**: Design beautiful emails with Notifuse's MJML editor instead of using default SaaS templates
- **Secure by Default**: TLS encryption support with STARTTLS on port 587
- **Simple Authentication**: Use your workspace API credentials (API email as username, API key as password)
- **JSON Payload Format**: Email body contains a JSON payload matching the Transactional API format

### Configuration

Enable SMTP Relay with these environment variables:

```bash
SMTP_RELAY_ENABLED=true
SMTP_RELAY_DOMAIN=smtp.yourdomain.com
SMTP_RELAY_PORT=587
SMTP_RELAY_TLS_CERT_BASE64="<base64-encoded-certificate>"
SMTP_RELAY_TLS_KEY_BASE64="<base64-encoded-private-key>"
```

## 📖 Usage Example

Simply configure your SaaS application's SMTP settings with Notifuse's SMTP relay credentials, and all emails will be sent through your custom-designed Notifuse templates.

**Connection Details:**

```
Host:     smtp.yourdomain.com
Port:     587
Security: STARTTLS required
Username: your-api-email@example.com
Password: your_api_key_here
```

**Email Body Payload:**

```json
{
  "workspace_id": "your-workspace-id",
  "notification": {
    "id": "notification-id",
    "external_id": "unique-id-123",
    "channels": ["email"],
    "contact": {
      "email": "recipient@example.com",
      "first_name": "John",
      "last_name": "Doe"
    },
    "data": {
      "product_name": "Premium Plan",
      "amount": "$99.99"
    },
    "email_options": {
      "reply_to": "support@example.com",
      "cc": ["manager@example.com"],
      "bcc": ["audit@example.com"]
    }
  }
}
```

## 🔧 Use Cases

- **SaaS Platform Customization**: Integrate with SaaS platforms that only offer SMTP for emails (Supabase Auth, Firebase Auth, Auth0, Keycloak, etc.)
- **Brand Consistency**: Maintain consistent email branding across all your SaaS tools
- **Design Control**: Use Notifuse's MJML editor to create professional, responsive email designs
- **No-Code Email Templates**: Let your marketing team design emails without touching SaaS platform code
- **Multi-Platform Integration**: Centralize email design and delivery for all your integrated SaaS tools

## 📚 Documentation

- **Installation Guide**: See [SMTP Relay Configuration](https://docs.notifuse.com/installation#smtp-relay-configuration) for production setup
- **Usage Examples**: Check the API Command Modal in your Notifuse console for language-specific examples

## 🔐 Security Notes

- Production deployments should use valid TLS certificates
- Self-signed certificates are supported for development only
- SMTP envelope To/From addresses are ignored - actual recipient is determined by `contact.email` in the JSON payload

## 🛠️ Technical Details

**Environment Variables:**

- `SMTP_RELAY_ENABLED` - Enable/disable SMTP relay (default: `false`)
- `SMTP_RELAY_PORT` - SMTP relay port (default: `587`)
- `SMTP_RELAY_DOMAIN` - Public domain name for SMTP relay
- `SMTP_RELAY_TLS_CERT_BASE64` - Base64-encoded TLS certificate
- `SMTP_RELAY_TLS_KEY_BASE64` - Base64-encoded TLS private key

**Features:**

- Support for all transactional notification features (deduplication, template variables, email options)
- Full integration with existing email service providers
- Error handling and validation

---

**Upgrade Instructions:**

```bash
# Pull the latest image
docker pull notifuse/notifuse:16.1

# Restart your container
docker compose restart
```

For detailed installation and configuration instructions, visit our [documentation](https://docs.notifuse.com/installation).

---

**Feedback & Support:**

If you have any questions or feedback about this release, please:

- Open an issue on [GitHub](https://github.com/notifuse/notifuse/issues)
- Join our community discussions
- Check our documentation at [docs.notifuse.com](https://docs.notifuse.com)