Marketing email promotes products, features, or events and generally requires prior consent. Transactional email completes an action the recipient already requested—a password reset, invoice delivery, TTN clearance notice, or order confirmation. Mixing the two in one list or template library is how Tunisian and MENA teams trigger spam complaints, personal-data authority questions, and mailbox-provider throttling.
At DarDev we operate Twenty CRM, Listmonk, and Stalwart on send.dardev.net. Cold Hesabi prospects stay in CRM with consent:unknown until documented opt-in; only then do sync-worker rules add them to Listmonk marketing lists. This guide explains the split we enforce in production. Legal interpretation for your sector belongs with your counsel and INPDP advisors.
What counts as marketing vs transactional?
Marketing tries to sell or nurture someone who has not agreed to promotional contact—EscaHire waitlist updates, Hesabi demo invites, cross-sell from DarDevLab, seasonal promos. Transactional mail follows a user action or contract: password resets, billing receipts, TTN status, security alerts. When product newsletters embed upgrade CTAs, treat the send as marketing even for existing customers.
Consent in Tunisia and the MENA context
Tunisia's Law 63-2004 (INPDP) treats contact data as personal information; direct marketing typically needs clear, prior, demonstrable consent. A trade-show business card, OECT directory row, or Startup Tunisia export does not grant promotional rights—we import to Twenty with consent:unknown until opt-in via mail.dardev.net/subscribe/* or another documented channel.
MENA operators also face EU GDPR for EU residents and Gmail/Outlook complaint policies that punish poor list hygiene faster than local statute. Keep evidence in one place: who consented, when, through which form, and to which list type (news vs marketing).
- Timestamp and source of opt-in (subscribe form URL, in-app checkbox label)
- List type subscribed—product news vs marketing promos are separate permissions
- Double opt-in confirmation token where the public form supports it
- CRM tag history before the sync-worker added Listmonk membership
- Suppression within 24 hours on hard bounce, complaint, or unsubscribe
How DarDev separates lists in production
Bulk mail exits through send.dardev.net with aligned SPF, DKIM, and DMARC—not the Zoho root domain used for human inbox traffic. See why-send-dardev-subdomain for that DNS split. Listmonk private news lists serve customers who want changelog-style updates; public marketing lists use double opt-in at mail.dardev.net.
Twenty CRM never sends mail—it holds relationship data and tags. When tags like customer:hesabi or product:hesabi:marketing change, the sync-worker updates Listmonk membership. See inside-unified-mailer-stack for the Twenty → Listmonk → Stalwart path and crm-driven-product-lists for tag conventions. CRM imports and marketing opt-in stay decoupled so a sales spreadsheet cannot become a campaign audience.
Checklist before the next campaign
- Classify every template
Label each Listmonk template marketing or transactional before upload. Transactional templates must not include promo modules or secondary CTAs.
- Verify list provenance
Marketing lists contain only subscribers with opt-in evidence. News lists sync from CRM tags tied to product relationships, not cold imports.
- Confirm From on send.dardev.net
Use noreply@send.dardev.net (or a sibling transactional subdomain) in Listmonk SMTP settings. Never configure Listmonk with an @dardev.net From header.
- Seed-test receivers
Send to Gmail and Microsoft test inboxes; review authentication headers and spam-folder placement before scaling batch size.
- Wire bounce and complaint handling
Pause or trim the batch when complaint rates spike. Review Stalwart and Listmonk logs weekly during active nurture programs.
Common mistakes
- Importing CRM prospects straight into marketing lists after a conference spreadsheet
- Using one master list for Hesabi product alerts and promo blasts so unsubscribe kills compliance notices
- Hiding marketing paragraphs inside invoice or receipt footers
- Assuming B2B contact data from a public directory equals marketing permission in Tunisia
- Sending cold outreach from the same subdomain as password-reset mail without list separation
Self-hosting Listmonk and Stalwart trades SaaS convenience for control over logs, suppression, and authentication—see self-hosted-email-vs-saas. The compliance split applies regardless: marketing needs provable opt-in, transactional needs a tight trigger, and the two must not share one list.
Questions about mailer architecture or deliverability reviews: news.dardev.net or dardev.net—requests land in Twenty CRM like any DarDev Services inquiry.
Can we email existing Hesabi customers about a new feature without fresh consent?
Release notes, TTN rule changes, and security patches belong on the news list they opted into at signup. Discounts and cross-sell need the marketing list and marketing consent path. When unsure, treat as marketing.
What evidence should we keep for INPDP or internal audit?
Store opt-in timestamp, form URL, list name, confirmation method, CRM tag history before sync-worker sync, and unsubscribe logs. This is operational guidance—confirm retention with qualified counsel.
Is a cold OECT or Startup Tunisia import enough for a nurture campaign?
No. Imports land with consent:unknown in Twenty. Run CRM outreach only if counsel approves that channel, but do not bulk-subscribe to Listmonk marketing until mail.dardev.net/subscribe/hesabi-marketing.html or documented consent.
Should transactional and marketing mail share send.dardev.net?
Yes, with separate Listmonk lists and templates so marketing complaint spikes do not affect password-reset delivery. Split to a sibling subdomain later if volume demands it.
How does this differ from DarDev News subscriptions?
News lists carry product updates; marketing lists carry promos and waitlist nurture. Each needs its own opt-in—see crm-driven-product-lists.
