Delivery
📄️ Scripted routing
Scripted routing is one of the most distinguished features of the Halon platform. It allows users to implement the best solution for any given challenge, instead of having to compromise. Since you have virtually unlimited possibilities with our product, we encourage you to contact support to discuss the best solution for you.
📄️ How to deliver using LMTP
The Halon platform supports LMTP delivery via the Try() function. It enables you to create setups with only Halon and an email storage server, such as Dovecot. Consequently, all filtering, routing, rewriting and forwarding takes place in the Halon.
📄️ In-line delivery
The Halon MTA is capable of doing queue-less, inline delivery resulting in
📄️ Outbound anti-abuse
Halon is highly effective for reducing outbound anti-spam. It handles compromised and abusive accounts to avoid blocklisting, without bothering legitimate users. Ensuring high delivery rates to external parties (email servers on the Internet) is important in many cases; marketing, transactional, mailbox, forwarding, cloud/VPS and internet service providers.
📄️ Using HAProxy with Halon
Halon MTA natively supports HAProxy (PROXY protocol) for both inbound and outbound SMTP routing. Outbound connections can go out via the HAProxy server, selecting any of the available source IPs. Inbound connections can be routed from the outside network back to Halon.
📄️ Enable the DSN extensions
Halon MTA supports the DSN extensions (RFC 3461). It's possible to store, forward or act upon the DSN extensions parameters. Halon MTA doesn't automatically announce the DSN extension in the EHLO reply. Instead that has to be done using a HELO script.
📄️ Sending bounces
If you have enabled bounces on any of your transports, you need to choose a "bounce" transport in order for bounces to be delivered correctly. In many cases a "MX lookup" transport will be the correct option for them to be delivered correctly, however there might be some circumstances where you need to use another transport.