Forward qualifying mail with programmable match rules
Route inbound traffic by sender, recipient, subject, or attachment patterns and relay matching messages to the right external destination.
How to choose forwarding, alias proxy, and routing rules
Choose the right inbox control for each job: forwarding for destination delivery, aliases for identity masking, and rulesets for policy enforcement.
Trusted by top companies worldwide
Routing primitives
Use the right inbox control for delivery, masking, and policy
Forwarders, aliases, and rulesets each own a distinct part of the inbound path so teams can route messages without blurring responsibilities.
Explore
Publish masked addresses without exposing the real inbox
Use aliases to hide the destination mailbox, preserve privacy, and keep reply handling attached to the workflow behind the public address.
Test forwarding behavior before it carries live traffic
Validate forwarder behavior and inspect forwarding events so routing changes can be reviewed before they affect production mail.
Enforce policy before downstream systems receive the message
Use rulesets as the decision layer for allow, block, and safety boundaries, then hand approved traffic into forwarders or operator queues.
Separate forwarding, alias masking, and ruleset enforcement before delivery
MailSlurp lets teams treat inbound handling as a sequence of clear decisions. Pick the destination, protect identities where needed, and enforce policy before messages move downstream.
Parse inbound data faster
Convert messages and attachments into structured fields for downstream systems and ops queues.
Automate OCR and document capture
Pull invoice and document data from attachments without leaving mailbox workflows.
Developer integration
Choose forwarding, alias masking, and policy controls in code
Use MailSlurp APIs to set forwarding destinations, protect identities with aliases, and enforce rulesets before mail moves downstream.
- Manage destination routing and fallback handling through the API
- Keep alias masking and reply continuity inside the same inbox model
- Apply policy before delivery reaches downstream systems or operators
Next step
Start with signup or docs
Use the free account to validate the workflow in your own stack, then move into implementation details in the docs.