Fake Inbox#

What is a fake SMTP inbox?#

MockLane includes a fake SMTP inbox that captures all outgoing emails from your application. Instead of accidentally emailing real customers during development and testing, all emails land safely in your workspace inbox.

This is especially critical when testing with production data — no more "sorry, that was a test email" moments.

What SMTP settings do I use?#

Each workspace gets unique SMTP credentials. Navigate to your workspace's Inbox tab and click Show SMTP Credentials to get:

  • Host — inbox.mocklane.com
  • Port — 25, plain SMTP with no TLS
  • Username — Auto-generated per workspace (e.g., ws_abc123)
  • Password — Random token, can be regenerated anytime

Point your application's email configuration to these credentials. All emails sent through this SMTP server will be captured and displayed in your inbox — regardless of the recipient address.

Workspace inbox SMTP settings panel showing host, port, username and password
Every workspace has its own SMTP credentials. Point your app's mail settings at these.

Using the Inbox#

The inbox provides a full email client experience:

Workspace inbox listing a received message titled Welcome to Acme
Mail your app sends lands here instead of a real mailbox.
  • Email list — See sender, subject, timestamp, and unread indicators
  • HTML Preview — Renders HTML emails in a sandboxed preview (safe, no script execution)
  • Plain Text — View the plain text version of the email
  • Headers — Inspect all email headers (Message-ID, Content-Type, etc.)
  • Attachments — Download attached files directly from the inbox
A received email open on the HTML Preview tab, rendered as the recipient would see it
Read the rendered HTML, the plain text, or the raw headers.

How do I send test email from Node, Python, Django or Rails?#

Point your application's existing mail configuration at the credentials from your workspace's Inbox tab. Nothing else changes: every message your code already sends lands in MockLane instead of a real recipient.

// dotnet add package MailKit
using MailKit.Net.Smtp;
using MailKit.Security;
using MimeKit;

var message = new MimeMessage();
message.From.Add(MailboxAddress.Parse("app@yourservice.com"));
message.To.Add(MailboxAddress.Parse("customer@example.com"));
message.Subject = "Order confirmed";
message.Body = new TextPart("html") { Text = "<h1>Thanks for your order</h1>" };

using var client = new SmtpClient();
// SecureSocketOptions.None: MockLane speaks plain SMTP. MailKit would
// otherwise try STARTTLS and fail in a way that reads as a bad password.
await client.ConnectAsync("inbox.mocklane.com", 25, SecureSocketOptions.None);
await client.AuthenticateAsync("ws_your_workspace_id", "your-smtp-password");
await client.SendAsync(message);
await client.DisconnectAsync(true);
Port 25 is blocked on many networks. Most cloud providers — AWS, Google Cloud and Azure among them — block outbound port 25 by default, and so do a lot of office and home ISPs. If a connection simply times out rather than being refused, that is almost always what has happened, and it is a property of the network you are sending from rather than of your credentials. Sending from a local development machine on a normal broadband connection usually works; sending from a cloud VM usually does not.
Every snippet above uses plain SMTP with no TLS, because that is what the server speaks. Leaving STARTTLS enabled — PHPMailer and MailKit both attempt it by default — produces a failure that reads like a rejected password.

Forwarding sandbox mail to a real address#

A sandbox inbox (a standalone mailbox at {prefix}@inbox.mocklane.com, separate from a workspace's SMTP inbox) can forward every message it receives to up to three real addresses. On the sandbox's Forwarding card, enter the addresses separated by a semicolon and save. Forwarding is on whenever the field has addresses in it; clear the field and save to turn it off. It applies to mail that arrives after you save, not to messages already in the sandbox.

Forwarded mail is sent by MockLane, not relayed as-is — it arrives from a MockLane address with Reply-To set to the original sender, so replying reaches them. Because the message is not from the original sender, any rule in your real inbox that filters on that sender will not match the forwarded copy. The original message is always kept in the sandbox as well; forwarding sends an additional copy, it does not move the message.
  • Limits: up to 100 forwarded messages per sandbox per hour and 500 per account per day. These count messages, not destinations — one message forwarded to three addresses counts once.
  • Every forwarded message includes a stop link. The recipient can use it to end forwarding to their own address at any time, and once an address has been stopped this way it cannot be added back — MockLane rejects it if you try. Marking a forwarded message as spam has the same effect: forwarding to that address stops automatically. That includes you: if you own the destination inbox, do not click the stop link on an address you want to keep — stopping is permanent and there is no undo.
  • If a message is too large to forward with its attachments, MockLane sends the forwarded copy without them and notes how many were dropped. The attachments themselves are not lost — they stay downloadable from the original message in the sandbox.

MockLane © 2026 · Built for developers

Go to Dashboard