71–80 of 127 posts
I'm fairly AI-optimistic, but I feel like I'm taking crazy pills. Every day the HN story is either "Apple patches actively exploited zero-click RCE" ... or ... "Show HN: Engage With Our Zero-Click RCE".
> We give AI agents their own email inboxes. An inbox to receive mail seems good and valuable. But I'm seeing that your service is also for sending e-mail. Having a domain oriented toward AI e-mail sending feels like a fast path straight to spam block lists. However good your intentions are, this will be used for AI spam. People hate AI spam. They will press the report spam button.
The only receiving mail applications that come to mind are bots registering for accounts. The point of verifying email is to prove you're not a bot.
I received this email the other day: From: Kushal Date: Mon, 18 May 2026 05:03:11 +0000 Saw your question on the Agent Vault thread about websocket-frame auth (Home Assistant) and the worry about the model reflecting the bearer token back into its own context. chrome-relay's answer is structurally different: the credential never enters the agent's context because the agent never touches it — the HA session lives in y…
Appreciate the concern Mike, and I actually read your email complaining, which helped us ship this next feature. We have a "sent via AgentMail" footer being added soon to outbound emails to identify emails coming from LLM's. We also are working on adding more robust checks and LLM-based filtering to prevent messages which contain spam or outbound-like copy. Re; AgentMail next to Claude, we're working on stateful inbo…
Earlier quoted context omitted.
Re "sent via AgentMail" - that's good to hear, but I hope it's not the entire planned text, as "AgentMail" will mean nothing to most people that receive an email from your service. It wont indicate that the email was composed by an AI rather than a person, which is the information that needs to get across.
yep we're going to have a footer linked to our website, which should allow people to see that we are an email service for agents. thanks!
Ban any sender using your domain that removes, obscures, hides, or alters this first line.
It looks interesting as a hackathon project. I might be short sighted but how does this is YC S25 level good? This looks like one of the easiest way to get your domain blacklisted in all the email providers.
Disrupt sounds like a strange word here. This is an area where they're going to have to innovate.
Earlier quoted context omitted.
Appreciate the concern Mike, and I actually read your email complaining, which helped us ship this next feature. We have a "sent via AgentMail" footer being added soon to outbound emails to identify emails coming from LLM's. We also are working on adding more robust checks and LLM-based filtering to prevent messages which contain spam or outbound-like copy. Re; AgentMail next to Claude, we're working on stateful inbo…
This response is a failure to understand the issue.
It looks interesting as a hackathon project. I might be short sighted but how does this is YC S25 level good? This looks like one of the easiest way to get your domain blacklisted in all the email providers.
> This looks like one of the easiest way to get your domain blacklisted in all the email providers. Disrupt sounds like a strange word here. This is an area where they're going to have to innovate.