Version 2026-10-13 · Effective 2026-10-13
Send only where you have a valid basis and recipient expectation for the message. Keep evidence of consent or the transaction that requires the communication. Do not use purchased, harvested or scraped lists. A verified sending domain is not evidence of recipient consent.
Hard-bounced recipients are suppressed before new deliveries are queued. Stop sending to invalid addresses and honor recipient complaints and opt-out requests. Temporary failures receive bounded queue retries; ambiguous submissions require review to avoid duplicate delivery. Receiving-provider retry behavior can differ after SMTP acceptance.
We process complaint information when an actual provider feedback source or an investigated abuse report is available. We do not claim a universal complaint feedback feed. High hard-bounce rates or credible abuse can pause sending for review. Ordinary password resets and receipts are not rejected solely for containing a keyword.
Sending cooldowns apply across REST and SMTP. Essential security, password recovery, payment receipts and suspension/exhaustion notices are system-funded and logically separate from customer sending. Eligible customer service notifications can count once against monthly usage; internal retries do not count again. Notification rate limits prevent alert loops.
Contact support to appeal. Explain list collection, consent, removal of invalid addresses and the changes that prevent recurrence. Paid accounts must follow the same sending policies as Free accounts.
Questions? Contact support@xdigitex.com.