> For the complete documentation index, see [llms.txt](https://docs.salesmap.kr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.salesmap.kr/videos/setup/organization/email-domain.md).

# 대량 메일 발송 도메인

마케팅 목적으로 잠재 고객에게 지속적으로 뉴스레터를 발송하거나, 광고성 이메일을 발송하고 계실 텐데요.

하루에 일정량 이상의 메일을 발송하는 경우 이메일 평판에 문제가 생길 수 있어요. \
그래서 마케팅 전용 이메일 도메인을 사용하시도록 권장 드리고 있습니다.

왜 마케팅 도메인을 사용해야 하는지와 세일즈맵에서 마케팅 도메인을 등록하는 방법까지 알려드릴게요.

{% embed url="<https://www.youtube.com/watch?v=-H6qTRmB_bg>" %}


---

# 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://docs.salesmap.kr/videos/setup/organization/email-domain.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.