> For the complete documentation index, see [llms.txt](https://help.stibee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stibee.com/email/manage.md).

# 관리하기

## 이 글에서는

이메일 관리 섹션에 대한 전반적인 설명을 제공합니다.

***

이메일을 편집하고 발송하면서 시간이 점점 지나다 보면 리스트에 작업한 이메일이 계속해서 쌓이게 됩니다. 쌓인 이메일 중에 원하는 이메일을 빠르게 검색하고 편하게 관리할 수 있도록 스티비에서는 몇 가지 기능을 제공하고 있습니다.&#x20;

다음 도움말을 통해 어떤 기능들이 제공되고 있는지 확인해 보세요.

{% content-ref url="/pages/hfjlYPcbkzvA0u1PltOn" %}
[이메일 수정, 복사, 삭제하기](/email/manage/modify-copy-delete.md)
{% endcontent-ref %}

{% content-ref url="/pages/mFXMzwI1AoAjuufjFfbS" %}
[이메일 검색하기](/email/manage/search.md)
{% endcontent-ref %}

{% content-ref url="/pages/XeKuqaMXQW42xLal36m5" %}
[\[태그\]로 이메일 분류하기](/email/manage/tag.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.stibee.com/email/manage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
