As Google recently announced (see more details here), starting January 2025, sending emails from less secure devices, apps, third-party apps, or devices that only require your username and password to sign in will no longer be supported for Google Workspace accounts. This change is part of a broader move toward stricter security protocols, and other public email providers are expected to follow suit.
While enhanced security measures are beneficial for protecting personal communications, they pose challenges for IoT devices like the TCW241, which may need to send email notifications about something as simple as a boiler’s temperature reading. However, these changes leave us with limited options: either we adapt or explore alternative solutions.
Consequently, relying on major public email servers to send email notifications from IoT devices is no longer a viable option. This guide will explore available alternatives and workarounds to ensure your TCW2xx devices can continue to send email alerts effectively.
What are the alternatives?
- Using a company email server
The best option is to use a company email server. While Google and other major providers consider devices like the TCW2xx insecure, it’s worth noting that they support encrypted connections with TLS 1.2—a protocol widely regarded as secure.
If you don’t currently have a company email server, setting one up is relatively simple. Start by purchasing a domain, such as myemail.com, which typically costs around $8–10 per year. Then, arrange for hosting, which generally costs $10–15 per month. Although this option isn’t free like public email servers, it grants you independence and greater control over your email notifications.
- Using public email servers with less restrictive policies
Another option is to find a public email provider that does not impose strict restrictions on connected devices like printers, cameras, IP controllers, and allows sending emails from less secure devices. While Gmail and similar services are moving toward stringent security, smaller email providers might still allow access without OAuth 2.0.
- Using a transactional email service provider
Transactional email service providers are a convenient and affordable option for devices like the TCW2xx. Many providers offer a free plan that covers up to 1,000 emails per month, which is more than sufficient for sending notification emails from IoT devices.
Popular providers include SMTP2GO, MailerSend, MailerLite, Mailjet, and Mailgun. These services generally operate in the same way: sign up, receive a username and password, validate your list of recipients, and you’re ready to go.
How does a transactional email service work?
As mentioned, the operating principles of transactional email providers are quite similar across platforms. Here, we’ll look at using Mailgun to send emails from TCW2xx devices, specifically the TCW241 model.
According to Mailgun, registration takes less than 60 seconds. Here’s the step-by-step process:
- Update your device with the latest firmware version available for download from its product page.
- Sign up on mailgun’s website
Go to Mailgun’s website and click on “Get started for free”.
2. Skip the payment information
In the new window, uncheck the payment checkbox labelled “Add payment info now”
Enter your account details in the provided fields.
3. Complete registration
If registration is successful, you’ll see a confirmation screen.
Click “Continue to login” to proceed
4. Activate your account
Once logged in
you’ll need to activate your account through a confirmation email sent by Mailgun.
5. Your assigned domain
After verification, Mailgun assigns you a default domain, which is used for sending emails
6. Add an authorized recipient(s)
Navigate to the “Overview” tab and add at least one authorized recipient.
The recipient must confirm that they agree to receive emails from Mailgun.
After confirmation, the email status will change to “Verified” in the system, allowing emails to be sent to this recipient.
7. Retrieve SMTP details
Click the “Select” button in the SMTP section to view the details required for sending emails—such as port, username, and password.
Mailgun supports several ports and protocols.
Important: Some TCW2xx devices (such as TCW210-TH, TCW220, and TCW241) do not support STARTTLS. We recommend using port 465.
8. Enter SMTP details in the device’s email settings
Input the SMTP details you obtained from Mailgun into the respective fields on your TCW2xx device.
Note: Some email clients may still interpret these emails as spam. Be sure to check spam folders regularly or adjust spam settings as necessary.