Emailing the address out
MSL can email the address to whoever needs it, so nobody has to ask you.
On this page 4 sections
On the free relay the address changes about once an hour. Rather than you fielding "what's the address now?", MSL can email it.
Each person gets their own key the first time, attached to the email, with the exact commands. After that they only get a short note when the address moves — same key, new port.
Setting it up#
MSL sends through Resend, which is free.
- Make an account
- Verify a domain you own at resend.com/domains
- Make an API key at resend.com/api-keys
msl public notify setup
Then add people:
msl public notify add Ubuntu sam@work.com SamOr in the app: Reach this from anywhere ▸ Email the address to someone…
What gets sent#
| When | What they get |
|---|---|
| You add them, or first publish | Their key attached, chmod 600, and the ssh line |
| The address changes | Just the new command — nothing to save |
Nobody gets an endless drip: rotation emails are capped per person per day, and the cap lifts once somebody actually connects.
Where the API key is kept#
In /Users/Shared/MSL, readable only by you.
Deliberately not in Application Support: MSL shares your whole home folder into every instance as /mnt/mac, so a key there could be read from inside any Linux instance. /Users/Shared sits outside that share.
Commands#
| Command | What it does |
|---|---|
msl public notify setup | Connect Resend |
msl public notify test <you@…> | Prove it works before anyone relies on it |
msl public notify add <instance> <email> [name] | Email this person the address |
msl public notify list <instance> | Who's on the list |
msl public notify remove <instance> <email> | Stop emailing them |
msl public notify forget | Remove the Resend setup entirely |
Taking somebody off the list does not revoke their key — that's msl public deauthorize, so the two are never confused.