Problem / Motivation
eM Client's Mass Mail (and SmarterMail's mailing-list / merge features) let you send a personalized message individually to many recipients using merge fields — each recipient gets their own separate email with their own name/fields, not a big visible CC/BCC. Bulwark already has reusable templates with placeholders ({{recipientName}}, {{date}}, …) but no way to fan a template out to a recipient list as individual personalized messages.
Proposed Solution
A "Mass mail / mail merge" action in the composer:
- Pick a template (or write one) containing merge placeholders.
- Choose a recipient source: a contact group, an address book, or a pasted list / CSV with columns usable as merge fields.
- Preview a couple of rendered messages.
- Send one individual message per recipient with per-recipient field substitution, and a configurable send-rate / delay (reuse the existing scheduled-send / send-delay plumbing to avoid tripping server rate limits).
Alternatives Considered
BCC a large list — no personalization, poor deliverability, and it exposes the list size. External mail-merge tools — force the user out of Bulwark's UI and to re-key identities/signatures.
Feature Area
Email
Mockups / Examples
eM Client "Mass Mail" with merge fields; SmarterMail mailing lists.
Additional Context
Builds directly on the template/placeholder engine and the scheduled-send / send-delay features already present in Bulwark — this is largely a new orchestration layer over existing pieces rather than net-new infrastructure.
Problem / Motivation
eM Client's Mass Mail (and SmarterMail's mailing-list / merge features) let you send a personalized message individually to many recipients using merge fields — each recipient gets their own separate email with their own name/fields, not a big visible CC/BCC. Bulwark already has reusable templates with placeholders (
{{recipientName}},{{date}}, …) but no way to fan a template out to a recipient list as individual personalized messages.Proposed Solution
A "Mass mail / mail merge" action in the composer:
Alternatives Considered
BCC a large list — no personalization, poor deliverability, and it exposes the list size. External mail-merge tools — force the user out of Bulwark's UI and to re-key identities/signatures.
Feature Area
Email
Mockups / Examples
eM Client "Mass Mail" with merge fields; SmarterMail mailing lists.
Additional Context
Builds directly on the template/placeholder engine and the scheduled-send / send-delay features already present in Bulwark — this is largely a new orchestration layer over existing pieces rather than net-new infrastructure.