Skip to content

Reseller Panel Branding ​

In Management, open Subscriptions and select Open control panel on the intended Active reseller service. Choose Reseller for customer administration or My Account for your own mail-hosting tools. These actions apply to that reseller account on the selected server.

Panel branding, mail-client and Roundcube hostnames, and in-house webmail branding each have their own configuration and DNS targets.

  1. Open Reseller → Branding.
  2. Under Panel Branding, set Panel Name.
  3. Choose primary/hover colors and sidebar background/text colors for both dark and light modes.
  4. Set the Documentation URL and Support URL under Dashboard Links.
  5. Review Preview, then click Save Branding.
  6. Check the result in both themes and on your customer-facing panel URL.

To restore defaults, use Reset to Defaults and accept its confirmation. This resets saved branding settings, which can include more than colors; record any server-label or DNS-guidance customizations you intend to restore.

Set up or remove a custom panel URL ​

  1. Open Branding → Custom Panel URL.
  2. At your DNS provider, add a CNAME for a hostname such as panel.example.com, pointing to the value displayed in this section.
  3. Enter the full hostname under Enter Your Domain.
  4. Click Check DNS and resolve any reported issue.
  5. Click Request Certificate when available.
  6. Wait for the certificate status, then visit the HTTPS URL and verify the intended branding and login page.

To remove it, click Remove Custom URL and confirm. Tell customers to use the main panel URL or your replacement before removing their established entry point. Removing a panel URL does not edit your DNS provider's records.

This is separate from custom IMAP/SMTP hostnames and webmail branding. Use the target displayed by the corresponding feature.

Customize the login server list ​

  1. With a custom URL configured, open Branding → Login Server Settings.
  2. Under Hide Servers, check servers you want omitted from that custom login page. An unchecked server remains visible.
  3. Under Custom Server Labels, select a server and enter a friendly display name. Use Add Custom Label for additional entries, or remove an entry to return to its default label.
  4. Click Save Settings.
  5. Open the custom login page and verify the visible choices and labels.

These are display settings for the custom URL. They do not move customer accounts between servers.

Set a custom SPF include ​

  1. Publish an SPF TXT record at a hostname you control, such as _spf.example.com, containing the provider include required by the page: include:mxroute.com or include:mxlogin.com.
  2. Open Branding → Custom SPF Include.
  3. Enter only that hostname in Custom Include Hostname. Do not paste include: or a complete SPF record into this field.
  4. Click Save Settings and resolve any DNS validation error.
  5. Verify the DNS guidance when logging in through your custom URL.

This shared include applies to DNS guidance across servers reached through that custom URL and can be used with the default MX records. Clear the field and save to return to the standard mxroute.com include. Changing guidance does not modify customers' already-published DNS records.

Configure custom MX guidance ​

The interface recommends the default MX records. Custom MX guidance requires you to maintain the destination DNS as mail-server addresses change. An MX target must not be a CNAME; this is different from the CNAME instructions for custom client hostnames.

  1. Open Branding → Custom MX Records.
  2. Select the intended server.
  3. Expand Advanced: Custom MX Records and read its warning.
  4. Enter Primary MX Server and its Priority. Optionally enter Secondary MX Server and its priority.
  5. Click Save Settings.
  6. Verify the displayed DNS guidance through your custom URL for that server.
  7. Repeat for each server needing custom guidance.

To restore a server's defaults, use Clear DNS for this server and save. Servers without custom values use the default records. These settings change instructions shown to users; customers still publish records at their own DNS providers.

Who needs a footer?