Cơ sở kiến thức GetMyBot

Email from your own domain

Send email from your company address: check your plan, verify your domain, and add DKIM, SPF, and DMARC records. Delivery, replies, and unsubscribes.

Trên trang này

Sending availability. If no platform email provider is configured in your region, campaigns and automated emails are disabled even when you connect your own SMTP. Custom SMTP can still be used for unread widget reply copies when the other requirements are met. Contact support to check availability.

Your bot can send from your company address, such as noreply@example.com. Verify the domain and configure DNS for the selected sending server. GetMyBot shows the DKIM and DMARC values; SPF depends on the server.

Choose a sending server

You can select the GetMyBot server or configure your own SMTP server. Delivery availability depends on the email provider configured in your region. To use your own public SMTP service, open Email → Sending domains → Email sending server and enter host, port, encryption, username, password and an authorised return address. STARTTLS commonly uses port 587 and TLS 465; check the provider’s instructions. Unencrypted connections are not supported.

Check and save tests the connection and authentication without sending a message. Passwords are never returned. Leave the password blank to keep it when editing; changing host, port, encryption or username requires it again. Choose Use GetMyBot to select the platform server; this does not guarantee that one is configured in your region. Switching modes resets domain verification: review DNS and verify again.

When marketing delivery is available in your region, this setting applies to campaigns and automated email. The company mailbox for support replies is configured separately; custom SMTP does not configure inbound email.

For example, info@gogol.school can be the visible From address configured for the sending domain. The SMTP return address (envelope_from) is separate and must be authorised by the selected provider. Your custom SMTP login may also differ from the visible address if the provider permits it. Choosing GetMyBot does not connect a personal info@gogol.school SMTP login.

Sending setup does not require changing MX records or move inbound mail. Existing MX records and your mail service continue to handle inbound mail. Configure a supported support mailbox separately if you need replies in GetMyBot.

First, the plan

Email is a paid bot-builder capability. It is in the Pro, Business and Enterprise plans; the free Start plan does not have it, and no Customer Engagement plan grants it. See Plans.

Check your plan before changing domain settings. On a plan without email, the whole section is closed: you cannot add a sending domain, and requests return 402. Adding SPF, DKIM, and DMARC before changing plans will not start email delivery.

Why the DNS records are needed

Consider the receiving side: Gmail, another mail service, or your customer's mail server. It sees a message claiming to come from your domain, but sent by a different server. That can look like a forged message.

The receiver checks your domain's DNS records to see whether that server is authorized. You publish these records in the DNS settings you control.

Without those records, the receiving server has less evidence that the sender is legitimate. Depending on its rules, it may put the email in spam or reject it. Verification is required to send through GetMyBot, but does not guarantee that every email reaches the inbox.

The three records below show that you permit GetMyBot to send from your domain.

The three records and what each one does

DKIM: a signature proving the message is genuine

DKIM is a cryptographic signature added to every outgoing message. The platform generates a key pair for your domain: the private half stays with us and signs your mail, the public half you publish in DNS. The receiver takes the public key from your DNS and checks the signature. If it matches, the message was sent by whoever holds the private key and its contents were not altered in transit.

Without DKIM, the recipient cannot verify GetMyBot's signature. That increases the risk of rejection or spam placement. GetMyBot requires DKIM, along with the other two records, to verify the domain.

SPF: which servers may send on your behalf

SPF lists authorised sending servers. For GetMyBot, the record must directly include include:esp.getmybot.dev. For custom SMTP, follow your provider’s SPF instructions.

DMARC: what a receiver should do when the checks fail

DKIM and SPF answer "is this message genuine". DMARC answers the next question: what to do if it is not. It is your instruction to the receiver: do nothing and just report, put it in spam, or reject it. DMARC is also the address receivers send aggregate reports to, including reports of other people forging your domain.

Start with the mildest policy, "report only". Tighten it later, once you are sure every legitimate sender of yours (accounting, CRM, newsletters, this bot) passes the checks. A strict policy switched on too early starts eating your own mail.

Without DMARC, your domain has no published policy for mail that fails the checks. GetMyBot requires the record to verify the domain.

Which records to add

First add the domain in the dashboard: the Email section → "Sending domains" → the "Add domain" button. The dialog has three fields: the domain itself (shop.example.com, say), the local part of the address (what goes before @, usually noreply) and the sender name the recipient sees instead of an address. Your DNS records appear on screen once you save.

