Lists that people want
Build a permission-first signup flow
Record a clear subscription request and make confirmation and removal predictable.
Language
Open the Academy in your preferred language.
The Deliverlens academy
Less guesswork. More useful evidence. Learn how email authentication, reputation and receiving systems fit together—one practical question at a time.
Explore the lessonsFollow a track, or find a specific answer below.
100 published lessons found.
Lists that people want
Record a clear subscription request and make confirmation and removal predictable.
Lists that people want
Set expectations and confirm intent without sending a marketing message prematurely.
Lists that people want
Keep unsubscribe, complaint, and permanent-failure decisions consistent across senders.
Lists that people want
Define evidence-based retry and suppression rules with provider-specific handling.
Lists that people want
Map message purpose and recipient expectation to the correct subscription controls.
Lists that people want
Preserve purpose, provenance, and suppression status while merging records.
Lists that people want
Choose a justified cohort and an exit path instead of repeatedly contacting everyone.
Lists that people want
Trace acquisition source, message expectations, frequency, and suppression processing.
Lists that people want
Check permission provenance and avoid assuming a verified address is permission to send.
Lists that people want
Assign accountable checks for acquisition, suppression, bounce handling, and deletion.
Reputation & blocklists
Identify the correct IP or domain, confirm the dataset, and act on the underlying cause.
Reputation & blocklists
Query each supported dataset with the right identifier and interpret its purpose.
Reputation & blocklists
Explain domain/address signal coverage without implying a universal mailbox blacklist.
Reputation & blocklists
Use trusted message evidence instead of checking the website hosting IP.
Reputation & blocklists
Document remediation and follow the list operator’s actual process.
Reputation & blocklists
Coordinate with the provider and separate customer controls from infrastructure controls.
Reputation & blocklists
Distinguish a network-use policy from evidence of a compromised server.
Reputation & blocklists
Inventory relevant link/redirect domains without claiming exhaustive reputation coverage.
Reputation & blocklists
Preserve unavailable/unknown states and honor licensing and resolver requirements.
Reputation & blocklists
Combine timestamped observations with bounce trends and provider feedback.