> For the complete documentation index, see [llms.txt](https://docs.yeymail.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yeymail.com/using-yeymail/sending-and-replying/other-mail-apps.md).

# Other mail apps

Anything that lets you add an outgoing (SMTP) server will work. The settings are the same everywhere:

| Setting           | Value                                      |
| ----------------- | ------------------------------------------ |
| Server / hostname | `mx1.yeymail.com`                          |
| Port              | `587`                                      |
| Encryption        | **STARTTLS**                               |
| Authentication    | Normal password                            |
| Username          | the full alias, e.g. `shop@yourdomain.com` |
| Password          | the SMTP password set on that alias        |

Apps this is known to work in include eM Client, Spark, Canary, BlueMail, Mailspring, K-9 Mail and FairEmail, plus anything that speaks standard SMTP: scripts, a CRM, a website contact form, or a printer that emails scans.

## Naming differences

Every client words encryption slightly differently. All of these mean the same thing and are what you want:

* **STARTTLS**
* **TLS (explicit)** or **Explicit TLS**
* **STARTTLS (always)**
* On Apple platforms, **Use SSL** *combined with port 587*

What you do **not** want is **SSL/TLS (implicit)**, **SMTPS**, or anything that switches the port to **465**. We don't run that port, so the app will hang and then report a timeout.

## Sending from code

Standard SMTP with STARTTLS and `LOGIN`/`PLAIN` authentication. For example, in Python:

```python
import smtplib
from email.message import EmailMessage

msg = EmailMessage()
msg["From"] = "shop@yourdomain.com"     # must match the login below
msg["To"] = "someone@example.com"
msg["Subject"] = "Hello"
msg.set_content("Sent through YeyMail.")

with smtplib.SMTP("mx1.yeymail.com", 587) as s:
    s.starttls()
    s.login("shop@yourdomain.com", "the-alias-smtp-password")
    s.send_message(msg)
```

The `From` header must match the address you log in with (see below).

## Rules that apply everywhere

**Send from the alias you signed in as.** The server rejects a message whose From address differs from the alias that authenticated. One alias, one password, one identity. You can't authenticate once and send as several.

**Encryption is required.** The server won't accept your password over an unencrypted connection, so an app configured for "None" will fail to authenticate rather than silently sending in the clear.

**25 MB per message**, attachments included. That's the same ceiling Gmail, Outlook and iCloud enforce, so anything we accept is something the recipient's provider will accept too.

**Your connection details don't travel with the message.** Your IP address, your provider and the name of your mail app are removed before it leaves us, so a recipient can't work out where you sent it from or link two aliases to one machine.

**Rate limits apply.** Fair-use limits keep the service off blocklists; ordinary human sending will never reach them.

## Webmail that won't work

Most webmail services other than Gmail don't let you send through an outside SMTP server at all; there's simply no setting for it. If you've looked through your provider's settings and found nothing, that's why, and no configuration on our side will change it.

You have two options:

* Use a mail app from this section on your computer or phone. It can read the same inbox you already use.
* Or just **reply** instead of composing. Replying already goes out as your alias from any inbox, anywhere, with nothing set up. It only needs the other person to have written first.


---

# 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.yeymail.com/using-yeymail/sending-and-replying/other-mail-apps.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.