2017-01-06 23:17:54 +01:00
|
|
|
# Message a stream by email
|
|
|
|
|
2018-09-16 04:30:18 +02:00
|
|
|
This can be useful if you want to copy an email into Zulip. If you're
|
|
|
|
planning on doing this in an automated way, consider using our
|
|
|
|
[send message API](/api/send-message).
|
2017-01-06 23:17:54 +01:00
|
|
|
|
2019-03-30 19:00:24 +01:00
|
|
|
### Message a stream by email
|
|
|
|
|
2019-02-13 21:24:15 +01:00
|
|
|
{start_tabs}
|
|
|
|
|
2018-09-16 04:30:18 +02:00
|
|
|
{relative|stream|subscribed}
|
2017-01-06 23:17:54 +01:00
|
|
|
|
2018-09-16 04:30:18 +02:00
|
|
|
1. Select a stream.
|
2017-01-06 23:17:54 +01:00
|
|
|
|
2018-09-16 04:30:18 +02:00
|
|
|
1. Copy the email address under **Email address**.
|
2017-01-06 23:17:54 +01:00
|
|
|
|
2018-09-16 04:30:18 +02:00
|
|
|
1. Send an email to that email address.
|
2018-03-05 15:58:47 +01:00
|
|
|
|
2018-09-16 04:30:18 +02:00
|
|
|
!!! warn ""
|
|
|
|
If you don't see the **Email address** section, most likely your server
|
|
|
|
administrator has not configured the **EMAIL GATEWAY INTEGRATION** section
|
|
|
|
of `/etc/zulip/settings.py`.
|
2019-03-30 19:00:24 +01:00
|
|
|
|
|
|
|
{end_tabs}
|
|
|
|
|
|
|
|
The email subject will become the Zulip topic, and the email body will
|
|
|
|
become the Zulip message.
|