Skip to main content
Connect SMTP2GO and the agent answers “the copier stopped emailing” and “why did this email bounce” from SMTP2GO’s own delivery records, and fixes the common causes after a technician approves. You need an SMTP2GO account on a paid plan with one subaccount per customer. The agent works per subaccount: on a customer’s ticket it reads and changes only that customer’s subaccount.

How to connect

1

Create an API key on the master account

Sign in to SMTP2GO with the master account, the one that owns the customer subaccounts, not a subaccount. Open Sending → API Keys and click Add API Key. Give it a description such as Rallied.
2

Set the key's permissions

Open the Permissions tab of the new key and enable these endpoints:If you want the agent to make changes after a technician approves them, also enable /users/smtp/add, /users/smtp/edit, /users/smtp/remove, /suppression/remove, /domain/add, /domain/verify, /single_sender_emails/add, /single_sender_emails/remove and /subaccount/edit. Leave /email/send and every /api_keys/* endpoint off: the agent never sends email and never manages keys.
3

Copy the key and note your region

Click Add API Key and copy the key. It starts with api-. Note the region your account is hosted in: it shows in the address bar when you are signed in (app-us, app-eu or app-au).
4

Connect SMTP2GO in Rallied

In Rallied, go to Settings → Integrations, find the SMTP2GO card and click Connect. Pick your Data region (or leave Automatic, which uses SMTP2GO’s global endpoint api.smtp2go.com) and paste the key into API key. Click Connect.
5

Confirm

Rallied checks the key’s permissions and lists the endpoints that are missing, if any. When the key is accepted, Rallied syncs your subaccounts and the card shows Connected.
Rallied refuses a key that lacks any of the read endpoints above and names the missing ones. The change endpoints are optional: without them, the agent’s read tools work and a change tool reports which endpoint to enable.

Mapping subaccounts to Rallied clients

When you connect, Rallied syncs your active SMTP2GO subaccounts and suggests a Rallied client for each one. Rallied skips closed and suspended subaccounts. An MSP admin confirms the suggestions in Match companies. The Companies tab of the integration’s page lists the synced subaccounts with their IDs; click Sync subaccounts to pick up subaccounts you’ve created since. On a client’s ticket, the agent reads only that client’s subaccount. It fills in the subaccount ID automatically, and SMTP2GO itself refuses a subaccount that doesn’t belong to your account.
A customer that sends through your master account rather than a subaccount is not covered: SMTP2GO offers no per-customer boundary there. Create a subaccount for that customer in SMTP2GO (Settings → Subaccounts, and migrate its SMTP users with Migrate), then click Sync subaccounts.
Only the MSP admin Chat can list every subaccount with its usage, or read your master account’s plan usage. Use it for questions such as “which customers are close to their monthly limit?”

How the agent uses it

On a ticket such as “the scanner stopped sending emails” or “our emails to Acme bounce”, the agent typically:
  1. Searches the customer’s delivery activity for the sender, recipient or SMTP login named in the ticket. Each event says whether SMTP2GO delivered the email, whether it bounced or was rejected, and what the receiving server answered.
  2. Checks the SMTP login the device uses: whether it’s allowed or blocked, and its rate limit. Passwords are never returned.
  3. Checks the sender domain’s DKIM and return-path verification and the exact DNS records SMTP2GO expects, or whether the sender address is verified.
  4. Checks the suppression list when one recipient never receives anything: a hard bounce or a spam complaint suppresses the address automatically.
  5. Reads the subaccount’s monthly email and SMS usage when sending stopped at the limit, or when you ask for a usage audit.
It writes what it found on the ticket as an internal note, quoting the server responses it read. Email bodies are never available to the agent: activity events carry senders, recipients, subjects and server responses only.

Changes the agent can propose

Every change needs a technician’s approval, requested where your technicians already work (see Approval settings):
  • Create an SMTP login for a new device, or delete a retired one. The password of a new login is generated and held by Rallied, like a reset.
  • Block or unblock an SMTP login, or change its sending rate limit.
  • Reset an SMTP login’s password. The agent generates the password and Rallied holds it; the agent only ever handles a reference to it, never the value. After approval, Rallied sets it in SMTP2GO and the technician receives it through your credential-delivery integration or an internal note. Every device using that login must be reconfigured, and SMTP2GO takes about a minute to accept the new password.
  • Release a suppressed address or domain.
  • Re-check a sender domain’s DNS right away, after the customer fixed it.
  • Register a sender domain. The agent returns the DNS records the customer must add; SMTP2GO verifies them within minutes.
  • Register or remove a sender address. SMTP2GO emails a verification link to a new address; nothing sends from it until the link is clicked.
  • Change a subaccount’s monthly email limit. SMTP2GO accepts only its own steps (2,000, 5,000, 10,000, 20,000 and so on) and nothing above what your plan allows.
A customer’s sending counts against your SMTP2GO plan. Raising a subaccount’s limit can raise your bill.

Tools

Reads default to Auto; changes default to Approval needed. To change a default, open the Policies tab on Settings → Integrations → SMTP2GO. See Approval settings.

See also