> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/openbsd/networking-and-daemons/services/mail-services.md).

# 邮件

邮件服务器页面：

* [Dovecot](/openbsd/networking-and-daemons/services/mail-services/dovecot.md) 在 OpenBSD 上的配置与使用。
* [Exim](/openbsd/networking-and-daemons/services/mail-services/exim.md) 在 OpenBSD 上使用 Exim 作为灵活且完全可配置的邮件传输代理。涵盖安装、TLS 设置、本地与远程投递，以及常见配置示例。
* [Postfix](/openbsd/networking-and-daemons/services/mail-services/postfix.md) 在 OpenBSD 上使用 Postfix 作为安全、灵活且广泛支持的邮件传输代理。涵盖安装、中继、TLS 与虚拟域支持。
* [Rspamd](/openbsd/networking-and-daemons/services/mail-services/rspamd.md) 在 OpenBSD 上配置 Rspamd 进行垃圾邮件过滤与邮件分类，并提供与 smtpd 及其他 MTA 的集成示例。
* [smtpd](/openbsd/networking-and-daemons/services/mail-services/smtpd.md) 在 OpenBSD 上使用 smtpd(8) 收发邮件，默认配置安全，支持中继、本地投递与 TLS。


---

# 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://book.bsdcn.org/openbsd/networking-and-daemons/services/mail-services.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.