Both halves of the address are validated on save, and the rules are stricter than mail in general:

  • The domain is lowercased and must be a fully qualified name of at least two labels (example.com, mail.example.com), no longer than 253 characters. Each label may contain Latin letters, digits and hyphens, and must begin and end with a letter or digit: -mail.example.com and mail-.example.com are refused. Write internationalised domains in punycode (xn--…).
  • The local part is lowercased, is at most 64 characters, may contain Latin letters, digits and ., _, +, -, and must begin and end with a letter or digit. So noreply, no-reply and news.2026 are fine, while noreply-, .noreply and no..reply- are not (the last character is neither a letter nor a digit).
  • Line breaks and other control characters are refused in both fields. They could otherwise inject extra headers into a message: one that is signed with your domain's key, that is, in your name.

An address that fails these rules is refused with 400 when the domain is saved, before anything is ever sent. Inbound addresses follow slightly different rules, described in Email campaigns.

All three are TXT records in your domain's DNS. You add them wherever you manage the domain: your registrar's control panel or your DNS provider.

The values below use example.com as an example. Copy the exact values from your domain card in GetMyBot, especially DKIM: it contains the public key for your domain.

Copy the displayed Host and Value fields separately. For custom SMTP the screen does not propose an SPF value: follow your provider’s instructions.

TypeRecord name (host)Value
TXTmybot._domainkey.example.comv=DKIM1; k=rsa; p= followed by the long key from the dashboard
TXTexample.com (the root of the domain)GetMyBot: v=spf1 include:esp.getmybot.dev ~all. For custom SMTP, follow the provider’s instructions.
TXT_dmarc.example.comv=DMARC1; p=none; rua=mailto:dmarc@example.com

Two things people trip over most often:

  • Many control panels append the domain to the record name for you. If the name field already shows ".example.com", enter only mybot._domainkey and not the full name, otherwise you end up with mybot._domainkey.example.com.example.com.
  • The DKIM value is long and must contain no line breaks or spaces inside the key. Copy it with the button rather than by dragging a selection.

If the domain already has an SPF record

If two SPF records already exist, do not add a third. Ask your DNS administrator to combine the rules into one while preserving all existing authorised senders.

The example below applies to GetMyBot. For custom SMTP, coordinate changes with the provider.

A domain may have only one SPF record. If you already send mail through your hosting, a CRM or another newsletter service, you already have one. Do not add a second: add another include to the existing record, before the trailing ~all:

v=spf1 include:spf.yourprovider.com include:esp.getmybot.dev ~all

Two SPF records on a domain is the same failure as none: the check does not pass, because the receiver has no way to know which of the two to believe.

Note that being "covered" through someone else's record is not enough. Even if your current provider includes us in their own SPF, our include has to sit in your record directly: see the verification section below for why.

Why GetMyBot SPF uses an include and not an IP address

The most common mistake is pasting an IP address spotted in a message header or someone's forum post. Do not do that.

include:esp.getmybot.dev is a pointer to our own, maintained list of sending servers. Today that name resolves to a single relay. Tomorrow there may be more of them, they may move, they may be replaced. When that happens we update the list on our side and your record keeps working with nothing for you to change. That is the entire point: the address changes in one place instead of in every customer's DNS.

A hand-written IP address simply stops being true at that moment. Mail starts failing SPF with no warning at all: no error in the dashboard, no notification. You find out from customers who "never received anything".

Write exactly include:esp.getmybot.dev and add nothing to it.

Domain verification

Domain verification is the platform looking into your domain's DNS itself and confirming that all three records are in place. If all three pass, the domain becomes verified and sending is allowed. While any of them fails, the domain stays pending.

Checks depend on the record and the selected server:

RecordWhat is actually checked
DKIMThe record is published and contains your own public key. Someone else's DKIM record, or a stale one from a previous key, does not pass.
SPFFor GetMyBot, the record directly contains include:esp.getmybot.dev. For custom SMTP, only the presence of SPF is checked; confirm with the provider that it authorises the selected server.
DMARCA record is published and starts with v=DMARC1. The policy itself (p=, rua=) is not checked: that is your decision, not an authorisation for us.

A custom SMTP SPF presence check does not prove the selected server is authorised. Domain verification does not guarantee inbox delivery.

Someone else's include does not count for GetMyBot

include:esp.getmybot.dev has to be in your own SPF record. If your SPF includes a third-party provider whose record in turn includes us, verification will not accept that: the platform does not resolve chains of other people's includes. The reason is simple: it keeps the answer to "did this specific domain authorise us" unambiguous.

