# How outbound mail is relayed
Source: https://docs.webgee.com/en/email/outbound-mail-relay



Every message sent from a WebGee account is routed through **MailBaby**, a
dedicated outbound relay. Applies to shared, reseller and Premium hosting, at no
additional cost.

<Callout type="info">
  MailBaby replaced **MailChannels** as the outbound relay. If you are working
  from older documentation, or have an SPF record referencing
  `relay.mailchannels.net`, it needs updating — see
  [Set your SPF record](/en/email/what-are-the-correct-spf-records-when-using-webgee-hosting).
</Callout>

## Why mail is relayed at all [#why-mail-is-relayed-at-all]

Sending directly from a shared server means your reputation is tied to an IP you
share with everyone else on it. One compromised account gets that IP
blacklisted, and everybody's mail starts failing.

A relay separates the two. Messages leave from a dedicated, monitored pool of
addresses with an established reputation, so a neighbour's problem is not yours.

It also means a **dedicated IP does not improve deliverability** — outbound mail
does not leave from your account's IP at all. See
[Dedicated IP addresses](/en/reseller/dedicated-ip-address-how-to-purchase-and-manage-your-dedicated-ips).

## What you need to do [#what-you-need-to-do]

**Get your SPF record right.** The relay must be authorised to send as your
domain, or every message fails SPF. Let cPanel generate it rather than copying
one — see
[Set your SPF record](/en/email/what-are-the-correct-spf-records-when-using-webgee-hosting).

**Enable DKIM**, under **cPanel → Email Deliverability**.

**Send authenticated.** Applications must use SMTP with a real mailbox, not
PHP's `mail()` — see
[Send WordPress email over SMTP](/en/hosting/wordpress/how-to-send-emails-in-wordpress-using-the-wp-smtp-mail-plugin)
and [Enable PHP mail()](/en/email/enabling-phpmail-on-your-account).

## Sending IP addresses [#sending-ip-addresses]

The relay sends from a pool that changes over time, so there is no fixed list
worth recording here. The authoritative answer is always the relay's own SPF
record, which is why `include:` is used rather than hard-coded addresses — the
list updates without you doing anything.

If a recipient asks you to allow-list your sending addresses, give them your
domain and SPF record rather than a list of IPs that will go stale.

## Monitoring what you send [#monitoring-what-you-send]

The **Mail Delivery Center** shows delivery statistics, logs and blocked
messages for your account — see
[Mail Delivery Center](/en/mail-delivery-center).

That is where to look when a message did not arrive, rather than guessing from
the bounce.

## Limits still apply [#limits-still-apply]

Relaying does not remove sending limits — see
[Email sending limits](/en/email/email-sending-limits). Messages are also scanned
before leaving, and anything scoring as spam is rejected back to you rather than
sent, which protects the shared reputation.

## Related [#related]

* [Set your SPF record](/en/email/what-are-the-correct-spf-records-when-using-webgee-hosting)
* [Mail Delivery Center](/en/mail-delivery-center)
* [Report a false positive](/en/email/report-a-false-positive)
