Help / Reseller guide

Reseller guide

A reseller looks after domains for customers. Your Dashboard lists both the domains you administer and the domains where you are the reseller. For all of them you can do everything in the Domain administrator guide (mailboxes and forwarders). This guide covers the extra things only resellers can do.

Adding a domain

  1. In the menu, under Domains, click All domains.
  2. Under Add domain, enter the Domain name (for example customer.com).
  3. Click Create domain. You are recorded as the domain's reseller and its primary administrator.
  4. The domain's DNS page opens. It lists every DNS record the domain needs for its mail to come here, and checks each against what DNS has now: what to add, what to change (with the current value), and which old records to remove. Make those changes wherever the domain's DNS is managed, or put its DNS on our name servers (below). Open the page again any time from DNS on the Domains page or in the menu.

DNS on our name servers

Under Name servers on the DNS page, Put the zone on our name servers creates the domain's zone on ns1 and ns2.securelyconnect.net with every record the page lists (if ns1 already has a zone for the domain, that one is taken on unchanged). Nothing changes for the domain until its name servers are changed to ours at its registrar; until then the page checks the records against our name servers, and after it, against public DNS. The page notices the change by itself and then shows Hosted here.

Publish the records not done yet writes the app's records that aren't right into the zone. Other records are left as they are, and an existing SPF record keeps what it already allows. The table shows the serial each name server serves, and Changes made by Mail Admin lists every change. Only you and the server owner see these buttons.

The zone editor

Once the zone is on our name servers, DNS zone (in the menu under the domain, or Edit every record in the zone on the DNS page) lists every record, and adds, changes and deletes any of them: A, AAAA, ALIAS, CNAME, MX, TXT, SRV, CAA and NS. ALIAS is like a CNAME but allowed at the domain itself (for example for a website on a hosting service that gives a host name, not an address); it can't be used in DNSSEC-signed zones. Each change is shown before and after first and saved only with Save; if someone changed the zone in between, nothing is saved. Records marked Mail Admin are the ones the DNS page keeps right, and can't be changed here; the SPF record can be changed but must keep allowing this server. History lists every change, and Undo puts back what a change replaced, as long as nothing has changed those records since.

On the Administrators page, Allow DNS editing lets one of the domain's administrators use the zone editor too.

A new domain also gets a DKIM key (for signing its outgoing mail). Once its DNS record shows Done on the DNS page, click Switch DKIM signing on there. And once autoconfig. and autodiscover. point here, the server gets their certificate by itself within the hour, and email programs can then set themselves up from just an address and password (Apple Mail excepted).

Giving the customer access: administrators

A domain can have several administrators. Each logs in with a mailbox on this server. One of them is the primary administrator: the only one who can change the domain's allowance and the quota for its new mailboxes, and the one whose cap the domain counts against. The others can do everything else, including setting individual mailbox quotas.

  1. Open Mailboxes for the new domain and create the customer's mailbox, for example local part owner.
  2. In the left-hand menu, open Domains, then the domain, and click Administrators. The page lists the domain's administrators, with the primary one marked (primary). Enter owner@customer.com under Add administrator and click Add.
  3. Click Make primary next to them if they should manage the domain's quota. You can remove yourself afterwards, or stay on as a second administrator.
  4. Send the customer the address, the password, and a link to the Domain administrator guide.

Only you (as the domain's reseller) and the server owner can add or remove administrators or choose the primary one, so only you and the owner see the Administrators link. If you remove the primary administrator, the one added earliest after them becomes primary. A domain always keeps at least one administrator.

The mail server will only accept mail for the domain once its DNS (MX record) points to this server: set up wherever its DNS is managed, or published from the DNS page when its DNS is on our name servers.

Quotas and caps

A quota limits how much mail one mailbox can store. A domain's allowance limits how much all its mailboxes together can store. A cap limits how much someone can hand out. Caps compare what is handed out, not mail actually stored: ten 1 GB mailboxes use 10 GB of a cap even if they are empty.

  • The server owner sets your cap.
  • You set a cap for each of your domains' primary administrators on the Quotas page (Set cap). Only you can: not even the server owner sets caps for another reseller's administrators. Their caps together must fit within yours. An administrator without a cap counts as whatever their domains take.
  • A domain with an allowance takes its allowance from the cap above it. Its mailbox quotas may then add up to more than the allowance (people rarely fill their mailboxes); instead, the mail server stops the domain at its allowance. A domain without an allowance takes whatever its mailbox quotas add up to.
  • Domains where you are the primary administrator yourself come straight out of your cap.
  • Administrators share their cap out between their domains (allowances) and mailboxes (see the administrator guide). You can change any of those too, for example to raise one for a while; they still count against the administrator's cap.

The Quotas page shows each cap, how much is handed out and what remains. You can lower a cap below what is already handed out: nothing is taken away, but it shows as Over-allocated and nothing under it can grow until it is brought back under.

No cap means no limit. Every mailbox has its own quota whatever the caps, and none can be unlimited. A new mailbox gets the size typed for it; else the domain's quota for new mailboxes; else the standard 5 GB. A quota set by hand wins even when it is lower.

Mailboxes that had no quota were given one on 16 October 2026: their usage plus 1 GB, rounded up to a whole GB, and at least 5 GB (or the domain's default, if larger). That was allowed even where it took a cap over; whoever was affected was emailed.

When quotas take effect

Existing mailboxes may already hold more mail than the quota you plan for them, so quotas start out proposed only: they are saved, counted against caps and shown everywhere, but mail keeps arriving as before. Each domain switches to enforced on a date you choose:

  1. Set the quotas you want, then caps.
  2. Once the mail server reports mailbox usage, the Quotas page lists Mailboxes over their quota. Warn those users, or raise their quota.
  3. On the Domains page (Quota on the domain's row) or at the top of the Mailboxes page, enter a date next to Quotas will be enforced beginning on the date you set and click Set date. From that day, new mail is deferred for a mailbox (or a domain) that is full. Leave it blank to go back to proposed only.
  4. To give one mailbox more time, set its own date under Quota on its row. Domain administrators can do this too, up to 90 days past the domain's date.

Enforcement dates can only be set once mailbox usage is being collected, so you can always see who would be affected first. Every change is recorded in the audit log.

A cap set below what is already handed out marks it Over-allocated straight away, so check the Quotas page totals before setting one.

Deleting a domain

On the Domains page, click Delete on the domain's row and confirm. This deletes the domain and every mailbox, forwarder and alias in it. Stored mail is not deleted from disk, but nobody can log in to it any more. You cannot undo this.

If the domain administrator's login mailbox was in that domain, they can no longer log in.

Suspended senders

If a mailbox in any of your customers' domains has its sending suspended because it sent too much in an hour or too many of its messages bounced (a stolen password or a bad mailing list), it appears in the Suspended senders in your domains panel on your Dashboard, with a Lift suspension button. Your customer can lift it too; the suspension also ends on its own. What to check first is explained under Suspended sending in the Domain administrator guide.

Your customers' view

Customers you set up are domain administrators. They can manage mailboxes and forwarders in their own domains, but they cannot add or delete domains and cannot see your other customers.