|
1
|
# Mail |
|
2
|
|
|
3
|
Mail is the domain mail-routing product. It's forwarding-first today, and it can |
|
4
|
now store inbound message history too. |
|
5
|
|
|
6
|
## What you can do |
|
7
|
|
|
8
|
- Run one Mail app per domain |
|
9
|
- Set up many inbox routes on a Mail app |
|
10
|
- Forward inbound mail where it needs to go |
|
11
|
- Store inbound message history |
|
12
|
|
|
13
|
## How it fits together |
|
14
|
|
|
15
|
- A project can have many Mail apps. |
|
16
|
- One Mail app maps to one domain. |
|
17
|
- One Mail app can have many inbox routes. |
|
18
|
|
|
19
|
Day to day, you work with **inboxes**, **forwarding**, and **stored messages**. |
|
20
|
The domain setup — DNS, bucket, prefix, and shared routing — lives on the Mail |
|
21
|
app's setup page, out of the way of everyday inbox work. |
|
22
|
|
|
23
|
## Getting started |
|
24
|
|
|
25
|
1. Create a Mail app for your domain. |
|
26
|
2. Complete the domain setup (DNS and routing) on the Mail app's setup page. |
|
27
|
3. Add inbox routes and forwarding. |
|
28
|
|
|
29
|
Mail is forwarding-first — it's not a full hosted mailbox suite. Stored messages |
|
30
|
add history on top of routing. |