mod_auth_cyrus: Add empty 'profile' table to SASL handler objects This is for compatibility with Prosody's built-in util.sasl objects. A SASL profile table usually includes methods supported by the backend, which can be used by SASL mechanism handlers to perform operations (such as testing the password). It also optionally contains a 'cb' field with channel binding method handlers. The Cyrus backend doesn't support channel binding, and doesn't have the same concept of auth backend methods (it handles all that internally, and Prosody has no insight or control over it). Thus, we create an empty profile which informs Prosody that the SASL handler does not support any of the auth or channel binding methods. Some features will not work, but they didn't work anyway. This just makes it explicit. This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to always contain a 'profile' field.

---
labels:
- 'Stage-Alpha'
summary: 'Track abuse/spam reports from remote servers'
---

This module tracks reports received from remote servers about local user
accounts. The count of reports and the servers they came from is stored for
inspection by the admin or for use by other modules which might take action
against the reported accounts.

## Configuration

### Trusted reporters

You can configure which servers the module will trust reports from:

```
trusted_reporters = { "example.com", "example.net" }
```

Reports from non-domain JIDs are currently always ignored (even if listed).

Reports from domain JIDs which are not listed here are logged so the admin
can decide whether to add them to the configured list.

## Compatibility

Should work with 0.12, but has not been tested.

Tested with trunk (2024-11-22).