· Updated:
Spotnewsletter Gateway was built for one job only: sending bulk e-mail for newsletters and marketing campaigns. It runs its own SMTP servers and services, and because it was never asked to do anything else, all of its capacity goes into that single task.
What it deliberately does not do
The Gateway SMTP server cannot be installed as your company's local mail server. It does not support SMTP and POP3 clients, and it neither accepts nor sends large mail files. Every resource that a general-purpose mail server would spend on those is spent on sending and reporting instead.
Deliverability
Getting bulk mail delivered is mostly a question of not looking like spam, so the infrastructure is built around that:
- Sending is spread across multiple IP addresses using a round-robin algorithm within a defined concurrent capacity
- Every server carries correctly configured PTR and SPF records, and the SMTP server signs with DomainKey and DKIM
- Every user on the servers is real and can receive mail — when a receiving server connects back to the sender address for a spam check, it gets an answer. This keeps you off blocklists, and makes getting removed from one a matter of replying to a message
- Capacity is expandable and not bound to a fixed limit; dedicated servers can be set up for a single organisation so that other senders' traffic cannot affect your reputation
Unsubscribes and rendering
The Gateway keeps its own blocklist for unsubscribe requests: even if someone forgets to remove an address from a list, no mail is sent to it. And because mail clients render HTML unpredictably, every message sent also has a web version that can be opened in a browser.
The Gateway is kept separate from other systems as a core service and communicates through an API, so the same sending and reporting capability can be integrated into your own software.
More at spotnewsletter.com.
