> For the complete documentation index, see [llms.txt](https://docs.resifactory.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.resifactory.net/reference/faq.md).

# FAQ

## Connecting

<details>

<summary>What are my IMAP settings?</summary>

```
Host      mail.resifactory.net
Port      993
Security  SSL / TLS
Username  your login email
Password  an app password
Folder    INBOX
```

In clients that take host and port in **one** field — Refract among them — enter `mail.resifactory.net:993`.

[Connection settings](/imap/connection-settings.md)

</details>

<details>

<summary>Why will Refract not connect?</summary>

Almost always the missing port. The IMAP server field must read `mail.resifactory.net:993`. Refract does not add the port for you.

[Refract](/imap/clients/refract.md)

</details>

<details>

<summary>Can I use my sign-in password for IMAP?</summary>

No. IMAP only accepts an [app password](/imap/app-passwords.md). This is deliberate: an app password can be revoked on its own, scoped to one batch, limited by IP, and given its own inbox window.

</details>

<details>

<summary>Do I add each mailbox to my client separately?</summary>

No. You connect **once** and every mailbox you own is merged into a single `INBOX`. New mailboxes join it automatically.

Each message keeps its real recipient in the `To:` header, so tools that route by recipient still work.

</details>

<details>

<summary>Is there an SMTP server? Can I send mail?</summary>

No. The mail server is read-only. If your client asks for outgoing settings, leave them blank or point them at a service you already use.

</details>

<details>

<summary>What is my IMAP username?</summary>

Whatever the **IMAP username** column shows on the app password you are using — by default your login email, ending `@buyers.resifactory.net`.

</details>

## The inbox window

<details>

<summary>What is the inbox window?</summary>

A per-app-password limit on how far back that credential can see. It slides — a 15-minute window always means the last 15 minutes.

[The inbox window](/imap/inbox-window.md)

</details>

<details>

<summary>Does a 15-minute window delay my mail by 15 minutes?</summary>

No. New mail arrives immediately, whatever the window. The window trims the **back** of the view, never the front.

</details>

<details>

<summary>What window should I use?</summary>

| Job                | Window     |
| ------------------ | ---------- |
| Shikari            | 15 minutes |
| Verification codes | 1–6 hours  |
| Order tracking     | 7–14 days  |
| Reading by hand    | 1–3 months |

</details>

<details>

<summary>My client shows far less mail than the console. Why?</summary>

The inbox window, working as configured. Nothing is deleted — widen the window and it comes straight back.

</details>

<details>

<summary>Does the window delete anything?</summary>

No. Mail outside it is still stored, still in the console [Inbox](/the-console/inbox.md), and returns the instant you widen the window.

</details>

## App passwords

<details>

<summary>I lost my app password. Can I see it again?</summary>

No. It is shown once and stored hashed. Revoke it and create a replacement.

</details>

<details>

<summary>How many should I have?</summary>

One per tool. Revoking one then never breaks another, and **Last used** tells you which tools are actually running.

</details>

<details>

<summary>What happens when I revoke one?</summary>

Live IMAP sessions using it are disconnected **immediately**, and it can never be used again. The row stays in the list, greyed out, so you keep the history.

</details>

<details>

<summary>Does changing my sign-in password break my IMAP clients?</summary>

No. App passwords are independent. Changing your sign-in password signs out web sessions only.

</details>

<details>

<summary>Can two app passwords share a username?</summary>

Yes. The **password** selects which credential — and therefore which scope and window — you are using. That is how you keep one username and vary the settings per tool.

</details>

## Mail

<details>

<summary>A code never arrived. Where do I start?</summary>

1. **App passwords → Last used.** If it reads `–`, your client never connected — that is a connection problem.
2. **Console Inbox.** Search for the sender or the code. If it is not there, the message never reached your mailbox.
3. **Accounts.** Check that mailbox's status.
4. **The window.** Too narrow for how long the service took to send?

[Troubleshooting](/imap/troubleshooting.md)

</details>

<details>

<summary>Does spam-filtered mail reach me?</summary>

Yes. Mail a provider filed as spam is still fetched and still appears in your `INBOX` here. There is no separate Junk folder to check.

</details>

<details>

<summary>How fast does mail arrive?</summary>

Seconds. Push notifications and always-on connections mean the server usually has a message within moments of delivery, and IDLE pushes it to your client immediately after.

</details>

<details>

<summary>Can I delete mail?</summary>

From the console [Inbox](/the-console/inbox.md), yes — and it is permanent, with no trash and no undo.

Over IMAP, no. The `\Deleted` flag is accepted but nothing is expunged.

</details>

<details>

<summary>How long is mail kept?</summary>

See **Message retention** on [Settings](/the-console/settings.md). Mail older than that is pruned permanently. If you need it kept longer, archive it yourself.

</details>

## Mailboxes

<details>

<summary>What do the statuses mean?</summary>

| Status        | Meaning                                                |
| ------------- | ------------------------------------------------------ |
| 🟢 `healthy`  | Fetching normally.                                     |
| 🟠 `degraded` | Reachable but unreliable right now. Usually temporary. |
| 🔴 `expired`  | Cannot currently fetch. Try **Resubscribe**.           |
| 🔵 `pending`  | New, not yet confirmed.                                |

</details>

<details>

<summary>A few mailboxes are degraded. Should I worry?</summary>

Not at a small number — providers throttle and sessions expire routinely. Watch the **Healthy share** on the [Dashboard](/the-console/dashboard.md); a sharp drop or a share that stays low is what merits attention.

</details>

<details>

<summary>How do I get the individual mailbox passwords?</summary>

**Accounts** → right-click → **View WTok credentials…** for one, or **Export** for many. [Exporting credentials](/credentials/exporting.md)

</details>

<details>

<summary>What is a batch?</summary>

A named group of mailboxes, usually one per purchase. Batches let you scope an app password, export a purchase in one action, and filter every list. [Batches](/the-console/batches.md)

</details>

## Account

<details>

<summary>I forgot my password.</summary>

**Reset it by email** on the sign-in screen, if you have a confirmed recovery address. The code expires in 10 minutes and works once.

Without a recovery address, this needs a manual request — which is why the console nags you to set one.

</details>

<details>

<summary>"Your mail-server subscription has expired."</summary>

Access has lapsed. Your mailboxes and mail are untouched. Contact whoever sold you access.

</details>

<details>

<summary>Can I give someone else access to part of my mail?</summary>

Yes — a [batch-scoped](/imap/scopes.md) app password. They see that batch's mail over IMAP and nothing else, and you can revoke it in one click.

</details>

<details>

<summary>Why can I not see a page someone else mentioned?</summary>

Your access covers the pages in your navigation. Anything else is a different role's surface and is not part of your account.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.resifactory.net/reference/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.