Search Mailpro® features, guides and resources

reliable departure gate. Our email is now on the runway. Second 1: The passport check (SPF, DKIM and DMARC) Before the receiving mail server lets your email

campaign list and fix the cause before sending again.Authenticate and clean before resendingConfigure SPF and DKIM for your sending domain, and read the broader

twice.Blocked / blacklisted IPCheck Mailpro’s sending IP reputation; pause the campaign.Authentication required / SPF or DKIM failsRe-check SPF, DKIM and DMARC on

yet authorized in SPF. Check your SPF, DKIM and DMARC records first — this is the most common cause. A blacklist hit. Your sending domain or IP showed up on a

tells filters « this is real, not phishing ». Layer 1: authenticate every send SPF — lists the IPs allowed to send for your domain. DKIM — cryptographically

, typos at signup, old addresses, or missing SPF/DKIM authentication. Cleaning your list before every send is the fastest way to cut bounces — Mailpro flags and

campaigns, the score will appear as "not enough data yet". Good news: The authentication and domain checks work immediately. You can set up SPF, DKIM and DMARC

& formatting A final score with recommendations Content is only half the battle — pair a clean score with SPF, DKIM and DMARC for the best inbox placement. Learn how

, or expected behaviour. 4 Have you already checked the FAQ? A lot of answers are already written up — deliverability, imports, SPF/DKIM, billing. A quick look

sender score Self-send detectedSuspected spoofing Fix in 4 steps Configure SPF correctly to authorise MailproAdd a DKIM recordCheck your DMARC policy (start