> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/email-api-smtp/advanced/unsubscribe-settings-footers-and-links.md).
# Unsubscribe settings - Footers & Links
Unsubscribe links are mandatory for bulk emails as per privacy laws. If your emails don't include an unsubscribe link, Mailtrap will add an unsubscribe footer automatically. This is what it will look like:
To add an unsubscribe link anywhere in your template, include this tag in your HTML template: `unsubscribe` . Mailtrap will render a clickable link in your email.
Unsubscribe footer and links are optional for transactional emails and are switched off by default.
However, if you want to, you can still add an unsubscribe footer to your transactional emails by toggling the switch On under **Transactional stream email footer** or adding an HTML tag mentioned above.
You can also mix both approaches: automatically add a footer to emails sent from one domain and do it manually (when applicable) for emails sent from another domain.
If an end-user uses an unsubscribe link, Mailtrap will reject any future emails sent to this address from this particular domain. You can quickly find all such emails in the [Email Logs](https://docs.mailtrap.io/email-api-smtp/analytics/logs) by filtering for the “reject” event.
You will still be able to email them using other domains or subdomains added to your Mailtrap account.
For that reason, it's worth having different domains or subdomains for different types of emails. This way, users can, for example, unsubscribe from your bulk or marketing messages while still receiving vital transactional messages.
---
# 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.mailtrap.io/email-api-smtp/advanced/unsubscribe-settings-footers-and-links.md?ask=&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.
