Don't include the configured welcome message subject with the body. If
that's desired, the admin can simply configure it that way. But if it's
undesired, there would be no way to avoid the subject duplication.
Originally, the welcome message was sent as type 'normal'. Apparently,
some clients don't display 'normal' messages as expected (see #4246).
To address that issue, commit 9a0ff13cc2
duplicated the welcome message as type 'chat'. However, we shouldn't
send both formats. The 'normal' message is either ignored by the
client, in which case it serves no purpose, or displayed, in which case
the user would see the message twice.
That is recommended since OTP 26, see
https://www.erlang.org/doc/apps/stdlib/proc_lib.html#init_ack/2
Warning
Do not use this function to return an error indicating that the process
start failed. When doing so the start function can return before the
failing process has exited, which may block VM resources required for a
new start attempt to succeed. Use init_fail/2,3 for that purpose.
- Partially rewritten state resolution
- Support for Hydra rooms
- Use double colon for separating a matrix server from a room ID in JID
with Hydra rooms
- Partially rewritten mod_matrix_gw_s2s
- Add notary_servers option
Updates this GitHub Action that's used to execute XMPP-based interop tests from v1.5.0 to v1.6.0.
In this update, 524 new tests were added (more than doubling the amount of tests that previously existed).
For example:
hosts:
- localhost
- locälhost3
- xn--loclhost4-x2a
all them are converted to utf8:
ejabberd_option:hosts().
[<<"localhost">>,
<<"locälhost3"/utf8>>,
<<"locälhost4"/utf8>>]
and if that path is too long, then try HOME directory,
if that's too long too, throw error explaining the problem.
By the way, cutting the base64 string to 107 is a bad idea,
as it encodes the final path, which would get lost and crash.
The Erlang containers from versions 20-23 use Debian Buster,
and require the debian repositories to install some development libraries.
The Debian Buster repositories are no longer available,
which means that we can no longer perform any test with Erlang 20-23.
Make sure Linux-PAM doesn't attempt to include logind support. This
avoids a build failure in case the host system has systemd's
development headers installed.
This is important when running the ban_account command and mod_auth_fast
is enabled, as the client may store auth tokens that bypass
the banning stored in private storage and enforced by ejabberd_auth.
