Business email

Meghly runs business email on your own domain (such as info@shop.com.bd). It takes three steps: add the domain, put its DNS records in place, and create mailboxes.

1. Adding the domain#

On the panel's Domains page, click Add domain and fill in:

As soon as the domain is added, Meghly creates a DKIM key for it (RSA 2048). The domain starts as Pending and turns Verified once all its DNS records are in place.

2. Putting the DNS records in place#

Open the domain: its DNS records tab lists every record it needs, with the state of each:

Each record shows In place, Different value (with the value it has now) or Not added yet. Copy the right value from Value to add into your DNS provider, then click Check again. Meghly also checks the records by itself every hour.

There are three easy ways to put the records in place:

• The domain's DNS is on Meghly: nothing to do — the mail records are added by themselves. See DNS hosting.
• Cloudflare: give Publish to Cloudflare a Cloudflare API token (with "Zone → DNS → Edit" and "Zone → Zone → Read"). Meghly adds all the records at once; the token is never stored. A record that already exists with a different value is reported before anything is changed.
• Any other provider: Export zone file downloads every record in one file, or copy them one by one.

Rotating the DKIM key#

Changing the DKIM key now and then is good practice. On the domain's DKIM keys tab, Rotate key makes a new key (2048, 3072 or 4096 bit). Add the new key's DNS record; the old key stays valid until its DNS record is removed, so no mail is caught out during the change.

3. Creating mailboxes#

On the domain's Mailboxes tab, click Add mailbox and fill in:

• Address — such as info or sales.
• Display name — the name recipients see (optional).
• Password — at least 12 characters, with at least one upper-case letter, one lower-case letter and one digit.
• Quota (GB) — the mailbox's space, 2 GB by default.

Each mailbox's menu has Open webmail, Mail client setup, Autoresponder (out of office), Reset password and Delete mailbox.

Autoresponder (out of office)#

Going on leave? Turn on Autoresponder (out of office) to reply automatically. You can set start and end dates (optional) and how many days pass before the same sender is answered again (1–30). Mailing lists, automatic mail and spam are never answered.

Aliases and forwarding#

To send one address's mail on to one or more others, use Add alias on the domain's Aliases tab. Put the original address in Source and where it goes in Destination (several separated by commas). To keep a copy in the original mailbox too, tick Keep a copy in the source mailbox.

4. Webmail and mail apps#

To read mail in the browser, use the Webmail button. The mailbox also works in Outlook, Thunderbird and the mail apps on Android and iPhone. Always use the full email address as the user name:

The server name (host) is shown in the mailbox's Mail client setup, along with step-by-step guides for Outlook, Thunderbird, Android and iPhone; Email these settings to sends them to someone (the password is never sent). Thunderbird often finds the settings by itself.

Sending limits#

• How many messages may be sent each hour and each day depends on your plan. The limit is for the whole account and counts every recipient.
• A message, attachments included, is at most 25 MB.
• Every message is checked for spam before it goes out.
• If more than 10% of at least 100 messages in an hour bounce, the account's sending pauses for 30 minutes by itself, to protect your domain's reputation.

Following your mail (Messages)#

The Messages page shows every message sent and received by your account and its state — Delivered, Deferred (held up for now, it will be tried again), Bounced, Failed and so on. Click a message to see the receiving server's answer (DSN code), the last error and every step it went through. Send test sends a test message. The record of each message is kept for 90 days.

Sending mail from your app by API#

To send welcome mail, receipts or password resets from your website or app, use the API. First create a key with the SendMail scope on the API keys page (see Account and team), then:

curl https://api.example.com/api/v1/messages \
  -H "X-Api-Key: mpk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "from": "info@shop.com.bd",
    "fromName": "Shop",
    "to": "customer@example.com",
    "subject": "Your order is confirmed",
    "html": "<p>Thank you! Your order number is <b>1042</b>.</p>"
  }'

Put Meghly's API address in place of api.example.com. On success the API answers 202 and the message is queued; its state shows on the Messages page.

• Templates: instead of html, give templateSlug and variables to build the message from a template on the Templates page. Templates may use variables such as {{ firstName }}; the Templates page edits, previews and saves them.
• Other fields: cc, bcc, replyTo, tags, attachments, and sendAt to send at a set time.
• Never the same message twice: send an Idempotency-Key header; a repeated request with the same key sends nothing new.

When something goes wrong#