noreply@ tells the recipient two things: you do not want a reply, and you may not read one if they try. Filters notice. People notice. Agents that summarize mail notice, and they will file the message as a notice instead of a conversation.
Almost no product email needs that posture.
What noreply actually does
It does not stop replies. It dumps them on a mailbox nobody checks, or bounces them, which is worse. A bounce from a “transactional” address is a reputation event. A silent drop is a support ticket that starts from zero.
It also trains customers not to trust the address. If the only way to contest a charge is a form buried in the footer, they forward the mail to a friend or mark it. Neither helps you.
Use a real address
Send from an identity you own and staff:
[email protected]for invoices and dunning.[email protected]for security and access.[email protected]when the mail might need a human.
If the From name is a product (“Acme Billing”), set Reply-To to a mailbox a person reads. Keep From and Reply-To on the same domain. Mixing a marketing domain in Reply-To is how you look like a forward.
When silence is the point
Password resets and two-factor codes should not start a thread with an on-call inbox. You can still avoid noreply@. Use security@ or accounts@, and auto-reply once: “This mailbox does not read replies. If you did not request this, contact support at …” That is honest. noreply@ is a locked door with no sign.
Make the reply useful
Route the mailbox to a shared inbox, not one founder’s Gmail. If an agent handles first response, keep the same address so the customer is not bounced between identities. Log the inbound copy. If you use webhooks for automation, keep the message in the mailbox anyway.
ArawaMail is built for this shape: a custom-domain mailbox plus the transactional send, so receipts and replies live together. If you are still sending application mail from noreply@localhost or a free mailbox, fix the domain first. Then read transactional email best practices before you pick the From name.