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.
@eduardnpetrache MailX doesn't discriminate :) Cold email tends to make deliverability pain more visible, but the same underlying issues affect marketing newsletters, transactional emails, onboarding emails, etc.
At the end of the day, inbox providers care about trust, authentication, reputation, and behavior regardless of the email category and that's where MailX comes in ;)
@eduardnpetrache All three. Cold email, newsletters, and transactional emails all rely on the same core layer: setup, authentication, reputation, and infrastructure.
Report
Email outreach is our core growth channel at Elvixs. One broken SPF record and your whole campaign is dead in spam silently. The diagnosis-first approach is exactly what was missing. Congrats on the launch 🚀
@rajanmishraaa That’s one of the scariest parts of deliverability things can break very quietly.
A single SPF or DMARC issue can tank an entire campaign while everything still seems normal from the sending side. That's a huge part of why we built mailX in the first place. And thank you I appreciate that :))
@rajanmishraaa Thanks! 'Dead in spam silently' is exactly the failure mode that kills campaigns for months while teams keep blaming the copy and rewriting subject lines. Glad the diagnosis-first framing lands.
@rajanmishraaa Oh woow, feel free to use Mailx and give us your feedback
Report
Congrats on shipping! 🚀
The "usable by AI agents" part stood out to me; most deliverability tools assume a human reading a dashboard. Are you exposing this as an MCP server / API that an outreach agent could call before every send, or is it more of a one-shot audit? Curious how you see agents using it in practice.
@natalia_zak Thank you!! and yes, the idea is much closer to an MCP/API workflow than a simple one shot audit.
We think agents should be able to check domain health, authentication, reputation signals, and deliverability risk continuously ideally before and during sending, not only after something breaks.
A big part of the vision is making deliverability understandable and actionable for agents, not just humans reading dashboards.
@natalia_zak Exactly. We expose it through both MCP and API. The first use case is: agent checks before sending or scaling, domain setup, auth, blacklists, risks, then says “safe to send” or “fix this first.” Today it’s mostly diagnostic. The direction is continuous checks inside outreach workflows, not just one-shot audits.
Report
the AI agent compatibility angle is interesting. Feels like more developer tools are starting to prepare for autonomous workflows now.
@robert_hughes5 For sure, I think a lot of infrastructure and developer tools will need to become more agent-friendly over time, not just human-dashboard-friendly.
@robert_hughes5 Exactly. Agents will need tools they can actually call, not just dashboards humans read. That’s the shift we’re building for with API + MCP.
@robert_hughes5 Exactly. It feels like the shift now is from “AI-assisted tools” to tools that are built assuming agents will actively interact with them.
@robert_hughes5 100% if your outreach is AI agent made, your deliverability should too
Report
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.
Congratulations on the launch. Email deliverability still feels weirdly opaque for most founders. curious how much of the fixing flow agents can automate already?
@shreyans_assistiv Thank you 🙏 Today, agents can already diagnose and explain what needs to be fixed through MCP. Full auto-fix is the next step, but we want it to be approval-based. DNS and sending settings are too sensitive to let agents change blindly.
So the flow is: detect => suggest => prepare fix => human validates.
Congrats on the launch! Have you implemented any cross-language deliverability analysis? I've noticed some of my emails land in spam in certain languages, while essentially the same message in another language reaches the inbox. Is language-specific spam classification something you've observed with providers like Gmail?
@davidsolsonap Yes, we’ve seen that. Language can affect deliverability through wording, structure, links, and engagement patterns, but today mailX is mainly focused on technical diagnosis. Which languages did you notice the biggest difference with?
@davidsolsonap Because spam filters work mainly with detecting spam words, they threat different languages just as different text, so if you translate to another language, check the text for spam words again as a new text
Is mailX mainly built for cold email, or can it also help newsletters and transactional emails?
Mailwarm
@eduardnpetrache MailX doesn't discriminate :) Cold email tends to make deliverability pain more visible, but the same underlying issues affect marketing newsletters, transactional emails, onboarding emails, etc.
At the end of the day, inbox providers care about trust, authentication, reputation, and behavior regardless of the email category and that's where MailX comes in ;)
Mailwarm
@eduardnpetrache MailX is both cold email, newsletter and transactional emails
Mailwarm
@eduardnpetrache All three. Cold email, newsletters, and transactional emails all rely on the same core layer: setup, authentication, reputation, and infrastructure.
Email outreach is our core growth channel at Elvixs. One broken SPF record and your whole campaign is dead in spam silently. The diagnosis-first approach is exactly what was missing. Congrats on the launch 🚀
Mailwarm
@rajanmishraaa That’s one of the scariest parts of deliverability things can break very quietly.
A single SPF or DMARC issue can tank an entire campaign while everything still seems normal from the sending side. That's a huge part of why we built mailX in the first place. And thank you I appreciate that :))
mailX by mailwarm
@rajanmishraaa Everything can look fine on the surface, and then a single SPF issue quietly kills deliverability without any obvious signal.
That “diagnosis-first” angle is what makes it actually usable at scale, especially when email is your core growth channel like at Elvixs.
Appreciate it 🚀
Mailwarm
@rajanmishraaa Thanks! 'Dead in spam silently' is exactly the failure mode that kills campaigns for months while teams keep blaming the copy and rewriting subject lines. Glad the diagnosis-first framing lands.
Mailwarm
@rajanmishraaa Yes, many people do not know this. They think it's only about the copy Thank youuu
Mailwarm
@rajanmishraaa Oh woow, feel free to use Mailx and give us your feedback
Congrats on shipping! 🚀
The "usable by AI agents" part stood out to me; most deliverability tools assume a human reading a dashboard. Are you exposing this as an MCP server / API that an outreach agent could call before every send, or is it more of a one-shot audit? Curious how you see agents using it in practice.
Mailwarm
@natalia_zak It's and MCP and API calling before every send is definitely overkill, honestly one check a day is enough!
Mailwarm
@natalia_zak Thank you!! and yes, the idea is much closer to an MCP/API workflow than a simple one shot audit.
We think agents should be able to check domain health, authentication, reputation signals, and deliverability risk continuously ideally before and during sending, not only after something breaks.
A big part of the vision is making deliverability understandable and actionable for agents, not just humans reading dashboards.
Mailwarm
@natalia_zak Exactly. We expose it through both MCP and API. The first use case is: agent checks before sending or scaling, domain setup, auth, blacklists, risks, then says “safe to send” or “fix this first.” Today it’s mostly diagnostic. The direction is continuous checks inside outreach workflows, not just one-shot audits.
the AI agent compatibility angle is interesting. Feels like more developer tools are starting to prepare for autonomous workflows now.
Mailwarm
@robert_hughes5 For sure, I think a lot of infrastructure and developer tools will need to become more agent-friendly over time, not just human-dashboard-friendly.
Mailwarm
@robert_hughes5 Exactly. Agents will need tools they can actually call, not just dashboards humans read. That’s the shift we’re building for with API + MCP.
Mailwarm
@robert_hughes5 Exactly. It feels like the shift now is from “AI-assisted tools” to tools that are built assuming agents will actively interact with them.
Mailwarm
@robert_hughes5 100% if your outreach is AI agent made, your deliverability should too
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.
AskCodi
Congratulations on the launch. Email deliverability still feels weirdly opaque for most founders. curious how much of the fixing flow agents can automate already?
Mailwarm
@shreyans_assistiv Thank you 🙏 Today, agents can already diagnose and explain what needs to be fixed through MCP. Full auto-fix is the next step, but we want it to be approval-based. DNS and sending settings are too sensitive to let agents change blindly.
So the flow is: detect => suggest => prepare fix => human validates.
Mailwarm
@shreyans_assistiv All the boring protocols, like SPF,DKIM,DMARK, BIMI, SMTP, IMAP... The rest is what still can't be checked by an agent.
Socrati
Congrats on the launch! Have you implemented any cross-language deliverability analysis? I've noticed some of my emails land in spam in certain languages, while essentially the same message in another language reaches the inbox. Is language-specific spam classification something you've observed with providers like Gmail?
Mailwarm
@davidsolsonap Yes, we’ve seen that. Language can affect deliverability through wording, structure, links, and engagement patterns, but today mailX is mainly focused on technical diagnosis. Which languages did you notice the biggest difference with?
Mailwarm
@davidsolsonap Because spam filters work mainly with detecting spam words, they threat different languages just as different text, so if you translate to another language, check the text for spam words again as a new text