Anti-spam

This Anti-Spam Policy (“Policy”) applies to all customers using LumaDock services operated by LumaDock Ltd. By using our network and infrastructure, you agree to comply with this Policy. LumaDock maintains a zero-tolerance stance toward unsolicited commercial email (“spam”) and abusive messaging practices. Sending spam through our network, or using third-party servers to promote any site or application hosted on LumaDock, may result in immediate suspension or termination without prior notice.

1. Definitions & Scope

• Spam: Unsolicited bulk or commercial electronic messages (email or similar), including UCE/UBE, regardless of content.
• Covered Services: All LumaDock compute, networking, storage, IP addressing, and related services that can originate or relay email.
• Applicable Law: EU/UK law (including GDPR and ePrivacy rules) and any local anti-spam laws; where relevant, CAN-SPAM (US) and similar regimes.

2. Port Access & SMTP Use

Default posture: SMTP port 25 traffic (both inbound and outbound) is filtered by default on LumaDock VPS instances to protect network reputation and reduce abuse. Customers should use authenticated SMTP submission on ports 587 or 465, or an approved third-party SMTP relay.

If you need to unblock port 25, you must submit a request through our official form and receive manual approval from our team. Eligibility requirements apply. You can start the process by submitting the SMTP port 25 unblock request form.

3. Prohibited Email Practices

• Sending unsolicited bulk or commercial messages without prior, provable consent (opt-in).
• Using harvested/scraped, purchased, leased, or third-party lists, or lists with outdated/inaccurate addresses.
• Using false, misleading, or forged headers/identities/subject lines; using non-existent domains or improper DNS/MX.
• Relaying through third-party servers or using third-party domains without explicit authorization.
• Operating an open relay or knowingly allowing unauthorized mail submission.
• Content containing malware, phishing, or deceptive material; or content that violates law or our Acceptable Use Policy.
• Practices that lead to RBL / blocklist listings of our IP space or ASN.

4. Mailing List & Consent Standards

• Confirmed (double) opt-in is required for marketing lists; retain verifiable consent logs (address, source, date/time, method).
• Every message must include a functional unsubscribe link; honor opt-outs promptly and in any case within 5 days.
• Use accurate sender identity, reply-to, and subject lines; identify the sender’s valid physical address where legally required.
• Perform continuous list hygiene: remove hard bounces immediately and repeated soft bounces.

5. Technical & Authentication Requirements

• Publish correct DNS for sending hosts: PTR/rDNS, matching HELO/EHLO, valid MX/A records.
• Implement SPF, DKIM, and DMARC with appropriate policies and alignment.
• Configure rate controls, submission auth, and abuse monitoring on self-hosted MTAs; no open relays.
• Keep server OS, MTA, and libraries patched; scan outbound content for malware where feasible.

6. Customer Responsibilities (Self-Hosted Mail)

• You are responsible for configuration, security, compliance, deliverability, and reputation of your mail systems.
• Investigate and resolve complaints, abuse tickets, and blocklistings without delay.
• Respond to LumaDock abuse inquiries within 48 hours (sooner for severe incidents).

7. Monitoring & Safeguards

To protect customers and network integrity, LumaDock may observe outbound email activity and employ safeguards. Indicative risk signals include (non-exhaustive): abnormal sending patterns, elevated bounce or complaint activity, spamtrap signals, or listings on major RBLs (e.g., Spamhaus) attributable to your IPs or domains.

Safeguards may include: temporary restrictions, filtering, port 25 limitations, a requirement to use an external transactional provider, or short-term isolation while you remediate.

8. Enforcement

• Warning & remediation request with a deadline and required changes.
• Temporary restrictions: throttle/disable outbound SMTP, null-route sender IP, or suspend the affected service.
• Account suspension or termination for severe or repeated violations.
• Cost recovery of reasonable administrative/mitigation expenses (e.g., RBL delisting, forensics, abuse handling), billed at posted rates.
• Escalation to upstream providers or competent authorities where required by law.

9. Delivery Disclaimer

LumaDock cannot guarantee delivery outside our network. Delivery depends on recipient policies, blocklists, spam filtering, sender configuration, and third-party systems. You are responsible for meeting technical and legal requirements to achieve deliverability.

10. Reporting Abuse

If you believe a LumaDock customer is violating this Policy, please submit an abuse report via the Client Area with relevant details (including full headers and message samples). We will investigate and take appropriate action.

11. Amendments

We may modify this Policy at any time. Material changes will be posted on our website or in the client area. Continued use of the Services after changes take effect constitutes acceptance.