01Who this is for
- Founders who run email campaigns and need reliable deliverability for client outreach.
- Marketing managers responsible for bulk email sends and maintaining sender reputation.
- IT administrators who manage domain authentication and troubleshoot delivery issues.
02Recipient policy blocks, explained
The policy block resolution workflow helps you address email rejections that stem from the recipient’s administrative or security rules rather than technical failures. It guides you through checking SPF, DKIM, and DMARC records, assessing sender reputation, contacting the recipient’s IT team, and refining email content.
All actions are performed inside HighLevel. Authentication details are found under Settings > Email Services > Sending Domain & IP. Reputation metrics and bounce analytics are available in Marketing > Email Marketing > Analytics. The steps provide a structured path from immediate technical checks to longer term relationship building with recipient organizations.
03How businesses use recipient policy blocks
- SaaS startup. The team verifies SPF, DKIM, and DMARC in the Sending Domain & IP screen, monitors bounce rates in the Email Marketing analytics, and contacts enterprise clients’ IT departments to request whitelist entries, ensuring product updates reach key accounts.
- Real estate agency. Agents check authentication, track complaint rates, and adjust property newsletter content to avoid spam triggers. They then reach out to local MLS administrators to be added to approved sender lists, improving lead communication.
- Medical clinic. The clinic’s outreach staff confirms domain authentication, reviews spam complaint metrics, and follows a strict list cleaning schedule. When a hospital’s portal blocks messages, they call the hospital’s IT desk to request inclusion on the whitelist.
04The numbers and rules that matter
- Sender based blocks include IP or domain blacklisting, sender reputation restrictions, unauthenticated sender policies.
- Content based blocks include spam filter triggers, content policy violations, attachment restrictions.
- Access control blocks include whitelist only policies, external sender restrictions, group membership requirements.
- Reputation score aim on senderscore.org is 80+.
05How to set up and use recipient policy blocks in HighLevel
Resolve recipient policy blocks
- Open Settings > Email Services > Sending Domain & IP.
- Confirm the SPF record is correctly set for your sending domain.
- Confirm the DKIM record is correctly set for your sending domain.
- Confirm the DMARC record is correctly set for your sending domain.
- Run an external SPF test on MXToolbox.com.
- Run an external DKIM test on MXToolbox.com.
- Check DMARC alignment using dmarcian.com.
- Visit senderscore.org to view your IP reputation score.
- Gather the recipient’s IT contact information from their website or phone directory.
- Send a whitelist request that includes your sending domain, IP addresses, and proof of proper authentication.
06Settings that matter
- Sending Domain & IP. Controls the verification status of SPF, DKIM, and DMARC records for the domain you use to send emails.
07Things to know before you rely on it
- Some policy blocks are permanent decisions by the recipient organization and cannot be overridden.
- Whitelist requests depend on the recipient’s internal processes and may take days or weeks.
08How it connects to the rest of HighLevel
- Set up a dedicated sending domain in HighLevel Dedicated sending domain
- Learn email warm up and DMARC best practices Email warm up guide
- Enable email verification and manage billing Email verification
Michael's take

From my experience, ensuring your SPF, DKIM, and DMARC records are correctly set up is a good first step because authentication based blocks are common. Monitoring reputation scores and preparing a clear whitelist request for the recipient’s IT team can also improve the chances of resolution.