> 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/connection-settings.md).
# Connection settings
## The settings
| Setting | Value |
| ------------------- | --------------------------------------------------- |
| **Host / server** | `mail.resifactory.net` |
| **Port** | `993` |
| **Encryption** | SSL / TLS (implicit) — **not** STARTTLS |
| **Username** | Your login email, e.g. `you@buyers.resifactory.net` |
| **Password** | An [app password](/imap/app-passwords.md) |
| **Authentication** | Normal password (`LOGIN` / `PLAIN`) |
| **Folder** | `INBOX` — the only one |
| **Outgoing / SMTP** | None. The server does not send mail. |
{% hint style="warning" %}
### Clients that want host and port in one field
Some tools — **Refract** among them — take a single "IMAP server" string and do **not** append the port for you. In those, enter:
```
mail.resifactory.net:993
```
Entering `mail.resifactory.net` on its own will fail to connect properly. See [Refract](/imap/clients/refract.md).
{% endhint %}
## What each setting means
### Host
`mail.resifactory.net` is the mail server. It is the same host for everyone — there is no per-customer hostname.
You can confirm it yourself: **Settings → Service → Hostname** shows the host your server is running on, with a copy button.
Hostname and IMAP port, straight from the server.
### Port 993 and TLS
Port `993` is IMAPS — TLS is established **before** any IMAP conversation starts. This is sometimes called "implicit TLS" or just "SSL".
* **Do not** use STARTTLS. It is not offered.
* **Do not** use port 143. Nothing is listening there.
* There is no unencrypted option. Your credentials never cross the network in the clear.
If your client asks you to choose, the right answer is whichever option it calls `SSL/TLS`, `IMAPS`, or `Implicit`.
### Username
Your username is the value in the **IMAP username** column of the app password you are using.
Whatever this column says is what your client should send as the username.
By default that is **your login email** — the `@buyers.resifactory.net` address you sign in with. You can set a different username per app password if you want a tool to connect under its own name; see [App passwords](/imap/app-passwords.md).
Usernames are **case-insensitive**. Leading and trailing spaces are ignored — but a space in the middle is not, so watch out for copy-paste artefacts.
### Password
Always an [app password](/imap/app-passwords.md), never your sign-in password.
App passwords are shown once when created. If you no longer have it, revoke that one and create a replacement — there is no way to read an existing one back.
### Folder
There is exactly one folder: **`INBOX`**.
Every mailbox you own is merged into it. There is no Sent, Drafts, Junk or Archive over IMAP. If your client insists on mapping special folders, point them all at `INBOX` or leave them unset.
{% hint style="info" %}
Mail that a provider filed as spam is still fetched and still appears in your `INBOX` here — you do not need a separate Junk folder to find it.
{% endhint %}
## Telling mailboxes apart
Since everything is merged, the way to know which mailbox a message went to is the **`To:` header** — it carries the real mailbox address.
Most tools that route by recipient will do the right thing automatically. If you are writing your own code, read the envelope's `To:` rather than assuming one account per connection. See [Your own code](/imap/clients/custom-code.md).
## Connection etiquette
The server is happy with normal client behaviour, but two habits will make your setup faster and more reliable:
1. **Use IDLE, not aggressive polling.** IDLE is supported: the server pushes new mail to your client the moment it arrives. A client sitting in IDLE gets mail faster than one polling every few seconds, and costs far less on both ends.
2. **Keep one connection per credential.** Opening many simultaneous connections with the same app password does not make mail arrive sooner.
Repeated failed logins will temporarily lock out further attempts from your address and IP — see [Troubleshooting IMAP](/imap/troubleshooting.md).
## Quick check from a terminal
If you want to prove the server is reachable before touching your client:
```bash
openssl s_client -connect mail.resifactory.net:993 -crlf
```
A successful connection prints the certificate chain and then an IMAP greeting beginning `* OK`. Press **Ctrl+C** to exit.
To go one step further and check the credential itself:
```
a1 LOGIN you@buyers.resifactory.net your-app-password
a2 SELECT INBOX
a3 LOGOUT
```
`a2` responds with an `EXISTS` count — the number of messages that credential can currently see. If that number is much smaller than you expected, your [inbox window](/imap/inbox-window.md) is doing its job.
---
# 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/connection-settings.md?ask=&goal=
```
`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.