Fix outgoing messages #11

Closed
opened 2022-05-04 00:25:49 +00:00 by phryk · 1 comment
Owner

Since the update to 0.12.0, outgoing messages to some, but not all
servers fail delivery. Never seems to be incoming messages.

No error messages in logs, no apparently corresponding debug log entries
either – just error stanzas sent to clients.

Triage this, fix depending on root cause – other server having
a security problem vs. misconfiguration on our side vs. bug in Prosody.

This means either opening an issue upstream or fixing local config.

After the fix, messages should either pass or be blocked in both directions.

Getting upstream to supply clients with a more specific error message
would be a nice bonus, as the error stanza currently seems to be empty.

Since the update to 0.12.0, outgoing messages to *some*, but not *all* servers fail delivery. Never seems to be incoming messages. No error messages in logs, no apparently corresponding debug log entries either – just error stanzas sent to clients. Triage this, fix depending on root cause – other server having a security problem vs. misconfiguration on our side vs. bug in Prosody. This means either opening an issue upstream or fixing local config. After the fix, messages should either pass or be blocked in *both* directions. Getting upstream to supply clients with a more specific error message would be a nice bonus, as the error stanza currently seems to be empty.
phryk added this to the Pre-deployment milestone 2022-05-04 00:25:49 +00:00
phryk added the
bug
label 2022-05-04 00:25:49 +00:00
Author
Owner

Was drive-by fixed with #12.

Was drive-by fixed with #12.
phryk closed this issue 2022-05-21 16:54:08 +00:00
Sign in to join this conversation.
No description provided.