> For the complete documentation index, see [llms.txt](https://postman-v1.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postman-v1.guides.gov.sg/campaign-guide-email/email/halting-of-email-campaigns.md).

# Bounced Emails and Halted Campaigns

Please read through this guide to understand the difference between hard and soft bounces, as well as halted campaigns.

## Bounces

Emails like <abc@gmail.com> may look like a well-formatted email address, but if it is not managed by a real human being, services like Google will send a bounce message when the email is sent out. This is considered a hard bounce, which increases Postman's bounce rate and negatively affects Postman's reputation score.

1. **Hard bounce:** Invalid email addresses.
2. **Soft bounce:** Out-of-office messages or message notifications that the recipient's email inbox is full.

## Reputation Score & Blacklisting Mechanism

Hard bounces affect Postman Legacy's reputation score. A reputation score is a measure of the email service reputation. **Postman Legacy needs to maintain a low bounce rate in order to have a good reputation score.**&#x20;

{% hint style="info" %}
Think of this as having good credit from the bank. Banks need you to have a good credit score in order to provide a credit card for transactions. Similarly, Postman Legacy needs a good reputation score to send emails to Internet Service Providers (ISPs) in order to deliver emails to recipients.
{% endhint %}

This is also why we have a **blacklisting mechanism**. When an email hard bounces in one campaign, it is added to the blacklist. Any subsequent campaigns emails would then not be sent if it is on the blacklist, preventing a bounce and reducing impact on reputation score.

We need your help as a user to reduce the occurrence of hard bounces.:

* Ensure that your mailing list is clean before you send an email campaign through our service.&#x20;
* We understand that the first email campaign that you send out might contain a lot of invalid email addresses. Please use the bounce and blacklisting report once your campaign is over to clean and maintain your contact list.

### Halted Campaigns

A campaign will be halted when there are **too many hard bounces** (due to invalid email addresses, which are addresses that do not exist), to reduce impact on Postman Legacy's reputation score.&#x20;

Postman Legacy encourages all users to maintain **clean contact lists** as a best practice.

If your halted campaign has high time sensitivity or high urgency (e.g. impact on MoP is high/ops will be severely impaired if campaign is not immediately sent out), please [contact us](https://go.gov.sg/postman-contact-us) for assistance.

## What are some ways to ensure my contact list is clean?

Here are some tips in building and maintaining your mailing list:

1. **Ensuring verified email collection upstream**: Consider using FormSG’s `verified email field` to collect email addresses from the intended recipients. This will ensure that you only collect email addresses from people who have access to the email account.
2. **Remove invalid email addresses from your mailing list**: We know that email addresses can become invalid over time when recipients change email addresses. You should always clean your mailing list regularly. You can do this easily with our export button on the campaign dashboard page. If an email campaign has bounced emails (hard bounce), it will be captured in the .csv file.
3. **Check for formatting errors:** Make sure that the format for the email is correct, e.g. <recipient@example.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://postman-v1.guides.gov.sg/campaign-guide-email/email/halting-of-email-campaigns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
