Sending Email
How to send mail from Axene Workspace, from webmail compose or any SMTP client, plus threading, identities, tracking, and deliverability.
There are two ways to send mail from a Workspace mailbox: the webmail composer in the browser (available on every plan), and SMTP from an external client such as Outlook, Thunderbird, Apple Mail, or your phone (paid plans). This page covers both, plus everything that happens around a send: threading, send-as identities, signatures, read tracking, and the DNS records that keep your mail out of spam folders.
Before you can send
Sending happens from a mailbox on a verified domain. During onboarding Workspace generates the SPF, DKIM, and DMARC records (plus ownership and MX) for your domain; once all five are live, the domain is verified, mail hosting is enabled, and DKIM signing of your outgoing mail is activated. The records and what each one does are covered in Domains.
- SPF tells receivers which servers may send for your domain.
- DKIM cryptographically signs each outgoing message so receivers can verify it was not tampered with.
- DMARC tells receivers what to do when those checks fail.
After your domain verifies, send a test message to an external account (for example a personal Gmail) and reply to it. A clean round trip confirms SPF, DKIM, and your MX record are all working end to end.
Sending from webmail
Press C anywhere in Mail, or click the compose button. The full composer is documented in Webmail; the send-relevant parts:
- Recipients - type into To, Cc, or Bcc. Addresses become chips as you type, and autocomplete suggests people you have recently corresponded with, mined from your own Sent mail and Inbox. At least one To recipient is required.
- From - if you have send-as identities, pick the sending address from the From selector.
- Attachments - attach files with the paperclip or drag and drop them onto the composer. The limits are 5 MB per file and 24 MB total per message, enforced on the server as well, so an oversized attachment is rejected rather than silently dropped.
- Format - the composer sends clean plain-text email, the most reliably delivered and universally readable format.
A copy of every sent message is filed into your Sent folder.
Undo send
When you click Send, the message is held for 5 seconds with an Undo button in the toast. Click Undo and nothing is sent; the composer stays open with everything intact. Once the window passes, the message goes out.
Schedule send
Next to the Send button is a schedule menu with three presets:
| Preset | When it sends |
|---|---|
| In 1 hour | One hour from now |
| This evening (6pm) | Today at 18:00, or tomorrow at 18:00 if it is already past |
| Tomorrow (8am) | Tomorrow at 08:00 |
A scheduled message is stored and sent by the server at the chosen time, so you can close the browser and it still goes out.
Scheduled sends do not yet support Bcc separately: Bcc recipients on a scheduled message are delivered via Cc, which makes them visible to everyone. If Bcc privacy matters, send the message immediately instead of scheduling it.
Replies, forwards, and threading
- Reply answers the sender, quoting the original below your text.
- Reply all answers the sender and puts everyone else from the original To and Cc lines (minus you) on Cc.
- Forward carries the original message and its attachments to a new recipient.
Replies set the standard threading headers (In-Reply-To, References), so the conversation stays grouped in your mailbox and in the recipient's mail client.
Send-as identities
If an alias routes to your mailbox (say [email protected] delivering to [email protected]), you can send as that address:
- Go to Settings > Identities and add the address, optionally with its own display name and reply-to.
- In the composer, pick it from the From selector.
You can only add identities for the mailbox address itself or an alias that routes to it; one identity can be marked as the default and is preselected in the composer. The server verifies the From address against your registered identities on every send, so an unregistered address is rejected.
Signatures
Set your signature under Settings > Profile & signature. It is saved as the default signature for your mailbox.
Read tracking
If read tracking is enabled for your Workspace deployment (it is off by default), you can opt in per message from the composer. A tracked message carries an invisible pixel; when the recipient opens it, the open count and last-opened time show under Settings > Tracking. Tracking data is kept for 90 days.
Read tracking is best-effort. Many mail clients block remote images, in which case a message shows as "not opened" even if it was read.
Sending from an external client (SMTP)
On the Lite and Business plans, any standard mail client can send through Workspace over SMTP. The settings are the same for every mailbox on every domain:
| Setting | Value |
|---|---|
| Server | mail.axene.io |
| Port | 587 (STARTTLS) or 465 (SSL/TLS) |
| Username | Your full mailbox address, e.g. [email protected] |
| Password | Mailbox password or, preferably, an app password |
| Authentication | Normal password (required) |
Port 587 with STARTTLS is the preferred submission port. Use an app password per device so you can revoke a lost laptop without touching anything else. Step-by-step setup for Apple Mail, Outlook, Thunderbird, iPhone, and Android is in Mail clients.
SMTP authentication is mandatory: enable "Require sign-in" (or "Use same settings as incoming server") in your client's outgoing settings, with the full address as the username. On the Free plan, SMTP logins are rejected; webmail sending still works.
If port 587 is blocked
Some ISPs, hotel networks, and mobile carriers block outbound 587. Switch the outgoing security to SSL/TLS on port 465, which works identically. Never fall back to port 25: it is reserved for server-to-server mail exchange and is blocked for client submission.
Sending limits
The enforced limits on outgoing mail are the attachment caps: 5 MB per file and 24 MB total per message, checked in the composer and again on the server. Workspace does not currently impose daily or hourly caps on how many messages you send.