Skip to content

Webmail

CorePanel ships a webmail client — Roundcube — so a mailbox owner can read and send mail from a browser, without configuring anything. There is nothing to install and nothing to enable: it is part of the server from the moment CorePanel is installed, and every domain gets its own address for it.

Webmail is provisioned with the domain, not separately. When you create a hosting account, add an addon domain or park an alias, CorePanel writes:

  • a website for webmail.<domain>, serving the webmail;
  • an A record for the webmail host in the domain’s DNS zone, when CorePanel manages the DNS;
  • webmail.<domain> into the domain’s certificate request, alongside www, mail, ftp and corepanel — see SSL/TLS Certificates.

This is why webmail is a reserved label: you cannot create a subdomain called webmail, because the domain already has one. The same goes for the account’s subdomains.

Gets webmail.<domain>
Primary domainYes
Addon domainYes
Alias (parked) domainYes — it serves the same webmail
SubdomainNo

All of these addresses are served by one shared Roundcube installation. The hostname decides which certificate is presented and nothing else — it is not a separate copy per domain, and there is no per-domain configuration to maintain.

Send the mailbox owner to https://webmail.<their domain>. They sign in on the mailbox page with the mailbox address and its password, and Open my mail takes them into Roundcube already signed in.

The sign-in screen at webmail.example.com: a card headed by the domain name example.com with its initial, an email address field where "info" is typed and "@example.com" is shown fixed after it, a password field with a show-password button, and a Sign in button. A line below tells Outlook and phone users they can sign in to set up a device or change the password; a language picker sits at the top right and a small "Powered by CorePanel" at the bottom.

Addresshttps://webmail.example.com
UsernameJust info — the field shows @example.com after it — or the full address. On Roundcube’s own sign-in screen (see Security), only the full address
PasswordThe mailbox password (not the hosting account password)

The webmail is a service for the people who own the mailboxes, and they do not need a panel login — only the address above.

Roundcube’s own sign-in screen is not shown any more: a visitor without a webmail session is sent to the mailbox page. Signing out of Roundcube signs out of the mailbox page too, so a shared computer is not left signed in to either.

Under the hood Roundcube reads the mail over IMAP from Dovecot on the same server, and sends through Postfix on port 587. Mail read in the webmail is the same mail seen over IMAP on a phone: folders, read state and filters are shared, because they live in the mailbox, not in the client.

https://webmail.<domain> opens a page for the person who uses a mailbox (its own address is https://webmail.<domain>/mailbox/). They sign in with the mailbox’s own address and password, and every sign-in lands on this page — whether they came to read mail in the browser or to change a setting for Outlook or their phone:

  • Open my mail — the page’s main button, already focused, so Enter goes into Roundcube, signed in, without typing the password again.
  • Usage — under the address, a bar with how much of the mailbox’s quota is in use (“1.9 GB of 2 GB”), or the size and “no limit” for a mailbox without one.
  • Automatic reply — answers each sender once while the person is away: a subject, a message, optional first and last days, and how many days to wait before answering the same sender again (1 to 60, the mail server’s maximum). It is the same autoresponder the panel edits for that mailbox, so a reply set on either side shows on the other. Subject up to 200 characters, message up to 8 KB. The first and last days are the server’s calendar days. Every change made here is written to core’s log with the address.
  • Rules and forwarding — sorts incoming mail as it arrives: each rule tests the From, To, Cc or subject (contains, is exactly, or matches a pattern such as *@example.com) and then moves the message to a folder, forwards it, keeps it in the Inbox too, deletes it, or stops the rules below; they run top to bottom and can be reordered. Above them, a switch forwards a copy of every message to another address, keeping a copy here or not. They are the panel’s filters for that mailbox — one list, edited from either side. A rule the provider set that this page cannot edit, such as one that pipes to a script, is shown by its name only, with a lock, and keeps its place in the list. Mail is forwarded to at most four addresses in all, never to the mailbox itself. If the list changed somewhere else while it was open, saving reloads it instead of overwriting the other change. Every save is written to core’s log with where the mail is forwarded.
  • Recent activity — where the mailbox signed in during the last 30 days: one line per kind of client (mail app over IMAP or POP3, sending over SMTP) and address, with the country, the last time and how many times, followed by the refused sign-ins. A sign-in from the server itself is shown as “Webmail or an app on this server”: Roundcube signs in from there, and so would a script running on the server, and the address cannot tell them apart. It reads the server’s sign-in record (see Access Protection), limited to this mailbox’s IMAP, POP3 and SMTP sign-ins. That record is trimmed by age and by size, so on a busy mail server it may reach back less than 30 days; the page then says how many days it covers. It is left out on a server that keeps no record.
  • Connect a new device — the server name, ports and username to type into Outlook, Thunderbird or a phone, each with a copy button, plus a profile for iPhone, iPad and Mac that sets the account up in one tap (the device asks for the password). The server name is mail.<domain> when the domain’s certificate covers it, and the server’s own hostname otherwise, so mail clients never warn about the certificate.
  • Change password — asks for the current password. Once changed, every other place signed in to this page with the old password is signed out; phones and mail clients need the new password too.

