What GDPR and ePrivacy requires#
GDPR requires a lawful basis (usually consent) for marketing email and documented consent records.
What cold email infrastructure is#
Cold email infrastructure is the set of secondary domains, mailboxes, authentication records, and sending tools used to run outbound campaigns without risking a company's primary domain.
Why it matters#
Cold outreach carries higher complaint risk. Isolating it protects the main domain's transactional and marketing reputation.
How cold email infrastructure supports GDPR and ePrivacy compliance#
Regulators and recipients need to identify who sent a message and trust that opt-out mechanisms work. Cold email infrastructure contributes by cold outreach carries higher complaint risk. Isolating it protects the main domain's transactional and marketing reputation.
Implementation steps#
- Register 2 to 5 lookalike domains and redirect them to your main site.
- Set up SPF, DKIM, and DMARC on every domain from day one.
- Create 2 to 3 mailboxes per domain and warm each for 3 to 4 weeks.
- Cap sends at 30 to 50 per mailbox per day and rotate across mailboxes.
- Monitor bounce and reply rates per mailbox; retire any that degrade.
Frequently asked questions#
How many emails can I send per mailbox per day?
Google Workspace allows 2,000, but for cold outreach 30 to 50 keeps you under behavioral thresholds.
Should I use Google Workspace or Microsoft 365 for cold email?
Both work. Workspace mailboxes tend to warm faster; Microsoft has stricter outbound spam filtering.