> 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/imap/clients/shikari.md).

# Shikari

[Shikari](https://shikari.tech) reads the inbox continuously while it waits for a verification code. That behaviour is exactly what it should do — and it is why the [inbox window](/imap/inbox-window.md) matters more here than with any other client.

{% hint style="success" %}

## The recommendation

Give Shikari its **own app password**, with the inbox window set to **Last 15 minutes**.

Every read Shikari makes then covers a tiny, recent slice of mail instead of your entire history, so the code it is waiting for surfaces in seconds.
{% endhint %}

## Settings

<figure><img src="/files/BUAsQm2L5tx6wusDKm5I" alt="Shikari IMAP settings with a 15-minute inbox window"><figcaption></figcaption></figure>

| Field            | Value                                                         |
| ---------------- | ------------------------------------------------------------- |
| **Host**         | `mail.resifactory.net`                                        |
| **Port**         | `993`                                                         |
| **Security**     | SSL / TLS                                                     |
| **Username**     | Your login email, e.g. `you@buyers.resifactory.net`           |
| **Password**     | A dedicated [app password](/imap/app-passwords.md)            |
| **Inbox window** | **Last 15 minutes** — set on the app password, not in Shikari |

{% hint style="info" %}
The inbox window is **not** a Shikari setting. It lives on the app password in this console. Shikari simply sees a smaller mailbox as a result.
{% endhint %}

## Step by step

1. Open **App passwords → New**.

   <figure><img src="/files/ZPnfwGUWBvDFQhjC1F1S" alt="The new app password dialog"><figcaption></figcaption></figure>
2. **Label**: `shikari-main` — or one per Shikari instance if you run several.
3. **Scope**: **Unified**, so every mailbox you own is covered by the one connection.
4. **IMAP username**: leave as your login email.
5. **Inbox window**: **Last 15 minutes**.

   <figure><img src="/files/hocXiYnzDV5gNnZvz8hE" alt="Selecting Last 15 minutes"><figcaption></figcaption></figure>
6. **Create**, and copy the password — it is shown once.
7. In Shikari, enter host `mail.resifactory.net`, port `993`, SSL on, your login email as the username, and the app password.

## Why 15 minutes

A verification code is useful for a couple of minutes and worthless after ten. Everything older than that is weight Shikari would otherwise carry on every single read.

<figure><img src="/files/px0PYhPi1WuT1xCDhBNX" alt="Only messages inside the window are served"><figcaption><p>Only the recent slice is served. Everything older stays stored and stays searchable in the console.</p></figcaption></figure>

New mail still arrives **instantly** — the window trims old mail, it never delays new mail. A 15-minute window does not mean a 15-minute wait.

## If Shikari misses a code

Work down this list:

1. **Check `Last used`** on the app password row. If it reads `–`, Shikari never connected — this is a connection problem, not a mail problem. Go to [Troubleshooting](/imap/troubleshooting.md).
2. **Check the mail actually arrived.** Open the console [Inbox](/the-console/inbox.md) and search for the sender or the code. If it is not there, the message never reached your mailbox and no client setting will help.
3. **Check the mailbox's health.** On [Accounts](/the-console/accounts.md), find the mailbox and look at its status. `expired` or `degraded` means that mailbox is not reliably fetching.
4. **Consider a slightly wider window.** If a service sends its code slowly — several minutes after you request it — and Shikari waits a long time, **Last 1 hour** gives more slack at very little cost.

## Running several instances

Give each instance its **own app password**, all with the same 15-minute window:

| Label             | Scope                | Window          |
| ----------------- | -------------------- | --------------- |
| `shikari-1`       | unified              | Last 15 minutes |
| `shikari-2`       | unified              | Last 15 minutes |
| `shikari-batch-a` | batch → aug-drop-100 | Last 15 minutes |

Separate credentials mean `Last used` tells you which instances are alive, and revoking one does not disturb the others.

## Combining with other tools

Shikari's tight window does not stop other tools from seeing history. The window belongs to the credential, so a second app password with a 14-day window reads the same mail over a longer horizon at the same time. See [The inbox window](/imap/inbox-window.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 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/imap/clients/shikari.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.