Hunta — give every client their own sender address on your domain

Optional. Without it, Hunta sends every application from your Gmail, signed "Candidate (via your brand)". With it, each client gets an address of their own on your domain — created automatically from their name, nothing to set up per client — and every reply still lands in one inbox you already read, with a Hunta alert when an employer answers. Operators and candidates both get copies of outgoing applications; replies are addressed to the candidate and the operator.

Paid feature: own-domain sending is available on Solo, Studio and Sovereign. Demo and the 7-day trial use a Gmail app password and send from that Gmail; they cannot connect a domain or a non-Gmail mail server.

What employers see	Lerato Dube (via Momentum Careers) <lerato.dube@momentumcareers.co.za>
Where replies go	Your reply inbox (Cloudflare forwards the whole domain there), plus the candidate directly (Reply-To); Hunta alerts the operator
Who sees sent mail	Candidate receives a private Bcc copy; the operator has a Sent copy in Gmail/IMAP
Who signs the mail	Your domain (DKIM through the relay), so Gmail and Outlook see a properly authenticated sender
Cost	Relay route: the domain only (about R100–R200/year for a .co.za); Cloudflare Email Routing and the relay free tier cost R0. If you already run a mail server, Hunta can use its SMTP + IMAP at no extra email-provider cost.

1 Domain DNS

Buy a domain from any registrar (a .co.za is cheapest), or use one you already own.
For the relay route, put the domain on a free Cloudflare account and change the registrar's nameservers to the two Cloudflare shows. For your own mail server, keep your existing DNS provider and MX if you prefer.

Already have a mail server (for example, your own cPanel/Exim setup)? Keep its MX and skip Cloudflare Email Routing. Your server must accept mail to the candidate addresses (catch-all or aliases), allow SMTP sending with those From addresses, and provide IMAP for Hunta's reply alerts. Use its own SMTP/IMAP login in section 2 and choose “My own mail server” in section 3. Hunta will save sent copies through IMAP. No separate relay subscription is required. If your existing provider is Google Workspace or Microsoft 365, it must permit the candidate aliases as send-as addresses; otherwise use a relay.

2 Forward the whole domain to your Gmail (free)

In Cloudflare: your domain → Email → Email Routing → enable. Let it add its MX and SPF records.
Destination addresses → add your Gmail → click the link Cloudflare emails you.
Routing rules → Catch-all address → action Send to an email → your Gmail → enable.

Now anything@yourdomain reaches your Gmail, which is why Hunta never has to create addresses one by one.

3 A free sending relay

Cloudflare only receives. To send as your domain, pick one free relay:

	Brevo (recommended)	SMTP2GO
Free tier / Hunta safety cap	300/day; Hunta allows up to 140 applications/day including each candidate's private copy	1,000/month; Hunta allows up to 15 applications/day including each candidate's private copy
Add your domain	Senders, domains & dedicated IPs → Domains → Add a domain → Authenticate. With Cloudflare, “authenticate automatically” adds the `brevo-code` TXT, the two DKIM records (`brevo1/brevo2._domainkey`) and DMARC for you.	Sending → Verified senders → Add sender domain → add the CNAME records it lists in Cloudflare → Verify.
Hunta needs	SMTP & API → SMTP tab: the SMTP login (…@smtp-brevo.com) and a new SMTP key	Sending → SMTP users → add a user: its username and password

Paste the SMTP key, not your account password. Free tiers are for your own clients' applications, one at a time after you approve them. That's exactly what Hunta sends, so don't use the relay for newsletters or bulk mail.

4 Tell Hunta

Hosted (Solo, Studio, Sovereign)

In your Discord workspace press 🔐 Connect. For Cloudflare Routing + a relay, section 2 is the Gmail (reply inbox), then section 3 is domain + relay credentials. For a server you already run, choose My own SMTP/IMAP server in section 2, enter its host/login/password, and select My own mail server from section 2 in section 3. Hunta tests SMTP, IMAP and DNS, then posts the results in your channel. If your server only supports SMTP port 465, choose 465; IMAP uses SSL port 993.

Self-hosted (Sovereign)

# tenant.yaml: the relay sends, your Gmail reads replies
mailbox:
  provider: brevo                 # or smtp2go, or custom + host/port
  address: applications@momentumcareers.co.za
  username: 9a1b2c001@smtp-brevo.com
  display_name: Momentum Careers
  app_password: enc:...           # hunta encrypt <SMTP key>
inbox:
  provider: gmail
  address: you@gmail.com
  app_password: enc:...           # hunta encrypt <Gmail app password>
sender_domain: momentumcareers.co.za

$ hunta sender-check momentum
✅ momentumcareers.co.za: ready
✅ Receiving: MX points to Cloudflare Email Routing (set a catch-all to your Gmail).
✅ SPF found.
✅ Brevo ownership code published.
✅ DKIM: relay signing key published.
✅ DMARC found.
  lerato01             -> lerato.dube@momentumcareers.co.za
$ hunta mailbox-test momentum

Already have your own SMTP/IMAP server? No Brevo or SMTP2GO account is needed. In the paid hosted form choose “My own SMTP/IMAP server” and “My own mail server from section 2”. In self-hosted tenant.yaml, use:

mailbox:
  provider: custom
  address: ops@momentumcareers.co.za
  host: mail.momentumcareers.co.za
  port: 465                    # implicit TLS; 587 STARTTLS also works
  username: ops@momentumcareers.co.za
  imap_host: mail.momentumcareers.co.za
  imap_port: 993
  app_password: enc:...        # encrypt the server's mail password
inbox: null                    # same server is the reply inbox
sender_domain: momentumcareers.co.za

Have your mail administrator verify catch-all/alias routing, “send as” permissions, SPF/DKIM/DMARC, and that IMAP login works. If you only have a domain but no mail server, choose Cloudflare routing + a free relay instead.

5 Addresses

Automatic: first and last name, lower-case, accents dropped. Ruth Nyasha Mhlanga becomes ruth.mhlanga@, and Lérato Dube-Mhlanga becomes lerato.dube-mhlanga@.
Two clients with the same name, or a preference? Set send_as: ruth.m@yourdomain in that candidate's profile (self-host), or ask in your help channel (hosted).
When a client finishes, nothing to delete: the address simply stops being used. Mail to it still reaches you.
Replies are matched to the right person by the address they were sent to, even when an employer answers from a different system with a new subject line.