OMEMO is forcing: *** [OMEMO] Unable to build any sessions, the message was not sent about plugins HOT 9 CLOSED

To give more context, from server PoV no XMPP payload is received at all. So whatever is going on, seems it only occurs on client side.

from plugins.

@stigger: Any news about this historical OMEMO bug?

I am very good, I have done a screenshot only for you:

• https://i.ibb.co/9Yr3b78/psi-omemo-plugin-problem-is-not-available-for-this-contact-grey-icon-and-unable-to-build-any-sessions-the-mesage-was-not-sent.png

Problem: Grey icon, OMEMO is automatically forced, impossible to disable OMEMO for this contact.

from plugins.

@tehnick: I confirm that the bug is always here with your last build:

• Psi+ 1.4.1303 (2020-05-27, Psi:f34443ba, Psi+:2170e90)

• *** [OMEMO] Unable to build any sessions, the message was not sent

• Grey icon

• Impossible to disable forced OMEMO messages

from plugins.

@kssytsrk: Can you look this ticket?

from plugins.

Might this be a result of Options > Plugins > OMEMO plugin settings > Configuration > OMEMO encryption policy being set to "Always enabled"? I have it set to "Disabled by default", and can't reproduce on Psi+ 1.5.1551 (2021-08-16) / FreeBSD 13.0.

from plugins.

I have "Disabled by default".

from plugins.

@kssytsrk: Thanks for your reply.

Can you test with 2 new test accounts without OMEMO used before?

Please use Psi+ and Psi+.

You will find the problem...

from plugins.

@tehnick: Example of the problem today with a roster contact who does not have/use OMEMO:

In tab, the OMEMO icon is in grey "OMEMO encryption is not available for this contact".

When I send a simple message, it is OMEMO forced, no possibility to change it...
[XX:XX:XX] *** [OMEMO] Unable to build any sessions, the message was not sent
[XX:XX:XX] Test

<iq id='XXXXXX' from='[email protected]' to='[email protected]' type='get'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<items node='eu.siacs.conversations.axolotl.devicelist'/>
</pubsub>
</iq>

<iq type="result" from="[email protected]" to="[email protected]/client" id="XXXXXX">
<pubsub xmlns="http://jabber.org/protocol/pubsub">
<items node="eu.siacs.conversations.axolotl.devicelist">
<item id="current">
<list xmlns="eu.siacs.conversations.axolotl">
<device id="XXXXXXXXX"/>
<device id="XXXXXXXXXX"/>
</list>
</item>
</items>
</pubsub>
</iq>

I have the same problem with the same contact in a MUC Room with "Role that May Discover Real JIDs of Occupants : Anyone" and 1:1 PM messages disabled (normal member, not admin).
No problem if "Role that May Discover Real JIDs of Occupants : Moderator" and 1:1 PM messages disabled (normal member, not admin)

from plugins.

@nullobsi: I have this problem with you in the client...

from plugins.