Plesk email routing

Forward a Plesk mailbox to another address

Send new messages received by a hosted mailbox to one or more destination addresses. Decide first whether Plesk should also retain a local copy, then test the route from an unrelated account.

Forward new mailExisting messages are not moved to the destination.

Choose local storageKeep the mailbox enabled for a local copy or disable its mailbox function when appropriate.

Test externallySend from a third address and confirm delivery, headers and any local copy.

Before you begin

Confirm which forwarding service you need

This guide is for mailboxes hosted inside a UKC Plesk hosting service. If the domain is parked and you use the Client Area’s included Email Forwarding feature, configure the alias from the domain’s Email Forwarding page instead.

The domain’s MX records must direct incoming mail to the Plesk mail server for Plesk forwarding to receive it.

Delivery choice

Forward only or keep a local copy?

Forward and retainLeave the mailbox enabled. Plesk stores a copy while forwarding another to the destination, so monitor mailbox quota.

Forward onlyUse forwarding without retaining mailbox delivery when no one needs to sign in locally. Confirm the exact option offered by your Plesk version.

Plesk steps

Set up the forward

1

Log in to PleskUse “Log in to Plesk” beside the correct UKC hosting service.

2

Open MailSelect the source email address that will receive and forward the messages.

3

Open ForwardingEnable Switch on mail forwarding.

4

Add the destinationEnter each complete email address carefully. Put separate destinations on separate lines where Plesk requests this.

5

Save the changeReturn to the account and confirm forwarding remains enabled.

Verification

Test the whole delivery path

  • Send a uniquely titled message from an unrelated external address.
  • Confirm it arrives at the forwarding destination.
  • If retaining mail, sign in to webmail and confirm the local copy.
  • Reply from the destination and remember that the reply normally uses the destination address, not the forwarded address.
  • Check spam and quarantine before deciding the forward failed.

Common problems

Forwarding can expose sender-policy issues

Forwarding loopDo not forward A to B when B already forwards back to A.

DMARC rejectionSome destination providers reject forwarded messages when the original sender’s authentication policy is strict.

Mailbox fullA retained local copy continues consuming quota even when the forwarded copy arrives elsewhere.

Wrong MX routeIf mail goes to another provider, changing Plesk forwarding will have no effect.

For important business mail, a directly configured mailbox is more predictable than forwarding.

Forwarding introduces another provider and another policy decision into the delivery path.

Need help?

Send a traceable example

Include the source address, destination provider, date and exact time of a test, external sender address, message subject, whether a local copy arrived and any non-delivery message with its diagnostic text.

Forward still not arriving?Open a ticket with that evidence. Never send either mailbox password.

Open a support ticket

Was this answer helpful?

« Back