Why your outgoing emails get blocked: cold outbound and per-minute, per-hour, per-day limits

If an email send from Omnifox gets rejected with a limit error, it's not a bug — it's an active safeguard so your domain doesn't end up flagged as spam from an accidental mass send or an attack.

The limits that apply

• Per minute, per hour, and per day — conservative default caps your plan can raise, but never below a minimum floor designed to never block a normal support reply.
• Cold outbound per day — a separate, smaller cap for new conversations the business opens (the first email to a customer who never wrote to you before). Replying to someone who already messaged you doesn't count against this cap.
• Max recipients per message — a single email can't carry too many combined To/CC/BCC addresses; this is a 1:1 channel, not a mass-email tool.
• Abuse-pattern freeze — if the same content is detected going out to too many distinct recipients in a short time, the workspace gets temporarily frozen for new sends.

Example

An agent trying to send the same promotional email to 300 different addresses in an hour first hits the per-message recipient cap, and if they split it into many individual sends, they'll eventually trigger the abuse-pattern freeze.

Tips

• The per-minute/hour/day limits are counted at the organization level and the workspace level separately — both need to be within their cap.
• If your operation legitimately needs to send more volume per day (e.g., transactional notifications), talk to support about reviewing your plan.

Troubleshooting

If a send gets blocked with a limit error, wait for that window to reset (minute/hour/day, per the error message) before retrying; retrying immediately won't unblock it.