SMTP relay in Belgium: your email sent from Belgian servers
An SMTP relay in Belgium is a sending service that accepts the email from your web shop, CRM or server and delivers it from servers on Belgian soil, with processing and storage inside the EU. 2Mail provides that relay as a managed service: you connect through port 587 or the API, we take care of reputation, authentication and delivery.
This page is about the offer for the Belgian market. If you first want to know how a relay works technically, read our explanation of SMTP relay; if your question is about data location and GDPR, that is covered on the page about our European email platform.
Why a relay on Belgian servers?
An SMTP relay as such is nothing special: any mail server can forward. The difference lies in who manages the servers, where they sit and who you call when a confirmation email does not arrive.
Processing and storage in Belgium
Your emails, logs and statistics stay on JAAN bv's own infrastructure in Belgium, inside the EU. That keeps your record of processing activities simple: one country, one processor, and a data processing agreement available on request.
A reputation you do not have to build yourself
Sending from your own server or a hosting package means building an IP reputation with Gmail, Outlook and the Belgian providers yourself. With a relay you send from a maintained IP pool with rate limiting per domain, and we handle the warm-up.
Support in your language, in your time zone
When an invoice gets stuck at a recipient, you want someone on the line who can read the logs. Our support works from Zelzate in Dutch, French and English, on +32 9 328 03 83.
Belgian recipients, Belgian practice
Many Belgian companies send from Microsoft 365, Odoo or a web shop to customers at Proximus, Telenet and the large webmail providers. We see every day how those recipients respond and tune retries and throttling accordingly.
Who is a Belgian SMTP relay for?
For anything that sends email automatically and where arrival matters. These are the four situations we come across most often.
Web shops
Order confirmations, shipping notices and password resets from WooCommerce, PrestaShop or Magento. One missed confirmation is a call to your customer service; a hundred missed confirmations are a reputation problem.
SMEs with their own software
Invoices from your accounting package, quotes from your CRM, reminders from Odoo. Today that often leaves through a hosting account or through Microsoft 365 with a sending limit. A relay removes that limit and that worry.
Developers
A Laravel or Symfony application that has to send transactional mail, with an API key per application, webhooks for bounces and a dashboard to see what happened. Without running a mail server yourself.
IT partners and system administrators
You manage servers, NAS devices or multifunction printers at customers that need to send mail while port 25 is blocked. One relay with a separate login per customer or device, each of which can be revoked on its own.
How you connect: SMTP on port 587 or through the API
Nothing to install. Any application that speaks SMTP connects with a server name, a login and a password. If you prefer to work in code, use the API.
SMTP with STARTTLS on port 587
The standard route for a web shop, a CRM, a NAS or a printer. Each application gets its own SMTP login, so you can shut off one device without touching the rest.
REST API and webhooks
For custom work or high volumes you send through the API with a key per application. Signed webhooks report delivery, bounce and open back to your system, so your CRM knows which addresses no longer work.
SPF, DKIM and DMARC in one click
From the dashboard you set up authentication for your domain. That way you send from your own domain name, with a signature that Gmail and Outlook check before placing your mail in the inbox.
Works with what you already use
WordPress, WooCommerce, Odoo, PrestaShop, Magento, Microsoft 365, Laravel and any other SMTP client. For the most common platforms we have a dedicated setup page with the exact fields.
Five reasons to choose a Belgian relay
Short and verifiable. You are welcome to put every point below to us in a conversation.
Torn between a relay and sending from your hosting package yourself? Work out one thing: how much does one invoice or order confirmation that never arrives cost in follow-up? That answer is usually clearer than any comparison of monthly rates.
Sending in four steps
Most customers are up and running the same day. This is the order we recommend.
Pick your volume tier and register your domain
Look at how many emails you send per month and pick the matching tier on the pricing page. You state the sending domain you want to mail from; several domains are possible, with shared volume on request.
Set up SPF, DKIM and DMARC from the dashboard
The dashboard shows the DNS records to place with your domain registrar and then checks that they are correct. Without this step you still send, but with a smaller chance of reaching the inbox.
Connect your application through port 587 or the API
Create a separate SMTP login or API key per application and enter it in your web shop, CRM, server or invoicing package. Send a test email to a Gmail and an Outlook address and check in the dashboard that they were delivered.
Build up the volume and follow the statistics
We guide the warm-up and watch the reputation. You follow deliveries, bounces and opens per domain in real time; bounces are processed automatically, so your list stays clean.
How 2Mail does it
The facts about our own platform, without fuss.