# Page Not Found

The URL `documentation/email-servers-spf-and-sender-id` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [On premise: NetServer URL and user creation](https://support.emarketeer.com/integrations/superoffice/on-premise/on-premise-netserver-url-and-user-creation.md)
- [Lead Board for SuperOffice](https://support.emarketeer.com/integrations/superoffice/lead-board-and-superoffice.md)
- [Whitelist of countries supporting SMS Sender ID](https://support.emarketeer.com/references/references/sms/whitelist-of-countries-supporting-sms-sender-id.md)
- [SMS Sender ID](https://support.emarketeer.com/references/references/sms/sender-id.md)
- [eMarketeer sender policy](https://support.emarketeer.com/references/references/email/emarketeer-sender-policy.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://support.emarketeer.com/integrations/superoffice/on-premise/on-premise-netserver-url-and-user-creation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://support.emarketeer.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://support.emarketeer.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/integrations/superoffice/on-premise/on-premise-netserver-url-and-user-creation.md`).

You may also use `Accept: text/markdown` header for content negotiation.