How to Create Send-Only Email Addresses in StackCP

Not every email address on your domain needs to receive replies. A Send-Only Address lets you create an address purely for outgoing mail — commonly used for automated notifications, website contact form confirmations, or "no-reply" style addresses — without setting up a full, monitored mailbox for it.

What Is a Send-Only Address?

A Send-Only Address can send email from your domain but isn't set up to receive incoming mail into a monitored inbox. This is useful for situations where mail genuinely only needs to flow outward — a website's automated order confirmation, a form submission notification, or a system alert — and where you don't want (or need) replies landing anywhere, since nobody would be checking that inbox regardless.

Step 1: Open Send-Only Addresses

1. Log in to StackCP.
2. Go to Manage Hosting, then Manage on your package.
3. Select Send-Only Addresses under the Email section.

Step 2: Create the Address

1. Enter the address you want to use (for example, noreply to create noreply@yourdomain.com).
2. Set a password for it, since applications sending mail through this address (like your website's contact form or e-commerce platform) will need valid credentials to authenticate via SMTP.
3. Save.

Step 3: Use It in Your Website or Application

Once created, use the address's SMTP credentials in whatever system needs to send outgoing mail on your behalf — your website's contact form plugin, an e-commerce order confirmation system, or any automated notification tool. The standard Stackmail SMTP settings apply:

• SMTP host: smtp.stackmail.com
• Username: the full send-only address
• Password: the password you set for it

Why Use a Send-Only Address Instead of a Regular Mailbox?

• Cleaner separation — automated system mail doesn't clutter a real, monitored inbox.
• No wasted storage — since it's not accumulating a growing inbox of unread automated confirmations sent to itself.
• Clear intent — a "no-reply" style address signals clearly to recipients that a response won't be seen, avoiding confused replies going nowhere.

Common Mistakes Beginners Make

• Using a send-only address where customers genuinely might need to reply. If there's any reasonable chance someone needs to respond to an automated message (like an order confirmation with a question about their order), consider a monitored mailbox or forwarder instead.
• Not testing that outgoing mail from the address actually works after setup, particularly if it's being used by a specific plugin or third-party system that needs correctly configured SMTP credentials.
• Reusing the same send-only address's credentials across many unrelated systems, making it harder to identify which system is responsible if something starts sending unexpected volumes of mail.

Troubleshooting

"My website isn't successfully sending mail through the send-only address." Double-check the SMTP host, username (the full email address), and password are entered correctly in your website or application's mail settings.

"Customers are trying to reply to my no-reply address and are confused when they don't hear back." Consider adding a line in the automated message itself clarifying that it's unmonitored, and providing an alternative contact address for genuine replies.

A Practical Example

Consider a small e-commerce store built on WooCommerce or a similar platform. Every time a customer places an order, the system sends an automatic confirmation email. This confirmation doesn't need — and shouldn't invite — a reply, since the store's actual order queries go through a proper support address. Configuring the store's "from" address as a send-only address like orders@yourstore.com keeps this automated traffic cleanly separated from support@yourstore.com, where a real person is actually reading and replying to messages.