> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/troubleshooting/emails-not-arriving.md).

# Emails not arriving

What to check when your recipients don't get request emails, or you don't get emails from Pipefile.

## Where Pipefile emails come from

| Email                                                                  | From                                                     | Replies go to          |
| ---------------------------------------------------------------------- | -------------------------------------------------------- | ---------------------- |
| Requests and reminders to your recipients                              | Your name (or your team alias) at `noreply@pipefile.com` | Your own email address |
| Emails to you: verification, new device, password reset, notifications | Pipefile at `noreply@pipefile.com`                       | Not monitored          |

Adding `noreply@pipefile.com` to your contacts or your organization's allowlist is the most reliable fix for both.

## Your recipient didn't get the request

Open the request and look at the recipient's details.

**The address shows "bounced".** The email couldn't be delivered, so Pipefile stopped emailing that address. Check the address for typos and fix it on the [contact](/team-and-account/contacts.md) if needed. If the address is right (for example their mailbox was full), click the **Retry Later** icon next to "bounced" to clear it, then use **Send reminder**.

**The address shows "marked as spam".** The recipient, or their email provider, reported a Pipefile email as spam, and we've stopped emailing that address. Ask the recipient to look in their junk folder, mark the email as not spam, and add `noreply@pipefile.com` to their contacts. Then email <support@pipefile.com> to have the address re-enabled.

**The phone number shows "unreachable".** Text messages to that number failed. Check the number, including the country code.

**No warning shows.** The email was probably delivered but filtered:

1. Ask the recipient to search their inbox, spam or junk folder, and any "Promotions" or "Other" tab for your name or the request subject.
2. Many business email systems hold messages in a quarantine the recipient can't see. Ask them to check with their IT team and allow `noreply@pipefile.com`.
3. Click **Send reminder** on the request to send the link again. A manual reminder also reaches recipients who unsubscribed from automatic reminders.

{% hint style="info" %}
If your plan includes SMS reminders, adding the recipient's mobile number gives them a second way to receive the link. See [SMS reminders](/reminders-and-notifications/sms-reminders.md).
{% endhint %}

## You aren't getting emails from Pipefile

1. Search your spam, junk and quarantine folders for `noreply@pipefile.com`.
2. Add `noreply@pipefile.com` to your contacts, or ask your IT team to allow it.
3. For upload, comment and expiration alerts, check that they're turned on in [Account → Notification Settings](https://pipefile.com/dashboard/settings/account#notifications). See [Your notification settings](/reminders-and-notifications/notification-settings.md).
4. Check that the email on your account is correct in [Account → Basic Information](https://pipefile.com/dashboard/settings/account#basic-information).

Waiting for a new-device or password-reset email? Those links expire, so use the newest one. See [Expired or invalid links](/troubleshooting/expired-links.md).

Still missing? Email <support@pipefile.com> with the recipient's address and the time you sent the request.

## Related

* [Login issues](/troubleshooting/login-issues.md)
* [Reminders and notification sequences](/reminders-and-notifications/reminder-sequences.md)


---

# 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://support.pipefile.com/troubleshooting/emails-not-arriving.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.