> For the complete documentation index, see [llms.txt](https://docs.messageflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.messageflow.com/email/message-statuses.md).

# Message Statuses

Every message sent through MessageFlow is assigned a status that reflects its stage in the delivery process - from the moment it's accepted into the system, through to potential rejection by the recipient's server.

Understanding these statuses helps you diagnose deliverability issues, monitor the quality of your recipient base, and make informed decisions about future sends. Below you'll find an overview of each status, along with example server messages and guidance on how to respond.

***

### Injected

The first status assigned to a message the moment it moves from your system into MessageFlow. It confirms the message was correctly received and passed on for further processing.

The number of messages with Injected status reflects how many emails were submitted to the system during a given period - this is the figure used for billing against your subscription package.

{% hint style="info" %}
Note: the Injected status does not yet mean the message has reached the recipient's inbox - it's only the first step in the sending process. Check the statuses below to follow the message's further journey.
{% endhint %}

***

### OK

The OK status confirms that the recipient's mail server accepted the message without rejecting it at any stage - the sending process completed successfully on a technical level.

This does not tell you which folder the email landed in - it could be the main inbox, but also Promotions, Updates, or Spam, depending on the filtering rules of the given mail provider. Providers don't share data on how they classify messages, so MessageFlow can't pass that information along either.

The OK status may come with an additional message, visible in the panel under status details, for example:

* **250 2.0.0 OK** - confirmation that the recipient's server correctly accepted the message.
* **250 2.0.0 Ok: queued as \[ID]** - the message was accepted by the recipient's server and placed in a verification queue (additional security screening); once the analysis is complete, the mail is either delivered or held.

***

### Softbounce

A soft bounce - the message wasn't delivered to the recipient, but the issue is likely temporary. Unlike a hard bounce, this status doesn't indicate a permanent error with the email address, and a future retry may succeed. The address is not added to the internal blacklist.

Most common causes:

* **a full recipient inbox**, e.g. 452-4.2.2 The recipient's inbox is out of storage space or 552 5.2.2 User is over quota;
* **temporary unavailability of the recipient's server**, e.g. during maintenance (Mailbox not available);
* **message size too large**, e.g. 552 Error: message too large.

You may also encounter the message Greylisted: Temporarily unable to process your email - this is an anti-spam mechanism that blocks messages from unknown senders until a retry is made. If the email comes from a legitimate source, a retry after a short delay should succeed; if the message keeps recurring, it's worth contacting the recipient server's administrator.

{% hint style="info" %}
Note: MessageFlow does not automatically retry sending on a Softbounce status - you'll need to resend the message from the system integrated with MessageFlow.
{% endhint %}

If a given address regularly returns Softbounce, check the detailed message that accompanies the status - it will point to the specific cause.

***

### Spambounce

Indicates that the message was rejected by the recipient's server on suspicion of spam or a potential threat - it doesn't reach the inbox or the Spam folder, but is blocked entirely at the server level.

This is caused by anti-spam filters configured on the recipient domain - they may react to too many links, oversized attachments, or missing authentication (SPF/DKIM/DMARC). A temporary block on the sending IP address can also occur in cases of bulk sending that violates a given provider's policies.

Example messages:

* 550 Spam message rejected.
* 550 Message discarded as high-probability spam
* 550-5.7.1 Gmail has detected that this message is likely unsolicited mail.
* 550-5.7.1 This message is not RFC 5322 compliant. There are multiple To headers.
* 554 IP=XXX.XXX.XX - None/bad reputation.
* 550-5.7.28 Gmail has detected an unusual rate of unsolicited mail...

{% hint style="info" %}
A message such as **550 5.7.1 ... part of their network is on our block list (S3150)** comes from Microsoft's servers and relates to a temporary IP block. In this case, it's worth reaching out to MessageFlow Customer Support, including your account name and the Message ID of an example message, to help with delisting.
{% endhint %}

The more often your messages receive a Spambounce status, the greater the risk that mail providers will start treating you as a source of unwanted content. If Spambounce appears regularly, it's worth reviewing your content and sending practices to improve deliverability.

***

### Hardbounce

A hard bounce - the message could not be delivered due to a permanent error, most often because the email address doesn't exist (a typo or a deleted account), or because the sender's address, domain, or IP is blocked on the recipient's side.

Example messages:

* 550-5.1.1 The email account that you tried to reach does not exist.
* 550 5.1.1 Account not found.
* 550 5.1.1 Recipient address rejected: User unknown.

Addresses that generate hard bounces lower the quality of your recipient base and your sender reputation. Mail providers seeing sends to non-existent addresses may treat the account as a potential spammer and restrict the deliverability of future messages.

{% hint style="info" %}
Messages with a Hardbounce status are automatically added to MessageFlow's internal blacklist - further attempts to send to that address will be blocked at the system level and will receive a Dropped status.
{% endhint %}

***

### Dropped

The message wasn't sent at all - the process was stopped at the MessageFlow panel level. Possible reasons include:

* the address is on the internal blacklist (e.g. it previously received a Hardbounce);
* the recipient previously reported a message as spam;
* the address was flagged as Abuse - the system detected potential misuse;
* the address is a spamtrap - used to detect bulk, unwanted sends;
* the recipient unsubscribed;
* the account's sending limit was exceeded (daily or monthly, as part of your package).

***

### Deferred

Sending was temporarily paused - MessageFlow was unable to establish a connection with the recipient's server right away. This is an intermediate status, not a final one: the system automatically retries delivery for the next 48 hours, after which the message receives a final status (e.g. OK or Hardbounce).

Most common causes: temporary technical issues on the recipient server, a hold placed by anti-spam filters for further analysis, or sending limits imposed by the mail provider (e.g. Gmail, Outlook).

Example messages:

* 452-4.2.2 The recipient's inbox is out of storage space
* Host or domain name not found. Name service error for name=gmial.com type=MX: Host not found, try again
* 421-4.7.28 Gmail has detected an unusual rate of mail originating from your domain... mail sent from your domain has been temporarily rate limited.

***

### Open

The Open status means the message was opened - one of the core indicators of sending effectiveness and recipient engagement.

Open tracking relies on an invisible pixel embedded in the message content - when it's loaded, the system registers the open.

{% hint style="info" %}
Note: the Open status can also appear when the recipient's mail client automatically loads images (even without the message actually being read), or when the email is opened by security systems, such as anti-spam filters.
{% endhint %}

***

### Track

Indicates that the recipient clicked a link contained in the message - one of the key engagement indicators, signaling that the content prompted a specific action.

The click-tracking system records every link click and logs it in detailed records.

{% hint style="info" %}
Note: clicks may also be registered by anti-spam filters that scan links before delivering the message to the recipient's inbox.
{% endhint %}

***

### Feedback

Also known as **spam\_complaint** - indicates that the recipient marked the message as spam or reported it as potentially harmful. This is an important signal that the content didn't meet the recipient's expectations.

{% hint style="info" %}
Note: not every mail provider shares information about a message being marked as spam - some (e.g. Gmail) only make this information available through their own internal tools.
{% endhint %}