> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/on-premise/how-to-guide/requirements/email-gateway.md). # Email gateway Set up an SMTP server to enable email notifications, invites, and reports in Navixy on-premise. Configure SPF and DKIM records to improve delivery reliability. SMTP (Simple Mail Transfer Protocol) server is used to send emails, such as notifications, invites, reports, and others. In order to use SMTP with Navixy On-premise, the following requirements should be met: * The SMTP server can be either remote or local. * The SMTP server can be with or without authorization (open relay). * The server must permit to replace the sender in the 'From' header (command mail from:<>). * It is recommended to add SPF (Sender Policy Framework) record and create DKIM (DomainKeys Identified Mail) for emails. This will protect your emails from being considered as spam by the recipient's server. Please note that Navixy does not provide an SMTP server and you will need to use your own or a third-party service. It is also important to configure your SMTP settings properly to ensure successful email delivery. --- # 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://navixy.com/docs/on-premise/on-premise/how-to-guide/requirements/email-gateway.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.