Enhance Email/Domain Deliverability

@naveed254

Spam placement on a warmed domain is almost always authentication alignment rather than content. What I'd check, in order: SPF - is the sending IP actually in the record and are you under 10 DNS lookups. DKIM - is the signature aligned to the From domain, not your ESP's domain. DMARC - present, and does the aggregate report show pass. Then rDNS/PTR on the sending IP, and whether the domain or IP is listed on Spamhaus, Barracuda or SURBL. After that: Google Postmaster Tools to see your actual reputation, and a seed test to confirm placement before you send volume again. I do SMTP and deliverability work full-time - this is a standard fix, not guesswork. Can you send me the sending domain and tell me whether you're sending through Gmail/Workspace, a VPS, or an ESP?

@sotat2

Hi, I can help diagnose why emails from your new domain are landing in Gmail Spam and identify the underlying deliverability issue rather than simply changing settings blindly. I can review your current domain/email configuration, including SPF, DKIM, DMARC, DNS records, Google Workspace authentication, and other factors that can affect Gmail deliverability and domain reputation. I’ll first review the checks you’ve already completed so we don’t repeat unnecessary work, then isolate the likely cause and make or recommend the required fixes. I understand your requirement regarding the quoted amount and will stick to the agreed price for the defined scope. Thanks, Sota

@thaiss93

Hi! I understand the issue: your new domain was manually warmed up, but emails are still landing in Gmail Spam. I can review the attached results, check your domain and email authentication (SPF, DKIM and DMARC), identify the actual deliverability issue, and help correct it. I’ll focus on finding the root cause rather than just making generic recommendations. I also understand that you want the work completed within the quoted amount. I’m ready to review the attachment and get started.

@pvhoan

Landing in spam on a new domain usually traces to one of three things, and the fix is different for each so diagnosis comes first, not a blind SPF/DKIM/DMARC rewrite. First check is alignment, not just presence: SPF and DKIM can both technically pass while DMARC still fails, if the domain in your From header doesn't match what SPF or DKIM actually authenticated. That's the single most common cause of "I set everything up and it's still landing in spam." Second is DMARC policy itself, if it's still at p=none you get visibility but no enforcement signal to mailbox providers, moving carefully to p=quarantine during warmup helps rather than hurts. Third is warmup pace and content, a brand new domain sending volume too fast, or heavy HTML/link-to-text ratio, gets flagged independent of your auth records being perfect. I'll pull your actual DNS records, check SPF/DKIM/DMARC alignment against your sending headers, read the test results you've attached, and run inbox placement checks across Gmail/Outlook to see where things actually land right now, not just where the records say they should. Fix goes in as corrected DNS records plus a specific explanation of which of the three was the actual cause, so you're not guessing next time this happens on another domain. Can you share the domain and the attached test file details, or paste the DNS records directly?

@ajits03

Hi, I specialize in email infrastructure, DNS authentication, and deliverability recovery across major mailbox providers (Google Workspace/Gmail, Microsoft 365, and Yahoo/AOL). I will thoroughly audit your domain, pinpoint why your emails are landing in spam, and apply the exact fixes needed to restore inbox placement. How I will resolve this: • Domain & DNS Audit: Inspect and correct your SPF syntax, align DKIM selectors, and configure an effective DMARC policy with reporting to stop spoofing and provider penalties. • Deliverability Diagnostics: Analyze your domain and IP against RBL blacklists (Spamhaus, Barracuda), review Postmaster/SNDS telemetry, and inspect message headers for MIME/content flags. • Root-Cause Fix & Validation: Apply the technical fixes directly in your DNS and email platform, then conduct live seed-test placements to verify primary inbox delivery. I am ready to start immediately. Which domain name and email sending provider (e.g., Google Workspace, Microsoft 365, or an ESP) are you currently using?

@farukhkaleem1

I can enhance your email/domain deliverability by thoroughly analyzing your setup and correcting issues with SPF, DKIM, and DMARC. With a detailed approach, I’ll ensure your emails reach the inbox, not Spam. Let's collaborate to boost your email performance effectively.

@vaishaliA46

Hi, I can review your domain and email configuration to identify why your new emails are landing in Gmail Spam. I can check the domain’s SPF, DKIM, and DMARC configuration, Google Workspace settings, DNS records, authentication results, and other email deliverability factors. I’ll identify the actual issue rather than simply making generic changes, then implement the required fixes and verify the results. I will also review the attached domain health report before making any recommendations. I can complete the work within 3 days and will stay within the quoted budget. I’m ready to start immediately.

@alexanders115

Hello, I reviewed both screenshots in your attachment before bidding. The health report shows 0 errors, 120 passed checks and no blacklist warnings. The remaining warnings include SOA settings, optional inbox branding, and a reverse-DNS/SMTP-banner mismatch on a Google-managed host. Those warnings alone do not establish the cause of Gmail spam placement. Postmaster shows the domain as verified but has insufficient data. For INR 1,500, I will review the DNS zone, SPF/DKIM/DMARC alignment and Workspace settings, inspect a representative message header, correct agreed customer-controlled configuration issues and provide a before/after report. This fixed scope covers one domain and one Workspace tenant over 2 days; the quote will stay at INR 1,500 for that scope. My background is full-stack development and practical technical troubleshooting. I will distinguish configuration defects from reputation issues: inbox placement cannot be guaranteed, and Google-managed reverse DNS cannot normally be changed by a Workspace customer. Please provide the sending setup and a sample header through the project workspace after award.

@Hoang14

With over 10 years of IT System, i can help you resolve this problem write to enough 100 characters: qweqweqweq