The mailbox page at webmail.example.com, signed in as info@example.com, with an Open my mail button beside the address and a nearly full usage bar reading 1.9 GB of 2 GB. Below it, four notices: the mailbox is 94 % full, automatic reply is on until Oct 25 with an Edit button, a copy of every message is forwarded to me@elsewhere.net with an Edit button, and refused sign-ins from Russia in the last 24 hours with a Review button. Under Your mailbox, three cards: Automatic reply, "On · until Oct 25"; Rules and forwarding, "Forwarding to me@elsewhere.net · 3 rules"; and Recent activity, "4 places · 14 failed sign-ins". Under Setup, Connect a new device and Change password are folded to one line each.

The page adapts to the mailbox rather than to settings anyone has to choose:

  • Notices appear only when there is something to say: the mailbox is 90 % full or more, an automatic reply is answering right now (with its last day), or sign-ins were refused in the last 24 hours from a country the mailbox has never signed in from. A copy of every message being forwarded is said on every visit, with the address: a forward someone else set with the password would otherwise copy the mail away unseen. Each opens the view it is about.
  • Connect a new device is shown open, at the top, while no mail app or phone has signed in to the mailbox in the span the record covers, and folds itself away once one has. A mailbox read only in the webmail gets a one-line “Want this mail on your phone too?” instead. On a server without a sign-in record — or with a corepanel-auth older than the page, which can hand back only its newest sign-ins — it simply stays folded, and the new-country notice is not shown either.
  • A link to https://webmail.<domain>/mailbox/#autoreply, #rules or #activity opens that view directly.

The automatic reply dialog open over the mailbox page: a switch to send automatic replies, the subject "Out of office", the message "Back on Monday.", an empty start date and an end date of 10/25/2026, a reply interval of 3 days, and the buttons Turn off &#x26; remove and Save.

The rules and forwarding dialog: a switch, on, to forward a copy of every message to me@elsewhere.net, keeping a copy in this mailbox; then three numbered rules, each with arrows to move it up or down. Rule 1, Newsletters: when all of these match, From contains "news@", then move to folder Newsletters. Rule 2, Helpdesk tickets, has a lock and reads "Set by your provider. It runs in this place in the list; only they can change it." Rule 3, Invoices to accounting: when any of these matches, Subject contains "invoice" or From matches the pattern "*@billing.example.org".

The account’s administrator can lock the rules for every mailbox of the account (see Locking the mailbox page’s rules). The page then shows them read only, with a note that the provider manages them; the rules keep running, and the automatic reply stays the mailbox user’s.

The recent activity dialog: under Signed in from, a mail app over IMAP and sending over SMTP from an address in Chile, "Webmail or an app on this server" from the server itself, and another IMAP address in Chile, each with how long ago and how many sign-ins; under Refused sign-ins, "14 in the last 30 days" and the latest ones from Russia over SMTP and IMAP and one through the webmail; then a suggestion to change the password with a button, and the time zone the times are shown in.

When the administrator has asked for a new password, the page shows only the change-password form — not Open my mail, not the device settings, not the automatic reply or the activity (the server refuses those too) — until one is chosen, and the server refuses to open the webmail for that mailbox until then. Mail apps, and Roundcube’s own sign-in screen, keep working with the old password meanwhile.

The page shows nothing about the hosting account and cannot reach the panel. It differs from Roundcube in two ways:

  • Only addresses of that domain sign in on its webmail. host: info@example.com signs in at webmail.example.com, not at another domain’s. On an alias domain’s host, the addresses of the domain it is an alias for sign in, typed with either domain. Typing only the part before the @ works.
  • Five wrong passwords for an address within 15 minutes lock that address out of the page — counted per mailbox, however the address is typed and on whichever of its domains’ hosts — for a minute, then longer if the guessing goes on; the page counts down the wait. Roundcube and mail clients are not affected.

A mailbox the administrator has disabled, or whose sign-in is closed, cannot sign in here either: the page lets in exactly the mailboxes the mail server lets in. A mailbox of a suspended hosting account still signs in and reads its mail, as it does over IMAP, but cannot set an automatic reply or forward mail until the suspension is lifted (it can remove them, and sort its mail into folders).

