oto.cx
mailpool

mailpool

mailpool.

Mailpool domains: read them, audit their deliverability setup, look up a new name.

ajouter à otoauth : —prefix : mailpool_*

setup & usage

⚠ mailpool api key

a Mailpool workspace member creates a key in Mailpool → Settings → API Keys, then pastes it into oto. The key is shown once.

  • byo-only: no shared oto key — these are your own sending domains and mailboxes
  • the "test connection" button reads the subscription slots: no domain or mailbox data is touched
    • ▸ is my sending setup healthy, and fix it
  • "audit my domains" → mailpool_domains(op="audit"): SPF, DKIM, DMARC, MX, CNAME conflicts and tracking domain per domain, worst first, 20 domains per call (next_offset for the rest)
  • "show the DNS of this domain" → mailpool_domains(op="list") to find its id, then mailpool_domains(op="dns", domain_id=…)
  • "switch SPF to -all and send DMARC reports to dmarc@…" → mailpool_domain_fix(domain_id=…, spf_hard_fail=True, dmarc_report_email="dmarc@…") returns the diff; re-call with dry_run=False to apply
  • "add the lemlist tracking domain" → mailpool_domain_fix(domain_id=…, tracking_host="track", tracking_target="custom.lemlist.com", dry_run=False), then set track.<domain> as custom tracking domain in lemlist; if lemlist then asks for a verification TXT, add it with add_records=[{"type": "TXT", "key": null, "value": "…"}]
  • "are my inboxes landing well?" → mailpool_spam_checks(op="run", mailbox_id=…): score and per-check status in a few seconds, free
  • "which mailboxes do we have?" → mailpool_mailboxes(op="list"), optionally domain_id=…
  • "is this domain name free?" → mailpool_domains(op="availability", domain="…") or op="suggestions"
  • "do we have room for more inboxes?" → mailpool_account(op="slots")
    • · what is misleading
  • ⚠️ a DNS write replaces the whole record set in Mailpool: mailpool_domain_fix always sends the full set, reads it back and restores the previous one if anything went missing. Never hand-build a partial list
  • a change that would break the domain is refused, preview included: a second SPF or _dmarc, MX, SPF or DKIM gone, a CNAME next to other records. add_records only ADDS: to change SPF, use spf_hard_fail, or remove the old record and add the new one in the same call
  • after dry_run=False, an error with reason dns_outcome_unknown, dns_not_kept or partially_applied means the records may have changed: re-read them with op="dns" before calling again
  • a domain without `_dmarc` gets one with p=quarantine; sp=quarantine; pct=100 when a report address is set: say so to the user
  • DMARC is published from Mailpool's DMARC setting: changing the report address also writes it as ruf (forensic reports) — Mailpool does not allow removing it
  • the audit reads Mailpool's stored configuration, not public DNS: right after a fix, public DNS follows within ~5 minutes
  • DMARC reports sent to another domain (e.g. your main domain) are only delivered if that domain publishes <sending-domain>._report._dmarc.<main-domain> (or a *._report._dmarc wildcard) as TXT v=DMARC1 — a change in the main domain's DNS, outside Mailpool. The audit flags it
  • a tracking CNAME alone does nothing: the sending tool must also be told to use it
  • -all only once every service sending as the domain is in SPF (Google Workspace, Microsoft 365 or Mailpool's relay — a sending tool connected through them needs nothing more)
  • some lookups are enabled per Mailpool workspace (Google Workspace / Microsoft 365 checks): refused otherwise
  • a spam check is refused (404) for some mailbox types
  • changing the DMARC policy or the web redirect is not served yet: Mailpool's settings calls for them are not verified live (a later report-address change may republish the stored policy). Do it in Mailpool, then run op="audit"
  • lemwarm or another warmup paused on a Microsoft 365 domain because "external forwarding is not allowed" is a tenant setting (Microsoft Defender → anti-spam outbound policy → automatic forwarding), not DNS
    • · credentials and scope
  • mailbox credentials are never returned (mailbox, IMAP/SMTP, admin passwords): they stay in the Mailpool dashboard. Handing inboxes to a sending tool is done from Mailpool's own export
  • registrant owners are served as company and country only: names, emails, addresses and phones stay in Mailpool
  • nothing billed is served: registering, transferring or renewing a domain, creating a mailbox, buying slots, enrolling in warmup and inbox-placement tests are done in Mailpool
    • ⚙ multiple comptes

    this connector accepts multiple comptes: each stored credential becomes a named account (one name per compte), at your level, your team's or your org's.

  • the first one doesn't need a name; from the second on, each one carries its own (the first then takes the name "principal", renamable)
  • without specification, the agent takes the only stored compte, otherwise the one marked as default; otherwise the call is refused, naming the available comptes — never a random choice
  • target a compte for a call: _account="<name>" on the tool; list them: oto_identity(op='list', connector='mailpool') (scope='org' or scope='group' for the org's or team's)
  • set the default: oto_identity(op='set', connector='mailpool', identity_id='<name>'); rename: op='rename' with new_name
  • ⚠️ no tool walks through the comptes on its own: a total across several comptes is obtained by calling each one (_account) and adding up

    • outils

    chargement…

    utilisation

    claude code — installe le plugin oto — claude plugin marketplace add otomata-tech/oto-plugin — mcp + skill configurés.
    claude.ai — branche mcp.oto.cx/mcp en connecteur custom (guide)
    cli — pipx install oto-cli puis oto mailpool …
    ← tous les connecteurscatalogue mcp →