7ce87c66ac
In our current implementation, loose lists and tight lists look the same visually. Loose lists are lists with blank lines between list items, and the contents of a list item should be enclosed in a paragraph tag in that case. For unordered lists, paragraph tags have a bottom margin in starlight and thus looses lists look much more spaced out than tight lists. That is not the behaviour we had in mind while writing the documentation, the reason we had all these loose lists is to make the documentation easy to write and read. So we attempt to remove all the blank lines and fix the problem at source. Since paragraph tags are used for other purposes in a list in starlight, it won't be a wise decision to let the source be as is and just change things in css, other expected behaviours might break in that case. See this topic for more details: https://chat.zulip.org/#narrow/channel/19-documentation/topic/new.20help.20center.3A.20regressions/near/2226084 All the changes were made by a one-off script which has not been commited to the repo. The script wasn't perfect and could not decide between blank lines that make a list loose vs blank lines necessary for a sub-list or a code block inside a list item. A manual review of all the changes was done before making this commit to ensure that no unintended changes were made to the help center files.
3.0 KiB
Message a channel by email
!!! tip ""
This feature is not available on self-hosted Zulip servers where
the [incoming email gateway][email-gateway] has not been
configured by a system administrator.
[email-gateway]: https://zulip.readthedocs.io/en/stable/production/email-gateway.html
You can send emails to Zulip channels. This can be useful:
- If you have an email that you want to discuss on Zulip
- For mirroring mailing list traffic
- For integrating a third-party app that can send emails, but which does not easily lend itself to a more direct integration
If you're planning on doing this in an automated way, and have some programming experience, another option is to use our send message API.
Message a channel by email
{start_tabs}
{relative|gear|channel-settings}
- Select a channel.
{!select-channel-view-general.md!}
-
Under Channel details, click Generate email address.
-
Select Who should be the sender of the Zulip messages for this email address.
-
Toggle the configuration options as desired.
-
Click Copy address to add the channel email address to your clipboard.
-
Send an email to that address.
{end_tabs}
The email subject will become the Zulip topic, and the email body will become the Zulip message.
Note that it may take up to one minute for the message to show up in Zulip.
Configuration options
You can configure who should be the sender of the Zulip messages for the generated email address, with the following options:
- Email Gateway bot: This option makes it easy to see that the message was sent via email.
- You: Messages will look the same as messages you send from the Zulip UI.
- Any bot you own
The following options control which parts of the email are included in the Zulip message.
- The sender's email address: Adds
From: <Sender email address>to the top of the Zulip message. - Email footers: By default, Zulip tries to automatically remove some footer text (like signatures). With this option enabled, Zulip will include all footers.
- Quoted original email: In many email clients, when you reply to a message (e.g., a message notification email), a copy of the original message is automatically added to the bottom of your reply. By default, Zulip tries to remove that copied message. With this option enabled, Zulip will include it.
- Use html encoding: The body of an email is typically encoded using
one or both of two common formats: plain text (
text/plain) and HTML (text/html). Zulip supports constructing the Zulip message content using either (converting HTML to Markdown for the HTML format). By default, Zulip will prefer using the plain text version of an email over the converted HTML version if both are present. Enabling this option overrides that behavior to prefer the HTML version instead.