Setup
Email Setup
Configure sender email, SMTP, verification, domain pacing, and deliverability requirements for GrowthEngene outreach.
Quick Answer
Required Email Configuration
Email sending requires a valid sender setup. Depending on the workspace, this can include SMTP credentials, domain configuration, sender verification, and deliverability checks.
GrowthEngene separates sending identities from verification/probing identities. This protects sender reputation and keeps verification traffic from damaging outreach domains.
- Verified sender email.
- SMTP or sending provider configuration.
- Sending domain with appropriate authentication status where managed domains are used.
- Valid recipient email checks.
- Suppression and unsubscribe checks.
- Domain pacing and sending limits.
- Encrypted credential storage for SMTP passwords.
What GrowthEngene Checks Before Sending
GrowthEngene can guard outgoing messages by checking sender status, recipient validity, suppression rules, resume attachments for job outreach, and domain pacing limits.
For outreach automation, the shared send-mode resolver can require verified sender, resume attachment, valid recipient, suppression clearance, and domain pacing clearance before a send is allowed.
- Sender identity is configured and allowed for the workflow.
- Recipient email is present, valid, verified, or high-confidence enough for the workflow.
- Suppression and unsubscribe rules do not block the contact.
- Recipient-domain pacing allows the send now.
- Resume attachment is available when the workflow requires it.
- Campaign or draft review state allows sending.
Email Infrastructure Concepts
The email infrastructure is domain-first. Domains can have SMTP accounts, policies, provider identities, usage logs, authentication state, and reputation information.
GrowthEngene separates three email streams so operational traffic stays easier to reason about: transactional messages, outreach campaigns, and verification/probing.
- Transactional stream: platform alerts, account email, password reset, billing, and system messages.
- Outreach stream: cold email, campaign sequences, resume emails, and follow-ups.
- Verification stream: SMTP handshakes, catch-all checks, and email validation probes.
- Quota-aware routing checks purpose, authentication health, caps, warmup, and historical success before choosing a sender.
Recommended First Email Test
For the first email test, prefer queued or reviewed sends. Do not treat a live send as the first proof of setup; first prove that sender, recipient, attachment, suppression, pacing, and draft content are visible and correct.
- Add or confirm the sending domain and SMTP account.
- Test the SMTP account where the UI supports it.
- Bind or select the sender identity for the account or workspace.
- Run email discovery or use a known valid test recipient.
- Queue a reviewed send before enabling guarded auto-send.
Common Email Setup Blocks
Most blocked email sends come from missing sender identity, missing SMTP account, weak recipient confidence, missing resume attachment, suppression, or same-recipient-domain pacing.
- Sender email is blank or not verified.
- SMTP account is inactive, untested, or not allowed for outreach.
- Recipient address is missing, invalid, risky, or below confidence threshold.
- Resume file is missing for job application workflows.
- Suppression, unsubscribe, or domain pacing blocks the send.
- Send mode is draft-only or review-first.
Frequently Asked Questions
Can GrowthEngene send email without sender verification?
For guarded sending flows, GrowthEngene should require a verified sender before outreach is sent.
Why does GrowthEngene separate sending SMTP and verification SMTP?
Verification traffic can be riskier than normal outreach, so GrowthEngene separates verification/probing identities from sending identities to protect sender reputation.
What blocks a guarded email send?
A guarded send can be blocked by missing sender verification, invalid recipient, missing resume, suppression, domain pacing, low score, low confidence, or review-first send mode.