2Mail anti-spam policy: what is allowed, what is not and how we enforce it
2Mail is shared sending infrastructure: your email leaves from an IP pool you share with other customers. The anti-spam policy protects the reputation of that pool — and with it the delivery of every customer. In short: you only email people who gave consent or are your customers, every commercial email carries a working unsubscribe link, and you act on bounces and complaints.
Below you will find what that means in practice, what your obligations as a sender are and how 2Mail monitors and intervenes. Anyone who follows these rules never notices them; they exist for the rare cases where things go wrong.
Why an SMTP relay needs an anti-spam policy
Mailbox providers judge not only your domain but also the IP address your email leaves from. If a single customer sends to a purchased list, the complaint rate of the shared IP rises and another customer's order confirmations end up in the spam folder too. The policy is therefore not a formality but the reason your email arrives.
Shared reputation
The IP pool is randomised and rate-limited per domain, but it remains shared. One bad sender weighs on everyone; the policy keeps them out.
Legal framework
Commercial email without consent is not permitted in Belgium or the EU (GDPR and the rules on electronic direct marketing). The policy asks nothing more than what the law already asks.
Your own domain
Your domain reputation suffers from complaints as well. What the policy prescribes is exactly what protects your deliverability in the long run.
What is allowed and what is not
The dividing line is consent and expectation: would the recipient be surprised to get this email from you? If so, it should not leave through 2Mail.
Allowed
Not allowed
Your obligations as a sender
Four things you keep in order for as long as you send through 2Mail. All of them can be arranged in the dashboard or in your own system.
Unsubscribing always works
Every commercial email carries a visible unsubscribe link and the List-Unsubscribe header, so recipients can also unsubscribe through their mail client's button. You process an unsubscribe without any further steps for the recipient.
Act on bounces and complaints
Hard bounces leave your list; anyone who complains gets no further email. 2Mail processes bounces automatically, but the list in your own system remains your responsibility.
A valid sender domain with SPF, DKIM and DMARC
You send from a domain you manage, with the three records published correctly. Sending from a free address or from a domain that is not yours is not possible.
Keep proof of consent
For every address you record when, where and how consent was given. In the event of a complaint, that is what you must be able to produce — to us, and to the supervisory authority.
How 2Mail monitors and intervenes
For each sending domain we measure the bounce rate, the complaint rate and the sending pattern, and compare them with the reference values the major mailbox providers apply. Rate limiting per domain prevents a mistake in your system — a loop, the wrong list — from hitting the whole pool at once. If a domain deviates, follow-up happens in three steps.
Warning
You receive a notice describing what we see and what needs to change. Usually that is enough: an old list, a forgotten bounce process.
Temporary restriction
If the pattern persists, we limit the volume or pause the domain until the cause has been removed. We try to spare transactional email in the process.
Termination
For abuse we cannot allow — purchased lists, phishing, repeated violations — we terminate access. In cases of clear fraud that happens immediately, without prior warning.
What we do not do: read the content of your emails to judge what you may say. We look at recipient behaviour and at the reports we receive, not at your message.
How to stay within the policy
Four habits that make the difference between a sender with a clean reputation and one who lands in the spam folder every few months.
Build your list yourself, with confirmation
Have subscribers confirm their address through a link. That rules out typos and fake addresses and gives you the proof of consent you will need later.
Set up SPF, DKIM and DMARC on your domain
Publish the three records before you send the first email; from the dashboard it takes one click. Afterwards, check with a test email that DMARC passes.
Separate transactional from commercial
Use a separate SMTP login or API key per application and, where possible, a dedicated subdomain. A complaint about the newsletter then does not touch the order confirmations.
Review bounces and complaints monthly
Open the dashboard, look at the rates per domain and remove whatever hard-bounces. A list that has not been cleaned in a year is the most common cause of a warning.
Reporting abuse
Receiving unwanted email that appears to have been sent through 2Mail, or suspect a 2Mail customer is breaching the policy? Send us the message with its full headers through the contact form. We investigate every report and get back to you where we can, without sharing sender data with you beyond what the law allows.