Add, Verify and Delete Webuzo Email Forwarders

Webuzo email forwarding routes incoming mail for a selected address to another destination. Older InterServer instructions called the interface Bread Basket; those screenshots are historical, not evidence of the current menu on every installation. Use this workflow only where your installed panel and account expose the feature.

Add a forwarder

1. Sign in through your verified HTTPS Webuzo end-user interface. Open Email > Email Forwarders; legacy Bread Basket used Email Server > Email Forwarder.
2. Choose the correct domain and enter the source address in the From/address-to-forward field. Enter the complete authorized destination in the To field. Do not reverse source and destination.
3. Select ordinary email forwarding, not a failure action, system account or program pipe unless that different behavior is intended.
4. Save with Create Forwarder, then inspect the exact saved pair. A success message proves the configuration was accepted, not remote delivery.

Confirm the domain’s MX/routing sends incoming mail to this server. An address elsewhere, even if you own it, cannot become a local source just by typing it into this form. Check whether a same-address mailbox keeps a local copy on your installation and monitor its quota rather than assuming forwarding removes stored mail.

Remove or replace a forwarder

Record the existing source and destination before changing anything. Locate the exact row, choose its delete action and confirm only that row. Recreate the intended replacement if the panel does not offer editing, then test. Removing a forwarder does not recall delivered copies, delete the separate mailbox or stop another rule that also routes the address.

Program piping is a separate integration

Webuzo’s email-pipe option passes a message to a program instead of simply delivering it to a mailbox. Use it only for an authorized application with documented interpreter, path, permissions, input and error handling. Do not paste a general shell command or a user-supplied path into it. Mail headers, bodies and attachments are untrusted input; the handler must not execute their content as commands. Protect scripts and secrets against modification and public download.

Verify the actual result

Use a harmless external test, check each intended destination and inspect delivery errors, spam folders and quotas. Avoid a destination chain that loops back to the source. External filtering and domain authentication can reject forwarded messages; neither a saved rule nor the presence of a row guarantees delivery. Keep failure evidence private and use a support ticket for account-specific routing questions.

References: Webuzo add-forwarder and pipe documentation and Webuzo deletion procedure.

Reviewed October 15, 2026. The add, delete and historical Bread Basket tasks were consolidated; no customer rule, script or mail flow was executed.