Answers to the questions we get asked most often about using ZeroSMTP.
Yes. ZeroSMTP is an SMTP relay — it doesn’t care which domain your hosting or website runs on. Setup is three steps:
@msgwing.com domain.mx.msgwing.com, port 587 with
STARTTLS or 465 with SSL/TLS).This covers contact forms, password resets, and notifications from any hosting provider, plus the other use cases in the main README (apps, scripts, printers, IoT, etc.).
No — by design. Every message is sent from an @msgwing.com address,
never from your own domain. ZeroSMTP only relays mail through the
msgwing.com domain and does not send on behalf of arbitrary sender
domains, mainly for anti-spam and deliverability reasons.
| Your need | Does ZeroSMTP fit? |
|---|---|
| Reliable outgoing mail for your app/site (contact forms, password resets, notifications) | ✅ Yes, regardless of your hosting’s domain |
| “From” address must show your domain | ❌ No — that requires your own dedicated mail server |
Yes. Registration generates a random @msgwing.com address by default, but
you can request a specific one (e.g. you@msgwing.com):
See Sending limits (rate limiting) in the troubleshooting guide.
No. See This project cannot receive email — ZeroSMTP is outgoing-only.
There isn’t a hidden one — the trade-offs are the ones already documented
on this page: mail always goes out from a shared @msgwing.com address,
not your own domain (see above), and sending is rate-limited per account to
keep the shared domain’s reputation good for everyone (see
Sending limits).
Beyond that, per the README: your data isn’t processed for marketing or resold, and abuse accounts are actively removed to protect deliverability for everyone else. If your use case needs more than what’s documented here, ask at abuse@msgwing.com rather than assuming it isn’t supported.
Contact abuse@msgwing.com, or open an issue on this repository.