Your emails go to spam. mailX shows you why, and how to fix it in seconds with clear answers and exact steps. Built for humans and AI agents. API and MCP ready.
Replies
Best
Email is one of the most effective and frustrating marketing channels for the products. But if you are on Google Workspace, doesn't it handle this process?
@vivekn4u Google Workspace definitely helps, but it doesn’t fully solve deliverability automatically.
You still have DNS/authentication configuration, domain reputation, sending behavior, spam filtering, forwarding setups, third-party tools, etc. And when something breaks, the debugging process can get messy
@vivekn4u Common misconception. Workspace gets your email out the door. Where it lands is a different problem.
A few things Workspace doesn't do for you. SPF and DMARC have to be configured in your DNS. DKIM needs to be enabled in admin and the matching key published in DNS, otherwise your sending domain isn't even signed by you.
Sending reputation is built over time based on engagement, and Workspace doesn't manage that for you. Cold outbound to people who didn't ask for it actively hurts that reputation, regardless of who hosts the inbox. And there's no visibility from inside Workspace into whether your emails land in primary, promotions, or spam.
That last one is where most teams find out their cold campaigns were quietly going to spam for months.
Report
@othman_katim Thank you for the detailed explanation.
@vivekn4u If you are using Gmail.com Google is handling everything. If you are using your own domain with Google Workspace, Google let you manage your DNS setting, while giving you general recommendation. In this case make sure to ask your AI agent with MailX to double check it
@vivekn4u Google Workspace gives you the sending infrastructure, but it doesn’t guarantee inbox placement. You still need clean authentication, reputation, sending behavior, and monitoring.
The line about an agent landing in spam being worse than not sending really stuck with me. Same thing is starting to happen with AI search. When ChatGPT or Perplexity recommends a competitor instead of you, most brands have no idea it even happened. The agent acted, the user trusted it, the brand never saw it. Feels like the same invisible plumbing problem, one layer up.
Are you seeing teams ask for this kind of visibility into what their agents are actually doing?
@francesco2689 This is an interesting parallel. We’re starting to see more conversations around visibility, trust, and observability for agent actions especially as agents become more autonomous. Once agents are acting on behalf of users, people want to understand the what and the why and whether the outcome was actually successful.
Same failure mode you described: the agent acted, the user trusted, the brand never saw. Visible to one side, invisible to the other.
Yes, teams ask for it, but framed as inbox placement so far. The agent-recommendation version isn't on most radars yet. It will be the moment founders realize their AI citation rate can drop silently the same way inbox placement always did.
@francesco2689 Yeah, this is exactly the direction things are heading.
There’s a growing gap between “what the system did” and “what the brand knows happened.” With email it’s spam filters and deliverability black boxes. With AI agents, it’s recommendations, tool calls, and decisions happening with zero audit trail for the brand. We’re starting to see teams ask for that visibility, not just logs, but explanations of outcomes: why something was recommended, what alternatives were considered, and when a competitor gets surfaced instead.
@francesco2689 The real issue is visibility. If agents start making growth decisions, sending emails, choosing sources, recommending vendors, we need to understand the signals behind those decisions. Otherwise companies will lose pipeline without even knowing where it leaked.
@francesco2689 Exactly. The real problem is visibility. If agents start sending, recommending, ranking, or choosing vendors, teams need to understand the signals behind those decisions.
Otherwise you lose pipeline silently, whether it’s email deliverability or AI search visibility.
That’s why we think diagnostics will become a core layer for AI workflows.
Report
Bravo @bengeekly@thamibenjelloun@amraniyasser!!! Is mailX for a more beginner audience while Mailwarm is more for advanced/expert audience or are they complementary?
@thamibenjelloun@amraniyasser@basmainparis MailX and Mailwarm are complementary. MailX is Free, with no sign up and help you set the technical part, we made it AI agent ready so it's easy for anyone to setup. Mailwarm is to warm up your inbox after, so your emails actually land in inbox and not spam. So you can see MailX as the first step (setup right your SPF, DKIM, DMARC...) and Mailwarm as the second step (build the reputation of your inbox so it's trusted). Both tools work for everyone, beginner or expert, just different jobs 🙏
@basmainparis Thank you! They’re definitely more complementary than overlapping.
Mailwarm focuses on email warmup and sender reputation, while mailX is more about diagnosing, understanding, and fixing deliverability issues across the whole setup.
There’s also a usability difference: mailX is designed to make deliverability much more accessible to non-experts and AI agents, while still being useful for more advanced senders too.
@asheer_ahmad Exactly! people can see SPF/DKIM/DMARC records or deliverability metrics, but translating that into what’s actually broken and what should I do next? is the hard part.
That’s the gap we’re trying to close with mailX :))
@asheer_ahmad We want mailX to show the result and score, explain it, and give steps on how to fix your email deliverability
Report
Interesting angle making deliverability usable by AI agents, not only operators. For teams that use email as a growth channel, the risk is an agent sending more volume before the domain is healthy. Does mailX expose a clear do-not-send-yet, safe-to-scale, or fix-these-first status through the API or MCP, so an agent can slow down instead of just reporting a score?
@cyrus_elmtalab Yes, that’s exactly the behavior we want. Today, mailX gives the agent the diagnostic layer: what’s broken, why it matters, and what to fix first. The next step is turning that into clearer action states like “fix this first” or “safe to scale”, so agents can slow down before damaging the domain.
@cyrus_elmtalab MailX Agent are mainly here to check if you apply your protocols properly they will not send on your behalf. We will give you the health check so your other agent can take decisions
Report
@bengeekly That separation makes sense. A diagnostic health-check layer is safer than letting an agent send blindly. The useful next step would be a simple action state that another agent can read: pause sending, fix protocol issues, or safe to scale.
Report
This actually can reduce a lot of time, especially for buessniss owners and people interacting a lot with Emails.
Myself, I get hunderends if not thousands of emails each day. mailX will help a lot.
@basheer_rjoub That’s exactly the kind of workflow mailX is for 🙌 When your inbox volume gets that high, even saving a few seconds per email adds up fast.
@basheer_rjoub Totally agree, this becomes a huge time saver, especially for business owners or anyone buried in emails. When you’re getting hundreds or even thousands a day, something like mailX can make a real difference.
@basheer_rjoub Absolutely. Email-heavy teams feel the pain very fast. When you deal with hundreds or thousands of emails, even small deliverability issues create a lot of wasted time.
That’s exactly why we want mailX to make diagnosis faster and clearer.
After spending years around email deliverability from the technical side, one thing still surprises me: very small details can have a real business impact. A missing DNS record, a weak setup, or one bad configuration can quietly affect whether emails reach the inbox or not.
With more teams adding automation and AI agents into their workflows, this matters even more. Agents can send emails, trigger workflows, and move fast. But they also need clear signals when something is wrong, otherwise they can scale issues without anyone noticing.
That’s what mailX solves: making deliverability easier to understand, not only for humans, but also for AI agents that need structured, actionable answers.
Happy to answer any technical questions with the team today.
I do really like the idea of giving AI agents a deliverability expert, because otherwise they might just send blindly. Something I'm curious about is how an agent would actually use mailX in practice?
@theokitsberg Really good question. Maybe agents will eventually need deliverability-awareness built into their workflows, because otherwise they’ll just optimize for volume and unintentionally damage sender reputation over time. The goal with mailX is helping agents monitor domain health, detect issues early, and adapt instead of sending blindly.But yeah I appreciate your question :))
@theokitsberg Good question. In practice the agent calls the MailX MCP before it sends, basically as a pre-flight check. It pulls SPF, DKIM, DMARC, blacklist status, MX for the sending domain, and gets back a verdict it can act on: send, hold, or fix first.
If something's broken (say DMARC is set to none), the agent can call the SPF/DMARC generator tool to produce the corrected record, hand it back to the user, then re-check on the next run.
The shift is from blind 'spray and pray' to an agent that knows before it sends whether the email has a chance of landing.
@theokitsberg In practice, mailX becomes the diagnostic layer the agent calls before sending or scaling. The agent can check the domain setup, authentication, blacklists, and risks, then decide: “safe to send” or “fix this first.” Today it’s diagnostic. The next step is remediation with human approval.
@theokitsberg If your agent have access to your outreach and DNS, he can actually use mailX to double check everything, switch between domains is one of them is unhealthy. Stop if there is a problem, and tell you if someone is trying to send emails on your behalf using DMARC.
@german_merlo1 Exactly, email is one of those fields that looks simple from outside, but becomes very deep when you start scaling. Appreciate the support!
@german_merlo1 Thank you so much. Email looks simple until you start scaling. That’s why we’re trying to make deliverability easier to understand and fix. Appreciate the support!
Replies
Email is one of the most effective and frustrating marketing channels for the products. But if you are on Google Workspace, doesn't it handle this process?
Mailwarm
@vivekn4u Google Workspace definitely helps, but it doesn’t fully solve deliverability automatically.
You still have DNS/authentication configuration, domain reputation, sending behavior, spam filtering, forwarding setups, third-party tools, etc. And when something breaks, the debugging process can get messy
@naimz so its somthing like manual vs automation?
Mailwarm
@vivekn4u Common misconception. Workspace gets your email out the door. Where it lands is a different problem.
A few things Workspace doesn't do for you. SPF and DMARC have to be configured in your DNS. DKIM needs to be enabled in admin and the matching key published in DNS, otherwise your sending domain isn't even signed by you.
Sending reputation is built over time based on engagement, and Workspace doesn't manage that for you. Cold outbound to people who didn't ask for it actively hurts that reputation, regardless of who hosts the inbox. And there's no visibility from inside Workspace into whether your emails land in primary, promotions, or spam.
That last one is where most teams find out their cold campaigns were quietly going to spam for months.
@othman_katim Thank you for the detailed explanation.
Mailwarm
@vivekn4u If you are using Gmail.com Google is handling everything. If you are using your own domain with Google Workspace, Google let you manage your DNS setting, while giving you general recommendation. In this case make sure to ask your AI agent with MailX to double check it
@bengeekly, understood.
Mailwarm
@vivekn4u Google Workspace gives you the sending infrastructure, but it doesn’t guarantee inbox placement. You still need clean authentication, reputation, sending behavior, and monitoring.
@thamibenjelloun Understandable; need to look deeper into this.
Congrats on the 🚀
The line about an agent landing in spam being worse than not sending really stuck with me. Same thing is starting to happen with AI search. When ChatGPT or Perplexity recommends a competitor instead of you, most brands have no idea it even happened. The agent acted, the user trusted it, the brand never saw it. Feels like the same invisible plumbing problem, one layer up.
Are you seeing teams ask for this kind of visibility into what their agents are actually doing?
Mailwarm
@francesco2689 This is an interesting parallel. We’re starting to see more conversations around visibility, trust, and observability for agent actions especially as agents become more autonomous. Once agents are acting on behalf of users, people want to understand the what and the why and whether the outcome was actually successful.
Mailwarm
@francesco2689 Thanks! Glad it landed.
Same failure mode you described: the agent acted, the user trusted, the brand never saw. Visible to one side, invisible to the other.
Yes, teams ask for it, but framed as inbox placement so far. The agent-recommendation version isn't on most radars yet. It will be the moment founders realize their AI citation rate can drop silently the same way inbox placement always did.
What are you building?
mailX by mailwarm
@francesco2689 Yeah, this is exactly the direction things are heading.
There’s a growing gap between “what the system did” and “what the brand knows happened.” With email it’s spam filters and deliverability black boxes. With AI agents, it’s recommendations, tool calls, and decisions happening with zero audit trail for the brand. We’re starting to see teams ask for that visibility, not just logs, but explanations of outcomes: why something was recommended, what alternatives were considered, and when a competitor gets surfaced instead.
Mailwarm
@francesco2689 The real issue is visibility. If agents start making growth decisions, sending emails, choosing sources, recommending vendors, we need to understand the signals behind those decisions. Otherwise companies will lose pipeline without even knowing where it leaked.
Mailwarm
@francesco2689 Exactly. The real problem is visibility. If agents start sending, recommending, ranking, or choosing vendors, teams need to understand the signals behind those decisions.
Otherwise you lose pipeline silently, whether it’s email deliverability or AI search visibility.
That’s why we think diagnostics will become a core layer for AI workflows.
Mailwarm
@thamibenjelloun @amraniyasser @basmainparis MailX and Mailwarm are complementary. MailX is Free, with no sign up and help you set the technical part, we made it AI agent ready so it's easy for anyone to setup. Mailwarm is to warm up your inbox after, so your emails actually land in inbox and not spam. So you can see MailX as the first step (setup right your SPF, DKIM, DMARC...) and Mailwarm as the second step (build the reputation of your inbox so it's trusted). Both tools work for everyone, beginner or expert, just different jobs 🙏
Mailwarm
@basmainparis Thank you! They’re definitely more complementary than overlapping.
Mailwarm focuses on email warmup and sender reputation, while mailX is more about diagnosing, understanding, and fixing deliverability issues across the whole setup.
There’s also a usability difference: mailX is designed to make deliverability much more accessible to non-experts and AI agents, while still being useful for more advanced senders too.
Mailwarm
@bengeekly @amraniyasser @basmainparis They are complementary.
mailX helps you diagnose what’s wrong and what to fix.
Mailwarm helps you build sender reputation and improve inbox placement over time.
Simple way to see it: mailX tells you the problem, Mailwarm helps you improve the reputation layer.
Tailgrids
Congrats on the launch Othman
Mailwarm
@musharofchy Thanks
i like the focus on explaining what is wrong instead of just showing technical metrics 👀 Most founders are not email infrastructure experts.
Mailwarm
@asheer_ahmad Exactly. Founders don’t need more raw metrics. They need to know what is broken, why it matters, and what to fix first.
Mailwarm
@asheer_ahmad Exactly! people can see SPF/DKIM/DMARC records or deliverability metrics, but translating that into what’s actually broken and what should I do next? is the hard part.
That’s the gap we’re trying to close with mailX :))
Mailwarm
@asheer_ahmad Got it right!!!
Mailwarm
@asheer_ahmad We want mailX to show the result and score, explain it, and give steps on how to fix your email deliverability
Interesting angle making deliverability usable by AI agents, not only operators. For teams that use email as a growth channel, the risk is an agent sending more volume before the domain is healthy. Does mailX expose a clear do-not-send-yet, safe-to-scale, or fix-these-first status through the API or MCP, so an agent can slow down instead of just reporting a score?
Mailwarm
@cyrus_elmtalab Yes, that’s exactly the behavior we want. Today, mailX gives the agent the diagnostic layer: what’s broken, why it matters, and what to fix first. The next step is turning that into clearer action states like “fix this first” or “safe to scale”, so agents can slow down before damaging the domain.
Mailwarm
@cyrus_elmtalab MailX Agent are mainly here to check if you apply your protocols properly they will not send on your behalf. We will give you the health check so your other agent can take decisions
@bengeekly That separation makes sense. A diagnostic health-check layer is safer than letting an agent send blindly. The useful next step would be a simple action state that another agent can read: pause sending, fix protocol issues, or safe to scale.
Mailwarm
@basheer_rjoub That’s exactly the kind of workflow mailX is for 🙌
When your inbox volume gets that high, even saving a few seconds per email adds up fast.
Mailwarm
@basheer_rjoub Thanks God, AI agents will save us from inbox anxiety!
Mailwarm
@basheer_rjoub That has always been our goal 😉
mailX by mailwarm
@basheer_rjoub Totally agree, this becomes a huge time saver, especially for business owners or anyone buried in emails. When you’re getting hundreds or even thousands a day, something like mailX can make a real difference.
Mailwarm
@basheer_rjoub Absolutely. Email-heavy teams feel the pain very fast. When you deal with hundreds or thousands of emails, even small deliverability issues create a lot of wasted time.
That’s exactly why we want mailX to make diagnosis faster and clearer.
Mailwarm
Hey Product Hunt 👋
After spending years around email deliverability from the technical side, one thing still surprises me: very small details can have a real business impact. A missing DNS record, a weak setup, or one bad configuration can quietly affect whether emails reach the inbox or not.
With more teams adding automation and AI agents into their workflows, this matters even more. Agents can send emails, trigger workflows, and move fast. But they also need clear signals when something is wrong, otherwise they can scale issues without anyone noticing.
That’s what mailX solves: making deliverability easier to understand, not only for humans, but also for AI agents that need structured, actionable answers.
Happy to answer any technical questions with the team today.
Prism
I do really like the idea of giving AI agents a deliverability expert, because otherwise they might just send blindly. Something I'm curious about is how an agent would actually use mailX in practice?
Mailwarm
@theokitsberg Really good question. Maybe agents will eventually need deliverability-awareness built into their workflows, because otherwise they’ll just optimize for volume and unintentionally damage sender reputation over time. The goal with mailX is helping agents monitor domain health, detect issues early, and adapt instead of sending blindly.But yeah I appreciate your question :))
Mailwarm
@theokitsberg Good question. In practice the agent calls the MailX MCP before it sends, basically as a pre-flight check. It pulls SPF, DKIM, DMARC, blacklist status, MX for the sending domain, and gets back a verdict it can act on: send, hold, or fix first.
If something's broken (say DMARC is set to none), the agent can call the SPF/DMARC generator tool to produce the corrected record, hand it back to the user, then re-check on the next run.
The shift is from blind 'spray and pray' to an agent that knows before it sends whether the email has a chance of landing.
Mailwarm
@theokitsberg In practice, mailX is the diagnostic layer the agent calls before sending or scaling.
It can check the setup, spot risks, and tell the agent: “safe to continue” or “fix this first.”
That’s the direction we believe AI outbound needs.
Mailwarm
@theokitsberg In practice, mailX becomes the diagnostic layer the agent calls before sending or scaling. The agent can check the domain setup, authentication, blacklists, and risks, then decide: “safe to send” or “fix this first.” Today it’s diagnostic. The next step is remediation with human approval.
Mailwarm
@theokitsberg If your agent have access to your outreach and DNS, he can actually use mailX to double check everything, switch between domains is one of them is unhealthy. Stop if there is a problem, and tell you if someone is trying to send emails on your behalf using DMARC.
Build Check
Hey Thami! it sounds awesome. Mailing is a hard field but key at the same time. I'm sure you'll rock it! All the best
Mailwarm
@german_merlo1 Exactly, email is one of those fields that looks simple from outside, but becomes very deep when you start scaling. Appreciate the support!
Mailwarm
@german_merlo1 Thanks for the support
Mailwarm
@german_merlo1 Thank you so much. Email looks simple until you start scaling. That’s why we’re trying to make deliverability easier to understand and fix. Appreciate the support!