2026-10-29T18:18:07Z https://nostr.now Holger Weiß https://nostr.now/npub1cyhzlzez9f7j8metsrt75n66u7dq0drm9gr84rwac650zrwzvc3qama45l https://media.metalhead.club/accounts/avatars/000/140/845/original/4321a8c843c731c2.jpg https://media.metalhead.club/accounts/avatars/000/140/845/original/4321a8c843c731c2.jpg https://nostr.now/nevent1qqsy2uzt032x35zzhy04rj543hf0j057fp9zpgzpkhrf04f3etpgruszyrqjututyg486gl09wqd06j0ttne5pa50v4qv75dmhr23ugdcfnzy006j35 In reply to <a href='/nevent1qqsvz5ss9elx39aanf8vnkeddfa37zp3q2halccl0leu9tm6s2d762ckluxm6'>nevent1q…uxm6</a><br/>_________________________<br/><br/>Binary packages that address the problem are available here:<br/><br/><a href="https://github.com/processone/ejabberd/actions/runs/37125232147">https://github.com/processone/ejabberd/actions/runs/37125232147</a> 2026-10-03T15:02:41Z https://nostr.now/nevent1qqsvz5ss9elx39aanf8vnkeddfa37zp3q2halccl0leu9tm6s2d762czyrqjututyg486gl09wqd06j0ttne5pa50v4qv75dmhr23ugdcfnzyhjus0g In reply to <a href='/nevent1qqs9m3nchlr3cwguwkypv8rp2m36hwqud3p9a8w27ehyzkfptzfj76gk4pjjc'>nevent1q…pjjc</a><br/>_________________________<br/><br/>Yes, <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1xxsakz442dmz57rx5s4tazelfqenfheha4k3j5v0njxf7fkhfwhqntxwre" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>monal-im.org :xmpp:</span> (<span class="italic">npub1xxs…xwre</span>)</a></span>&#39;s push service is unhappy with the new ordering of XML elements within the notifications sent by ejabberd 26.09. The XML Schema does indeed mandate the pre-26.09 ordering, which is the why Monal&#39;s push service insists on it. Then again, the Schema isn&#39;t authoritative, and I think it makes no sense at all to insist on a specific ordering here.<br/><br/>This actually happened as an unintended side effect of an attempt to address the same issue in another place:<br/><br/><a href="https://github.com/processone/ejabberd/issues/4606">https://github.com/processone/ejabberd/issues/4606</a><br/><br/>The ejabberd side of the problem can be tracked here:<br/><br/><a href="https://github.com/processone/ejabberd/issues/4626">https://github.com/processone/ejabberd/issues/4626</a> 2026-10-03T10:22:55Z https://nostr.now/nevent1qqszpppxk9fggdmetgrtf0vh2aen6wrgvhaedxut3ffvptrz2jlmqqczyrqjututyg486gl09wqd06j0ttne5pa50v4qv75dmhr23ugdcfnzyg8q3k7 In case you&#39;re using the official ejabberd packages on Debian stable: They&#39;re affected by a recent CA policy change (e.g., Let&#39;s Encrypt), causing ejabberd to reject newly issued certificates and thereby breaking federation with some remote servers. Deploy this update to fix the issue:<br/><br/><a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128568#23">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128568#23</a><br/><br/>You may also want to consider enabling mod_s2s_dialback to deal with remote servers that haven&#39;t been updated yet.<br/><br/>#ejabberd #XMPP #Jabber #Debian #LetsEncrypt 2026-03-15T19:00:58Z https://nostr.now/nevent1qqsf88an09rhf5wl4h77v6lh7c0gne8pgkk2ghgmnn9rmcxlt6dqxwczyrqjututyg486gl09wqd06j0ttne5pa50v4qv75dmhr23ugdcfnzyegcq37 In reply to <a href='/nevent1qqstg96jsm4gw5gvh68ea36g88c5sxk9a9dwjhacfcrszu9rmxaywmc5t9kn6'>nevent1q…9kn6</a><br/>_________________________<br/><br/>Your answer was unrelated to the question. 2026-03-11T23:02:10Z