The automatic reply and the rules can be saved or removed at most 20 times in 10 minutes per mailbox, together; a save the server refuses does not count.

Open my mail does not hand Roundcube the password, which the page does not keep. It hands it a one-off key for that mailbox, which the mail server accepts only from the server itself — where Roundcube runs — so a key that leaks opens nothing from anywhere else. It stops working when the webmail session goes idle for four hours, after twelve hours at most, and as soon as the mailbox password changes.

Roundcube covers reading and writing mail: folders, search, an address book, an Archive button, and downloading several messages or attachments at once as a zip. It is deliberately kept to that.

Anything that changes the mailbox itself is done in the panel, not in the webmail:

Where
Change the mailbox passwordThe mailbox page, Panel → Email accounts, or the client panel
Autoresponder (out of office)Panel → the mailbox’s workspace
Filters (Sieve rules)Panel → the mailbox’s workspace
Quota, enabling and disablingPanel → Email accounts

Keeping them in one place is the point: a filter written in the panel applies to mail arriving at the server, so it works the same in the webmail, on a phone and over POP3. See Mailboxes and Forwarders.

Roundcube accepts uploads of up to 25 MB per message. The message still has to leave through Postfix, which enforces its own limit (10 MB by default) on the whole encoded message — and attachments grow by roughly a third when encoded for mail. In practice anything much over ~7 MB of actual file is better sent as a link than as an attachment.

The webmail is reachable from the whole internet, for every domain on the server. It is configured accordingly, and these defaults are visible to users, so it is worth knowing what they do:

  • HTTPS is forced. A plain HTTP request to webmail.<domain> is answered with a redirect to HTTPS, so no password travels in the clear. The redirect is only issued while that hostname has a currently valid certificate — otherwise users would be bounced to a handshake that cannot complete, which would take the webmail off the air on both ports instead of merely leaving it unencrypted.
  • A session is bound to the address that created it. A stolen session cookie is useless from anywhere else. The cost is real: a client whose IP address changes mid-session — a phone moving between mobile data and Wi-Fi, some ISP proxies — is signed out and has to sign in again.
  • Every sign-in attempt is recorded, successful or failed, with the client’s real address. Roundcube talks to Dovecot over loopback, so without this record every webmail attempt would appear in the mail logs as coming from 127.0.0.1.
  • Only webmail.* hostnames are answered, so the installation cannot be made to generate links pointing at somebody else’s host.
  • Open my mail works from the server only. The key it hands Roundcube is accepted by the mail server only for a login from the server itself. Do not enable Dovecot’s auth_cache: with it, a key accepted once would be answered from the cache for any address. CorePanel checks: while auth_cache_size is anything but 0, Open my mail sends mailbox users to Roundcube’s own sign-in, where they use their password, and the panel log says why.

Mailbox passwords are what stands between an attacker and the mail. Set strong ones — the panel generates them when you create or edit a mailbox — and check a mailbox’s Security section, or Access Protection, when something looks wrong.

A suspended account keeps its webmail: mail is still delivered and still readable, which is what you want while a billing issue is sorted out.

The webmail is a PHP application exposed to the internet, so it does not run as any hosting account and cannot reach one:

  • it runs as its own roundcube system user, which has no shell, in its own PHP-FPM pool, separate from every account’s pool;
  • its PHP is confined to the Roundcube directory (open_basedir), with the process-execution functions disabled;
  • temporary files, including attachments being uploaded, stay in Roundcube’s own directory rather than the shared /tmp, where other accounts could read them;
  • its small SQLite database holds preferences, contacts and caches. Messages are never stored there — they stay in the mailbox, on Dovecot.

One operational consequence: Roundcube requires PHP 8.4, so that version cannot be removed from the server while the webmail is in use. Server maintenance never removes a PHP version for exactly this kind of reason.

SymptomCause
webmail.<domain> does not resolveThe A record is missing — normal when the domain’s DNS is hosted elsewhere
Certificate warning, or no redirect to HTTPSNo valid certificate for that hostname yet. Check the domain’s certificate status; issuance needs the name to resolve to this server
”The address or the password is not correct” with the right passwordThe mailbox address of that domain (or just the part before the @). The hosting account username will not work, and another domain’s address signs in at that domain’s webmail
Signed out every few minutesThe client’s IP address is changing mid-session (mobile networks, some proxies)
Cannot change the password from the webmailBy design — it is changed on the mailbox page, in the panel or in the client panel
”Too many attempts” on the mailbox pageFive wrong passwords for that address in 15 minutes. Wait for the time the page shows — a minute at first, up to an hour if the guessing goes on. Mail apps are not affected
Large attachment refused on sendThe message exceeds the server’s mail size limit, not the upload limit