> For the complete documentation index, see [llms.txt](https://docs.emaillabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emaillabs.io/en/guides/technical-aspects-of-emails-and-integration/message-statuses-what-do-they-mean-and-how-to-use-them.md).

# Message Statuses – What Do They Mean and How to Use Them?

While using the EmailLabs panel, every message you send receives a specific status. These statuses provide key information about the delivery process - from the moment the message is accepted by our system, through to its potential rejection by the recipient's server.

Correctly interpreting these statuses is essential for effective deliverability management, diagnosing issues, and optimizing campaigns. In this article, we explain in detail the meaning of each status and indicate what actions can be taken based on the information obtained.

***

### Injected

This is the first status assigned to all messages sent from your system to the EmailLabs Panel. It means the system has successfully received the messages and started further processing.

The number of messages with the Injected status shows how many emails were sent to the system within a given period. These are the messages taken into account when billing your subscription package.

{% hint style="info" %}
Remember! The Injected status does not yet mean the message has been delivered to the recipient's server – it is only the first step in the entire sending process.
{% endhint %}

If you want to track the further path of your messages, check the subsequent statuses in the EmailLabs Panel.

***

### OK

OK means the message was successfully accepted by the recipient's mail server. This status confirms the email was not rejected at the server level and the sending process was completed successfully.

The OK status confirms the email was received by the receiving server, but it does not tell us which folder the message ended up in. It may land in the Primary inbox, but also in Promotions, Notifications, or Spam - this depends on the filtering rules of the given mail provider. Keep in mind that mail providers do not share information about message classification.

The OK status may come with an additional message - in the EmailLabs panel you can find it in the message log, in the status details field. Example messages are listed below:\
\
**250 2.0.0 OK** - This message confirms the email was correctly accepted by the recipient's server.

**250 2.0.0 Ok: queued as \[ID]** - In this case, the message was received by the receiving server and then added to a so-called queue. This means the email required additional verification by security algorithms. After the analysis, the email may remain in the queue or be delivered to the inbox.

***

### Softbounce

Softbounce indicates that the message was not delivered to the recipient, but this may only be a temporary unavailability of the receiving server. Unlike a hard bounce, this status does not indicate a permanent error with the email address, and resending in the future may succeed. Such an address is not added to the panel's internal Blacklist.

The most common causes of a Softbounce are:

Najczęstsze przyczyny Softbounce to:

* **Full inbox** – an example message you might see is:
  * 452-4.2.2 The recipient's inbox is out of storage space, or
  * 552 5.2.2 User is over quota (in reply to RCPT TO command);
* **Recipient server temporarily unavailable** - e.g. during technical maintenance (Mailbox not available);
* **Message too large** – 552 Error: message too large - this message appears when an email exceeds the allowed size limit.

You may also encounter the following message - Greylisted: Temporarily unable to process your email. This means the recipient's server has temporarily rejected the message due to a greylisting mechanism. This is an anti-spam technique that blocks emails from unknown senders, expecting them to be resent.

If the message comes from a legitimate server and is resent after a short time, it should be accepted. If the message keeps recurring, we recommend contacting the recipient server's administrator for details on the reason and to request the sender be added to the allowlist.

{% hint style="info" %}
Remember! In the case of a Softbounce status, our system does not make automatic attempts to redeliver the message. If you want to try delivering the message again, you need to resend it from the mail system integrated with EmailLabs.
{% endhint %}

If a given address frequently receives the Softbounce status, it's worth checking the detailed message returned along with the soft bounce, as it will indicate the reason it was received.

***

### Spambounce

The Spambounce status indicates that your message was rejected by the recipient's server due to suspicion of spam or a potential threat. This means the email did not reach the inbox or the Spam folder, it was completely blocked at the server level.

Spambounce rejections result directly from the anti-spam filters set for the recipient's domain. Algorithms may flag the content of a message as suspicious, for example due to an excess of links, oversized attachments, or missing proper authentication. You may also occasionally receive a temporary block on your IP address in the case of mass sending that violates a given ISP's rules.

Some messages may be very general, such as:

**550** S*pam message rejected.*

**550** *Message discarded as high-probability spam (in reply to end of DATA command).*

**550-5.7.1** \[XXX.XXX.XX] *Gmail has detected that this message is 550-5.7.1 likely unsolicited mail.*

Or they may point to a specific element that needs to be verified:

**554** IP=XXX.XXX.XX - *None/bad reputation. Ask your postmaster for help or to contact <tobr@rx.t-online.de> for reset.*\
\
**550-5.7.28** \[XXX.XXX.XX] *Gmail has detected an unusual rate of 550-5.7.28 unsolicited mail originating from your IP address. To protect our 550-5.7.28 users from spam, mail sent from your IP address has been blocked.*

You may also often notice the following message:\
\
**550 5.7.1** *Unfortunately, messages from \[XXX.XXX.XX] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3150). You can also refer your provider to <http://mail.live.com/mail/troubleshooting.aspx#errors>. (in reply to MAIL FROM command).*

