> For the complete documentation index, see [llms.txt](https://docs.acymailing.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acymailing.com/old/main-pages/newsletters/spam-test.md).
# Spam Test
Since AcyMailing 3.7.0, we included in all version 5 paid versions a spam test so you can easily test your Newsletter against spam filters (SpamAssassin), check your server configuration and malformed content.
## Test your Newsletter against spam filters
When you preview a newsletter, you will see a button named "Spam Test" in the top right corner of the window. Click it to start the test.
AcyMailing will send an e-mail from your server and check it.
If this is the first time you run a test for this newsletter, you will be asked to wait a few seconds in order for your mail to be processed.
Once your newsletter is processed, you should be able to see the following page with your score.
Clicking on a test title will give you details.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.acymailing.com/old/main-pages/newsletters/spam-test.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.