Email Forwarding

85 vues Markdown

Give a customer a working address on their own domain by pointing it at a mailbox they already use.

Opening the Screen

Open a domain service from Orders › Services, then pick the Email Forwarding tab: {admin}/services/detail?id={service}&content=email-forwarding

The tab appears only when the service is a domain and its registrar module can read forwarding rules. That is why it shows up at one registrar and not at another.

When the tab is not there

The service is not a domain Hosting, server and software services never get the domain tabs. Whatever their module offers sits on the Management tab.

The registrar module does not offer forwarding A module that registers and renews domains but cannot list forwarding rules counts as unsupported. The tab is skipped without a message.

The module could not be loaded Both forwarding tabs disappear and Transfer loses its lock and auth code actions. The Details tab names the module the product uses.

What Is on the Screen

One card with four areas. Nothing is kept in WISECP: the card is a view onto the rules that exist at the registrar. A rule created in the registrar's own panel appears here, and one deleted here disappears there. Each add, edit and delete is written to the operator's action log.

Area	What it holds	When it appears
Card header	The Email Forwarding title and the green Add Forwarding button.	Always, including while the list loads.
Information note	A fixed sentence: mail sent to the source address goes to the destination address.	Always. It is guidance, not a status message.
Rule table	One row per rule: source address, arrow, destination address and row actions.	When the registrar returned at least one rule.
Empty state	An information icon above No data available yet.	When there are no rules, after the last one is deleted, and when the read itself failed.

The rule table

Source Address shows the full address on this domain. Destination Address shows the mailbox that receives the mail. Between them sits a narrow arrow column.

The last column holds a pencil button with an Edit tooltip and a bin button with a Delete tooltip. Both are icon only, so hover to tell them apart. There is no bulk action; rules are handled one at a time.

How the list is loaded

First opening Opening the tab reads the rules once from the registrar.

Switching tabs Leaving the tab and coming back does not read again. You still see the first answer.

After adding or editing The whole list is read again, so what you see is the provider's answer.

After deleting Only that row leaves the table. Nothing is read again.

To read the list again at any other moment, reload the service detail page.

Fields

Both fields sit in one window, opened by Add Forwarding in the card header or by the pencil button on a row.

Source Address Required. Only the part before the at sign, for example info. The panel adds the domain, and it cannot be typed here.

Destination Address Required. The full mailbox that receives the mail, for example [email protected]. It has to be an address that already works.

Domain suffix Not a field. The grey box attached to Source Address shows the domain of the service. It is fixed, and no other domain can be forwarded here.

Save button state Not a field. The footer button stays disabled until both fields are filled, and while editing until a value changes.

Tasks

Adding a forwarding rule

On the Email Forwarding tab, click Add Forwarding in the card header.
Fill in Source Address and Destination Address.
Click Add Email Forwarding at the bottom of the window.
The window closes and the table reloads with the new row in it.

Editing a forwarding rule

On the row you want to change, click the pencil button whose tooltip reads Edit. The Edit Email Forwarding window opens with both current values.
Change Source Address, Destination Address or both.
Click Save Changes at the bottom of the window.
The window closes and the row shows what the registrar stored.

Deleting a forwarding rule

On the row you want to remove, click the bin button whose tooltip reads Delete.
The Confirm Deletion window names the rule and warns that it will be gone for good.
Click Yes, go ahead.
The row leaves the table at once. If it was the last one, the No data available yet. empty state takes its place.

Things to Watch

Every change reaches the registrar at once

There is no draft state here. Adding, editing and deleting are carried out the moment you confirm, and there is nothing to roll back. Restoring a rule means creating it again by hand.

Deleting is silent for whoever writes to that address

Once the deletion is applied, mail sent to that source address stops reaching the destination. Nobody is told and nothing is held. Confirm with the customer before removing a rule that is in use.

An unreadable answer looks like an empty one

If the registrar refuses the read, the table falls back to the same No data available yet. state as a domain with no rules. Expired credentials, a provider outage or a domain the account no longer holds all end this way, and the provider's message is not shown. Before you conclude that no rule exists, reload the page or check the module log.

Required Privileges

Reading the rule list needs SERVICES_LOOK or SERVICES_OPERATION. Adding, editing and deleting all need SERVICES_OPERATION.

The check happens on submission, not on the buttons. A staff member with only SERVICES_LOOK still sees the buttons and can open the window, but gets an authorization error instead of a confirmation.

Cet article vous a-t-il été utile ?

Merci pour votre retour !

Besoin d'aide supplémentaire ?

Notre équipe d'assistance est disponible 24h/24 pour tout ce que vous ne trouvez pas ci-dessus.

Nous contacter Ouvrir un ticket