Platform Rules

Understand the automated rules, thresholds, and enforcement mechanisms that protect your infrastructure

System Modes

Superkabe operates in 3 modes that control enforcement behavior:

Logs all events, no automated actions

Use for: Testing, learning baseline metrics

Provides recommendations, no blocking

Use for: Review suggestions before automation

Fully automated pausing and blocking

Use for: Production-ready automated protection

We use a two-tier threshold system to catch issues early:

3 bounces within 60 sends

~5% bounce rate — early detection

Action: Mailbox transitions to warning state

5 bounces within 100 sends

5% bounce rate — hard stop

Action: Mailbox transitions to paused state

healthy → warning (3/60) → paused (5/100)
  ↑__________________________________|
  └── recovering → healthy (after clean window)

Domain health uses percentage-based thresholds that scale with infrastructure size:

Threshold	Ratio	Action
WARNING	30% unhealthy	Domain → `warning`
PAUSE	50% unhealthy	Domain → `paused` + cascade

Mailboxes	Unhealthy	Old Logic	New Logic
3	1	✅ Healthy	⚠️ Warning (33%)
10	2	🛑 Pause	✅ Healthy (20%)
10	5	🛑 Pause	🛑 Pause (50%)

After a mailbox is paused, it enters a cooldown period with exponential backoff:

Formula: Cooldown = 1 hour × 2^(consecutive_pauses - 1)

Maximum: Capped at 16 hours

These thresholds are production-hardened based on email deliverability best practices:

• 5% bounce rate is the industry-accepted maximum before reputation damage
• Early warnings at 3 bounces give operators time to investigate
• Ratio-based domains scale from small (3 mailboxes) to large (200+) infrastructure
• Exponential cooldown prevents rapid re-entry into unhealthy patterns