> 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/aycd.md).

# AYCD

There are two ways to use your mailboxes with AYCD. Which one you want depends on whether AYCD needs to hold each mailbox individually, or just needs to read the mail.

## Option 1 — import the mailboxes (AYCD Email Accounts CSV)

The console can produce AYCD's Email Accounts CSV directly, with the columns already filled in.

From **Batches**, right-click a batch → **Export AYCD CSV**:

<figure><img src="/files/gfy3jxhj8sXvBS1aDHWX" alt="The batch context menu with Export AYCD CSV"><figcaption></figcaption></figure>

The file is AYCD's standard 34-column Email Accounts format. The columns that matter are filled in for you:

| Column       | Value                                                                  |
| ------------ | ---------------------------------------------------------------------- |
| Provider     | `Outlook`                                                              |
| Username     | The mailbox login                                                      |
| Password     | The mailbox password                                                   |
| Port         | `993`                                                                  |
| Requires SSL | `true`                                                                 |
| Login Type   | `OAuth2`                                                               |
| Category     | Pre-filled; change it in AYCD after import if you want a different one |

Import it into AYCD as an Email Accounts file. Mailboxes without a stored password are skipped, so every row in the file is usable.

{% hint style="warning" %}
This file contains real mailbox passwords. Treat it like any other credential file — see [Keeping credentials safe](/credentials/security.md). Every export is recorded.
{% endhint %}

## Option 2 — one IMAP connection for everything

If you would rather not add mailboxes one at a time — or you are running into a cap on how many accounts a tool will hold — point AYCD at the unified inbox instead:

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

To this connection you have **one** account, no matter how many mailboxes you own. Each message still carries its true recipient in the `To:` header, so routing by recipient continues to work.

Set an [inbox window](/imap/inbox-window.md) on the app password to match the job — **Last 1 hour** for codes, **Last 7 days** if it also tracks orders.

## Which to choose

|                                            | Import CSV      | Unified IMAP     |
| ------------------------------------------ | --------------- | ---------------- |
| Tool needs each mailbox as its own account | ✅               | ❌                |
| Tool caps how many accounts you can add    | ❌               | ✅                |
| New mailboxes appear without reconfiguring | ❌ re-export     | ✅ automatic      |
| One credential to revoke                   | ❌               | ✅                |
| Passwords stored in the tool               | Every mailbox's | One app password |

For most people the unified connection is less work and safer — one credential in one place, revocable in one click.

## Other export formats

The same context menu offers plain lists if you need them elsewhere:

* **Export emails** — logins only, one per line.
* **Export email:password** — `login:password` lines, mailbox password or WTok password.

Full detail: [Exporting credentials](/credentials/exporting.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/aycd.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.
