Your project emails its users: your replies in the Inbox, and its own emails about your portal. To keep email from Tuti reaching inboxes, a new project sends a limited number of emails a day, and a project whose emails bounce or are marked as spam too often is paused. This is what happens then, and what still goes.
What your project emails
From | |
|---|---|
Your replies in the Inbox | Your support address, or your own address once it's verified, with the teammate's name |
Portal sign-in links, password resets, and emails saying you gave someone access to a private portal |
|
Emails about posts: when one ships, and your replies to voters | The same |
Changelog emails to subscribers | The same |
When people answer one of your replies by email, their answer joins the same conversation. The updates@ emails come from your project's name, and while Messages in the widget is on, answers to them go to your support address and land in the Inbox. See Set up support email.
Your first week: up to 200 emails a day
For its first 7 days, a project sends up to 200 emails a day to its users. The day starts at midnight UTC. Your replies, emails about posts and changelog emails all count. Sign-in links and password resets don't, and always go.
Past the limit, the rest wait for the next day. A reply that's waiting says under it: "Emailed tomorrow: in its first week, a project sends up to 200 emails a day". People who have the widget open still see your replies there.
When your project's email is paused
Tuti pauses a project's email to its users when too much of it bounces or is reported as spam over the last two weeks:
more than 1.5% of its emails bounced, once it has sent 100, or
5 people marked its emails as spam, or 3 when that's more than 0.03% of what it sent.
Settings → Inbox and email then says why, under Email:
Owners and admins also get an email saying why. If you know what happened, reply to it: your answer comes to us.
While it's paused:
Your replies still reach people in the widget. Under each one, the Inbox says "Not emailed while your project's email is paused (Settings → Inbox and email)".
Emails about posts and changelog emails wait, and changelog sign-up confirmations aren't sent.
Sign-in links and password resets still go, so people can sign in.
We look into each pause, and resume your email once it's safe to. Then your waiting replies and changelog emails go out, however long the pause was. Emails about posts are different: only those that became due in the 24 hours before your email is back on go out. Older ones (a post that shipped, or a reply to voters, more than a day before) are never sent, so after a long pause, tell those people another way if it matters.
Bounces and spam reports on your replies
Each reply you send by email shows how it went (see Reply to a conversation):
The email bounced, with the reason from their mail server. Later replies still go to the same address, so if it keeps bouncing, reach them another way. Bounces count toward a pause.
They marked the email as spam: replies reach them only in the widget now. From then on, your replies to that address aren't emailed. They still see them in the widget.
Keep your email healthy
Reply from an address people recognise: set up your own address.
Mark junk conversations as spam rather than answering them: replies in spam conversations are never emailed.