When sending stops itself

A newsletter that keeps mailing after people mark it as spam hurts the readers and the domain. Geenius Newsletter is built to stop and wait.

Two lines, and a minimum#

A send does not pause itself on the first few mails. The check waits until at least 50 mails are in the count (what was sent, plus hard bounces). After that, either of these pauses it:

• Complaints above 0.1 % of what was sent.
• Hard bounces above 2 % of that count.

A hard bounce, a complaint, or three soft bounces suppress the address. A suppressed address is not mailed again, and it is not imported again.

You decide whether to go on#

A paused send waits. Look at the list, then resume or leave it. The numbers on the send are what was sent, hard bounces and complaints. Opens and clicks are not counted. Counting them is not available.

A stopped workspace#

A workspace can also be stopped outright. While it is stopped, nothing new can be scheduled, and a send that is already going stops. The send screen shows the reason.

Why it waits for 50 mails#

A rate on five mails says little: one complaint out of five would be 20 % and stop a send that is fine. So the check waits for a count that means something, then compares. The same numbers are on the send screen while it runs, so you can see how close a send is to the line, and on the publication for the last 30 sends.

If a send pauses, nothing is lost. The readers who already got the mail keep it, the ones still waiting are not mailed, and the send keeps its place. Resuming is a person's decision in the web app; your own AI can pause or cancel a send through the door, but it cannot resume one.

Where it stands#

The pause is built. Newsletter is in early access, and sending to real inboxes is not switched on yet: sends run in test mode, so no mail leaves the app. The steps are in When a send pauses.