How does Catch-all address work?
Without a catch-all, mail to an unknown address is refused during the SMTP conversation, which is the clean outcome: the sender learns immediately and no bounce is generated. A naive catch-all accepts first and decides later, which invites spam and, if it bounces afterwards, backscatter.
The useful middle ground is deciding per recipient while the sender is still connected: accept an unknown address only if it fits a pattern you recognise, such as a customer id or a ticket number.
How does nofeb use Catch-all address?
- nofeb's inbound.resolve hook is that decision. When mail arrives for an address on your verified domain with no inbox, nofeb asks your HTTPS endpoint, which can create the inbox on the spot or refuse it. Inboxes created this way count against your plan like any other.
- nofeb's MX checks recipients at RCPT time, so mail for an address that will not be created is refused before any data is accepted.
- Plus-addressing also routes
name+tag@toname@without a catch-all.
Frequently asked questions
Can nofeb create an inbox when mail arrives for a new address?
Yes, through an inbound.resolve hook on a verified domain: your endpoint decides, per address, whether the inbox should exist.
Does a catch-all hurt deliverability?
Receiving everything does not affect your sending reputation, but bouncing mail after accepting it does: bounces go to forged senders. Decide at RCPT time instead.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| HTTPS hooks in the pipeline | Signed HTTPS callouts that change what happens: create or reject an inbox for an unknown recipient, accept, reject or quarantine a message before delivery, and allow, deny or hold a send, each with a timeout and a fail-open or fail-closed mode. | Shipped |
| Inbound mail server that checks mail at the door | nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. | Shipped |
| Plus-addressing | Mail to name+tag@ reaches the name@ inbox. | Shipped |
| Unlimited inboxes | Create as many inboxes as the work needs, with a generated or chosen address and an idempotent client reference. | Shipped |