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-Beta'
summary: Sequential MOTD messages
...

Introduction
============

mod\_motd\_sequential is a variant of
[mod\_motd](https://prosody.im/doc/modules/mod_motd) that lets you
specify a sequence of MOTD messages instead of a single static one. Each
message is only sent once and the module keeps track of who as seen
which message.

Configuration
=============

``` lua
modules_enabled = {
  -- other modules
    "motd_sequential";
}
motd_sequential_messages = {
  "Hello and welcome to our service!", -- First login
  "Lorem ipsum dolor sit amet", -- Second time they login
  -- Add more messages here.
}
```