Anti-Spam Policy

What is Considered Spam?

Spam is any commercial email or unsolicited bulk email sent to someone who has not explicitly requested or consented to receive emails from you.

Mailgridder adheres strictly to the definitions provided by the CAN-SPAM Act, the GDPR, and CASL. Under our policy, an email is considered spam if:

• The recipient’s identity and context cannot be verified via an explicit opt-in.
• The sender’s identity (the “From” or “Reply-To” address) is concealed, forged, or misleading.
• The subject line is deceptive or attempts to trick the recipient into opening the email.
• The email fails to include a working, clear mechanism to unsubscribe.

Mandatory Proof of Consent

To use Mailgridder, you must be able to prove that every contact in your Mautic instance has granted you permission to email them.

• Double Opt-In (DOI): We strongly recommend configuring a Double Opt-In workflow within your Mautic instance for all new subscribers.
• Audit Trails: You must retain logs of consent. If a spam complaint is filed against your domain, Mailgridder or Amazon AWS may request proof of opt-in. This proof must include the date, time, IP address, and the URL of the form where the contact subscribed.
• Scope of Consent: Consent is brand-specific. If a contact subscribes to Brand A, you may not use Mailgridder to send them emails promoting Brand B, even if you own both brands.

Prohibited Contact Lists

We do not allow the use of third-party data on our infrastructure. You may never import or send to the following types of lists:

Unsubscribe Requirements

Every marketing or commercial email sent from your Mailgridder container must include a functional, clearly visible unsubscribe link.

• One-Click Unsubscribe (RFC 8058): Mailgridder instances are configured to support automated list-unsubscribe headers required by Google and Yahoo. You may not disable or attempt to bypass these headers.
• Instant Processing: While the law allows up to 10 days, Mailgridder’s Mautic configuration processes unsubscribes instantly. You may not attempt to re-import or re-subscribe a user who has opted out.
• Physical Address: In compliance with CAN-SPAM, every marketing email must include your valid physical postal address at the bottom of the email.

Infrastructure Protection Protocols

Because your instance routes through Amazon SES, we employ automated systems to protect your sender reputation and the integrity of our IP ranges:

• SNS Bounce Webhooks: If an email hard-bounces (the address does not exist), our Amazon SNS webhook instantly flags that contact as “Do Not Contact” in your Mautic instance.
• Complaint Feedback Loops: If a user clicks the “Mark as Spam” button in Gmail, Yahoo, or Outlook, our system receives a notification and permanently suppresses that contact from all future sends.
• Suppression Evasion: Any attempt to manually un-suppress hard bounces or spam complainers will result in immediate container suspension.

Immediate Suspension Triggers

Mailgridder relies on automated thresholds provided by Amazon SES. If your sending practices trigger any of the following limits, your outbound sending capabilities will be automatically paused:

• Hard Bounce Rate > 5%: Indicates you are sending to purchased or severely outdated lists.
• Spam Complaint Rate > 0.1%: Receiving more than 1 spam complaint per 1,000 emails sent.
• Direct AWS Intervention: If Amazon AWS Trust & Safety flags your domain identity for violating their Acceptable Use Policy.
• Spam Trap Hits: Hitting known spam traps managed by organizations like Spamhaus or SpamCop.

How to Report Spam

If you believe you have received unsolicited email from a Mailgridder client or a domain hosted on our infrastructure, please report it to our abuse team immediately.

To help us investigate, please forward the entire email—including the full raw email headers—to the address below.