# Email Piping

https://docs.wisecp.com/fr/email-piping

Turn messages sent to department mailboxes into support tickets, decide which senders are accepted and connect each department to a local or external mail provider.

## Reaching the Screen

Open **Support Settings** and choose **Email Piping**: `{admin}/tickets/settings?tab=pipe`

## What Is on the Screen

Global rules appear first. Provider credentials are configured once for the installation, while sender and mailbox settings are stored separately for each support department.

## Fields

### Global Rules

- **Enable Email Pipe**: Turns the incoming-mail conversion process on or off.
- **Processing Method**: **Default** always imports incoming mail. **Associate** links a matching registered client and still imports other senders. **Restrict** creates a ticket only for a registered client's address.
- **Enable Spam Protection**: Stops mail marked as spam from becoming a ticket.
- **Email Subject Prefix**: Defines the reference prefix used in ticket email subjects, such as REF.

### Providers and Departments

- **Service Provider**: Opens the configuration supplied by the selected Email Piping module. Shared client credentials are saved once and validated before department mailboxes use them.
- **Department**: Each department has its own sender identity and mailbox connection.
- **Sender Name**: The name recipients see on outgoing support mail for the department.
- **Sender Email**: The address used by the department for support mail.
- **Provider**: Uses the Local Server or one of the installed provider modules.
- **Connect or Disconnect**: Authorizes or removes the mailbox connection for the selected department. The connected address is shown after authorization.

Choosing Local Server displays the forwarding command for the mail server. External providers can expose a setup guide, redirect URI, credential validation and a mailbox authorization popup.

## Tasks

### Connect a provider mailbox

1. Enable Email Piping and choose the processing and spam rules.
2. Configure the provider once, enter its shared credentials and use **Validate**.
3. Open the target department, enter its sender name and email, choose the provider and connect its mailbox.
4. Save the settings. New matching messages can now be converted into department tickets.

### Configure a local mail server

1. Choose **Local Server** for the department.
2. Copy the displayed forwarding command into the matching mailbox forwarding rule.
3. Save the department and send a controlled test message.
4. The message appears as an Email Piping ticket with its source marker.

## Things to Watch

> **Restrict rejects unknown senders**
> 
> With Restrict selected, mail that does not belong to a registered client does not create a ticket. Use Associate when unknown senders should still enter the queue.

> **Credentials and mailboxes have different scopes**
> 
> Provider client credentials are shared across departments. Each department still authorizes its own mailbox and keeps its own sender identity.

## Privileges

**Ticket Operations** is required to save Email Piping settings. The direct menu shortcut may be shown only to staff with administrator privilege-management access.

## Related Screens

- [Departments]({admin}/departments)
- [Tickets]({admin}/tickets)