Features

Everything a device needs to send email — and nothing it doesn’t.

DeviceSMTP is a specialist SMTP gateway for the hardware you run: printers, cameras, alarms, HVAC, industrial controllers, IoT and network gear. These are the capabilities that make device email dependable, secure and accountable.

Delivery & reliability

A relay built for always-on hardware

Your devices only send a handful of messages — but each one carries a fault, an alert or a report that someone is waiting on. DeviceSMTP treats every message that way.

Reliable SMTP relay

A hardened submission relay that accepts your device’s mail over standard SMTP and takes responsibility for getting it delivered.

Smart retries

Temporary failures at the receiving server are retried on a backoff schedule instead of being silently dropped on the first try.

Multiple submission ports

Connect on 587 and 2525 with STARTTLS, or 465 with implicit TLS, so you can match whatever ports your firmware is limited to.

Durable queueing

Accepted messages are queued and held through transient delivery problems, so a momentarily unreachable mailbox doesn’t lose an alert.

Ready when hardware needs it

A relay designed to be available the moment a device decides to send — day, night or during an incident.

High availability

Redundant relay infrastructure so a single failure doesn’t stop your fleet from sending.

Security & authentication

Encrypted in transit, authenticated at the door

Security is not a plan tier. Every connection is encrypted and every sender is authenticated, and your sending domain stays yours.

TLS & SSL everywhere

STARTTLS on 587 and 2525 and implicit SSL/TLS on 465, with modern TLS 1.2 / 1.3 cipher suites on every supported port.

SMTP AUTH

Standard authenticated submission — your device presents a username and password before any mail is accepted.

Scoped credentials

Per-device credentials mean the scope of a single compromised device is limited to that device, not your whole account.

SPF & DKIM alignment

Verify your sending domain and align SPF and DKIM so mail from your hardware is trusted and lands in the inbox, not the spam folder.

Sender domain verification

Prove ownership of the domains your devices send from, so only your verified senders can use them.

Encrypted channel for old firmware

Even hardware with limited TLS support can negotiate an encrypted session on a port it understands.

IP-based authentication — Planned Authenticating a device by its source IP address, as an alternative to SMTP AUTH for firmware that cannot store credentials, is on our roadmap. It is not available today; use SMTP AUTH with per-device credentials in the meantime.

Under the hood

Standard SMTP, carefully handled

No SDKs and no firmware changes — just the SMTP conversation your device already speaks, negotiated securely and answered honestly.

ESMTP capability advertisement

The gateway advertises STARTTLS and AUTH so your device can negotiate the most secure path it supports.

Clear accept / reject responses

Every message gets a definitive response — accepted and queued, or rejected with a reason you can act on.

smtp session — camera-warehouse-1
$ device connects to mail.devicesmtp.com:587
220 DeviceSMTP ESMTP ready
EHLO camera-warehouse-1
250-STARTTLS
250 AUTH LOGIN PLAIN
STARTTLS
220 TLS 1.3 negotiated ✓
AUTH camera-warehouse-1 ********
235 authenticated
MAIL FROM <alerts@yourco.com>
RCPT TO <security@yourco.com>
250 Message accepted — queued for delivery

Device & credential management

Manage a fleet, not a spreadsheet

Give every piece of hardware its own identity, label it like a human would, and keep control of the whole fleet from one place.

Per-device credentials

Issue a separate SMTP username and password for each printer, camera or controller instead of sharing one login across the building.

Meaningful device labels

Name credentials the way you think about them — “Camera — Warehouse entrance” or “UPS — Server room” — so logs read like your site.

Rotate & revoke

Rotate a password or revoke a device instantly when hardware is replaced or retired, without touching any other device.

Device-level separation

Each device stands alone. A problem with one credential never cascades to the rest of your fleet.

Centralized fleet view

See every device, its label and its status together, so onboarding the next hundred units is as simple as the first.

Organized by what matters

Group and scan devices by location, type or purpose to keep a growing deployment legible.

Configuration at a glance

What you enter into a device

The same four settings every device already asks for. Point them at DeviceSMTP and it just sends.

SMTP hostYour account’s gateway hostname
Ports587 or 2525 (STARTTLS) · 465 (implicit SSL/TLS)
EncryptionSTARTTLS or SSL/TLS — whichever the device supports
UsernameThe per-device SMTP username you created
PasswordThe per-device password you created (rotate or revoke anytime)
AuthenticationSMTP AUTH (standard username & password)

See the configuration docs for step-by-step setup, or the how it works overview.

Monitoring & reporting

Know exactly what every device sent

Stop guessing whether a notification went out. DeviceSMTP records each message so you can answer “did it send?” in seconds — per device and across the fleet.

Email activity log

A searchable, per-device timeline of every message, with timestamp, destination and outcome.

Delivery status

See at a glance whether each message was accepted, delivered or still in flight.

Bounce monitoring

Rejected and bounced mail surfaces immediately, along with the reason the receiving server returned.

Per-device statistics

Volume, delivery rate and bounces broken out for each device, so a misbehaving unit stands out.

Fleet statistics

Roll the same numbers up across your entire deployment for a single health view.

Usage tracking

Track sending volume over time so you can plan capacity and spot unexpected changes early.

Integration & API

Programmatic control is on the roadmap

Today, DeviceSMTP is configured through the dashboard and used by your devices over standard SMTP. Deeper automation is coming — and we would rather be clear about what is and isn’t available yet.

Public REST API Planned

Create devices, rotate credentials and pull activity programmatically. Not yet available — on our roadmap.

Webhooks Planned

Push delivery and bounce events to your own systems as they happen, instead of polling. On our roadmap; not yet available.

Honest status The REST API and webhooks above are planned, not shipped. Everything else on this page is available today. If programmatic integration is important to your deployment, tell us on the contact page — it helps us prioritize.

Give every device a reliable way to send email.

Create your DeviceSMTP account and connect your first device today. No code, no firmware changes — just encrypted, authenticated, accountable delivery.