Limits that keep Magpie safe

Magpie sends emails for you, such as team invitations, invoices, proposals, signature requests and calendar invitations, and those emails carry your name, your team's name and what you wrote. These limits stop anyone using Magpie to send spam or phishing under its name.

How much Magpie trusts an account

• Paying: your Personal plan, or a team you own, is on a paid plan.
• Established: the account is more than 7 days old and has been used on at least 3 different days.
• New: any other account. That includes an old account that was never used until now, because spammers often sign up accounts and come back to them later.

Using Magpie on more days, or paying, moves an account up straight away.

Invitations a day

One person can send this many team invitations a day, to members and guests together, by handle or by email address:

• Paying: 200
• Established: 50
• New: 15

Sending an invitation again, with Resend or by sharing with the same person again, counts too. Links to join a team are not counted, because they are not emailed. At the limit, Magpie says to try again tomorrow.

People you can email a day

Magpie emails this many people a day for one account, counted together across invoices, proposals, signature requests, shares, calendar and meeting invitations, gift cards, purchase orders and every other email you send to people by typing or choosing their address:

• Paying: 1,000
• Established: 200
• New: 20

A day is the last 24 hours. An email to your own address is not counted. Payment reminders, recurring invoices and the invoice a Store order sends are not counted either. A Newsletter post, an Outreach campaign and imported webinar or course attendees are counted only for a new account, because those areas have their own limits. At the limit, Magpie says how many more people you can email today, or to try again tomorrow.

Before Magpie emails anyone else for you, your account's email address must be confirmed.

Web addresses in emails

A new account cannot put a web address in an email Magpie sends to other people, such as an invoice's message or a proposal's note. Magpie asks you to remove it. Once the account is established or paying, web addresses are fine.

Nobody can send a short link (such as bit.ly/…) or a link that forwards somewhere else (such as calendar.app.google/… or a Google redirect), because the person reading it cannot see where it goes. Magpie asks you to use the page's full address instead.

An account that tries to email a link made to look like another company's, such as poshmark.example-security.com or paypal-secure-login.com, is turned off at once, whatever its standing, and nothing is sent.

Email that goes out from your own domain (Mail, Outreach, and a Helpdesk inbox connected to a Mail mailbox) can include web addresses and short links from the first day, and is counted towards the people a day only for a new account. A link made to look like another company's is still refused in Outreach and Helpdesk.

Web addresses in names

Your name and your teams' names cannot include a web address, such as https://…, www.… or a link like example.com/page. A plain domain on its own, such as Acme.io, is fine.

• An established or paying account that types a web address into a name is asked to enter the name without it.
• A new account that does it is turned off at once.
• Anyone who sends an invitation while their name or the team's name has a web address in it is turned off at once, and the invitation is not sent.

When an account is turned off

A turned-off account is signed out on the website, in the app and in the browser extension, and its API keys and Git access stop working. Invitations it sent and nobody has answered are withdrawn, so their links no longer work. Payment reminders, recurring invoices, scheduled emails and campaigns stop sending. Everything in the account is kept.

If your account was turned off by mistake, we will turn it back on: contact support.