I have a website form that sends notifications through Mailgun’s SMTP service at port 587. The setup uses [email protected] as the sender credential. My business email runs on Google Workspace and messages should arrive at [email protected]. When visitors submit the contact form, their email becomes the reply-to address while [email protected] is the recipient. Mailgun’s dashboard shows 100% successful delivery rates for all outbound messages. However, none of these form submissions are appearing in my Gmail inbox or spam folder. This means I’m missing important customer inquiries completely. The SMTP connection seems to work fine since Mailgun confirms delivery, but something is preventing the emails from reaching my actual mailbox. Has anyone experienced similar issues with Google Workspace not receiving Mailgun-sent emails?
hey, i’ve dealt with this b4. check ur dns settings - esp. your spf and dmarc records. google’s really strict about those. also look for any bounce messages you might recive. good luck!
Been there. Google Workspace email filtering is a nightmare. Manual troubleshooting takes forever and you’re bleeding leads the whole time.
I built an automated monitor with Latenode that tests the full email flow every hour. Sends test messages through Mailgun, checks if they hit the Gmail inbox via API.
When emails don’t arrive, it auto-runs diagnostics - SPF records, Google admin logs, Slack alerts. Runs completely hands-off.
Best part? Catches delivery problems before customers notice. Last month it flagged Google silently filtering our transactional emails after a DMARC change.
Takes 30 minutes to build. Beats checking logs manually every day.
This sounds like a Google Workspace filtering issue, not Mailgun delivery. I hit the same thing migrating from Office 365 to Google Workspace. Messages reached Google’s servers but never hit the inbox. Log into your Google Admin console and go to Reports > Email log search. Search for your [email protected] address and see if the missing messages show up there. They’re probably getting quarantined or rejected at the server level. Also check if you’ve got mail routing rules in Google Admin that might be interfering. In my case, there was a default rule filtering messages based on external authentication that wasn’t visible in the regular Gmail interface.
Had this exact issue last year with our corporate Google Workspace. Google was silently dropping messages without bounce notifications. Check your Google Admin console under Security > Investigation tool - that’s where you’ll see if emails are getting blocked. In my case, Google flagged them because the envelope sender ([email protected]) didn’t match the reply-to from form visitors. Google sees this as spoofing. Fixed it by setting Mailgun to use a consistent From address and only putting the visitor’s email in Reply-To. Also double-check your MX records are right and that Mailgun’s IP ranges are in your SPF record.