Skip to main content

Email for your domain

Email is set up in the dashboard under Domains → (select domain) → Email. There are two options: Kotisivukamu forwarding and outgoing mail server, or another provider such as Microsoft 365 or Google Workspace.

The Email card is available for domains registered or transferred through Kotisivukamu. The settings are in effect when the domain's nameservers are at Kotisivukamu (see Nameservers). Only team administrators can change the settings.

Option 1: Kotisivukamu​

Kotisivukamu offers two services:

  1. Incoming mail forwarding. Mail sent to an address such as info@yourcompany.com is forwarded to an existing mailbox you specify (e.g. firstname.lastname@gmail.com).
  2. Outgoing SMTP server. You can send messages from an @yourcompany.com address through Gmail or Outlook, for example, so the recipient sees the correct sender.
Kotisivukamu does not provide mailboxes

We do not store email. You need a "real" email service (e.g. Gmail) that messages are forwarded to and that you send from.

When you choose "Kotisivukamu", we add the required DNS records automatically as you start using the services:

TypeNamePurposeAdded when
MX@Receives incoming mail on our serverthere is at least one forward
TXT@SPF record (allows our servers to send mail on your behalf)there is a forward or an SMTP credential
TXT_dmarcDMARC policythere is an SMTP credential
CNAME*._domainkeyDKIM keys for signing outgoing mailthere is an SMTP credential

If records have gone missing or were deleted by accident, Update DNS adds them again.

Adding a forward​

  1. Open Domains → (select domain) → Email.
  2. In Source address, enter the first part of the address (e.g. info, or * for all addresses).
  3. In Email addresses, enter one or more destination addresses separated by commas.
  4. Click Add a forward. The forward is active as soon as the DNS records have propagated (usually minutes).

You can edit a forward's destinations later, and switch a forward off temporarily without deleting it.

Gmail: send messages from your @yourcompany.com address​

This is the most common setup: you use Gmail for daily reading, but want to send messages from your business address.

1. Create SMTP credentials in the dashboard​

  1. In the Email card, enter the address you want to send from (e.g. info) in Sender address and click Create SMTP credentials.
  2. Save the username and password immediately. The password is not shown again; if you lose it, create new credentials. The server is mail.kotisivukamu.fi, port 587 (STARTTLS). Port 465 (SSL/TLS) also works.

Each credential is tied to one sender address. If you want to send from several addresses (e.g. info@ and sales@), create credentials for each.

2. Add the address to Gmail​

  1. Open Gmail settings → Accounts and Import → Send mail as → Add another email address.
  2. Enter:
    • Name: the name you want recipients to see
    • Email address: e.g. info@yourcompany.com
    • Treat as an alias: untick if you want replies to come to Gmail while the "From" field shows correctly.
  3. Next Step. Gmail asks for the SMTP settings:
    • SMTP Server: mail.kotisivukamu.fi
    • Port: 587
    • Username: the username you got from Kotisivukamu
    • Password: the password you got from Kotisivukamu
    • Secured connection using TLS: selected
  4. Gmail sends a verification code to info@yourcompany.com. Because you have set up forwarding in Kotisivukamu, the code arrives in your Gmail — copy it and confirm.

Done. When composing a new message, you can choose the sender address in the From field.

Other email services​

  • Outlook.com / Microsoft 365: Settings → Mail → Sync email → Connected accounts → new POP/SMTP account.
  • Apple Mail (macOS/iOS): Mail → Preferences → Accounts → new Other Mail Account, use the same SMTP settings.
  • Mozilla Thunderbird: Account Settings → Outgoing Server (SMTP) → Add.

The settings are the same everywhere: server mail.kotisivukamu.fi, port 587 (STARTTLS) or 465 (SSL/TLS).

Forwarding as a webhook​

Email can also be forwarded to your own service as an HTTP POST request. This is handy if, for example, you want a customer's message to open directly in your ticketing system or CRM without a mailbox in between.

  1. Create a forward with these fields: Source address (e.g. support) and Webhook URL (e.g. https://yourservice.com/incoming-email). Leave the destination addresses empty if you want only the webhook, or fill in both so the message is both forwarded and POSTed.
  2. Save. When a message arrives, we parse the MIME body and send a JSON request to your webhook in the following format:
{
  "from": "sender@example.com",
  "to": ["support@yourcompany.com"],
  "to_local": "support@yourcompany.com",
  "subject": "Order status",
  "messageId": "<abc@mail.example.com>",
  "date": "Mon, 20 Apr 2026 19:00:00 +0000",
  "headers": { "...": "all headers" },
  "body": { "text": "Plain text...", "html": "<p>HTML...</p>" },
  "attachments": [
    { "filename": "attachment.pdf", "contentType": "application/pdf", "size": 12345, "content": "base64..." }
  ],
  "authentication": { "spf": {...}, "dkim": {...}, "dmarc": {...} }
}

Your server must respond with a 2xx status code within 20 seconds. Otherwise we retry up to three times with increasing delays; 4xx responses are not retried (our interpretation: a configuration error, not a temporary fault).

Tip

Use an HTTPS address only. Attachments arrive base64-encoded inside the JSON body, so you can handle everything with a single parse.

Limits​

  • Destination addresses: up to 10 per forward.
  • Maximum message size: 50 MB (headers + body + attachments combined). Larger messages are rejected before forwarding. The practical limit for a message forwarded to an email address is about 40 MB; a message delivered to a webhook can be 50 MB.
  • Outgoing messages: about 30 messages per minute per SMTP credential. The service is meant for ordinary business email, not bulk mailings.

Option 2: Another provider​

If you use Google Workspace, Microsoft 365, or another commercial email service, choose Another provider in the Email card. Kotisivukamu then does not add or remove email-related DNS records automatically.

Microsoft 365 and Google Workspace​

For Microsoft 365 and Google Workspace the Email card has the buttons Set up Microsoft 365 and Set up Google Workspace. They add the records the service needs for you. The buttons show when the domain's nameservers are at Kotisivukamu.

  1. Add the domain in the service's admin. The service shows the DNS records it needs.
  2. Copy the records into the dialog as text or paste a screenshot. The dialog shows which records will be added, which already exist and which are missing. At minimum the ownership verification record (TXT) and the incoming mail MX record must be included.
  3. Save, and verify the domain in the service.

Microsoft 365 shows the rest of the records only after verification, so its setup has two steps: first the verification record, then the other records.

Old conflicting records, such as a previous MX record, are removed, and the dialog shows them before you save. If the domain has no DMARC record, we add a default one.

Other services​

  1. Sign up for the service of your choice using your domain.
  2. The service gives you a list of DNS records (MX, SPF, usually also DKIM).
  3. Add the records in the DNS records card on the domain's page. Import from text or a screenshot recognises the records from the service's instructions, so you don't have to type them by hand.
  4. The service verifies the records, usually within a few minutes.
Need help?

If adding the records doesn't work out, contact customer support and we'll add them for you.