> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/misc/broken-email-addresses.md).
# Broken email addresses
When browsing the platform, you see a lot of email addresses from [members](/event/planning/members.md), [list attendees](/event/accreditation/lists/forms/attendees.md), [company email addresses](https://docs.eventication.com/company/features/email-addresses), ... Some of those might not be valid after some time.
An email address might
* be cancelled
* have a full inbox
* have a typo
* reject our platform emails
* have their user mark one of our email as spam
* etc.
The platform will add an indication that an email address is unusable.
* 
A spam complaint is a manual action from the user, they clicked the button to mark an email as spam. This email address will be blocked and can **never** be used on our platform again.
* 
A temporary unavailability of an email address. This might have a couple of reasons like DNS error, full mailbox, ...
* 
The user has manually deactivated their email address.
* 
An unknown reason and not reachable.
* 
The email address doesn't exist, might be a typo.
Only a ***temp bounce*** can be reactivated by a registered user. Next time they log in they will be asked to resolve the problem and reactivate it.
All other reasons are unsolvable by registered users. Next time they log in they will be forced to add and verify another email address.
Moderators can change email addresses of list forms and attendees to resolve the problems. Member email addresses can **not** be changed by a moderator, only by the member (user).
## Resources
* [Information about Spam](/event/misc/spam.md)
---
# 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.eventication.com/event/misc/broken-email-addresses.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.