In practice: even if you are confident you are "covered through your provider", add our include directly to your own record. The screen says the same thing in its SPF explainer: if the domain already has an SPF record, add the include:... value to it rather than replacing the record wholesale, because the domain may send mail through others too. That note is always on screen, not something that appears only after a failed check.

DNS does not update instantly. After you save the records, they must reach other DNS servers. This usually takes minutes, sometimes hours, and occasionally up to a day. Timing depends on your provider and how long servers cache the records (TTL).

You do not have to wait passively, though. The platform re-checks pending domains once an hour on its own, but the domain card also has a "Verify now" button: the very same check, run immediately, with the result on screen straight away. Use it right after saving the records: if there is a typo, you find out in a second rather than in an hour. You can run it as often as you like.

The domain's status is shown on the card: "Pending verification", "Verified" or "Not verified". While it is unverified, the card also carries the warning "Sending from this domain is disabled until it is verified."

The result is not just "failed". Each of the three records has its own status on screen: "Passing", "Not passing" or "Not checked yet": and its own line explaining what is wrong.

For the GetMyBot server, the SPF check distinguishes two situations:

For custom SMTP, follow your provider’s SPF instructions. The check only establishes that an SPF record exists.

  • The domain has no SPF record at all. Publish one, using the value from the table above.
  • An SPF record exists but does not contain our include. Add the include to the existing record: do not create a second one and do not replace it wholesale. The same message also covers the chained case explicitly: if the include only reaches us through another provider's SPF record, that does not count: chains are not resolved.

The second case is the single most confusing moment in this flow: the record is already there, you have just re-read it yourself, and verification still refuses. The error message now says exactly what the always-visible hint next to the record says: add our include to what you already have.

If verification does not pass:

  1. Read which of the three records is marked "Not passing" and what its explanation says, then act on it.
  2. Make sure the records really are published: many panels need a separate "apply changes" click.
  3. Check the record name for a doubled domain (see above).
  4. Check that there is only one SPF record. For GetMyBot, check the direct include; for custom SMTP, follow the provider’s instructions.
  5. Wait a bit and check again: the change may simply not have propagated yet.

Sending refuses to work until the domain is verified

Until the domain is verified, email is not sent. The attempt fails with an unverified-domain error visible in the log.

This protects the platform's shared sending infrastructure. Email from an unverified domain may lead to spam complaints and damage its reputation. Sending is therefore blocked until verification rather than merely showing a warning.

If you see the error, check the DNS records and run verification again. A typo in a record name is a common cause.

Unsubscribes, complaints and bounces

Three rules apply when sending email.

Every marketing email includes one-click unsubscribe. GetMyBot adds an unsubscribe link to the email footer and headers that a mail client can use to show an "Unsubscribe" button beside the sender. You cannot remove it in settings or by editing the email. Unsubscribing takes effect without an extra confirmation step. Omitting this feature would hurt the deliverability of bulk email.

An unsubscribe cannot be undone from the interface. An unsubscribed address receives no more email from this bot. Re-importing a list does not override the person's choice. They can opt in again themselves through your subscription form.

If the service receives a spam complaint from the provider, the address is permanently suppressed. Not every SMTP provider sends complaint events automatically.

A permanent bounce received by the service excludes the address. If SMTP accepts a message and later delivery fails, GetMyBot only learns about it when the relevant provider event is connected.

Soft bounces (a full mailbox, a server that is temporarily down) do not suppress the address: sending to it continues.

Why the open count is imprecise

Email statistics include an open count, but it is not the number of people who read the email. The measurement method has limits.

An open is recorded when a mail client loads a tiny tracking image. Some clients block external images, so an actual open is missed. Others, including Apple Mail with privacy protection, may load the image before the person opens the email, so an open can be counted that never happened. The image cannot tell GetMyBot whether the person read the message.

The open count can therefore be too low or too high. Do not treat it as the exact number of readers, and use care when comparing campaigns: their audiences' mail apps may handle images differently.

To gauge interest, look at "Link clicks". Delivery, complaint and bounce information depends on events from the provider and the configured integration. SMTP acceptance does not prove inbox delivery. Statistics are on the Email screen.

What's next

  • Channels: multichannel bots and channel capabilities.
  • Broadcasts: sending to many people at once.
  • Analytics: where to find the numbers.