Which plan includes this?

Team. The Owner or an Admin sets it up in Settings, Tester email.

Which emails stay with AppForShare?

Account, security and billing emails always come from AppForShare, so a problem with your mail server never locks anyone out.

What if my server refuses a message?

That email goes out once from AppForShare's own sender instead, so the tester still gets it. The delivery log lists it as "Sent by AppForShare instead", and the Owner gets at most one notice a day about it.

Can I see what was sent?

Yes. Recent deliveries in Settings, Tester email shows each email as Sent, Sent by AppForShare instead or Failed, with the addresses masked.

Is there a CLI command or MCP tool for it?

No. The mail server password is a secret, so the setup stays in the dashboard and out of AI assistants.

AppForShare Open Settings

Docs

Tester email through your own mail server

Send the emails your testers get from AppForShare through your company's own mail server, from your own address. Team.

1. Fill in the mail server

Settings, Tester email. The Owner or an Admin enters:

Mail server: The host name, for example smtp.example.com. It must resolve to a public address.
Port and security: STARTTLS (usually 587) or TLS (usually 465). Plain text connections are refused.
User and password: The sign in of the mail account. The password is encrypted with Google Cloud KMS, never shown again, and kept out of logs and the activity feed.
From address: The sender testers see, for example [email protected]. Use an address your server may send for.
From name (optional): For example Acme QA.
Reply-To (optional): Where tester replies go.

2. Send a test

Tick "Use it for tester email", save, and send a test to an address you can read. Tester email uses your server only after a test went through since the last change. Until then the status says "Not in use until a test goes through" and emails go out from AppForShare as before.

Which emails it covers

Only tester facing email:

Tester invites and join confirmations
New build emails and reminders
Install link emails
Replies to tester feedback
Emails to channel followers
"Device ready" and "opens now" emails

Account, security and billing email stays with AppForShare.

Fallback and delivery log

If your server fails to take a message, it goes out once from AppForShare's sender instead, so testers are not left without their link. Recent deliveries lists each email with its status and a masked address, and the card shows the last send and the last error. The Owner gets at most one notice a day about failed sends. Remove the mail server at any time; tester email then goes out from AppForShare again.

Questions

Which plan includes this?: Team. The Owner or an Admin sets it up in Settings, Tester email.
Which emails stay with AppForShare?: Account, security and billing emails always come from AppForShare, so a problem with your mail server never locks anyone out.
What if my server refuses a message?: That email goes out once from AppForShare's own sender instead, so the tester still gets it. The delivery log lists it as "Sent by AppForShare instead", and the Owner gets at most one notice a day about it.
Can I see what was sent?: Yes. Recent deliveries in Settings, Tester email shows each email as Sent, Sent by AppForShare instead or Failed, with the addresses masked.
Is there a CLI command or MCP tool for it?: No. The mail server password is a secret, so the setup stays in the dashboard and out of AI assistants.

Overview: tester email through your own mail server. Related: single sign on, plans.