---
title: "Email Account & Inbox"
space: "Frappe Framework"
url: "https://prilk.com/docs/frappe-framework/email"
updated: "2026-09-07"
---

## Email Account & Inbox

Frappe's Email module covers two flows: **sending** (outgoing) and **receiving** (incoming).

### Outgoing Email
**Email Account → New**:
- SMTP server, port, encryption (STARTTLS / SSL)
- Email address and password (or OAuth for Gmail / Microsoft 365)
- Mark as **Default Outgoing**

You need at least one outgoing account or transactional emails (notifications, password reset, PDF attachments) can't be sent.

### Incoming Email
Same form, but enable IMAP/POP3:
- IMAP/POP server, port, encryption
- Credentials
- **Email Sync Option** (`UNSEEN` — only new messages)

Incoming emails appear as **Communications** in the desk inbox. They auto-link by subject reference (e.g., "Re: SO-0001" attaches to Sales Order SO-0001), keeping threads stuck to the right document.

### Email Domain
Reusable SMTP/IMAP settings shared by multiple Email Accounts on one domain. Define once in **Email Domain**, then point each Email Account at it. Cleaner than repeating credentials.

### Inbox
Each user with an inbox-enabled Email Account gets a Gmail-lite Inbox view on the desk. Read, reply, archive. Replies thread back to the originating document.

### OAuth
For Gmail and Microsoft 365, prefer OAuth over App Passwords — more reliable, fewer revocations. Frappe drives it through a **Connected App** on the Email Account. See [Email with Microsoft 365](/docs/frappe-framework/email-microsoft-365) for the full setup, including the redirect URI and UPN traps.

### Bounces and queue
**Email Queue** lists every outbound message with status. Failures stay visible — review, fix, retry manually.