{% hint style="info" %}
This message is returned by Microsoft's servers in connection with a temporary block placed on the IP address. If you notice this message, please write to our Customer Support Department - <support@emaillabs.io> - who will contact the mailbox provider to arrange delisting. In your message, please include your account name and the Message ID of an example message.
{% endhint %}

The more often your emails receive the Spambounce status, the greater the risk that mail providers will consider you a sender of unwanted content. This can lower your reputation and hinder deliverability. If the Spambounce status appears regularly, it's worth analyzing your sending practices and adjusting your strategy to improve deliverability.

***

### Hardbounce

Hardbounce means your message could not be delivered due to a permanent error. This most often happens when the email address does not exist (it may contain a typo or have been deleted) or in connection with a block on receiving messages from your email address, domain, or IP address.

Email addresses with a hard bounce are an unwanted part of your recipient database - not only will you fail to deliver messages to them, but having too many of them can harm your sender reputation. Mail providers, seeing sends to non-existent addresses, may treat you as a potential spammer and restrict the deliverability of your emails.

As soon as you notice an increase in the Hardbounce status, check the messages you're receiving, they will let you know the specific reason for the hard bounce.

Below are example delivery details returned along with this status:

**550-5.1.1** *The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces.*\
\
**550 5.1.1** *Account not found.*

**550 5.1.1** *Recipient address rejected: User unknown (in reply to RCPT TO command).*

{% hint style="info" %}
At EmailLabs, we care about protecting your reputation as a sender (both your IP address and domain), which is why messages marked as hardbounce are automatically added to the internal Blacklist. This means that further attempts to send to these addresses will be blocked at the system level (they will receive the dropped status).
{% endhint %}

***

### Dropped

The Dropped status means the message was not sent, and the sending process was halted at the EmailLabs panel level. This can result from several reasons:

* the address is on the internal Blacklist - e.g. it previously received a Hardbounce status;
* the recipient reported the message as spam, meaning they no longer want to receive further emails;
* the address was flagged as Abuse - the system detected potential misuse;
* the email is a spamtrap - a so-called "spam trap" used to detect mass and unwanted sends;
* the user unsubscribed, so you can no longer send them messages;
* the account has exceeded its sending limit - e.g. a daily or monthly limit within your package.

***

### Deferred

Deferred means the sending of the message was temporarily put on hold - EmailLabs could not immediately establish a connection with the recipient's server. However, this is not a final status, as our system makes automatic attempts to redeliver the email over the following 48 hours. The message then receives a final status, e.g. OK.

The most common reasons for receiving the Deferred status are temporary technical issues on the recipient server's side, a temporary hold placed on the email by anti-spam filters for additional analysis, or exceeding sending limits imposed by a given mail provider (e.g. Gmail, Outlook).

Below are examples of messages returned by receiving servers along with the Deferred status:

**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 SPF 421-4.7.28 domain \[xxx.com]. To protect our users from spam*, **421-4.7.28** *mail sent from your domain has been temporarily rate limited*.

***

### Open

The Open status indicates that your message was opened. This is an important indicator that lets you monitor the effectiveness of your send and the level of user engagement.

Open tracking works based on an invisible image (tracking pixel) placed in the content of the email. When the email is opened, the image is downloaded, and the system registers the opening.

{% hint style="info" %}
Remember! The Open status may also appear if the mail system automatically loads images, even if the recipient hasn't actually read the message, or if the email is opened by security systems (e.g. anti-spam filters).
{% endhint %}

***

### Track

This status indicates that the recipient clicked a link included in your message. This is one of the key engagement indicators - it means the content of the email was interesting enough that the recipient decided to take a specific action.

The click-tracking system registers every click on a link contained in the message and records it in detailed logs.

{% hint style="info" %}
Remember! Clicks can also be triggered by anti-spam filters that scan links before delivering the message to the recipient's inbox.
{% endhint %}

***

### Feedback

The Feedback status, also known as **spam\_complaint**. It indicates that the recipient marked the message as spam or reported it as potentially dangerous. This is an important signal that your message did not meet the recipient's expectations and may have been considered unwanted.

{% hint style="info" %}
Remember! Not every provider shares information about a message being marked as spam. Some providers, such as Gmail, make this information available through their internal tools.
{% endhint %}