Changelog
What's changed in the engine.
This lists changes to the engine behind MagpieCRM and the APIs, newest first. Each one links to its release of the open-source app on GitHub.
- Latest
- v0.9.110, 31 October 2026
- Covers
- Verification, finding, search, sending, MCP and hosting
- Source
- MagpieCRM's releases on GitHub
- Licence
- AGPL-3.0
SpecAll releases
Releases
Newest first.
Only the engine's changes are here. Every release, including changes to the CRM itself, is on GitHub.
October 2026
Verified people search checks each company's mail domain before showing its people
- Each batch is tested against the company's mail server before anyone in it is shown or charged for
- People hidden by those tests don't fill the page and don't use a credit
- Opt-outs and contacts you already have are left out, as in every other search
- Searching again doesn't show you the same people
Verified people search
- On hosted copies, a people search by job title can be answered by a search that checks each person against their live profile: title, location and employer
- People show as they're checked: slower than before, but every person is confirmed
- Revealing and saving people, and finding their emails, work as before
Email guesses in the order the data supports
- A person's six checks cover the likely formats and spellings together, such as both halves of a double-barrelled surname, and umlauts written out
- At companies of 50 people or fewer on their own domain, first@ is tried first
- Website-builder and link-in-bio hosts are never taken for a company's mail domain
- A learned format loses confidence only when a second person is rejected under it
Search tests each new mail domain before showing the people there
- People at a domain that takes no email, or accepts every address, are hidden before a credit is spent on them
- The checks are the ones a first email lookup there would make, and are kept for it
- Half of each minute's and each day's verification allowance is left for finding emails
Search uses the shared database of business contacts
- People the shared database already holds need no new profile lookup, and their verified email comes from it
- Used only when the profile names the same employer, or the email was verified in the last 90 days
- Anyone else is looked up as before
A reputation score out of 100 for each sending domain
- Worked out per sending domain and kind of mail, from the last 7 days
- 100, less the points the weakest signal takes off: hard bounces, spam complaints, unsubscribes or real opens
- 80 and over is good, 50 to 79 at risk, under 50 poor
- Shown beside each domain and each daily limit in Settings, Sending
Daily sending limits that follow reputation
- Cold email starts at 30 a day and can grow to 300 over six weeks
- Opt-in email starts at 200 a day and reaches the plan's allowance after five weeks
- A limit steps up after a good week, holds when at risk or with too little sent to judge, and steps down when poor
- A campaign over the day's limit sends that day's share and carries on the next day
MCP: draft and run email sequences
- New tools to create, update and preview sequences, see who a list would add, and enrol people
- Starting a sequence and enrolling people send email, so both ask you first
- A sequence can be named instead of given by its id
September 2026
Bounces, complaints and unsubscribes handled the same way for every provider
- A soft bounce, such as a full mailbox, counts only against that email; only a hard bounce stops email to the contact
- A send refused because the mailbox doesn't exist counts as a hard bounce
- Unsubscribes, complaints and hard bounces are remembered as a keyed hash, so a contact deleted and imported again stays unsubscribed
Email checks paced to each hosted copy's share
- Each hosted copy paces its checks to its share of our verification servers, per mail provider
- Checks over the pace wait their turn instead of ending early as unanswered
Catch-all checks confirmed twice, and formats learned from each company
- A company is marked catch-all only when a second made-up address, in a separate session, is accepted too
- Verdicts last 30 days unconfirmed, 90 days confirmed and 180 days behind a mail security gateway
- Addresses already known at a company decide which format is checked first
- Hosted copies share format counts per company domain, never names or addresses
- Campaigns send unconfirmed guesses in a first batch of 50, and the rest an hour later only if 2% or fewer bounced
MCP: the email and survey builder tools
- AI apps connected over MCP get the copilot's builder tools by the same names, such as applyTemplate, addBlock and previewEmail
- Each works on a campaign, saved template or survey by its id; sent campaigns are read-only
One-click unsubscribe, and opt-outs respected at import and send
- Campaign emails carry List-Unsubscribe and List-Unsubscribe-Post headers (RFC 8058)
- Always on when we run your sending
- Contacts on the opt-out list are skipped at import, and campaigns skip them unless they've signed up again since
Opt-outs shared between hosted copies
- Opt-outs pass between copies as keyed hashes, not addresses
- An opt-out from another copy removes matching saved contacts, as one made in your own copy would
Managed sending from your own domain
- Add the domain you send from, then put its DKIM records, an ownership TXT record and a recommended DMARC record in DNS
- Email only goes out from a domain once both its DKIM records and its ownership record check out
- Spam complaints unsubscribe the contact straight away, and hard bounces mark them bounced
FAQ
Questions, answered.
Why are some releases missing?
This page lists only changes to the engine: verification, finding, search, sending, MCP and hosting. Every release of MagpieCRM, including changes to the CRM itself, is on GitHub.
Do the APIs have versions of their own?
Not yet. The APIs are in early access, so what's listed here are changes to the engine they'll run on, which MagpieCRM uses today.
Keep exploring
Related
Build on the engine behind MagpieCRM.
The APIs are in early access. Tell us what you'd use them for, and we'll write when your key is ready.