HomeSMTP service
SMTP relay service

SMTP service for your applications, devices and business systems

Connect your ERP, your CRM, your devices or your own applications to an authenticated SMTP relay: they send with your domain, you decide who can send, and every email is logged with its status.

  • Ports 587 and 465 with TLS
  • Allowed senders and IPs per domain
  • Free plan, no card required

Mailiqo SMTP settings

Server
smtpmq.mailiqo.com
Port and encryption
587 with STARTTLS or 465 with SSL/TLS
Authentication
Your domain's SMTP username and password
Sender
An address on your verified domain

The same values work in any plugin, application or device that sends over SMTP.

Use cases

For anything that sends email over SMTP

If your system lets you set an SMTP server with a username, a password and TLS, it can send through Mailiqo.

ERP and invoicing

Invoices, quotes, delivery notes and payment reminders that leave your ERP with your company's domain and are logged.

CRM and business tools

Notifications, reminders and customer communications from tools that only offer an SMTP setting.

Devices and equipment

Printers and scanners with scan-to-email, alarm systems, NAS units or cameras, as long as they support authentication and TLS.

Your own applications

Any language with an SMTP library: Node.js, PHP, Python, Java or .NET. And if you prefer HTTP, the same account has an API.

Requirements

What your system needs

  • SMTP authentication (SMTP AUTH) with your domain's username and password.
  • TLS encryption: STARTTLS on port 587 or implicit TLS (SSL) on port 465.
  • A sender on your verified domain that matches exactly: a subdomain isn't covered by its parent domain.
  • Ports 25 and 2525 aren't available: a device that only supports port 25 or doesn't support TLS can't send through Mailiqo.
  • Up to 50 recipients per message.
SMTP ports: which to use and why

Does your network block SMTP ports?

Many cloud and hosting providers block outgoing SMTP ports. If you can open neither 587 nor 465, send with the Mailiqo API, which works over HTTPS (port 443) with the same account and the same domains.

See the sending API
Control

You decide who can send

Each domain has its own credentials and its own rules, so a misconfigured device or application can't send on your behalf.

Credentials per domain

Each domain has its own SMTP username and password. If you regenerate them, the previous ones stop working immediately.

Allowed IPs

Accept sends only from the IPs of your office, your servers or your devices.

Blocked IPs

Stop sends from a specific IP without touching the credentials.

Authentication only

Mailiqo doesn't accept messages from clients that don't authenticate: the server is never an open relay.

Your domain on every email

Emails go out signed with your domain thanks to the DNS records you verify when you add it.

Tracking

Every email, with its status and history

The dashboard shows everything your systems send, and you can filter by the SMTP channel to see the rejected ones and why.

  • Statuses: queued, sent, delivered, opened, clicked, bounced or rejected.
  • The provider message ID, the delivery time and the destination server.
  • Technical headers and, on a bounce, the bounce type and the SMTP response.
  • Sends rejected over SMTP appear with their reason, so you can fix the device's or the application's settings.
  • How long the history is kept depends on your plan.

Clear limits

Recipients per message
Up to 50. If you need more, split the send into several messages.
Hourly and daily limits
New accounts start with limits that rise automatically with a healthy sending history. When one is reached, the server answers with a temporary 451 error and the email can be sent again later.
Monthly quota
Your plan's. SMTP and API sends count together.
Bulk sending from day one
Contact support first so we can adjust your account's limits.
How sending limits work
Plans

Plans for any volume

Start on the free plan and move to Early Access when your systems send more or you need more domains.

FAQ

Questions about the SMTP service

How is it different from my hosting's or my mailbox's SMTP?

Hosting SMTP or a personal mailbox is designed for a person sending from an email client, not for applications: its limits are usually set for that use and it doesn't give you a log of every message with its status. An SMTP relay like Mailiqo authenticates every send with your domain, lets you limit who sends and keeps the status of every email.

My device only supports port 25 or doesn't support TLS. Can it send?

No. Mailiqo only accepts authenticated, encrypted connections on ports 587 (STARTTLS) and 465 (SSL/TLS). Check whether the device has a firmware update that adds TLS.

Can I limit which IPs can send?

Yes. On each domain you can set allowed and blocked IPs, and also which addresses on the domain can act as the sender.

How many emails can I send?

As many as your plan includes each month, SMTP and API combined. New accounts also have an hourly and a daily limit that rise automatically as the account sends without problems.

Can I use the API instead of SMTP?

Yes. The same account and domains work for sending through the HTTP API, which helps when your network blocks SMTP ports or when you'd rather build sending straight into your code.

Where do I see whether an email arrived?

In the dashboard, under Email → Logs. Every email appears there with its status and history; filter by the SMTP channel to also see the rejected ones and why.

Connect your systems to an SMTP relay you control

Create your free account, verify your domain and set the server smtpmq.mailiqo.com in your application or device.

Create a free account