diff --git a/scripts/campaigns/README.md b/scripts/campaigns/README.md index e2da8a7..dacf781 100644 --- a/scripts/campaigns/README.md +++ b/scripts/campaigns/README.md @@ -84,6 +84,27 @@ The `--sandbox` flag does TWO things: so the test gifts (non-redeemable in sandbox) don't actually land in any real customer inbox +### `--from` sender + +The Mailjet account has `targo.ca` verified at the domain level (SPF + +DKIM + DMARC), so any `*@targo.ca` sender works out of the box. The +default we use for gift campaigns is: + +``` +--from "Gigafibre Support " +``` + +Reasoning: it's a human-monitored mailbox (unlike `noreply@`), so if a +recipient hits reply with a question about their gift, someone sees it +and can help. The hub's transactional emails (invoices, magic links) +still go from `noreply@targo.ca` — campaigns are different in that +they invite a reply. + +If you ever need a `@gigafibre.ca` sender, that's a 30-min DNS + Mailjet +setup (add the domain in Mailjet → publish SPF/DKIM CNAMEs in +Cloudflare) — not done yet because all customer-facing email currently +flows through `targo.ca`. + ## Stage 2 — send the personalized French emails ## Dry run (no emails sent, HTML written for preview) @@ -96,7 +117,7 @@ node send_gift_campaign.js \ --subject "🎁 Un cadeau pour vous, de la part de Gigafibre" \ --amount "50 $" \ --expiry "31 décembre 2026" \ - --from "Gigafibre " \ + --from "Gigafibre Support " \ --dry-run ``` @@ -118,7 +139,7 @@ node send_gift_campaign.js \ --subject "🎁 Un cadeau pour vous, de la part de Gigafibre" \ --amount "50 $" \ --expiry "31 décembre 2026" \ - --from "Gigafibre " \ + --from "Gigafibre Support " \ --smtp-host in-v3.mailjet.com --smtp-port 587 \ --smtp-user "$SMTP_USER" --smtp-pass "$SMTP_PASS" \ --throttle-ms 600