Complete guide to configuring email alerts on Teltonika industrial routers and gateways using IoTMail. Covers RUT series, TRB series, and RUT241.
Teltonika Networks was founded in 1998 in Vilnius, Lithuania, initially as a GPS tracking hardware manufacturer. The company pivoted to networking in 2005 and has since become one of Europe's leading manufacturers of industrial-grade cellular routers, gateways, and switches. With over 15 million devices deployed across more than 190 countries, Teltonika is the most widely deployed brand in European IoT and M2M networking.
Teltonika built its market position on three things: competitive pricing against Cisco and Sierra Wireless, a genuinely powerful web interface called RutOS based on OpenWrt, and a very active developer community. The RMS cloud platform allows centralised management of thousands of devices, which made them the default choice for integrators managing large fleets.
Their devices are ubiquitous in UK utility monitoring, transport telematics, retail kiosk connectivity, and industrial automation.
All current Teltonika routers run RutOS and support SMTP email via the Events Reporting system. Setup is identical across the range.
Teltonika's Events Reporting system handles SMTP email natively. These steps apply to all RUT and TRB series devices running RutOS 7 or later.
192.168.1.1 (default). Log in with your admin credentials.Services then Events Reporting. This is the built-in system for sending alerts when router events occur.Add to create a new sender configuration. Set the type to Email. Give it a descriptive name such as IoTMail.SMTP server: smtp.iotmail.co.uk Port: 587 Security: STARTTLS Username: yourhandle+devicetag # from IoTMail portal Password: your-device-password # from IoTMail portal From address: yourhandle+devicetag@iotmail.co.uk To address: alerts@yourdomain.com # where alerts should go
WAN failover, SIM switch, Reboot, I/O state change. Set each rule to use the IoTMail sender.Test button in the sender configuration. You should receive a test email within a few seconds. If it fails, check the username and password match exactly what is shown in the IoTMail portal.portal.iotmail.co.uk and check the send log for your device. The test send should appear with a delivery status.yourhandle+devicetag@iotmail.co.uk - the same value as the username. IoTMail enforces this binding on every send. If they do not match, the message will be rejected with a 550 error.
The most common failure mode for Teltonika email alerts is silent delivery failure. Here is why it happens and how IoTMail prevents it.
Most broadband providers block outbound port 25. Teltonika devices default to port 25 for SMTP. Without a relay on port 587 or 465, email never leaves the router. The device reports success but nothing arrives.
Dynamic IP addresses used by SIM-connected routers have no sending reputation. Major mail providers reject messages from unknown dynamic IPs. IoTMail routes everything through Amazon SES, which has established deliverability to all major providers.
When a Teltonika router sends email directly, there is no SPF, DKIM, or DMARC coverage. IoTMail publishes all three on iotmail.co.uk, so every alert passes authentication checks at the receiving server.
Free account. Five devices. No card required. Setup takes five minutes.
Create free account