Stage 8 of 12
Acceptable Use and Abuse Prevention for an Email Service Provider
On shared IPs one bad sender hurts every customer. This guide covers how an ESP on Octeth vets signups, uses trust levels, ramps new accounts, screens list imports, sets bounce and complaint limits, suppresses complaints and suspends abusive accounts. Set it up before you take the first payment.
By Cem Hurturk, founder of Octeth Updated 12 min read
- Account review and sender screening
On this page
Abuse prevention decides who may send, how much, and what happens when they break your rules. On shared IPs, one sender’s bad list hurts every customer’s inbox placement. Your acceptable use policy from stage 2 sets the rules. This stage builds the controls that enforce them.
Vet accounts before you take payment
This stage comes before billing for a reason. Once paid signups open, a sender you would refuse can pay, send and dispute the charge.
Disputes cost more than the refund. Stripe says the card industry treats dispute activity above 0.75% as excessive, and that card networks can place a business with high dispute activity in a monitoring program, with extra monthly fines and fees (Stripe: measuring disputes, disputes analytics). A new ESP has few payments, so a handful of disputes moves that rate. Stage 9, Stripe billing, covers the account setup. Have review, holds and suspension working before it.
Gate every new signup
Treat a new signup as unknown until staff review it. On Octeth that takes four settings and one routine.
- Signups start Untrusted. From 6.0.1, new accounts get the reputation in the
USER_SIGNUP_REPUTATIONsetting, Untrusted by default. Keep it. - The gateway requires Trusted. With
EMAILGATEWAY_REQUIRE_TRUSTEDon, the default from 6.0.1, Octeth refuses gateway API, journey and SMTP relay sends from accounts that are not Trusted. The SMTP relay requires Trusted even with the setting off. - One gate, not two. Leave phone verification for gateway sends off, the install default, so the Trusted gate is the only approval gate.
- Staff hear about signups. Octeth sends a
user.signed_upevent to the operator webhook (staff area, Webhooks). Route it to a workflow that alerts staff, so each new account reaches a person. A campaign from an Untrusted account waits in Pending Approval, and Octeth emails the administrator.
The two install settings, in .oempro_env:
EMAILGATEWAY_REQUIRE_TRUSTED=true
PHONE_VERIFICATION_REQUIRED_TO_SEND_EG_EMAILS=false
Then review every new account and mark it Trusted in the staff area, or decline it.
The signup itself also confirms the email address with an emailed link, so the app’s mail must work before you open signups. Stage 4, installing Octeth, covers it. If you turn on Google sign-in (6.0.7), accounts created through it go through the same signup path and also start Untrusted.
What Octeth screens at signup
From 6.0.2, Octeth scores every new account with local checks and stores the result for staff. The signals it reads:
| Signal | What it flags |
|---|---|
| Disposable mailbox | The signup address uses a throwaway mailbox service |
| No MX record | The address’s domain cannot receive mail |
| Young domain | The address’s domain was registered recently. Needs the optional external lookups |
| Website not live | The website given at signup is unreachable or parked. Needs the optional external lookups |
| Signup burst | Several accounts came from the same IP within a day |
| Suspended domain | Accounts on the same domain were suspended before |
Each user group sets signup screening to off, flag or hold, with a score threshold. Flag reports the result to staff. Signup and import screening flag by default. The external lookups (domain registration date and the signup website) leave your server, so they are off until you turn them on.
A third point, content screening, runs SpamAssassin on a campaign as it starts sending. It is off for every group by default.
Screening narrows what staff look at. It does not replace the review.
Ask the questions you need
From 6.0.6, a held account sees a review page that says what is paused and why, and a questionnaire you configure. Each question is off, optional or required. The ones that decide most reviews:
- company name and website
- industry, which lets you spot refused categories early
- what they will send
- how they collected their contacts, with “purchased or rented list” as one of the answers
- how many contacts they have and their expected monthly volume
- whether they will use the API or SMTP relay, and for what
- agreement to your acceptable use policy
The AUP agreement and the question about past suspensions are off by default. Turn on the ones your review needs. When staff mark an account that submitted the questionnaire Trusted, Octeth emails the customer that the account is approved.
Decide what you verify
Write the review checklist before the first signup, so every reviewer decides the same way. Start from your refused sender list in the AUP and the signup answers. Two more checks worth adding: a minimum age for sending domains, with a public website that leads to the sender’s legal pages, and a custom account instead of self-serve for regulated businesses such as lending, investments, medicine and gambling, with the right to ask for licences and documents.
A customer whose sender domain fails verification, or whose first campaign fails DMARC, is not ready for shared IPs. Stage 6, sender domain authentication, covers the domain checks.
Trust levels
Octeth gives you three controls per account. Combine them into levels.
| Level | Settings | What the account can do |
|---|---|---|
| New | Untrusted, in the signup group with low limits | Build lists and campaigns. Campaigns wait for approval. Gateway, journey and relay sends are refused |
| Approved | Trusted, in its plan’s group | Send within the plan’s limits from the plan’s IPs |
| Suspended | Disabled, in the Suspended group | No sign-in. Gateway API and SMTP relay sends are refused, and the group’s sending limit is 1 |
Two rules apply at every level:
- Paying does not make an account Trusted. Staff do. A customer on a paid plan whose account is still Untrusted keeps the holds.
- Approval covers one version of a campaign. Only an administrator can release a campaign from Pending Approval, and an edit to the approved campaign puts it back on hold.
From 6.0.6, journey emails from a held account wait for the hold to lift instead of failing.
Ramp new accounts slowly
Build a warm-up ramp for new accounts from groups and limits:
- Put new accounts in a low-limit group, such as a free plan with a small monthly allowance. Send that group from an IP it shares only with the Suspended and Cancelled groups, so a new account never touches a paid plan’s IP. Stage 7, plans and sending limits, sets the groups. Stage 5, sending infrastructure and IP warm-up, sets the new-account pool.
- Use the day limit. A plan group’s emails per day caps how fast a new account can spend its monthly allowance.
- Watch absolute volume. Peak Monitor, one of Octeth’s abuse plug-ins, alerts when an account younger than 7 days sends more than 500 gateway emails (API, SMTP relay and journeys) in an hour or 2,000 in 24 hours. It does not count campaign sends. The group’s daily limit and campaign approval cover those. Those are the defaults on a fresh install, and they alert only (Octeth abuse protection). Turn on its suspension switch if you want it to stop the account.
Set your own ramp: how much a newly Trusted account may send per day, and how many clean sends it needs before it gets its plan’s full limits.
List import rules
Most bad sending starts with a bad list. Put these rules in the AUP and enforce them at import.
- Own opt-in lists only. No purchased, rented, scraped or appended lists. The review questionnaire asks how contacts were collected.
- Bring the suppressions with the list. A customer moving from another ESP brings its unsubscribes, bounces and complaints along with its contacts. Octeth imports them with the
suppression.importAPI command. Call it with the customer’s own API key. With the admin key the rows apply to every account on the install. - Clean before the first send. From 6.0.6, Octeth can verify a list or segment through my.octeth.com, paid in verification credits and off until an administrator enables it. The email verifier checks a single address.
From 6.0.2, Octeth also screens each import on a sample of its addresses:
| Signal | What it flags |
|---|---|
| Role addresses | A high share of info@, sales@ and other shared mailboxes |
| Invalid syntax | A high share of malformed addresses |
| No MX | A high share of domains that cannot receive mail |
| Spam trap patterns | Matches against patterns you configure |
| Bounce history | Addresses that hard bounced or complained on any account on your install |
| Free-mail shift | A mix of free-mail addresses far from the customer’s other lists |
The bounce history signal reads other customers’ data, so it only reaches staff. It never holds an import and never appears in the reason the customer reads.
Bounce and complaint thresholds for an ESP
Keep each customer’s spam complaint rate below 0.10%, Gmail’s limit, which also keeps it under Yahoo’s 0.3%, and set your own bounce threshold, because neither provider names one. These mailbox provider rules are the line your whole platform must stay under, because each customer’s mail affects the reputation of the IPs it shares.
| Mailbox provider | Spam complaint rule |
|---|---|
| Gmail | Below 0.10%, never 0.30% or higher |
| Yahoo | Below 0.3% |
Sources: Gmail sender guidelines, Yahoo sender best practices. We checked them on 2026-11-19. Stage 6, sender domain authentication, covers the rest of the bulk sender rules.
Both Gmail and Yahoo say to remove invalid recipients. They also name no limit for unsubscribes, spam trap hits or unjustified abuse complaints. We recommend setting one for each in your AUP, with zero for spam trap hits.
Set your own threshold for each measure, and decide what happens at it: a warning, a campaign hold, lower limits or suspension. Put the same numbers in the AUP, so a customer you act against has read them. Keep your complaint limit below Gmail’s 0.10%. Gmail measures the spam rate per domain, and each customer’s mail is signed with the customer’s domain, so one customer can cross it while the platform average looks fine.
Octeth shows bounce and complaint rates on each campaign report. Peak Monitor’s change rate checks watch bounce, unsubscribe and complaint rates of each account’s gateway sends (API, SMTP relay and journeys) and can alert or suspend. They are off on a fresh install. If you turn them on, check how each one measures before you set its threshold.
Complaints and the global suppression list
Octeth suppresses complaints and hard bounces automatically. Its suppression list has three scopes: one list, one account, and the whole install.
- Where a complaint lands depends on how it reaches Octeth. Feedback loop mail read from the FBL mailbox unsubscribes the address from its list and adds it to that customer’s account-wide list. A complaint found in the bounce mailbox, or a campaign complaint posted from the MTA’s accounting log, adds an install-wide row and does not change the subscriber’s list status. A gateway complaint from the accounting log adds an account-wide row. Test your own route and read the row it writes.
- A hard bounce adds one install-wide row, from 6.0.6. No customer on your install mails that address again. Only an administrator can remove it.
- The global suppression list in the staff area holds the install-wide rows, plus addresses and patterns staff add.
Suppression works only on the events that reach Octeth. Complaints come from feedback loops and bounces from the MTA. Stage 5, sending infrastructure and IP warm-up, gets bounces back from PowerMTA. Stage 10, Deliverability operations, covers the mailbox provider feedback loops. Octeth alerts when MTA feedback goes silent, and Peak Monitor flags an account that sent at least 500 gateway emails in a day without a single delivery, bounce, complaint, open or click event.
Suspend abusive accounts
Suspending an account means setting it to Disabled. On 6.0.1 or later a Disabled account cannot sign in, cannot send through the gateway API or the SMTP relay, its queued gateway mail is held back, and its gateway links stop redirecting. Its campaigns stop sending as well. Links in campaigns it already sent keep redirecting. From 6.0.4, staff can also stop one account’s gateway link redirects without suspending it.
Disabled is what stops a suspended account. With billing on, do not rely on moving a paying account to the Suspended group by hand: the hourly billing check moves it back to its plan’s group. Cancel its subscription if you end the relationship. Billing uses the Suspended group for accounts it suspends for failed payments. Give that group a sending limit of 1, because 0 means unlimited, and send its mail from the free plan’s IP.
From 6.0.6, three plug-ins suspend accounts on their own (Octeth abuse protection):
| Plug-in | What it watches | Default on a fresh install |
|---|---|---|
| Peak Monitor | Gateway sends per account: volume, bounce, unsubscribe and complaint rates, missing delivery events | Alert only |
| SpamAssassin Content Validator | The spam score of sampled gateway emails | Suspends at a score of 5.0 |
| PhishGuard | Phishing phrases in delivered gateway emails | Suspends after 20 detections in 24 hours |
All three check mail after it is delivered, so they limit the damage but cannot stop the first emails. That is why review comes first. On an upgraded install, apply the new defaults from the staff dashboard and restart the background workers. Review PhishGuard’s phrase list against what your customers send, and add a false positive’s user ID to the plug-in’s whitelist when you re-enable the account.
Gateway mail carries a signed abuse ID from 6.0.4, which ties a report to the account that sent it. Ask for full headers on your report-abuse page, as stage 2, legal and policies, describes.
Octeth versions this stage relies on
| Feature | Octeth version |
|---|---|
| Signups created Untrusted, gateway sends only from Trusted accounts | 6.0.1 |
| Disabling an account stops gateway sends | 6.0.1 |
| Signup, import and content screening. Only an administrator releases a held campaign | 6.0.2 |
| Per-account switch to stop link redirects, signed abuse ID on gateway mail | 6.0.4 |
| Account review page, questionnaire and approval email | 6.0.6 |
| Abuse plug-ins suspend accounts natively | 6.0.6 |
| Hard bounces suppressed install-wide | 6.0.6 |
| Journey emails wait out account holds | 6.0.6 |
| List and segment email verification | 6.0.6 |
| Google sign-in | 6.0.7 |
Build on 6.0.6 or later. Then test each control in this guide on the version you install: a throwaway signup that cannot send, an import that screening flags, a test complaint that lands on the suppression list and a suspension that refuses the account’s gateway API and SMTP relay sends.
Before you move on
- New signups are created Untrusted, and EMAILGATEWAY_REQUIRE_TRUSTED is true.
- Phone verification for gateway sends is off, so the Trusted gate is the only approval gate.
- Someone on staff is told about every new signup and every campaign that waits for approval.
- The account review questionnaire asks what you need to decide, including how contacts were collected.
- You have a written review checklist and a refused sender list that matches your AUP.
- New accounts land in a low-limit plan group that sends from IPs no paying plan uses.
- Signup and import screening are on for every plan group, in flag or hold mode.
- You know your complaint and bounce limits, what you do at each one, and they match the AUP.
- Bounce and complaint events reach Octeth, and you have tested both.
- Peak Monitor, SpamAssassin Content Validator and PhishGuard are enabled, and you chose which checks suspend.
- You have tested a suspension: the account cannot sign in, its gateway API and SMTP relay sends are refused, and its gateway links stop redirecting.
- You run Octeth 6.0.6 or later.
What we've seen go wrong
Bounce limits measured on part of the bounces
An MTA that accepts inbound mail only for its own relay domains refuses bounces sent back later to customer return paths, because those sit under the customer's domain. Only bounces returned during delivery reach Octeth. A bounce rate built from those counts is lower than the real one. Know which bounces your setup sees before you set a bounce limit, and add a separate inbound MX if you need the late ones.
Related tools
Related glossary terms
We build ESPs
Rather have us build this?
We configure the user groups and sending limits that hold new accounts back. You decide who gets approved.